Release: v0.16.12

Diagnose Flow: Failure Point Model

investigator / verifier / solver

• Replaced hypothesis-based reasoning with a failure point model in the diagnose workflow
• Investigator now identifies concrete failure points instead of generating abstract hypotheses
• Verifier validates failure points against evidence rather than ranking hypotheses
• Solver derives solutions from verified failure points with clearer causal chains

E2E Test Generation Fix

acceptance-test-generator

• Fixed ROI calculation that made E2E test selection mathematically impossible (max score ~3.16 against threshold of 50)
• Simplified ROI to raw Value Score (0-120) for same-type candidate ranking
• Replaced blanket push-down rule ("already integration-tested → no E2E") with journey-aware retention
• Added reserved E2E slot for user-facing multi-step journeys, emitted regardless of ROI threshold
• Added structured generation report with nullable generatedFiles.e2e and e2eAbsenceReason

integration-e2e-testing skill

• Added environment-agnostic multi-step user journey definition (Web, mobile, CLI, API)
• Added user-facing vs service-internal classification for reserved slot eligibility
• Added ROI calculation examples showing selection outcomes

work-planner

• Added E2E Gap Check in common planning path (fires for both Strategy A and B)
• Gap Check respects e2eAbsenceReason to skip warning on intentional E2E absence

Downstream contract updates

• Updated orchestration guide to treat nullable E2E as valid (not an error)
• Updated recipe-plan, recipe-front-plan, recipe-implement, recipe-fullstack-implement to propagate e2eAbsenceReason through the handoff chain