required_gate_bankruptcy: count-free incident receipt for the T? == T wall firing

[gunbai-bot]

Appends a count-free INCIDENT RECEIPT to the authored text of gunbc.rung_drop.required_gate_bankruptcy, beside its existing receipts (this incident is a further firing of that drop): the EqualityOptionalityMismatch wall (failure mode optional_compared_with_required_value) landed with consumers outside the gate; repaired by gunbc#13549. Projection docs/design-rung-drops.md updated with the same sentence. No count, no instrument claim, no change to standing, trigger or gate prefixes; failure-mode row untouched.

🤖 Generated with Claude Code

[gunbai-bot]

Addressed review 77787: the // block is gone from the rung drop; the receipt now lives as a receipts entry on the existing failure-mode row for this wall, with no copied count. — sent from still-raven-321

[briansrls]

NO-LAND at exact head e54fd5e.

Review 77787's two concrete objections are closed: the inert // annotation is gone, and the scratch census count is no longer transcribed. The remaining blocker is the carrier.

This incident is a firing of gunbc.rung_drop.required_gate_bankruptcy, not a new occurrence of optional_compared_with_required_value. The decisive facts are that the wall's consumers sat outside the required gate closure, stayed unresolvable while every required lane was green, and were found only by a whole-population compile sweep. That is exactly the loss population and prioritization fact the drop owns. The drop's existing AuthoredProse.authored already carries two INCIDENT RECEIPT clauses for the same reason: a drop whose population has demonstrably fired ranks differently for restoration.

Putting the fact only on the equality row leaves the drop's own incident history incomplete, and the new sentence admits the mismatch itself: “the class of loss is the one required_gate_bankruptcy already declares; this row records the incident against the wall that exposed it.” The wall exposed the loss; it did not own it. The equality class is now structurally prevented at its stated seam, and this event did not reopen or recur its representation-dependent equality defect.

Also, this is not actually a typed relation. RecurringFailureMode.receipts is List<String>; its authority explicitly says those parts are “SEVERABLE, NOT TYPED” and names receipt classification as an open §4c gap. The drop identity inside the new string is not joined to the rung-drop roster. Moving a prose string from a comment into that list makes it modeled/rendered, but does not make it typed.

Required repair: remove this receipt from optional_compared_with_required_value and append a count-free INCIDENT RECEIPT inside required_gate_bankruptcy.declaration's existing AuthoredProse.authored, beside its prior incident receipts. Name EqualityOptionalityMismatch / optional_compared_with_required_value and gunbc#13549 as the concrete wall and repair; do not claim the scratch script is a durable instrument or copy its count. No second debt row, standing change, gate-prefix change, or trigger change is needed.

Exact-head seed, generated, floor, emit-build, and aggregate witnesses succeeded; rust-unit-tests was skipped on the pull-request event by workflow policy. The rejection is solely the ownership/single-authority defect.

[briansrls]

LAND at exact head 1da92bf.

The ownership blocker at e54fd5e is closed. The incident is now recorded on gunbc.rung_drop.required_gate_bankruptcy, whose loss population actually fired: consumers outside the required gate remained broken while every required lane was green. EqualityOptionalityMismatch / optional_compared_with_required_value is correctly named as the wall that exposed the gap, and gunbc#13549 as the repair, without moving ownership of the incident back to the failure-mode row.

The receipt is count-free and does not present the scratch census as a durable instrument. It sits inside the existing AuthoredProse.authored beside the drop's prior incident receipts, which is the coherent representation for this legacy-prose row. No second debt row was added; standing, restoration trigger, and gate prefixes are unchanged. The generated docs/design-rung-drops.md projection carries the same sentence and no independent meaning.

The net diff is exactly those two authority/projection lines; optional_compared_with_required_value is untouched. Exact-head seed, generated, floor, emit-build, and aggregate witnesses all succeeded; generated passed all-target lint and the fixed-point check. rust-unit-tests was skipped on the pull-request event under current workflow policy and remains a merge-queue obligation. No blocker found.