docs(spec): the IAutomationService.toggleFlow contract says it switches packaged flows

The service contract's docblock read "Enable or disable a flow", the same
published line the API page carried. It now says the switch records the
installation's choice for packaged flows, that a flow authored in the
deployment is refused with RESOURCE_CONFLICT / 409, and that such a flow's
switch is its own status, published through registerFlow. Prose only.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XY5uCwTjZj7884yYtyur4H

Author: claude

.changeset/20726-toggle-door-docs-spec.md

@@ -4,4 +4,4 @@
 
 docs(spec): the Automation API docblock says the toggle door switches packaged flows only, and names a customer flow's switch (#20726)
 
-The module docblock of `api/automation-api.zod.ts` listed `POST /api/v1/automation/:name/toggle` as "Enable/disable flow". That file ships as source, and its docblock is also the source of the Automation API reference page. The line now reads "Enable/disable a packaged flow". A new paragraph says what a flow authored in the deployment uses instead: its `status`, published with the complete definition through `PUT /api/v1/automation/:name`. The toggle door refuses such a flow with 409 `RESOURCE_CONFLICT`. This is prose only: no schema, type or export changes.
+The module docblock of `api/automation-api.zod.ts` listed `POST /api/v1/automation/:name/toggle` as "Enable/disable flow". That file ships as source, and its docblock is also the source of the Automation API reference page. The line now reads "Enable/disable a packaged flow". A new paragraph says what a flow authored in the deployment uses instead: its `status`, published with the complete definition through `PUT /api/v1/automation/:name`. The toggle door refuses such a flow with 409 `RESOURCE_CONFLICT`. The `IAutomationService.toggleFlow` docblock, which read "Enable or disable a flow", says the same. This is prose only: no schema, type or export changes.

packages/spec/src/contracts/automation-service.ts

@@ -716,7 +716,12 @@ export interface IAutomationService {
     getFlow?(name: string): Promise<FlowParsed | null>;
 
     /**
-     * Enable or disable a flow
+     * Enable or disable a PACKAGED flow — one a code package ships — by
+     * recording the installation's choice in the activation ledger
+     * (ADR-0126 §7.2). A flow authored in the deployment is not this switch's:
+     * the automation service refuses it with `RESOURCE_CONFLICT` / 409 and
+     * changes nothing. That flow's switch is its own `status` (`'obsolete'` /
+     * `'active'`), published through {@link registerFlow}.
      * @param name - Flow name (snake_case)
      * @param enabled - Whether to enable (true) or disable (false)
      */