chore: re-baseline log.md onto freeze-on-write (fab 2.6.0)#285
Merged
Conversation
Apply fab kit migration 2.5.5 -> 2.6.0. Runs fab memory-index --rebuild once to produce a clean frozen log.md baseline from current git, so subsequent runs are append-only stable. Bumps fab/.kit-migration-version to 2.6.0.
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.
What
Applies fab kit migration 2.5.5 → 2.6.0 (
/fab-setup migrations) and bumps the kit version to 2.6.1.As of fab 2.6.0,
fab memory-indexuses freeze-on-writelog.mdgeneration: existinglog.mdcontent is authoritative and write-once, and regeneration only appends new entries keyed on(file-base, change-id). This makes the logs deterministic across git history rewrites (squash-merge + branch-delete) instead of churning on every touch.Existing projects carry
log.mdfiles generated under the old pure-projection model, so a one-time--rebuildre-baseline is required to establish a clean frozen starting point.Changes
docs/memory/run-kit/log.md— appended previously-missing attributable entries (chore: migrate fab project files to kit 2.5.0 #279 kit-migration, fix: make the done status dot a sharp square (rounded-none) #280/docs: add status-dot section to README; move status-dot.md to docs/site #281 ui-patterns)docs/memory/run-kit/index.md— refreshed "Last Updated" dates forrk-riffandtmux-sessionsfab/.kit-migration-version— bumped2.5.5→2.6.0fab/project/config.yaml— bumpedfab_version2.5.5→2.6.1Verification
fab memory-index --checkexits 0 (clean)fab memory-indexrun is append-only stable (no new churn — "already up to date")This is the last churn from this migration; every subsequent
fab memory-indexrun is append-only stable.🤖 Generated with Claude Code