long-eyed-buildlisted

# Long-Eyed Build Complete Long-Eyed Inspect, then understand the requirement and affected system before building. Stop at the first rung that holds: 1. Is it already implemented in the codebase? 2. Can the existing canonical implementation be extended? 3. Does the language or runtime standard library handle it? 4. Does the native platform handle it? 5. Does an already-installed dependency handle it? 6. Only then, write the minimum code required for a fully functional, coherent, modular, and structurally sound implementation. Reuse before creating. Keep ownership singular, responsibilities clear, dependencies understandable, and the code and system doing only the work necessary. If required foundational behavior is broken or incoherent, stop Build and use Long-Eyed Rework. Resume Build only after that boundary is verified. ## 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 Build 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_outco