Compare seat contracts with the design in the prepare, and call a verdictless merge unchecked

On 2026-11-10 a seat contract and an event's subject that differed from design 47
surfaced only in develop, and the checker twice dropped a check still running when
its pull request merged. The prepare now compares every seat contract the milestone
touches with its design lines, each difference a design question before develop;
and a merged change with no verdict is reported as unchecked, never as passed.

Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
This commit is contained in:
2026-11-10 17:24:02 +01:00
parent 8f9a6d4f7b
commit 6e90fa443e
3 changed files with 16 additions and 3 deletions
+3 -1
View File
@@ -23,7 +23,9 @@ proves each; the order of the subtasks (a subtask that uses a contract, type, ve
adds starts from that subtask's commit; contracts and packages first) and one writer per file; the section `What
exists today` with its three answers, every search written as run; the design line that places each new exported
type, field, constant, package or module; the one placement of the siblings every agent uses, as the running checker
places them; the test budget. Code: read the repositories at `origin/main` (`git fetch`, `git show`, `git grep`),
places them; the test budget. Compare each seat contract the milestone adds or changes (its fields, subjects,
callers and kinds, as on main) with the design lines that name that seat, field by field: every difference is a
design question. Code: read the repositories at `origin/main` (`git fetch`, `git show`, `git grep`),
never a working tree; the live mesh through its tools.
**Everything the design does not say is a design question, never your answer.** A reader or an effect with no fate,