fix(mind): record --apply auto-regenerates complete/index.md - #97
Merged
Conversation
record --apply wrote the completion record but left complete/index.md stale; the separate `index --apply` step (documented in the ship skills) was easy to forget, so the Lifecycle Drift workflow failed on every push to main landing a record and emailed the maintainer. Fold the index regen + git-add into cmd_record's --apply branch so the two can't drift apart. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Jammy2211
pushed a commit
that referenced
this pull request
Jul 24, 2026
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Jammy2211
pushed a commit
that referenced
this pull request
Jul 30, 2026
The Lifecycle Drift guard has emailed a failure on every push to main since 2026-07-28: vacuous-jax-assertions shipped (record written, index refreshed per PR #97) but its '## vacuous-jax-assertions' section was never removed from the active.md registry — that edit was still a separate manual step in the ship skills, and it was forgotten. Same failure shape as the index drift PR #97 fixed, one file over. Fold the registry prune into cmd_record --apply (new _prune_ledger_section: drops the H2 section through the next H2/EOF, matched via safe_name), stage active.md alongside the record, and announce the pending prune in dry-run output. Also clears the current red by pruning the stale vacuous-jax-assertions section (both PRs merged 2026-07-28, issue closed). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 30, 2026
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.
Problem
The Lifecycle Drift workflow runs
lifecycle.py index --checkon every push tomaintouchingcomplete/**. Because Mind pushes go directly to main (no PR to pre-catch drift), a stalecomplete/index.mdfails the run and emails the maintainer — every time a shipped record lands.Root cause:
record --applywrites + stages the completion record but leaves the index stale. The separateindex --applystep is documented in the ship skills but gets forgotten. (It happened again live today:dpie-simulator-portshipped without a regen.)Fix
Fold the index regeneration into
cmd_record's--applybranch — regenerate via the existing_render_index/_existing_curatedhelpers, writecomplete/index.md, andgit addit. Same effect asindex --apply, but it can no longer drift from the record write.Behaviour-preserving except that
record --applynow also freshens the index.Test
Ran
record <slug> --applyon a throwaway record: both the record and a refreshedcomplete/index.mdwere staged, andindex --checkpassed. Reverted the scratch record.🤖 Generated with Claude Code