Repository navigation
fix(build-plan-status): --refresh keeps an existing build-plan.json current - #437
Merged
Merged
Conversation
…urrent exec.sh and gate-check.sh run --refresh after every step, but only an explicit --json rewrote build-plan.json, so a Stage 4 snapshot read 0 built after a day of building. --refresh now regenerates an existing json with the same parser (skipping the write when only generatedAt would differ) and never creates one. Docs, manifest and routing rows updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md
4 tasks done
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
project-bin/build-plan-status.sh --refreshruns after everyexec.shrun and every fullgate-check.shrun. It refreshedarchitecture/build-plan.htmlbut never rewrotearchitecture/build-plan.json, which only an explicit--jsonrun writes (typically once at Stage 4). On a real project the json still showed the Stage 4 snapshot (0 rows built) after a day of building, while build-plan.md showed 27 built.Fix
--refreshmode, ifarchitecture/build-plan.jsonalready exists it is regenerated from build-plan.md with the same parser--jsonuses. The write is skipped when onlygeneratedAtwould differ.--refreshnever creates the json when it did not exist.Tests run
tests/wave2/test-build-plan-json.sh: PASS=70 FAIL=0 (new T11: flipped State shows in json after --refresh, no rewrite on timestamp-only change, no json created when absent)bin/render-routing.sh --check: in syncbin/check-skill-routing.sh: all routedtests/wave2/test-closeout.sh(manifest consumer)🤖 Generated with Claude Code