Design 47 H: H-A-99 the placement's build is the want's target; H-A-100 the forge module's merge-check removal

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 03:50:17 +01:00
parent 922f7017b8
commit 62d60bf43d
@@ -420,3 +420,12 @@ Where two preparers disagreed, the chosen one is named.
old-form event: the contract's strict decode (a required field such as `call` missing) is the refusal, the handler
writes one journal line naming the subject and ends the message. H-A-58's "shared follower" is read so for H1; a
shared shape, if any, is H4's with the wake-up rule. P3, P7.
- **H-A-99 (assigner developer, 03:51)** The placement's `build` is read as the want's target before the rule (option
b): the want's `fp` is that build and its `version` the one released at it, with no pipeline, no rank and no put steps;
`placementPuts` goes. "Read before the rule" literally, with no hold. P7.
- **H-A-100 (gate-and-forge developer, 03:51; the forge module's merge-check machinery)** As recommended: the poll that
goes is the pass's pull-passing half with its 60-second retry, the timer the 10-minute keep-main-rules step (it keeps
a protection ADR 0682 §13 no longer judges); the repository poll (`repo.created`) and the start's whole read stay.
`announceHead` goes whole with its pending status and sibling weighing; `pull.updated` is said by the webhook path
alone; the poll of merged and closed pulls stays. The seat verb `status` writes a head's status through the client
directly; `GateWriter` and its chain go. P7; §764.