Skip to content

T-1504 closes #719, and says what it accepted to do so - #770

Merged
MongLong0214 merged 2 commits into
mainfrom
close-719
Aug 18, 2026
Merged

T-1504 closes #719, and says what it accepted to do so#770
MongLong0214 merged 2 commits into
mainfrom
close-719

Conversation

@MongLong0214

Copy link
Copy Markdown
Owner

All five of T-1504's rewritten acceptance criteria have a run behind them, and the ticket now names which run for which so a later reader checks rather than trusts.

criterion evidence
a contributor never produces the canonical artifact #761 carried src/ and test/ only
the workflow produces the merge candidate, checked in full #762, twelve contexts on an App-opened pull request
the artifact matches the source landing with it e4e5154, no local build
a mismatched artifact is refused #763 — hand-edited bundle, src/ untouched, both check jobs red
the source head reaches main unaided #761 merged by reachability; bundle authored by the build App
the handoff is checked rather than trusted scripts/verify-canonical-handoff.mjs + one mutation per rule

The last row arrived last and caught a defect in its own first version — the inline check required two parents on the canonical tip, and a real tip has one. Every assertion I had written read the workflow as text and passed.

What closing accepted, stated rather than implied: no external contributor has taken this path yet. That is adoption evidence, not a correctness gate, and holding the work open for it would leave it unfinished for a reason unrelated to the work.

Limit (on the commit): the closing evidence is six runs and one repository — its own — so it shows the mechanism works, not that it works for somebody else.

All five acceptance criteria have a run behind them. The table in the ticket
names which run for which, so a later reader checks rather than trusts.

The last criterion arrived last and caught a defect in its own first version:
the inline handoff check required the canonical branch tip to have two parents,
and a real tip has one, because the rebuild commits on top of the merge
whenever `dist/` changes. Every assertion I had written read the workflow as
text and passed. That is why the rule lives in a script with one mutation per
case now.

What #719 accepted in order to close is on the issue and in the ticket rather
than implied: no external contributor has taken this path yet. That is adoption
evidence, and holding a correctness gate open for it would leave the work
unfinished for a reason unrelated to the work.

Limit: the closing evidence is six runs and one repository -- its own -- so it shows the mechanism works and not that it works for somebody else
Blast: local
Undo: easy
Certainty: firm
Record-Id: r-t1504done
Provenance: authored
Verified: each row in the new table names a pull request, run or commit that exists, and the five criteria were read from main rather than from the branch that wrote them
CommitLore-Version: 2.0.0
@github-actions

github-actions Bot commented Aug 18, 2026

Copy link
Copy Markdown

CommitLore — record lint

Trailers: clean — 2 commits in origin/main..9cc0c58b19303dac32d09b170d1f41a319ab9011
Active constraints: not read — commitlore: the index is incomplete: the build stopped after its time budget with 832 commit(s) or note(s) unread — records in them are missing from this answer. fix: commitlore init (or commitlore index) to finish the index (1 changed path)

Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.

@MongLong0214
MongLong0214 merged commit 67e3a71 into main Aug 18, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant