docs: archive monorepo consolidation planning

2026-08-13 10:13:54 -05:00
parent 063de8cd85
commit 9c7fb4eda6
10 changed files with 37 additions and 0 deletions
@@ -58,6 +58,7 @@

 - [Reports index](reports/README.md) — all tracked report categories and evidence boundaries.
 - [Archived missions](archive/missions/README.md) — historical CLI, harness, install UX, and storage-abstraction delivery records.
+- [Archived planning](archive/planning/README.md) — historical briefs, board reviews, and work-package specifications.
 - [P8-003 performance report](reports/qa/p8-003-performance-optimization.md) — historical implementation evidence, not a current SLO.
 - [Plans index](plans/README.md) — approved intent and implementation/audit plans.
 - [Documentation information-architecture design](plans/2026-08-10-docs-information-architecture-design.md) — approved documentation structure decision.
@@ -19,6 +19,11 @@ Do not use these pages as instructions for the current TUI. Current TUI implemen

 Archived mission manifests and task ledgers preserve their original status and context. They do not replace current orchestrator-owned [`docs/TASKS.md`](../TASKS.md) or authorize old installation procedures.

+## Archived planning
+
+- [`Planning archive index`](planning/README.md) — historical briefs, reviews, and work-package specifications.
+- [`Monorepo consolidation bundle`](planning/monorepo-consolidation/README.md) — prior Forge, MACP, and framework-plugin consolidation planning. Current package existence does not validate every historical criterion.
+
 ## Retention rules

 - Preserve historical wording unless a migration task explicitly requires a rewrite.
@@ -0,0 +1,9 @@
+# Archived planning records
+
+> **Status:** Historical planning index. These records preserve prior intent and review context; they are not current requirements, task state, implementation evidence, or operational authority.
+
+## Monorepo consolidation
+
+- [Planning bundle](monorepo-consolidation/README.md) — historical brief, board review, and Forge/MACP/framework-plugin work-package specifications.
+
+Use current package source, tests, audience guides, and approved control documents for present behavior and status.
@@ -0,0 +1,19 @@
+# Monorepo consolidation planning bundle
+
+> **Status:** Historical planning evidence. The five source records were moved byte-identically from migration quarantine on 2026-08-10.
+
+This bundle records the decision and proposed work packages for consolidating prior Forge, MACP, and OpenClaw framework work into this monorepo.
+
+## Records
+
+- [Consolidation brief](brief.md) — original scope, target layout, constraints, and success criteria.
+- [Board review](board-review.md) — historical deliberation and conditional approval.
+- [WP1: Forge package](wp1-forge-package.md) — proposed TypeScript Forge implementation.
+- [WP2: MACP package](wp2-macp-package.md) — proposed protocol, gate, credential, and event implementation.
+- [WP3: Mosaic framework plugin](wp3-mosaic-framework-plugin.md) — proposed OpenClaw framework plugin port.
+
+## Current boundary
+
+`packages/forge`, `packages/macp`, and `plugins/mosaic-framework` exist in the current checkout. That existence is sufficient to classify this bundle as historical planning, but it does **not** prove that every stated success criterion, integration, coverage target, or behavior remains satisfied.
+
+Use current package source, manifests, and tests for implementation truth. Do not use this bundle as an active task ledger or as authority to change package behavior.
@@ -86,6 +86,7 @@ Shared indexes, navigation, audit records, integration review, and final commits
 - [x] Replace the stale sitemap link inventory with fully resolvable current navigation and an authority-gated backlog summary.
 - [x] Complete independent navigation, safety, and stop-condition reviews; remediate every autonomous finding.
 - [x] Migrate the bounded historical mission archive and repair its two broken sibling links.
+- [x] Archive the unreferenced five-file monorepo-consolidation planning bundle byte-identically with explicit historical boundaries.

 ## Initial findings

@@ -107,6 +108,7 @@ Shared indexes, navigation, audit records, integration review, and final commits
 - The lease-broker acceptance suites directly consumed two quarantined `docs/architecture/` paths; promoting the protocol, security, mutator-gate, and compaction-revocation contracts to `DEVELOPER-GUIDE/architecture/` and updating those consumers restored the intended contract family without changing runtime behavior.
 - The #756 Discord code-review, security-review, and documentation-checklist reports had no source/test consumers and moved byte-identically to their canonical report categories. `docs/reports/README.md` labels their historical evidence boundary.
 - Independent safety review found that Discord external route strings are not proven to map to UUID conversation rows. Current pages now promise live routing/delivery only, disclose that persistence can fail while dispatch continues, and require pre-enrollment for privileged durable-session controls.
+- The monorepo-consolidation brief, board review, and three work-package specifications had no live consumers or internal links. They moved byte-identically to `archive/planning/`; current package existence supports historical classification but does not prove every old acceptance criterion.

 ## Method

@@ -165,3 +167,4 @@ Shared indexes, navigation, audit records, integration review, and final commits
 | Root test suite             | BLOCKED/FAILED SAFELY — Fleet tests require missing `docs/fleet/`; gateway isolation test inherited a daemon DSN and failed authentication before cleanup DML. Not retried. |
 | Focused final tests         | PASS — types 71, Discord 44, web 33, focused gateway 32, and lease-broker/mutator acceptance 57; `DATABASE_URL` unset, no services started                                  |
 | Historical mission archive  | PASS — 11 completed/superseded records moved under `archive/missions/`, indexed, and two broken sibling links repaired                                                      |
+| Historical planning archive | PASS — five monorepo-consolidation records moved byte-identically under `archive/planning/`; source hashes and zero-consumer scan verified                                  |