docs(lanes): wire ship-feature-lane to the real integration toggle check (F3a)

docs/LANES.md

@@ -1063,6 +1063,16 @@ A lane whose source repo has no `mcpServers` configured gets a clear `ENOMCPCONF
 
 Restart the lane's Claude session after syncing — MCP config is read at session start.
 
+### Checking integration toggles: ccam lanes integration
+
+A profile can declare `.ccam/profile/integrations.env` with `TRACKER_ENABLED`, `DEV_QC_ENABLED`, `CI_WAIT_ENABLED` flags (all off by default — see `profiles/_template/integrations.env`-style declarations in a profile's own docs). Check one:
+
+```bash
+ccam lanes integration tracker    # exit 0 = on, 1 = off
+```
+
+This only reports what the PROFILE wants — it doesn't file a ticket, run dev-QC, or wait on CI. The agents that would act on an enabled toggle (`ticketer`, `dev-qc`) aren't built yet; `ci_wait`'s consumer (`ccam ci`) isn't either. `ship-feature-lane`'s Stage 9/13/10 stay skipped/fallback regardless of what the toggle reads, until those land.
+
 ### Pipeline template: ship-feature (16 node stages)
 
 The skill uses the `ship-feature` pipeline template, which defines the following 16 stages (node IDs):

docs/superpowers/plans/2026-08-03-shipyard-parity-lanes.md

@@ -326,7 +326,7 @@ behaves as documented. Each of those commands gets a CLI test.
 `<repo>/.ccam/profile/integrations.env`, exposed as `ccam lanes integration <name>`
 (exit 0/1) and in `GET /runtime`.
 
-**Progress:** `mcp sync` (F1) done 2026-08-05 — see `docs/superpowers/specs/2026-08-05-mcp-sync-design.md`. Tracker, dev-QC, CI-wait remain.
+**Progress:** `mcp sync` (F1) done 2026-08-05 — see `docs/superpowers/specs/2026-08-05-mcp-sync-design.md`. `integration` toggle reader (F3a) done 2026-08-05 — see `docs/superpowers/specs/2026-08-05-integration-toggle-design.md`. `ticketer`/`dev-qc` agents, CI-wait (`ccam ci`), and dev-QC remain.
 
 - **Tracker** — file one ticket per feature, idempotent (update, never
   duplicate), writing `proof/<slug>/ticket/REPORT.html`.