Skip to content

Phase 2 Production Hardening Backlog

Date: 2026-04-15
Scope: Security, sync resilience, and production controls for school deployment readiness.

Prioritized Worklist

PriorityWork ItemOwnerRequirement MappingAcceptance CriteriaDepends On
CriticalBackend password KDF for user create/reset flowsBackendSRS NFR-007, SCR-001, ADR-0003✅ Implemented — workers/src/modules/auth/password.ts uses PBKDF2N/A
CriticalLocal PII encryption-at-rest strategy and rolloutFrontend + SecuritySRS NFR-007, SCR-004, ADR-0004✅ Implemented — encryptionHooks.ts + testsAuth/session lifecycle hardening
HighAuth/session bridge hardening with expiry-safe offline queue behaviorFrontend + BackendSRS FR-016, FR-017, SR-001, SCR-002Offline queue is preserved on expiry, protected submission blocked, and recovery after re-auth validatedSession validation contract
HighAutomatic sync drain with retry/backoff and reconnect triggersFrontendSRS NFR-006, SR-001, SR-005, ADR-0002Pending queue drains automatically when online, retries are bounded, and timeout recovery is observableSync queue status telemetry
HighConflict resolution UX from sync conflicts metadataFrontendSRS SR-002, SR-003, SR-004, SR-005, ADR-0005Users see conflict winner/loser policy and actionable state instead of silent failureSync response conflict payload
HighGlobal and route-level error boundariesFrontendSRS NFR-001, NFR-009✅ Implemented — AppErrorBoundary in main.tsxNone
HighSecurity headers and input sanitization defaultsBackendSRS NFR-008, SCR-005, ADR-0002✅ Implemented — middleware security-headers.ts activeNone
MediumLean MVP role simplification in UIFrontendPRD goals, SRS FR-009🔄 Post-MVP — no forecastNone
MediumRetention policy for synced queue/event records (audit-safe)Product + BackendSRS DR-002, SR-004, LGPD baseline30-day purge policy documented and excludes audit-critical recordsAudit retention rules
MediumProduction CI/CD safety gates (no dev auth, mandatory migrations, release checks)DevOps + BackendADR-0008, deployment guidancePipeline blocks production deploys without migrations and hardened auth modeEnvironment matrix

Delivery Order

  1. Backend auth hardening + API security defaults.
  2. Frontend runtime safety + automatic sync draining.
  3. Auth/sync bridge validation and conflict visibility UX.
  4. PII encryption-at-rest rollout.
  5. Governance controls (retention + CI/CD safety gates).

Distributed under MIT License.