Release: v0.27.1

• The requirements stop presents one shape: confirmed scope, decision evidence, open decisions, and workflow route. Only your explicit answer enters confirmed scope.
• Confirmation stops no longer push answers into pre-written options, so requirements and exclusions are recorded in your own words.
• requirement-analyzer returns repository evidence only, and scans from the responsibility your outcome implies rather than from likely file paths.
• A product-facing responsibility found during codebase or UI analysis returns to the requirements gate when it would change the confirmed outcome or an exclusion.
• Reverse engineering re-runs discovery for a unit with no routes, tests, or public exports instead of verifying it against no evidence.