Cause 2's forcing function was about to vanish: record the executed false-green as a typed stall row

dag/gunbc/guarantee_rung_drop.dag

@@ -288,3 +288,25 @@ data next_rung_trigger_enforcement_stall: GuaranteeStall = GuaranteeStall {
   },
   next_rung_trigger: "every class this repository declares below its ceiling declares it through gunbc.guarantee_rung_drop GuaranteeStall rather than in prose, at which point the population becomes a fold over rows and a stall missing its trigger has no spelling. Not satisfied by this carrier existing: one row is a carrier with a consumer, not a migrated population, and the 4b(2) obligation stays review diligence for every class still stalling in an annotation"
 }
+
+// THE REMOVAL SIDE OF NAMESPACE WAVE ADMISSION REPORTS A LOAD-BEARING IMPORT AS UNUSED, AND IT
+// IS A GREEN RATHER THAN A REFUSAL. This row exists because the class was about to lose its only
+// forcing function: the lane that felt it was unblocked by a repair that routed the ADD direction
+// around the same blind position, and a defect whose one complainant gets routed around stops
+// ranking -- the deficit frequency driven to zero by construction, which is precisely the shape
+// DESIGN section 5 names. It is replaced here by a measurement, which does not get unblocked.
+data field_type_removal_false_unused_stall: GuaranteeStall = GuaranteeStall {
+  subject: "namespace wave admission reports UnusedSubjectMembershipRemoved for an import whose only use is a DECLARED FIELD TYPE. The fact needed to answer correctly IS PRODUCED: v1.02_parse stamp_parsed_inferred stamps a Resolved inferred node with ParsedOccurrenceReference { category: TypeOccurrence }, so the declared type is an exact type occurrence carrying parser-minted identity, containment and an authored-name projection. It is then DISCARDED before any consumer sees it -- ParsedNodeStampResult returns the node UNCHANGED and the stamps live only in the threaded ParseContext, so declaration_index builds referenced from a Node-tree walk that no longer holds them",
+  current: OutsideTheLadder,
+  ceiling: StructurallyGuaranteed,
+  blocker: ClimbableButUnbuilt,
+  population: BoundedPopulation {
+    members: [
+      "v1_compiler.declaration_index record_from_module -- builds referenced from a Node-tree walk instead of ingesting the parser-issued occurrence transport",
+      "v1_compiler.declaration_index for_each_node -- the walk itself, which cannot reach a fact the tree does not carry",
+      "v1_compiler.namespace_wave_admission membership_bound_through -- reads referenced and so inherits the gap",
+      "v1_compiler.namespace_wave_admission membership_declared -- the add-side judgment over the same set"
+    ]
+  },
+  next_rung_trigger: "THE TRIGGER IS THE CAPABILITY: the removal and binding judgments consume the parser-issued authored-reference transport, WITHOUT traversing Node.inferred, WITHOUT moving the declared type into type_annotation, and WITHOUT reconstructing identity from an authored name or a span. Each of those three is a way to reach the right answer through a channel that is not the producer, and each buys a per-consumer exemption rather than a climb. The RED is authorable at the fixture boundary and has been AUTHORED AND EXECUTED: a module importing a coproduct used in exactly one position -- a declared field type in a variant payload -- has that import dropped while the reference remains, and the gate answers dispositions=[UnusedSubjectMembershipRemoved], a verdict that a still-referenced import is dead. That executed measurement is this class's forcing function and does not expire. The ceiling is StructurallyGuaranteed rather than StructurallyImpossible deliberately: the disposition is a COMPUTED verdict derived from the transport, and a verdict can be miscomputed. Unwritability would require a carrier in which a removal judgment has no spelling that ignores the transport, which this one does not provide, so claiming the top rung here would be the inflation 4b(1) forbids"
+}