Implementation Plan 153

Status: Reviewed implementation plan; not authorization to execute. Owning issue: #153. Current status, approval, blockers, and results remain on that issue. This plan is based on repository main 921469ab440f10f2365387b14a7c185bf66f053f and Wiki f0f8e675c73bd19a513a6c97436a52b695fb2ec8.

Outcome and boundaries

Move the full-product plan to the Wiki, preserve ten Phase 5E/6 and RR-R10 visual references on #153, then remove only the stale repository routes and delivery artifacts listed in #153. Keep code-coupled assets in Git under docs/design/brand/, retain docs/delivery/progress.md, preserve stable catalog identities for retained material, and repair affected direct routes. Do not change application behavior, the generic managed-documentation contract, accepted ADR bodies, hooks, permissions, releases, or deployment.

Ordered delivery

0. Review and publish this implementation plan before cleanup. An independent Reviewer reviews this candidate. After Required findings are resolved and under the ticket's existing owner authorization for publication, publish it as Implementation-Plan-153.md; the coordinator confirms and coordinates that authorized endpoint. Add it to Implementation-Plans.md and _Sidebar.md through the existing Implementation Plans route, read back the page and navigation, then link it on #153 with its exact Wiki revision. This is the reviewed-plan gate; it precedes all repository cleanup.

1. Publish destinations before deletion (#155). Copy docs/delivery/plans/2026-09-06-full-product-architecture-and-delivery-plan.md to the Wiki as Full-Product-Architecture-and-Delivery-Plan.md. Preserve its qualification language and substantive text. Convert its repository-relative links: authority and progress links to their current repository/GitHub locations; ADR-005/006 links to their canonical Wiki ADRs; design/brand routes to canonical Wiki specifications or the retained docs/design/brand/ location as applicable. Add it to Implementation-Plans.md and _Sidebar.md through the existing Implementation Plans route. Update the canonical RR-Development-Delegation-Model.md to state explicitly that Release Radar development uses the owning GitHub issue and delegated role prompt and does not create repository task-brief files; preserve the separate generic managed-documentation product contract. Directly read back the published page, its anchors, guidance, and navigation links; record the exact Wiki commit on #153. Do not delete docs/delivery/plans/ until this succeeds.

2. Preserve visual evidence before deletion. Post one clearly labeled #153 comment using GitHub's issue attachment flow, with a feature/provenance table and inline attachments for these exact files:

   Files	Mapping
   phase5e-lifecycle-native.png	Phase 5E explicit lifecycle; PR #43
   2026-09-10-phase6b-goals-{wide,compact,registration-recovery}.png	Phase 6B Goals; PR #45
   2026-09-10-phase6c-evidence-{wide,compact}.png	Phase 6C revision-bound evidence; PR #46
   2026-09-10-phase6e-{search-wide,search-compact,help}.png	Phase 6E Search/shared Help; PR #48
   rr10-needs-review.png	RR-R10 needs-review visual reference; retain its existing provenance qualification

   Use the GitHub browser comment composer to upload the PNGs (the installed gh issue comment does not expose --attach). Confirm every generated attachment URL renders and every table mapping is present by reading the posted comment. Use the resulting comment anchor or attachment URLs when repairing Wiki links. Do not delete any retained image before that readback.

3. Consolidate retained repository assets (#158). After #155's destinations and attachments are directly verified, move docs/brand/ to docs/design/brand/ without changing its substantive guidance or assets. Update catalog paths and generated indexes while retaining the current artifact IDs: 37012d12-2f27-4282-a8ab-8e21d3c6eb14, a357e108-aae8-4f15-a44a-3bad0e98c9d5, 69ed9247-6243-4511-bf52-594c98e9d649, and 9484b9ea-9656-471a-92ee-cd0aac9f000a. Rewrite docs/design/README.md as the local route to canonical Wiki specifications, mockups/, brand/, and the #153 historical-visual comment. Keep the ten attached image bytes unchanged until attachment verification completes; delete only the four rr-r9-active-phase-* images in this stage.

4. Repair routes, then delete the now-obsolete material (#156). Start only after #155 and #158 are complete and their destinations are directly verified. Update the affected non-ADR Wiki specification links to canonical Wiki ADR/specification pages, the new full-product-plan page, and verified #153 attachment locations. Do not edit an ADR body; historical links pinned to an older repository commit remain historical evidence unless an unambiguous current route needs replacement. Update AGENTS.md, docs/README.md, docs/catalog.json, and generated repository indexes so RR development is routed through the owning GitHub issue and delegated role prompt, with ticket-owned plans in the Wiki. Preserve the generic managed-documentation product contract and its unrelated paths.

   Only after stages 1–3 are verified, remove: docs/architecture/; the ten direct docs/design/*.md Wiki-routing stubs; docs/delivery/task-briefs/; docs/delivery/plans/; the ten attached evidence PNGs and then docs/delivery/evidence/; and docs/delivery/README.md. docs/delivery/ must then contain only progress.md.

Direct checks and review

• Before each destructive stage, verify the required target: Wiki page plus navigation and exact commit; #153 comment plus all ten rendered attachments; then the relocated brand files and unchanged retained IDs.
• Regenerate repository index blocks only through ReleaseRadarDocumentationTool write --root <isolated-checkout> after the catalog is coherent; run its check mode, swift script/check_development_docs.swift --root <isolated-checkout>, and focused searches proving no removed repository path remains referenced. Check direct Wiki routes separately, including all replacement plan/evidence links.
• Confirm docs/delivery/progress.md remains regular, within its existing 60-line/6,144-byte constraint, and that no generic product source or bundled marketplace guidance was changed.
• Keep one qualified independent Reviewer task for this plan at stage 0 and the actual final #156 documentation/evidence-relocation/deletion candidate. Required findings are corrected and only the affected portion is re-reviewed. No cleanup begins before stage 0 publication, #155 attachment readback, and #158 completion.