Repository navigation
docs(maintenance): audit and rehabilitate repository ownership and contributor entry points - #52
Merged
Merged
Conversation
…fication boundaries
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mAsyamJ
marked this pull request as ready for review
November 9, 2026 16:22
This branch was successfully deployed
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
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.
Scope
Non-destructive first deliverable for RetroPick Monorepo Rehabilitation, based on
main@ccad6e32109d03337b560c3c876848665d9d157a.This PR does not claim completion of the whole monorepo refactor. It establishes an auditable inventory, documents canonical ownership and compatibility boundaries, improves maintainer onboarding, and adds a reproducible inventory checker. Source-code and financial-logic refactors are expressly gated on separate baseline and regression evidence.
Delivered
docs/maintenance/TRACKED_FILE_CENSUS.tsv.docs/maintenance/{README,REPOSITORY_AUDIT,CLEANUP_DECISIONS,DEPENDENCY_MAP,VALIDATION_REPORT}.md: canonical vs legacy / historical vs research boundaries, detailed non-deletion decisions, declarative workspace dependency map, and honest gate status.README.md,CONTRIBUTING.mdanddocs/README.mdlink to canonical Viteapps/retro-uiand distinguish frozen historical Kuru Monad V2 deployment from actively developed contracts and research.scripts/maintenance/git_inventory.py: read-only, stdlib-only, deterministic Git inventory / workspace-manifest graph generator.scripts/maintenance/test_git_inventory.py: regressions for Gitlinks, unusual paths, duplicate blob handling, manifest dependency extraction, repeatability, and worktree non-mutation.Verified before PR
mainunchanged.main, zero behind.apps/,contracts/,deployments/,packages/, or any license/provenance files.Blocked / required before ready for review and merge
pnpm install --frozen-lockfile,pnpm check:app,pnpm check:services, canonical Playwright fixture smoke.Why draft: The tool environment could verify the complete Git tree and execute isolated Python regression tests, but could not clone the full repository (network/DNS blocked) or run npm/Foundry/browser suites. The historical CI record contains mixed passes and failures on older commits, so these are not represented as current-
mainpasses or known pre-existing failures.Safety invariants:
apps/web/**stays zero-write;contracts/legacy-v2/**is immutable; ABI/storage/selectors/CREATE2/financial accounting unchanged; PRISM remains research-gated. No automatic merge.See Validation Report and Cleanup Decisions.