docs(topics): prune delivered AI-ladder WP slices at effort end

[kyle-sexton]

Summary

Effort-end housekeeping for the AI-adoption-ladder effort: all seven work packages are merged,
so the per-WP topic slices come out per the close-out convention (publish the PLAN, then prune
the slice).

• WP4–WP7 PLANs were already spliced into their PR bodies at each close-out (feat(autonomy): trigger-dispatch package - contract, setup slice, envelope check (WP4) #372, feat(autonomy): guardrail matrix, security binding, setup slice (WP5) #377,
  feat(autonomy): standing-routine catalog, v1 leaves, setup routine slice (WP6) #600, docs(autonomy): autonomous-runner design pack (WP7) #676).
• WP1–WP3 PLANs are now published the same way into feat(autonomy): autonomy plugin — category, topology contracts, guided-setup v0 (WP1) #333, feat(autonomy): telemetry contract + setup slice, conformance check, live-proven demo (WP2) #343, and feat(autonomy): return-accounting convention, capture slice, live-proven demo (WP3) #356 (each merged PR body
  gained a PLAN (published at effort-end close-out) details block), so every slice's content
  has a durable home on its merged PR before the directory is removed.
• The WP map in docs/topics/ai-adoption-ladder/index.md now records delivery PRs instead of
  live slugs. The effort hub itself (index, design evidence, research docs) stays.

No content is lost: every deleted PLAN.md is byte-recoverable from git history and readable in
its merged PR's details block.

Related

No linked issue (effort-end housekeeping; the WP map issue #239 is already closed).

• Map: AI adoption ladder — climb 2→3 (plugins fleet) #239 (WP map: AI adoption ladder — the effort this closes out)
• feat(autonomy): autonomy plugin — category, topology contracts, guided-setup v0 (WP1) #333 / feat(autonomy): telemetry contract + setup slice, conformance check, live-proven demo (WP2) #343 / feat(autonomy): return-accounting convention, capture slice, live-proven demo (WP3) #356 (WP1–WP3 delivery PRs, PLANs published into their bodies in this
  close-out)
• feat(autonomy): trigger-dispatch package - contract, setup slice, envelope check (WP4) #372 / feat(autonomy): guardrail matrix, security binding, setup slice (WP5) #377 / feat(autonomy): standing-routine catalog, v1 leaves, setup routine slice (WP6) #600 / docs(autonomy): autonomous-runner design pack (WP7) #676 (WP4–WP7 delivery PRs, PLANs published at their own close-outs)

[claude]

Claude finished @kyle-sexton's task in 1m 19s —— View job

---

PR Review

• Gather context and understand the PR
• Review docs/topics/ai-adoption-ladder/index.md changes
• Verify deletion rationale and content-preservation claims
• Post review findings

---

This is a clean effort-end housekeeping change. No issues found.

What changed

Seven PLAN.md files (one per WP topic directory, WP1–WP7) are deleted. Each WP directory contained only its PLAN.md, so the directories are fully removed with no orphaned files. The index.md is updated from a "live effort" view to a "delivered" record.

index.md review

The rewrite is well-judged:

• The preamble (All seven packages are DELIVERED...) is clear and accurate at effort end.
• The new table (WP → delivery PR#) is the right durable artifact — it survives the removal of the topic slice directories and gives anyone reading the hub a direct pointer to each WP's merged work.
• WP7's contract-source note correctly sharpens "Brief locked" to "design pack; build stays trigger-gated" — accurate to how WP7 actually closed.
• Removing the dependency order and /planning:interview / /planning:architect workflow paragraphs is correct: those instructions only make sense for an in-progress effort and would be misleading here.

Content-preservation check

• Deleted PLAN.md files: All are byte-recoverable from git history (commit b0eded0's parent). The PR description says WP4–WP7 PLANs were published into their delivery PR bodies at their own close-outs, and WP1–WP3 PLANs were published into feat(autonomy): autonomy plugin — category, topology contracts, guided-setup v0 (WP1) #333, feat(autonomy): telemetry contract + setup slice, conformance check, live-proven demo (WP2) #343, and feat(autonomy): return-accounting convention, capture slice, live-proven demo (WP3) #356 as part of this close-out. That process happens on GitHub PR bodies (outside this repo's working tree), so it can't be verified from diff alone — but the PR description is explicit and the convention is consistent with what was done for WP4–WP7.
• Design evidence: The design/ directory (11 files: design-threads.md, 9 RESEARCH-*.md files, boris-step-and-your-role.txt) is fully preserved. The effort hub stays intact as documented.

No concerns

There are no correctness, security, or structural issues. The scope matches the PR description exactly. Approved to merge.