docs: consolidate repository guides and preserve audit history

docs/roadmap/README.md

@@ -0,0 +1,9 @@
+# Roadmap and open work
+
+This directory contains only outstanding or decision-relevant work. Completed historical phase logs, audit packets, and implementation diaries are archived.
+
+- [TODO](todo.md)
+- [Technical debt](technical-debt.md)
+- [Known issues and blockers](known-issues.md)
+
+The root [BLOCKERS.md](../../BLOCKERS.md) remains the operator-facing source for external credentials, production access, and deployment decisions.

docs/roadmap/known-issues.md

@@ -0,0 +1,15 @@
+# Known issues and blockers
+
+The following items are preserved from the current blocker/audit records and are not represented as resolved merely because local tests pass.
+
+- **Production release/verification:** authenticated production smoke, provider delivery, backup restore, rollback rehearsal, proxy topology, host firewall, and complete UI/browser verification require operator access. See root `BLOCKERS.md`.
+- **Stripe activation:** code exists, but the recurring `price_...` value, portal, webhook, and production secrets are not fully configured/verified.
+- **Account deletion:** self-service deletion stays disabled until retention, legal-hold, tombstone, restore, and provider-cleanup policy is approved and rehearsed.
+- **Legacy schema cutover:** duplicated opportunity columns remain for compatibility until production data/backups and old-client requirements are validated.
+- **Ingress/DNS:** outbound URL import destination validation is enforced at socket connection by completed B01, including mapped-address regression coverage. The separate inbound F04/B06 production proxy-peer, client-IP and firewall boundary still needs deployed evidence; local tests do not close it.
+- **Email/AI operational durability:** local failure handling exists, but independent delivery alerts, provider outages, and worker containment require runtime verification.
+- **Accessibility/UI:** full keyboard, screen-reader, zoom, contrast, focus, and CV-builder failure-state review remains partly manual.
+- **Open audit carryovers verified against source:** stale CV/profile/job saves still expose version counters without a client revision precondition (F01); startup still falls back to SQLite when the provider or connection is missing (F19); and calendar export still treats unspecified `DateTime` values as UTC, so offset/DST preservation is not proven (F21).
+- **Conditional worker risk:** AI worker processing is disabled by default, but the enabled hosted loop still has no outer catch/backoff boundary for unexpected database failures (F20). Treat worker survival as requiring verification before enabling it in production.
+
+For exact source IDs, dates, and evidence, use the archived audit packets rather than adding duplicate status reports here.

docs/roadmap/technical-debt.md

@@ -0,0 +1,16 @@
+# Technical debt
+
+## P1
+
+- EF migrations and startup reconciliation still share historical schema ownership. Keep compatibility bootstraps until a production restore rehearsal supports an expand/verify/contract migration.
+- `JobApplication` duplicates opportunity data now owned by `Job`. Keep dual writes and compatibility reads until the production report/restore gate passes and one observation release completes.
+- Background workers are single-instance; add database leasing before deploying more than one backend replica.
+
+## P2/P3
+
+- Central log aggregation is deployment-owned; add it only when multi-host operation or incident response requires it.
+- Tags remain a JSON string and attachment-purpose flags remain compatibility columns; normalize/remove only with measured need and an API/schema compatibility release.
+- Checklist reads intentionally seed/synchronize system items and are non-cacheable until measured workspace volume justifies separation.
+- Large controllers/components should be split only around a cohesive behavior change with regression coverage; do not perform a standalone rewrite.
+
+Intentional design choices are not debt: free-text statuses preserve custom user values, Next.js remains the static shell, and the current CV queue targets one backend instance.

docs/roadmap/todo.md

@@ -0,0 +1,25 @@
+# TODO
+
+Status reconciled: 2026-09-11.
+
+## Current repository work
+
+- **P4-02 — open:** finish the current UI semantic-control and modal-state review, preserve `RichTextField`/draft behavior, then run full regression and visual evidence. The active implementation record is [`docs/redesign/phase-4/p4-02/README.md`](../redesign/phase-4/p4-02/README.md).
+- **P2-D01 — open:** repair the SQLite `DateTimeOffset` ordering baseline before package/tailoring restructuring; retain the expected-failure browser oracle until native capture and historical-binary preservation are proven. P2-O01's initial rules-500 behavior also remains unconfirmed.
+- **P3-O01/P3-O02 — open:** address analytics population/period labels and navigation/query/error retention when those surfaces are next changed. Evidence is in the current [redesign decision records](../redesign/phase-3/OPEN_DECISIONS.md).
+- **F04/B06 — open:** complete the authorized main release and production ingress/runtime verification; the browser gate and runner diagnostics remain unresolved. No gate should be bypassed.
+
+## Delivery and feature gates
+
+- Deploy the verified CV Builder/UI batch through protected `main` and confirm the live health/version transition.
+- Run authenticated production CV editing/PDF, existing-data, attachment, email-verification, OAuth, and rollback smoke checks when an authorized session is available.
+- Activate Stripe only after the recurring Pro price, portal, webhook, and external secrets are configured; see [known issues](known-issues.md).
+- Rehearse backup/restore and the legacy `Job`/`JobApplication` cutover against a restored production backup before removing compatibility columns.
+
+## CV Builder preservation and next slice
+
+The current builder already includes expandable sections, preset/free-text custom sections, section AI review, Code and other capability-aware templates, accent/typography controls, shared preview/PDF rendering, and extraction confidence handling. Preserve these under PRES-C02/C07/C08/C09/C12; they are not new backlog requirements. See the [functionality inventory](../redesign/audit/FUNCTIONALITY_INVENTORY.md) and [57-group preservation matrix](../redesign/phase-2/PRESERVATION_MATRIX.md).
+
+P4-03's future scope is the loaded preview keyboard/viewport boundary, after review of P4-02. Broader editor changes require their own approved slice and preservation evidence; do not restart already-completed builder work from archived plans.
+
+Completed phase items are intentionally omitted here; their evidence remains recoverable in the pre-cleanup backup and existing archive.