Fix Incident approval-delivery state confusion

[dotnetpower]

Problem

The Incident current-situation projection treats an A1 human-approval dispatch failure as an A2 operational-alert routing failure. Operators can receive alerts while the Incident detail incorrectly says that no operational alert channel accepted the notification.

Scope

Separate recorded A1 approval delivery from A2 operational notification routing in the Console, preserve the required human-input state, expose direct recovery navigation, and keep the bilingual owner contract synchronized. Runtime secrets remain deployment-owned and must not enter the repository.

Exit criteria

• A1 approval dispatch failure has a distinct Console phase and bilingual copy.
• A2 notification success is not overwritten by an unrelated A1 failure.
• Human approval remains required and recovery links reach Approvals and Settings integrations.
• Focused Incident, localization, documentation, and production-build checks pass.
• At least 10 independent critique-and-hardening rounds leave only Low-or-lower residual findings.
• Authenticated Incident detail shows the corrected state without horizontal overflow.

[dotnetpower]

Completed in local commit 9c4e54d (not pushed). The Incident current-situation projection now separates A1 approval delivery from A2 operational-alert routing, preserves concurrent delivery failures, clears stale failures after later delivery or terminal decisions, keeps required human approval explicit, aligns roster counts with current disposition, and links to /approvals plus the read-only /settings/integrations status surface. Fifteen critique-and-hardening rounds ended with no confirmed Medium-or-higher residual. Focused validation: 69 Console tests passed; Console typecheck and production build passed; 18 catalog pairs, 211 English/Korean doc pairs, readable-Hangul, punctuation, roadmap tracking, design-impact, diff-check, and pre-commit gates passed. Exact-commit changed-test selection completed with 0 Python tests selected because the commit contains only Console and documentation paths. Authenticated-shell synthetic presentation checks measured the corrected heading and body, User input: Required, exact recovery links, 0 px desktop/mobile overflow, 44 px mobile targets, and a 2 px keyboard focus outline. No runtime channel-health claim was inferred from the synthetic fixture.

[github-actions]

This issue was reopened because unchecked exit criteria still record residual work. Complete or revise the criteria before closing.

[dotnetpower]

Completion revalidation for issue #274:

• Commit 9c4e54d4ebc3af34b3eb98a2c20a402c8874746f is an ancestor of both the current repository HEAD and origin/main.
• The focused Incident overview suite passed 21 cases on the current checkout; the original completion evidence also records 69 Console tests, typecheck, production build, localization, documentation, design-impact, and pre-commit gates.
• The original fifteen hardening rounds plus this ten-lens re-review found no verified residual issue above Low severity.
• The authenticated Console /incidents route loads successfully. The current live incident corpus contains no A1 approval-dispatch failure specimen, so no live delivery-channel health claim is made.
• The retained authenticated-shell synthetic projection proves the distinct A1 phase and bilingual copy, preservation of independent A2 notification success, required human approval, recovery navigation to Approvals and Settings integrations, zero desktop/mobile horizontal overflow, 44 px mobile targets, and visible keyboard focus.
• Synthetic presentation evidence demonstrates the UI contract only; it does not grant mutation authority or claim live channel health.

Residual work: none for this UI issue.