docs(roadmap): preserve continuous directive and integrity checkpoints

2026-11-11 18:25:49 +01:00
parent 3fe83f5ef7
commit 760360f443
6 changed files with 343 additions and 1 deletions
@@ -51,3 +51,5 @@ Resolved: delayed job export/CSV conversion downloaded or announced after sessio
 Import/conversion one-item wording resolved in44112c7c;50 overlapping tests and two copy-focused profiles/six native conversions passed. Broader language review remains open.

 V47 Rules third-column/mobile-gap discrepancy resolved in99b144f4;final76 affected cases and12 configurations/84 scans passed. V45–V47 dispositions and route evidence are published in9f341750. Remaining full-route/native/security/release obligations unchanged.
+
+Submitted package CV metadata/render revision mismatch and disappearance reproduced/fixed (e161ea33; integratedf807d46f). Legacy0 compatibility failure corrected,22casespass. Backup permission double-failure falsely continued through actual conditional gates; fixed1c8761b1,19methods pass. Concurrent Career Profile render consistency and attachment cleanup ownership remain open investigations, not fixed claims.
@@ -1,6 +1,16 @@
 # Direct execution continuation

-Current published A3 ref:9f341750ece2a3d2ddb11c14482df1ecc485a5c1; app/verifier99b144f4. Release separately:e1c8e84502e08144a32f496af8b03cb26f0ec815. Four bounded TODO subitems qualified/published this continuation. Next: connected document/application workflows and remaining offline recovery/completion paths; protected gates remain pending.
+Current published A3 ref:dbae196291cce2c3ecc4e35fee6e336328e00b53 (package sourcef807d46f/e161ea33); release4019569ab7cd03115371d3820898c324b4cc8252. Continuous directive preserved below. Root continues sequentially after delegate quota/C-drive capacity failures. Next: Career Profile snapshot/render coherence, CV library lifetime and connected workflows. Protected gates unchanged.
+
+## 11 November continuous directive: document and backup integrity
+
+- Full owner continuous directive preserved at sources/CONTINUOUS_DEVELOPMENT_DIRECTIVE_b2425dc6.md, original SHA256 809b52c1373c81c46920d0d0c3c93a6b4416e320118cfe342d43b1d0409bfc8d. Review entire TODO after each increment; no checkpoint-only stops or routine questions. Existing gates remain; no orchestrator. Both implementation delegates hit usage limits; root continued sequentially rather than retrying unchanged failures.
+- A3 published/ref-readbackdbae196291cce2c3ecc4e35fee6e336328e00b53. Sourcef807d46f is exact cherry-pick of isolatede161ea33; source/evidence branchcodex/frozen-document-integrity published444d5c89a23f8df1de5b681355ea5f55df980f41. Full API/test/config diff equivalence passed after integration. Submitted CV capture now binds the selected revision, rechecks stored revision/settings after render, rejects disappeared CVs and maps capture conflicts to existing409revision_conflict. Legacy revision-zero capture remains supported; public positive revision validation unchanged.
+- RED8 cases:3failed/5passed; intermediate20:1legacy compatibility failure/19passed; final22:allpassed/noskips across package/controller/export-revision/native SQLite suites. Final includes6new race/auth cases; do not add overlapping counts. Native bytes/hash, owner denial, missing attachment and frozen account-export checks retained. Report docs/cv-integration-qa/PACKAGE_REVISION_CAPTURE.md in A3. No renderer/physical PDF/style change or fresh physical metric claim.
+- C: filled before initial test execution. Only this attempt's fresh ignored bin/obj paths were removed after absolute containment/Git checks; cached restore and all build/temp/results moved to E by CLI flags. C remains constrained (~100MB after graph work); do not start normal C-output builds or delete unrelated worktrees/cache/user data. Source/evidence/dependencies preserved. Graph update custom --out unsupported; default AST update executed; no optional extractor/tool repair.
+- Release separately published/ref-readback4019569ab7cd03115371d3820898c324b4cc8252, source1c8761b1. Failed host+fallback backup permission protection now explicitly stops verification/nextgate, preserving artifact. RED3methods/6scenarios with2failedsubtests; final19backup methods passed, syntaxpassed. Prior6rollback methods not rerun (handlerunchanged). All chmod/Docker/content/size commands mocked around synthetic files; no actual permissions/prune/upload/deploy/recovery. Report release docs/release-readiness/11_BACKUP_RESTORE_ROLLBACK.md#rr-13-backup-permission-gate.
+- Next highest-priority eligible: concurrent Career Profile snapshot/render coherence investigation, then queued CV library action/download lifetime and connected workflows. AttachmentStorage destination cleanup ownership remains source-backed/unreproduced; no fix claimed. Broader linked document/backend/browser/MariaDB/native/physical/provider/security/recovery acceptance remains open. Phase10 D02, final A3, homepage/provider and release decisions stay protected.
+

 ## 11 November final Settings/retention continuation

@@ -16,3 +16,5 @@ Edit Job V39 is qualified/published at c172427f; do not repeat its nine paired j
 Export/session lifetime is qualified; singular import/conversion feedback is now qualified. Continue Rules density/recovery. Release e1c8e845 is published separately; do not repeat unchanged external recovery attempts or claim real pruning/restore.

 Current Rules source99b144f4 passed combined76 cases/seven suites and12 configurations/84 scans. Releasee1c8e845 remains a separately qualified branch; actual recovery is gated.
+
+Latest priority: resume canonical Career Profile/render coherence from isolated codex/frozen-document-integrity (444d5c89; exact backend integrated in A3dbae1962), then CV library action lifetime. All .NET artifacts/temp/results belong on E; no retry of C-output build or delegate quota. Release4019569a is separate; normal push/readback succeeded.
@@ -33,3 +33,5 @@ Implemented, tested, accepted, published and production-ready are separate. Prod
 - V39 resolved within `/jobs`; the 34-route/57-group inventory and final owner/human qualification remain open. Other shared MUI labels and legacy timestamp semantics remain independent tasks. Phase 10 D02, launch selection, providers, integrated security/recovery and release gates are unchanged.

 EN/NB import/conversion singular feedback qualified through511b68a1:50 overlapping cases, two paired profiles/six native conversions/six scans. Broader localisation and native-language review remain open.
+
+11 November continuation: A3dbae1962 integrates submitted-CV revision integrity (22 scoped backend cases; legacy0 retained). Release4019569a closes mocked permission failure propagation (19 backup methods). Frontend76-case and UI matrices remain historical/source-bound; no new app-wide acceptance. Delegate quota and C-capacity limits documented; E build lane works.
@@ -30,6 +30,7 @@ Updated 11 November 2026. This is the cross-phase work list. The source prompts,
 - [ ] **Discover**. Existing NAV search-first/mobile filters shipped through `d027754d`. Both complete existing native discovery specs passed all11 cases with31 screenshots/27 audits, following the separate controlled drawer36/108 and saved16/48 checks. Continue results/detail and broader route/workflow review. New search skills, radius, tree/map and providers belong to GJ/EUROPE with qualified data and rights.
 - [ ] **Applications**. Title-first rows, explicit selection, preparation wording and compact keyboard row actions shipped through `1d733675`. Four server-backed EN/NB/theme density/action journeys passed after long-status wrapping and selected dark-link contrast fixes. Finish broader table/board/detail workflow and native/visual acceptance, including follow-up.
 - [ ] **Calendar**. Recorded closing dates and follow-ups are covered. Resolve genuine interview scheduling, original precision/timezone and provider/ICS qualification as applicable. Preserve agenda/month toggle and preference.
+- [x] **Submitted CV revision binding, bounded scope**.Integratedf807d46f/dbae1962;22 targeted backend cases passed, including legacy0/nativeSQLite/controller409. Canonical Profile concurrent rendering and remaining file/package races stay open.
 - [ ] **Career, CV, letter and documents**. Finish connected overview-to-document reuse and create/import-to-edit/preview/export evidence. Preserve revisions, null-as-inherit, canonical profile ownership, frozen packages, import review and RD21.
 - [ ] **Correspondence**. Read ordering/manual-note recovery qualified at1f3bdbcd (27 tests/eight journeys/40 scans); Pasted-email recovery also qualified at72be6144 (33 overlapping tests/eight pasted journeys/40 scans). V42–V44 recovery and decorative surfaces are qualified through214eb25f (latest12 note configurations/60 scans plus separate pasted canary). Remaining provider/completion-path, draft-navigation, native and final visual checks stay open. Improve inbox, mailbox state, relevant job context and review. Scope explicit consent, provider permissions, multi-mailbox storage and retention separately. Preserve conflict, attachment and confirmed-send flows.
 - [x] **Admin Users compact actions**. One keyboard menu retains existing role, reset and delete paths. Published `327d99df` with 14 tests and 72 controlled browser states.
@@ -116,6 +117,7 @@ Bounded offline fixes and root security policy exist. Formal integrated scope, t

 - [ ] **Stage 1** Close discovery, prior blockers and baseline scope. Census/parser, RR-13 transfer/monthly guards and RR-12 rollback health checks are published through release `55431b5a`. Six offline rollback and twelve backup tests passed. Release e1c8e845 also closes masked retention-command failures, with16 backup/6 rollback offline methods. Runtime rollback and recovery remain open.
 - [x] **RR-13 retention failure propagation, offline scope**.e1c8e845;daily prune/monthly enumeration/sort/prune failures explicitly stop continuation.16 backup/6 rollback mocked-function methods and syntax passed. Actual pruning, recovery and release qualification remain open.
+- [x] **RR-13 permission failure gate, offline scope**.1c8761b1/4019569a;19 backup methods including six permission scenarios passed. No real chmod/container/recovery acceptance.
 - [ ] **Stage 2** Freeze exact candidate, environment, image/digest, migration/config/dependency identities, CI and evidence provenance.
 - [ ] **Stage 3 · Functional** Accounts/auth, jobs/tracking, dashboard, career/CV/documents, AI, correspondence, integrations, notifications, admin, billing and exports. Qualify real browser, sidecar and MariaDB lanes separately.
 - [ ] **Stage 3 · UX** Responsive/visual and keyboard/AT/accessibility, EN/NB and launched locales, reflow/contrast, physical devices and representative workflows.
@@ -178,3 +180,5 @@ Latest independently validated A3 increments: flat Edit Job `c172427f`, shared w
 Current development ref b9bb3c44 includes V40/V41 disposition and the explicit backend Saved-date guard clarification. The frontend/date request defect is fixed; stored-data corruption was not reproduced.

 I18N/PERF continuation: correspondence fallback errors now translate without another read or lost draft (red extra-request regression;27-case package). This is bounded duplicate-read prevention, not latency/load or European locale acceptance. Latest scoped visual source c6375876; do not rerun unchanged matrices merely to resume.
+
+Environment: delegate implementation quota unavailable; root sequential. C: capacity constrained; use E build/temp/results, preserve unrelated data. Next inspect concurrent canonical profile/render binding; attachment cleanup race source-only; CV library stale action/download checks still eligible.
@@ -0,0 +1,322 @@
+# Jobjakt — CONTINUOUS DEVELOPMENT DIRECTIVE
+## Keep Working Until No Further Authorised Work Is Possible
+
+I want you to continue developing Jobjakt autonomously for as long as the current execution environment permits.
+
+**Do not stop after completing one task, checkpoint, commit, feature, test suite or workstream.**
+
+Continue selecting and completing the next eligible task from my entire Jobjakt roadmap.
+
+Do not use the autonomous orchestrator. Continue directly in this Codex conversation using my existing development environment and account.
+
+## 1. Authoritative task sources
+
+Read and continually maintain:
+
+- `docs/direct-roadmap/ROADMAP_TODO.md`
+- `docs/direct-roadmap/ROADMAP_STATUS.md`
+- `docs/direct-roadmap/LATEST_CHECKPOINT.md`
+- Relevant source prompts, implementation plans and acceptance documents.
+
+Use the actual repository state as the source of truth.
+
+The roadmap includes:
+
+- Remaining Phase 10 acceptance.
+- A3 application UI/UX modernisation.
+- Product Review.
+- International Global Job Search.
+- European localisation.
+- Europe-wide geographic support.
+- Performance and scalability improvements.
+- Public homepage redesign.
+- Security audit and remediation.
+- Release readiness.
+- Existing technical debt and preservation requirements.
+
+Do not abandon existing tasks or replace their acceptance criteria.
+
+## 2. Continuous execution loop
+
+After completing any task or checkpoint:
+
+1. Verify the implementation.
+2. Run the appropriate tests.
+3. Fix bounded failures.
+4. Record actual verification evidence.
+5. Commit validated changes.
+6. Push where available and required.
+7. Update the authoritative TODO and continuation records.
+8. Review all remaining eligible tasks.
+9. Select the highest-priority independently authorised task.
+10. **Immediately continue working on it.**
+
+Repeat this process for as long as useful work remains and execution is available.
+
+Do not end your response merely to provide a progress summary.
+
+Do not ask whether I want you to continue.
+
+Do not wait for a new "continue" instruction between checkpoints.
+
+## 3. Latest progress
+
+Recent published work includes:
+
+- A3 application UI improvements and visual flattening.
+- Discovery filter drawer and saved-search workflows.
+- Settings freshness, locale-aware sorting and timezone fixes.
+- Correspondence recovery and duplicate-submission fixes.
+- Session-safe exports and CSV downloads.
+- Import/conversion localisation fixes.
+- Rules UX and recovery improvements.
+- Offline backup and rollback improvements.
+
+The latest reported application checkpoint is `214eb25f`, followed by further published TODO work.
+
+Verify the actual current Git HEAD and continuation records rather than assuming this summary is the latest commit.
+
+Avoid repeating completed work.
+
+The next reported focus is connected document/application workflows, followed by further eligible items in the existing roadmap.
+
+## 4. Work through the entire TODO
+
+Do not restrict yourself to the most recently discussed page or feature.
+
+Continue across all authorised workstreams.
+
+Prioritise:
+
+1. Confirmed security or data-integrity defects.
+2. Work that unblocks other roadmap tasks.
+3. Incomplete core user journeys.
+4. A3 UI/UX and accessibility gaps.
+5. Global Job Search and European localisation.
+6. Performance and scalability improvements.
+7. Homepage implementation.
+8. Broader security and release qualification.
+
+Adjust priority using actual dependencies, risk and impact.
+
+A roadmap task marked PARTIAL is not complete.
+
+A task marked BLOCKED must remain open until its blocker is genuinely resolved.
+
+## 5. Work concurrently when safe
+
+Where the environment supports parallel Codex agents, use them for independent tasks.
+
+Examples:
+
+- Frontend UI/UX and accessibility.
+- Backend performance and query optimisation.
+- European translations.
+- Global Job Search research and provider-independent implementation.
+- Security static analysis.
+- Release-readiness documentation and offline checks.
+
+Use separate worktrees or otherwise isolated scopes.
+
+Avoid conflicting modifications to the same files.
+
+Do not run incompatible database migrations or competing tests against shared mutable fixtures.
+
+Respect reasonable resource limits.
+
+If safe parallel execution is unavailable, continue sequentially.
+
+**Do not stop simply because concurrency is unavailable.**
+
+## 6. Blockers must not stop the roadmap
+
+If an individual task cannot proceed:
+
+1. Investigate the blocker.
+2. Attempt reasonable safe remediation within the authorised scope.
+3. Record the exact issue in the existing TODO.
+4. Mark it BLOCKED or AWAITING_APPROVAL.
+5. Record the required action.
+6. Identify another independently eligible task.
+7. Continue immediately.
+
+Do not retry unchanged failures indefinitely.
+
+Do not waste time repeatedly investigating unavailable external providers, infrastructure or approvals.
+
+Do not treat production NO-GO as a reason to stop unrelated development.
+
+## 7. Batch all owner questions
+
+I do not want to be interrupted for ordinary development decisions.
+
+Maintain one consolidated list of questions and approvals.
+
+If a task requires my input:
+
+- Record the decision.
+- Explain the available options.
+- Provide your recommendation.
+- Identify the dependent work.
+- Continue other eligible work.
+
+Only ask me questions when there is no further useful authorised work that can proceed, or when an immediate security/data-loss risk genuinely requires my attention.
+
+When that point is reached, present all outstanding questions together in one prioritised decision batch.
+
+Do not interpret silence as approval.
+
+Do not bypass mandatory approval gates.
+
+## 8. Use accepted decisions
+
+Do not repeatedly ask me to approve decisions I have already made.
+
+Preserve:
+
+- The approved A3 design direction.
+- The requirement to remove unnecessary nested cards on desktop and mobile.
+- All 34 routes and 57 preservation groups.
+- The international, Europe-wide product scope.
+- Country-aware geographic filtering and maps.
+- Full European localisation goals.
+- The existing PDF visual approval and accepted S01 metrics.
+- Previously authorised reversible development changes.
+- All genuine remaining approval requirements.
+
+If an approval applies only to a particular scope, do not extend it to unrelated work.
+
+## 9. Testing and acceptance
+
+For every meaningful change:
+
+- Run relevant automated tests.
+- Validate data integrity.
+- Check authorisation where applicable.
+- Check desktop/mobile behaviour.
+- Check English/Norwegian and affected European locales.
+- Preserve existing functionality.
+- Record actual results.
+- Fix regressions when possible.
+
+Run broader regression suites when the applicable acceptance gates require them.
+
+Do not fabricate passing results.
+
+Do not mark incomplete implementation or tests as accepted.
+
+Distinguish:
+
+- Implemented.
+- Tested.
+- Accepted.
+- Published.
+- Production-ready.
+
+Use valid historical evidence where appropriate, without presenting it as newly executed tests.
+
+## 10. Maintain durable continuity
+
+After every validated increment, update:
+
+`ROADMAP_TODO.md`
+
+`ROADMAP_STATUS.md`
+
+`LATEST_CHECKPOINT.md`
+
+Record:
+
+- Exact branch and commit.
+- Completed work.
+- Tests executed.
+- Outstanding defects.
+- Blockers.
+- Required approvals.
+- Next eligible tasks.
+
+Ensure another Codex session could resume from the latest checkpoint without repeating work.
+
+Do not create a replacement orchestrator or additional automation infrastructure.
+
+## 11. Do not stop prematurely
+
+The following are NOT reasons to stop:
+
+- One feature is complete.
+- A set of tests passes.
+- A commit is published.
+- An external provider is unavailable.
+- One workstream needs approval.
+- A design review is pending.
+- Hosted CI is unavailable.
+- A production-only gate remains blocked.
+- A partial acceptance report has been generated.
+- A single development task has no further actions.
+
+Continue with another independent task.
+
+## 12. Genuine stopping conditions
+
+Stop only when:
+
+1. No further independently authorised, useful work remains.
+2. All remaining tasks genuinely require owner decisions, external permissions or unavailable prerequisites.
+3. A safety issue makes further work unsafe.
+4. The current Codex execution session reaches a technical, context, resource or usage limit.
+
+If execution must end because of a technical limit, preserve a complete continuation checkpoint and identify the next eligible task.
+
+Do not claim that work will continue in the background unless an actual supported scheduled continuation mechanism is running.
+
+## 13. Final consolidated report
+
+When no further work can proceed, report:
+
+- All completed tasks.
+- All incomplete tasks.
+- Actual verification results.
+- Remaining security issues.
+- European market and language coverage.
+- UI/UX implementation progress.
+- Performance improvements.
+- Outstanding acceptance gates.
+- Grouped owner decisions.
+- Highest-priority next actions.
+
+Present the owner questions together, with recommendations.
+
+Do not claim the whole roadmap is complete unless every relevant acceptance criterion is satisfied.
+
+## Hard restrictions
+
+Never:
+
+- Use or modify the autonomous orchestrator.
+- Merge into `main`.
+- Deploy production.
+- Perform destructive migrations without approval.
+- Change production infrastructure without approval.
+- Self-approve protected gates.
+- Activate unqualified production AI models.
+- Access private production data unnecessarily.
+- Ignore security or tenant-isolation failures.
+- Weaken tests to obtain passing results.
+
+## Final instruction
+
+**START CONTINUOUS ROADMAP EXECUTION NOW.**
+
+Keep implementing, testing, fixing, documenting and committing.
+
+After each completed task, immediately move to the next eligible task.
+
+Use safe concurrency where supported.
+
+If blocked, record the issue and move on.
+
+Do not pause for routine questions or milestone summaries.
+
+**Continue until there is genuinely no more authorised work you can do within the available execution session.**
+
+Only then provide a consolidated report and batch the outstanding questions for me.