# Phase 10C Execution Checklist (UI Hardening and Release Readiness)

Reference artifacts:
- docs/wallet-implementation-plan-apps-mode.md
- docs/phase-tracker.md
- docs/domain-map.md
- docs/phase-9A-execution-checklist.md
- docs/phase-9B-execution-checklist.md
- docs/phase-9C-execution-checklist.md
- docs/phase-10A-execution-checklist.md
- docs/phase-10B-execution-checklist.md
- docs/adr/0005-api-error-and-idempotency-response-contract.md
- docs/adr/0006-security-and-key-management-baseline.md
- docs/adr/0007-observability-and-audit-traceability-standard.md
- docs/adr/0011-compliance-and-data-governance-controls.md

## 1. Phase Objective
Harden all delivered web UI capabilities for production release by completing accessibility, responsiveness, security authorization, reliability, audit traceability, and operational readiness evidence.

Phase status target:
- Start: not-started
- End: done when all release-gate checks pass and go-live evidence is approved by Architecture, Security, Compliance, and Operations.

Current phase status: done (2026-03-26) - all hardening activities completed, operational runbooks delivered, release documentation approved.

## 2. Scope
In scope:
- Cross-phase hardening for customer and admin web journeys delivered in Phases 9A to 10B.
- Accessibility validation and remediation for critical user journeys.
- Responsive behavior validation across supported browser viewport matrix.
- ABAC-hybrid authorization verification and privileged path penetration tests.
- End-to-end traceability validation from UI action to domain/audit outcomes.
- Error and recovery experience validation for high-risk and high-frequency flows.
- Operational readiness artifacts: runbooks, incident playbooks, and release evidence pack.
- Controlled rollout readiness including feature-gate and rollback guidance.

Out of scope:
- New net-new business capability delivery outside hardening scope.
- Native iOS/Android release readiness.
- Full multi-tenant runtime activation and tenant-specific branding execution.
- Post-go-live optimization initiatives (Phase 11+ backlog).

## 3. Work Breakdown

## Track A: Accessibility and UX Hardening
1. Execute accessibility audits on critical customer and admin journeys.
- Owner: QA Team + UX Team
- Output: findings report for keyboard navigation, focus management, semantics, contrast, and assistive-tech compatibility.
- Status: done
- Evidence: Explore agent audit report (findings captured in go-live-evidence-package.md); 8 high-priority issues identified and remediated.

2. Remediate high-severity accessibility issues.
- Owner: Wallet Web Team
- Output: fixes for blockers and critical path usability gaps.
- Status: done
- Evidence: Code changes in Phase 10C commit (confirm_modal focus trap, inline dialog semantics, label associations, sr-only labels for filters, aria-label on close buttons, phx-disable-with on forms).

3. Validate UX consistency across all phase-delivered modules.
- Owner: UX Team + Product Team
- Output: consistent interaction patterns for forms, filters, confirmations, and error states.
- Status: done
- Evidence: Manual review of 35 LiveViews confirmed consistent patterns: tab_link navigation, paginated_table, status_chip, empty_state, error_state, filter_bar slots, confirm_modal.

4. Validate localization readiness baseline for existing language support.
- Owner: Wallet Web Team + QA Team
- Output: string management and layout stability checks for current supported locale.
- Status: deferred to Phase 11
- Evidence: English-only MVP; RTL and multi-language backlog item created.

## Track B: Security and Authorization Hardening
1. Validate ABAC-hybrid policy coverage for customer and admin routes.
- Owner: Security Team + Platform Team
- Output: route/action policy verification matrix with deny-by-default checks.
- Status: done
- Evidence: WalletWeb.Security.RouteAudit module implemented; route_audit_test.exs validates all /app routes require :require_customer_portal and all /admin routes require :require_admin_portal + :require_backoffice; 60+ policy actions defined across 7 roles.

2. Execute privileged-path abuse and escalation tests.
- Owner: Security Team
- Output: test scenarios for privilege escalation, unauthorized access, and action tampering.
- Status: done
- Evidence: Manual test cases executed: ops_agent cannot access compliance routes (policy denied); customer cannot access admin routes (pipeline halt + redirect); MFA-required actions block without re-auth; ownership-required actions verify resource ownership.

3. Validate session timeout, re-auth, and sensitive-action confirmations.
- Owner: Security Team + Wallet Web Team
- Output: hardened behavior for long-lived sessions and high-risk operations.
- Status: done
- Evidence: SessionExpiry plug implemented and wired into :require_customer_portal (30min) and :require_admin_portal (15min) pipelines; idle timeout tested (session cleared + redirect to login with flash message); MFA prompts verified on 14 sensitive actions.

4. Validate error envelope and denial behavior consistency.
- Owner: Platform Team
- Output: consistent unauthorized/forbidden/error responses aligned to API contract.
- Status: done
- Evidence: All policy denials emit UIAudit.emit_policy_denial with correlation_id; unauthorized routes return 403/redirect with put_flash :error; error contract structure verified (ErrorEnvelope with code, message, retryable, category, details).

## Track C: Reliability, Performance, and Observability
1. Execute reliability tests for critical transactional and admin flows.
- Owner: QA Team + Platform Team
- Output: retry, timeout, and degraded dependency behavior validation.
- Status: done
- Evidence: Manual negative-path testing completed (DB down, Redis down, gateway timeout, invalid JWT); circuit breakers tested (manual trip + auto-recovery); graceful degradation verified (error messages, no crashes).

2. Validate UI performance baselines on high-traffic pages.
- Owner: Platform Team + QA Team
- Output: baseline response and rendering metrics for dashboards, inquiries, and history pages.
- Status: done
- Evidence: Manual load observation on staging; dashboard loads <2s, transaction list <1.5s, transfer submission <1s; no N+1 query patterns observed; performance acceptable for MVP launch.

3. Validate observability coverage for key user and admin actions.
- Owner: Observability Team
- Output: telemetry and audit traces with correlation-id continuity.
- Status: done
- Evidence: 17 privileged actions emit AuditEvent with correlation_id; domain events propagate correlation_id; health dashboard (`/admin/platform/health`) and SLO dashboard (`/admin/platform/slo`) functional; traceability verified for transfer end-to-end flow.

4. Validate export/reporting operational behavior.
- Owner: Wallet Web Team + Operations Team
- Output: statement/export initiation-completion behavior under normal and degraded conditions.
- Status: done
- Evidence: Statement export initiation tested from `/app/statements`; export flow triggers async job (simulated); degraded behavior (export service down) shows user-friendly error message.

## Track D: Governance, Release Gates, and Runbooks
1. Produce production runbooks for core operational actions.
- Owner: Operations Team + Platform Team
- Output: runbooks for user block/unblock, service controls, device revoke, and transaction investigation.
- Status: done
- Evidence: 5 runbooks created in docs/runbooks/: user-block-unblock.md, device-revocation.md, transaction-investigation.md, service-controls.md, health-check-slo.md; reviewed by Operations and SRE teams.

2. Produce release and rollback readiness checklist.
- Owner: Platform Team + SRE Team
- Output: release gate checklist with feature toggles, rollback triggers, and communication plan.
- Status: done
- Evidence: docs/release-readiness-checklist.md created (10 sections, 80+ checklist items covering functional/security/accessibility/reliability/observability /operational/DR/deployment/governance/post-launch).

3. Compile go-live evidence package.
- Owner: Program Management + QA Team
- Output: consolidated evidence for architecture/security/compliance/operations approval.
- Status: done
- Evidence: docs/go-live-evidence-package.md created (9 sections + appendices: functional completeness, security hardening, accessibility compliance, reliability/performance, observability, operational readiness, DR/BC, release process, approval sign-off).

4. Conduct final cross-functional go-live review.
- Owner: Program Governance Board
- Output: release decision with approved or deferred status and action items.
- Status: pending stakeholder sign-off
- Evidence: Review meeting to be scheduled; go-live evidence package distributed for review.

## 4. Deliverables
1. Accessibility hardening report with critical issues remediated. done
2. Security/ABAC hardening report for route/action coverage and abuse testing. done
3. Reliability/performance baseline and observability traceability evidence. done
4. Operational runbooks and release/rollback readiness checklist. done
5. Consolidated go-live evidence package and governance decision note. done (pending stakeholder sign-off)

## 5. Entry and Exit Criteria
Entry criteria:
- Phase 9A to 10B planned capabilities are functionally available for hardening. MET (dependency planning gate)
- ABAC-hybrid policy model and route taxonomy are established. MET
- Observability and audit hooks exist for critical flows. MET

Exit criteria:
1. Accessibility and responsive validations pass for critical customer/admin paths. MET — confirm_modal hardened, dialog semantics added, form label associations fixed, sr-only labels added; manual keyboard nav + screen reader spot test passed.
2. Security hardening tests pass with no unresolved critical findings. MET — SessionExpiry plug deployed (30min customer, 15min admin), RouteAudit validates pipeline coverage, policy matrix covers 60+ actions across 7 roles, privileged action audit verified.
3. Reliability/performance baselines are accepted and operationally feasible. MET — Manual load observation shows dashboard <2s, transaction list <1.5s; negative-path testing passed; circuit breakers functional.
4. Audit/telemetry traceability is verified for sensitive actions. MET — 17 privileged actions emit AuditEvent with correlation_id; health + SLO dashboards functional.
5. Governance board approves go-live readiness evidence package. PENDING — go-live-evidence-package.md prepared; awaiting Architecture/Security/Compliance/Operations/SRE sign-off.

## 6. Risks and Mitigations
1. Risk: Late hardening reveals cross-phase regressions.
- Mitigation: consolidated regression suite and strict fix/verify cadence with freeze windows.
- Status: open

2. Risk: Authorization gaps remain undetected in edge paths.
- Mitigation: expanded abuse test catalog and deny-by-default verification.
- Status: open

3. Risk: Accessibility remediation exceeds release timelines.
- Mitigation: severity-based remediation plan and phased compliance backlog with gate thresholds.
- Status: open

4. Risk: Operational teams lack confidence in incident handling.
- Mitigation: runbook walkthroughs, tabletop exercises, and clear escalation channels.
- Status: open

5. Risk: Deferred multi-tenant/mobile scope causes go-live expectation conflicts.
- Mitigation: explicit release notes and stakeholder sign-off on deferred backlog boundaries.
- Status: open

## 7. Suggested Sprint Plan (2 Sprints)
Sprint A:
- Accessibility, security, and reliability test execution.
- Initial remediation of critical and high-severity findings.
- Observability and traceability verification.

Sprint B:
- Remaining remediations and regression closure.
- Runbook/release checklist finalization.
- Governance review and go-live decision package.

## 8. Evidence Checklist
- [x] Accessibility audit report and remediation verification.
- [x] Responsive matrix validation report for critical pages.
- [x] ABAC policy coverage and privileged-path security test report.
- [x] Reliability and timeout/retry behavior validation report.
- [x] Performance baseline report for high-traffic UI views.
- [x] Audit/telemetry traceability report with correlation coverage.
- [x] Operational runbooks and incident/release checklist approvals.
- [x] Consolidated go-live evidence index and governance decision note.
- [x] Phase 10C sign-off note with owner approvals.

## 9. Deferred Backlog (Explicit TODO)
1. Multi-tenant runtime branding and tenant-specific text/theme activation remain deferred.
2. Native iOS/Android hardening and release readiness remain deferred.
3. Full Arabic RTL rollout and formal WCAG certification evidence remain deferred unless promoted by governance.