long-eyed-reworklisted

# Long-Eyed Rework Complete Long-Eyed Inspect, then understand the scope of the problem, reproduce or characterize it, and trace the affected behavior to its root cause before editing. Complete each applicable repair in order: 1. Remove obsolete, conflicting, or duplicated code. 2. Consolidate competing implementations under one canonical owner and path. 3. Fix the root cause at its canonical owner. 4. Rework any foundational boundary that is incoherent or repeatedly fails instead of hiding the problem with patches, fallbacks, or parallel paths. Only then, write the minimum code required for a fully functional, coherent, modular, and structurally sound result. ## TCG methodology provenance When `intel_methodology_catalog`, `intel_record_methodology_intervention`, and `intel_methodology_interventions` are available, fetch the catalog before recording. On selecting Long-Eyed Rework and its current phase, append a catalog-bound `exposure`; include the real TCG `boundaryId` when that boundary already exists, but omit it for a genuinely pre-boundary descriptive exposure. Append an `intervention` only when the method actually changed a concrete action. It must name the immutable `boundaryId`, the exact existing `actionEventRef` under that boundary, and the expected no-method counterfactual. Append `verified_outcome` only after the canonical `boundaryEvaluationId` for the same boundary includes that action and fresh exact evidence exists. At the moment the method changes an a