The board's double-claim warning counts only plans still in flight - #77
Merged
Merged
Conversation
…clash The board warned that a scope item "is being worked on from 2 plans at once" whenever two specs named it, a finished one included. That is not what the sentence says and not what a reader needs: an item worth two rounds of work carries two specs forever, so the heads-up would stand for the life of the project and teach the reader to skim the one place the board raises its voice. Closing spec 011 made it concrete: SC-8 was shipped first by the archived baseline and owned since by 011, both done, and no ordering of those two would ever clear the line. A later spec supersedes an earlier claim, which is ordinary history. The clash worth reporting is two unfinished plans on one item, where nobody has decided yet who owns it, so the warning now counts only the specs that have not finished, and names those. The item's own state is untouched: the furthest spec still wins, so an item one plan already shipped keeps reading done while a second plan reworks it. Three self-tests hold the rule from both sides: two unfinished plans still warn, a finished plan plus a later one in flight does not, and two finished plans are history rather than a clash. The two older fixtures that paired a building spec with a done one moved to two unfinished specs, because they were written to exercise the clash and that pairing is no longer one. Traces-to: SC-10
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
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 changed and why
The board warned that a scope item
is being worked on from 2 plans at oncewhenever two specsnamed it, a finished one included. That is not what the sentence says, and not what a reader needs.
An item worth two rounds of work carries two specs forever, so the heads-up would stand for the
life of the project and teach the reader to skim the one place the board raises its voice.
Closing spec 011 made it concrete. SC-8 was shipped first by the archived baseline spec 000 and has
been owned by 011 since, both
done, and no ordering of those two would ever clear the line. Thealternative on the table was dropping SC-8 from 000's
Traces to:, which edits what the baselinesays it shipped; the owner chose to fix the gate instead, so the historical record stays as it was.
A later spec supersedes an earlier claim, which is ordinary history. The clash worth reporting is
two unfinished plans on one item, where nobody has decided yet who owns it. The warning now
counts only the specs that have not finished, and names those.
The item's own state is untouched: the furthest spec still wins, so an item one plan already
shipped keeps reading
donewhile a second plan reworks it.Evidence
plus a later one in flight does not, and two finished plans are history rather than a clash.
buildingspec with adoneone to exercise the clash. That pairingis no longer one, so both moved to two unfinished specs rather than being deleted.
node checks/progress.mjsnow prints no heads-up and still reads 12 of the 12things done, exit 0.
check.mjsOK, progress 27 (25 before, three added, one rewritten), links 19, cockpit 21,code 35.
Scope
One gate and its suite. No document changes:
docs/state/STATE.local.mdis gitignored and carriesthe decision on the maintainer side.
Traces-to: SC-10