Add Step 10 mechanical-pass inventories as archaeological reference (#166)#172
Merged
Merged
Conversation
…166) Issue #166's Step 10 required (per End-to-end Verification gate #5) a runtime-vs-v5 comparison report with categorised inventories and 8 per-area prose sections. The parent plan's Step 11 focused-session structure (lines 387-405 of Plans/v5-0-0-is-a-major-keen-wall.md) explicitly authorises descoping the full multi-day prose deliverable: > "The plan describes Step 11 as design-doc generation driven by > Step 10's multi-day prose report. In practice, a focused session > produces a thinner just-enough version sufficient to drive port > priorities — without blocking on Step 10's full-prose deliverable." > > "The full Step 10 prose report can come later as archaeological > reference; it does not block the port work." This commit ships the mechanical first pass of gate #5 only: reports/v5-comparison/inventory-pai.txt — 674 entries, path-shifted diff marrair:.pai/ ↔ v5:.claude/ (v5 is single-root per the design doc's two-root decision, so the literal .pai/ ↔ .pai/ diff in the parent plan does not apply). reports/v5-comparison/inventory-claude.txt — 162 entries, apples-to-apples marrair:.claude/ ↔ v5:.claude/ user-config diff. Both files carry a header documenting methodology, excludes (runtime ephemera: node_modules/, sessions/, projects/, paste-cache/, file-history/, shell-snapshots/, etc.), and the <marrair> / <marrmini-fresh> path tokens for machine portability. Not delivered here (deferred as archaeological-only per the plan): - 7-label categorisation of every divergent file - 8 per-area prose sections (Algorithm, MEMORY, Skills, SecurityValidator, PAI-Install/installer engine, AISTEERINGRULES, Hooks, Two-root separation) The Learning area was separately deep-dived and shipped as reports/v5-learning-loop-vs-pack.md via PR #170. Gate #5 remains partially open by design; the design doc (Plans/v5-0-0-plus-port.md) carries the decision-grade content needed for port work. Issue #166 stays closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
inventory-pai.txt(674 entries, path-shiftedmarrair:.pai/ ↔ v5:.claude/diff) +inventory-claude.txt(162 entries, apples-to-applesmarrair:.claude/ ↔ v5:.claude/diff).node_modules/,sessions/,projects/,paste-cache/,file-history/,shell-snapshots/, etc.), and<marrair>/<marrmini-fresh>path tokens for machine portability.Context
Issue #166's End-to-end Verification gate #5 demanded "every divergent file in
inventory-pai.txtandinventory-claude.txthas a category label" plus "8 per-area prose sections present". The parent plan's Step 11 focused-session structure (lines 387–405 ofPlans/v5-0-0-is-a-major-keen-wall.md) explicitly authorises descoping the multi-day prose deliverable:This PR delivers the mechanical first pass only, keeping gate #5 partially open by design. The categorisation pass + 8 prose sections remain deferred as archaeological-reference work; the Learning area was separately deep-dived and shipped as
reports/v5-learning-loop-vs-pack.mdvia PR #170. Issue #166 stays closed; the design docPlans/v5-0-0-plus-port.mdcarries the decision-grade content needed for port work.Why now
Surfaces the structural reality (v5 is single-root; v4 fork was two-root) as a committed reference, so future port sessions can grep the inventories rather than regenerate the diff from backups each time.
Test plan
wc -l reports/v5-comparison/inventory-pai.txt→ 688wc -l reports/v5-comparison/inventory-claude.txt→ 180/Users/ianmarr/backups/...paths; only<marrair>/...and<marrmini-fresh>/...tokens