docs(specs): handoff for regen/staleness source_hash mismatch#41
Merged
Merged
Conversation
Phase 2 of attune-gui's living-docs-regen-automation (Smart-AI-Memory/attune-gui#62) surfaced an attune-author bug: regenerate writes a source_hash that the immediately-following status check disagrees with. Likely cause: regen hashes a budget-truncated source view while staleness hashes the full set. This decisions.md captures the handoff — repro, code pointers, fix directions to choose between — so the next session picking this up starts with the architecture context already laid out. No code fix yet; that needs Phase 1 (failing test) first. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Adds
docs/specs/regen-staleness-hash-mismatch/decisions.md— a handoff doc capturing a bug surfaced by attune-gui's Phase 2 ofliving-docs-regen-automation(parked there pending this fix; see attune-gui#62).The bug:
attune-author regenerate <feature>writes asource_hashto frontmatter, butattune-author status <feature>immediately afterwards still reports the feature as stale. Loop never reaches a fixed point. Likely cause: regen hashes a budget-truncated source view; staleness hashes the full set.This PR is docs only — no code change. The doc lays out the architecture, code pointers, and three candidate fix directions so a future session can dive straight into Phase 1 (repro test) without re-discovering the context.
Test plan
🤖 Generated with Claude Code