jobtrackingapp/docs/work-programmes/master-progress.md

JobTracker master programme progress

Updated: 2026-08-15

• Overall programme status: Active. Seven packages are locally verified; twenty-two are implemented with verification incomplete; JOBS-002 is in progress. The prioritized admin-only version indicator is implemented and focused-tested on the release branch; the current branch still requires full/remote gates and production verification.
• Current work package: JOBS-002 — applications table and dedicated workspace (IN PROGRESS). The canonical page/table/sidebar integration exists; remaining parity, dirty-edit, tenant-authorization and browser regression work is tracked in the immediate queue.
• Completed work packages: None are DONE; all repository security/AI packages still have applicable browser, provider and/or production gates.
• Locally verified work: SEC-001, SEC-002, SEC-003, SEC-005A, CORE-001, PROD-002 and DEP-001 (VERIFIED LOCALLY).
• Implemented, verification incomplete: SEC-004, SEC-005B, SEC-008, CORE-002, BG-001, OPS-001A/B/C, POL-001/002, AI-001/002/003/004, UX-001/002/003, QA-001, CAREER-001/002, MAIL-001 and JOBS-001 (IMPLEMENTED — NOT VERIFIED). UX-003 safe local/browser scope is implemented; production/native-device gates remain.
• Production-verified work: None.
• Blocked work: SEC-006 parser upgrades remain outside the scoped frontend advisory permission; PROD-001/003/004 and REL-001 require documented production access and unfinished dependencies. Real provider, SMTP/MariaDB and production environments are unavailable; DEP-001 awaits approved merge/live verification. The in-app browser is available for local UI checks.
• Deferred work: None. Conditional multi-replica coordination, model deletion, realtime operation delivery and unrelated production changes remain outside current packages.
• Immediate order: JOBS-002 parity/regression; cross-app contrast/accessibility; PRODUCT-001; VER-001. Admin version (a6cffe0), Career lossless persistence (f0b9b22) and CV contact contrast are locally complete. External-only work remains skipped, not allowed to stall this queue.
• Status counts: 7 VERIFIED LOCALLY; 22 IMPLEMENTED — NOT VERIFIED; 1 IN PROGRESS; 4 NOT STARTED; 5 BLOCKED; 0 DONE; 0 DEFERRED.
• Test status: backend 644/644; CV renderer/settings 25/25; CV Builder/public UI 22/22; affected Career/import/profile/job paths 112/112; Career/Profile UI 17/17; prior frontend 53/53 suites and 221/221 tests plus optimized production build/TypeScript pass. Real Chromium contrast/overflow checks pass and the harder pathological fixture exports a 17-page A4 PDF with final-page text. Prior AI sidecar 22/22, Playwright 6/6 and npm audit 0 evidence remain current. Historical JT-019 and Jest force-exit/open-handle behavior remain recorded.
• Deployment status: Gitea pull-request run 609 passed the complete CI job in 4m20s. Deploy was intentionally skipped because the workflow deploys only a push to main; live remains unchanged. No merge/deployment was performed directly, no production migrations were run and the AI operation worker remains disabled by default.
• Production status: Unchanged and unverified. No provider/model call, model pull, external request or paid API occurred.
• Known regressions: None found by automated/local browser checks. Jest still needs --forceExit and reports its existing open-handle notice. Email-provider/send tests are fake/local only; real delivery is not claimed. Current MAIL browser evidence is 1280×720 only because the browser surface could not resize or perform native Tab traversal. Interrupted attempts are aged after 15 minutes and notified without retry; the five-minute scan is unmeasured on a large ledger. Direct clean EF-only SQLite migration still hits the pre-existing historical blank-chain defect before later migrations; normal startup owns reconciliation. Cross-feature monthly AI usage accounting remains a rollout gap.
• Outstanding security findings: JT-001 repository ownership remains High deployment risk until migration/inventory/provider checks; production portion of JT-002; JT-006/JT-009 and associated JT-011/JT-012/JT-022 prerequisites. JT-005 foundations are implemented; AI worker activation awaits controlled rollout. JT-007/JT-008/JT-010 lack browser/provider/production verification.

Current evidence

• docs/audits/audit-remediation-backlog.md
• docs/audits/verification-log.md
• docs/verification/sec-001-canonical-origin.md
• docs/verification/sec-002-ingress-compose.md
• docs/verification/sec-003-microsoft-tenant.md
• docs/verification/sec-004-microsoft-identity.md
• docs/verification/sec-005a-session-revocation.md
• docs/verification/sec-005b-email-ownership.md
• docs/verification/core-001-sqlite-provider-parity.md
• docs/verification/core-002-route-uniqueness.md
• docs/verification/sec-008-attachment-consistency.md
• docs/verification/bg-001-tenant-workers.md
• docs/verification/ops-001a-durable-operations.md
• docs/verification/ops-001b-notifications.md
• docs/verification/ops-001c-operation-ui.md
• docs/verification/pol-001-free-pro-entitlements.md
• docs/verification/pol-002-ai-privacy.md
• docs/verification/ai-001-durable-ai-queue.md
• docs/verification/ai-002-provider-routing.md
• docs/verification/ai-003-strategy-snapshot-queue.md
• docs/verification/ai-004-cv-processing-queue.md
• docs/verification/ux-001-unified-authentication.md
• docs/verification/ux-002-deterministic-theme-state.md
• docs/verification/qa-001-job-term-quality.md
• docs/verification/career-001-career-workspace.md
• docs/verification/career-002-cv-builder.md
• docs/verification/mail-001-job-email-hub.md
• docs/verification/jobs-001-job-discovery.md
• docs/verification/ux-003-kanban-theme.md
• docs/verification/prod-002-ai-evaluation.md
• docs/work-programmes/master-work-plan.md