govkit-fix-recordlisted

# Fix Record Author the fix record for a reported defect. When invoked, determine the defect from the user's request; if it is not described, ask before proceeding. A defect that restores behavior something already established carries one record — `fixes/<id>/fix.yaml` — instead of the five-artifact feature contract. A change that introduces behavior does not qualify, however small it looks. ## Check eligibility first All four conditions must hold. Decide this **before** writing any code or any record — a change that fails one belongs in the feature lane, and finding that out after the fix is written wastes the work. 1. **It restores established behavior.** Name the requirement, contract, ADR, or spec that established it. If nothing did, this is new behavior. 2. **A reproduction test is possible.** You will write a test that fails before the fix and passes after. 3. **It introduces no new intended behavior.** Fixing a defect by adding a capability is not a fix. 4. **It does not change** architecture, security or auth, data handling, a public contract, an NFR, or cross-service ownership. If any condition fails, stop and say which one, then direct the user to `/govkit-architecture-preflight` and the feature lane. Do not author a fix record for a change that does not qualify — the lane is narrow on purpose, and widening it by assertion is the failure mode it exists to prevent. ## Inputs to read Feature specs (to find what established the behavior): - `features/<feature_n