Repository navigation
process(change-intake): CRs update the module brief and stay visible until built - #430
Merged
Merged
Conversation
…until built The BRD stays the source of truth; a CR touching a module's build steps, screens, access or rules gets a CR-tagged Build steps row, every CR that adds work gets a build-plan row, and agreed unbuilt CRs are "waiting" (RESUME.md Waiting changes line). exec.sh --cr CR-NN warns (never blocks) when the module brief lacks the id. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…equires Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e; RESUME checklist names Waiting changes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # CHANGELOG.md
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.
What
change-intake.md/change-intake-detail.md: replaces "most BRD edits need no brief edit". The BRD stays the source of truth. The module brief's Build steps table gets a CR-tagged row (CR-07-1) for every CR touching build steps, screens, access or rules. Every CR that adds work gets a build-plan row taggedCR-NN(S: the module's phase; M/L: wait for a change round). Agreed, unbuilt CRs are "waiting" and are surfaced at session start and module close. Class to entry artifact table kept. A full unplanned-changes view and change rounds come in a follow-up.close-the-loop.mdand the RESUME template: aWaiting changes:line listing agreed, unbuilt CR ids.project-bin/exec.sh: with--cr CR-NN, WARN (non-fatal) when the brief of a module the script writes to (folder form or merged## Module briefsection) does not contain the id. Reuses the existing brief-advisory module detection.Why
A CR on a closed module left the brief stale, so
context-pack.shhad no row for it and nothing counted it as unbuilt work.Tests
tests/wave2/test-exec-cr-brief-warn.sh: 14 checks (warn when lacking, silent when present, CR-1 vs CR-12, no--cr, merged form incl. id in another module's section, no brief, exit 0); 4 fail against master's exec.sh.render-routing.sh --checkclean.🤖 Generated with Claude Code