R82.F — deploy.md + boot.md execution packet

0. Preflight

  • Worktree: E:/AMS/.worktrees/claude/r82-f-deploy-boot (pre-created per task prompt; verified git status clean and log matches main at b88d7ca0 with audit + contract commits on top).
  • Branch: feature/r82-f-deploy-boot.
  • Gate: audit (88f58182) + contract (17cca7fc) committed. Step 4 may proceed.

1. File 1 — docs/guides/deploy.md edits

Edit 1.1 — mode table row FULL (line 48)

Target line 48:

| `FULL` | yes | yes | all 19 tools | Normal laptop / dev operation |

New line 48:

| `FULL` | yes | yes | all 14 shipped tools | Normal laptop / dev operation |

Edit 1.2 — mode table row TEST (line 50)

Target line 50:

| `TEST` | yes (fresh temp DB) | yes | all 19 tools | CI runs, integration tests |

New line 50:

| `TEST` | yes (fresh temp DB) | yes | all 14 shipped tools | CI runs, integration tests |

Edit 1.3 — mode table row MINIMAL (line 51, phantom strike)

Target line 51:

| `MINIMAL` | yes | no | `server_health` + `server_status` only | Smoke check, first connect |

New line 51:

| `MINIMAL` | yes | no | `server_ping` + `server_health` only | Smoke check, first connect |

Edit 1.4 — paragraph after mode table (line 53)

Target line 53:

The 19 tools are defined in [`docs/reference/mcp-tools-phase-0.md`](/AMS/reference/mcp-tools-phase-0.html) per ADR-004.

New line 53:

The 14 shipped tools are defined in [`docs/reference/mcp-tools-phase-0.md`](/AMS/reference/mcp-tools-phase-0.html) per ADR-004 (R75 Wave H amendment; the original 19-tool plan is retained in that doc for heritage reference).

Edit 1.5 — Boot sequence step 5 (line 63) + advisory callout

Target line 63:

5. **Tools list.** Register the 19 Phase 0 tools (minus the subset gated out by `COLIBRI_MODE`). Advertise them in the MCP `tools/list` response.

New line 63 (expanded to two lines so the callout sits inline with the step):

5. **Tools list.** Register the 14 shipped Phase 0 tools. Advertise them in the MCP `tools/list` response. Note: `capabilitiesFor(mode)` is read at construction time but is currently advisory in Phase 0 — every registered tool is exposed in every mode regardless of the active capability record. Enforcement at registration time is a Phase 1 follow-up.

Edit 1.6 — Laptop profile description (line 104)

Target line 104:

Full read + write, all 19 tools, local DB. This is what a developer runs daily.

New line 104:

Full read + write, all 14 shipped tools, local DB. This is what a developer runs daily.

Edit 1.7 — “What Phase 0 does NOT deploy” table row (line 141)

Target line 141:

| Agent spawn / orchestration tools | Phase 1.5 per ADR-005 | `agent_spawn`, `agent_status`, `agent_list` not in the 19 tools |

New line 141:

| Agent spawn / orchestration tools | Phase 1.5 per ADR-005 | `agent_spawn`, `agent_status`, `agent_list` not in the 14 shipped tools |

Edit 1.8 — Cross-links footer (line 179)

Target line 179:

- [`docs/reference/mcp-tools-phase-0.md`](/AMS/reference/mcp-tools-phase-0.html) — the 19 tools per ADR-004.

New line 179:

- [`docs/reference/mcp-tools-phase-0.md`](/AMS/reference/mcp-tools-phase-0.html) — the 14 shipped tools per ADR-004 (R75 Wave H amendment).

2. File 2 — docs/2-plugin/boot.md edits

Edit 2.1 — FULL mode bullet (line 116)

Target line 116:

- **`FULL`** — all 19 tools active (default).

New line 116:

- **`FULL`** — all 14 shipped tools active (default).

Edit 2.2 — MINIMAL mode bullet (line 119, phantom strike)

Target line 119:

- **`MINIMAL`** — health/shutdown tools only.

New line 119:

- **`MINIMAL`** — `server_ping` + `server_health` only.

Edit 2.3 — Boot failure paths table (line 159)

Target line 159:

| 2 | Handler registration failed | 73 | CONFIG — one of the 19 schemas is malformed |

New line 159:

| 2 | Handler registration failed | 73 | CONFIG — one of the 14 tool schemas is malformed |

Edit 2.4 — Exit code table (line 171, phantom strike)

Target line 171:

| 0 | Success | Clean shutdown via `server_shutdown` |

New line 171:

| 0 | Success | Clean shutdown via SIGINT/SIGTERM |

3. Edit tool strategy

Each edit uses the Edit tool with a unique old_string anchored by enough neighboring context. The target lines are already unique in each file (verified by grep in Step 1 audit §5). For each Edit, the old_string is the exact current line (with trailing pipe / period preserved verbatim).

4. Test strategy

Docs-only. No test runner gate. Verification sweeps per §2 of the contract.

5. Rollback plan

If any Edit fails or introduces corruption:

  1. git reset --hard HEAD~0 (no effect — Step 4 is a single commit).
  2. If partial Edits committed: git revert <impl SHA>.
  3. Re-inspect via Read and re-apply clean.

6. Risks

  • Very low: old_string uniqueness conflicts — mitigated by auditing in Step 1 §5 (grep confirmed one instance per target pattern per line).
  • Very low: Breaking a Jekyll --- frontmatter block — mitigated by leaving lines 1–9 of both files strictly untouched.
  • Very low: Accidental cross-slice scope — guarded by the contract §3 do-not-touch list.

7. Commit strategy

Single fix(...) commit for all eight + four = twelve Edits. One commit. Message:

fix(r82-f-deploy-boot): 19→14 tool-count + phantom tool strike

Reconcile docs/guides/deploy.md and docs/2-plugin/boot.md to the 14
shipped Phase-0 tool surface. Strikes phantom `server_status` and
`server_shutdown` references. Adds an advisory callout on
capabilitiesFor(mode) to deploy.md's boot-sequence step 5.

deploy.md changes:
  - mode table FULL/TEST rows: "all 19 tools" → "all 14 shipped tools"
  - mode table MINIMAL row: "server_health + server_status only" →
    "server_ping + server_health only"
  - paragraph + links footer: "19 tools" → "14 shipped tools"
  - boot step 5 prose: "19 Phase 0 tools (minus subset gated out by
    COLIBRI_MODE)" → "14 shipped Phase 0 tools" + advisory callout
  - laptop profile + deferred table: "19 tools" → "14 shipped tools"

boot.md changes:
  - FULL mode bullet: "19 tools" → "14 shipped tools"
  - MINIMAL mode bullet: "health/shutdown tools only" → "server_ping
    + server_health only"
  - failure-paths table: "19 schemas" → "14 tool schemas"
  - exit-code table: "Clean shutdown via server_shutdown" → "Clean
    shutdown via SIGINT/SIGTERM"

No src/ changes. No test impact.

8. Post-impl verification plan (Step 5)

Captured in docs/verification/r82-f-deploy-boot-verification.md:

  1. grep -cE "19 tools|all 19" docs/guides/deploy.md docs/2-plugin/boot.md — expect 0:0.
  2. grep -cE "server_shutdown|server_status|task_transition|audit_session_end|task_delete|task_depends_on" docs/guides/deploy.md docs/2-plugin/boot.md — expect 0:0.
  3. grep -cE "14 tools|14 shipped" docs/guides/deploy.md docs/2-plugin/boot.md — expect ≥ 1 each.
  4. head -10 both files — confirm frontmatter intact.
  5. Confirm line 63 of deploy.md contains “currently advisory”.

Part of R82 Phase 0-1 stabilization, Wave 2 (task F). Governed by docs/agents/executor-contract.md.

Back to top

Colibri — documentation-first MCP runtime. Apache 2.0 + Commons Clause.

This site uses Just the Docs, a documentation theme for Jekyll.