Nightly maintenance: also try to re-bootstrap each member repo - #150
Merged
Conversation
The single nightly fleet routine sequenced only the growth lifecycle and the repo tidy-up, so a consumer's Claudinite *wiring* (the sync hook generated artifact, settings.json hook registrations, skill symlinks, gitignore, pack declaration) drifted from canon until someone re-bootstrapped by hand — Method B re-syncs the corpus contents each session but never this wiring, and Method A's pinned submodule drifts in both. Add re-bootstrap as a third independent step the routine sequences, mirroring the repo tidy-up: no ordering dependency on the growth phases, one isolated subagent per member repo, over the API, opening a PR only when something drifted (usually a no-op — hence "try to"). It runs against members only, never the home repo/canon (which doesn't mount itself). On re-bootstrap the enrollment-issue step is skipped: a repo the routine reached is provably already on the maintenance access list, so there is nothing to request. Scope that step to first-adoption in bootstrap.md, where the enrollment logic lives. Refs #149 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HzjetxNGYuN5wwF1vRdkA8
missingbulb
marked this pull request as ready for review
July 7, 2026 10:22
This was referenced Jul 7, 2026
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
2 participants
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.
Closes #149.
Problem
The single nightly fleet routine (
routines/auto-all-repos-maintenance.md) sequenced only two things across the fleet: the growth lifecycle and the repo tidy-up. Nothing re-bootstrapped consumers, so each member repo's Claudinite wiring drifted from canon until re-bootstrapped by hand — thesync-claudinite.shgenerated artifact, thesettings.jsonhook registrations, the.claude/skills/symlinks, the gitignore rules, and the pack declaration. Method B re-syncs the corpus contents every session but never this wiring; Method A's pinned submodule drifts in both.Change
Add re-bootstrap as a third independent step the nightly routine sequences, mirroring the repo tidy-up:
bootstrap.md, the content of theadopt-claudiniteskill). The routine only sequences it.bootstrap.md, where the enrollment logic lives.Files
routines/auto-all-repos-maintenance.md— new step 3 in "What it sequences"; the run-the-flow step, launcher prompt, and never-do guardrails updated.bootstrap.md— Part 4 scoped to first-adoption (re-bootstrap skips it).Full check sweep (
node checks/run.mjs) passes clean (exit 0).🤖 Generated with Claude Code
https://claude.ai/code/session_01HzjetxNGYuN5wwF1vRdkA8
Generated by Claude Code