docs(repo): #415 Phase-2 execution plan — cluster-coordinated filter-repo playbook (gated) - #702
Merged
Merged
Conversation
…repo playbook (gated) Turns the Phase-2 proposal (analysis + costing) into a concrete, step-by-step EXECUTION playbook ready to run when jsboige green-lights. Read-only: 0 history mutation, 0 force-push, 0 Cards/ write. Adds vs the proposal: - Fresh empirical inventory on master 70bd160 (.git 2.2 GB, top blobs resolved to paths, 4 open PRs counted) confirming the bloat source is unchanged. - Strip-target table (1.8 GB regenerable: Published/ 1.2 GB + Mindmapper/Published/ 187 MB + DNNPlatform Downloads/ 205 MB + .resources 150 MB), design sources preserved. - Post-purge projection (~0.45-0.5 GB, ~75% reduction). - Pre-flight checklist (jsboige go/no-go, 4 open PRs merged/closed, timing tag-before-vs-after, cluster re-clone window announced). - Exact git filter-repo strip set (including the 2 Mindmapper/Published entries from the 2026-07-03 affinement), local verification (du, git fsck, git-weight-audit.py), re-add origin, coordinated force-push, post-rewrite re-clone for every cluster machine. - Risks refreshed (4 open PRs not 3), gate explicit (DEFER to post-v0.9.0-tag, unchanged reco). No filter-repo/BFG run. No .gitignore change (companion PR, orthogonal). Dispatch ka7vl5 (PRIMAIRE). Base 70bd160. Co-Authored-By: Claude <noreply@anthropic.com>
42 tasks
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.
#415 Phase-2 —
.gitreduction EXECUTION PLAN (gated, read-only)Base:
70bd1605· Dispatch:ka7vl5(PRIMAIRE) · Status: PROPOSAL/PLAN ONLY — 0 history mutation, 0 force-push, 0Cards/write.What this adds vs the existing proposal
The Phase-2 proposal (merged) gave the analysis + costing + the
filter-repostrip set. This PR turns it into a concrete, cluster-coordinated execution playbook ready to run when jsboige green-lights:70bd1605:.git2.2 GB, top-5 blobs resolved to paths (Print&Play.zip 93.6 MB, Published/*.zip ×4 ~83 MB), 4 open PRsPublished/1.2 GB +Mindmapper/Published/187 MB + DNN Downloads 205 MB +.resources150 MB. Design sources (Packaging/Sketch/SVGs) preserved.git2.2 GB → ~0.45–0.5 GB (~75 % reduction, ~1.7 GB saved per clone)git filter-repostrip set (incl. the 2 Mindmapper entries from the 2026-07-03 affinement) → local verify (du/git fsck/git-weight-audit.py) → re-add origin → coordinated force-push → post-rewrite re-clone for every cluster machineWhat this does NOT do
git filter-repo/ BFG run, no clone, no force-push, no history mutation..gitignorechange (companion PR, orthogonal, can proceed independently now).Reproducibility
All inventory numbers re-derivable via
python tools/git-weight-audit.py(Phase-1, merged #621) + the read-onlygit verify-pack/rev-list --objectscommands documented inline.Relates #415, #621. Dispatch
ka7vl5PRIMAIRE.🤖 Generated with Claude Code