docs(jobs): record discovery provenance evidence

docs/audits/verification-log.md

@@ -185,3 +185,4 @@ Output was reduced to filenames and commit counts. The token artifact appears un
 | V-151 | Focused `EmailDraftsControllerTests`; full backend; focused/full correspondence-inbox Jest; production build; staged diff review | Repository root / `job-tracker-ui` | Verify persisted delivery identity rotates only after the matching definitive failure | PASS — draft API 5/5; backend 630/630; inbox 12/12; frontend 50 suites/197 tests; build pass; no ledger row/refused, failed/rotated, stale/refused and foreign/not-found paths pass; `29de263` pushed | Synthetic SQLite and mocked UI only; two npm commands were initially run from repository root and failed environmentally before correct-directory reruns passed; no provider/send/production action | Durable failed-attempt rotation verified locally |
 | V-152 | Focused/full correspondence-inbox Jest; production build; accessible-role inspection; staged diff review | `job-tracker-ui` / repository root | Verify new-message drafting uses an owned job and connected send-capable provider while reusing draft/send safety | PASS — inbox 13/13; frontend 50 suites/198 tests; build pass; owned paged jobs load, read-only provider is excluded, selectors have accessible names, empty job/re-consent guidance is visible, and saved new message uses null thread; `b735963` pushed | JSDOM/mocked APIs only; hub selector is bounded to 100 recent owned jobs; browser/provider/send/production not exercised | New-message repository flow verified locally |
 | V-153 | Complete Phase 9 requirement reread; provider interface/scope/controller inventory; canonical hub and embedded correspondence action comparison | Repository root | Determine whether safe independent MAIL-001 implementation remains | PASS/PARTIAL — routing, suggestions/dismissal, link/relink/unlink, shared saved domain, provider-neutral reads/detail, reply/new-message drafts and explicit send are implemented; Gmail modify/Graph read-write and IMAP outgoing/category contracts are absent, so read/unread/pin/read-later/archive/spam/trash cannot be honestly enabled | Source inspection only; no provider/re-consent/browser/production action. Full SEC-009 deletion and real-provider gates remain | Repository scope implemented; external/authority verification blocked |
+| V-154 | Phase 4 and discovery/import execution-path trace; `dotnet test ... --filter FullyQualifiedName~JobDiscoveryControllerTests --no-restore`; focused `job-discovery.test.tsx` and `quick-capture.test.tsx`; full backend/frontend; `npm run build`; `git diff --check` | Repository root / `job-tracker-ui` | Verify honest NAV provenance, explicit deadline/retrieval mapping and source preservation through reviewed import | PASS — focused backend 1/1; focused UI 2 suites and 4/4; backend 630/630; frontend 50 suites and 198/198; production build and diff check pass; `511a9f6` pushed | One npm command was initially run from repository root and failed environmentally before the correct-directory run passed. Synthetic fixtures/mocked API only; no NAV/browser/production request. Jest retains its existing force-exit/open-handle warning | Repository provenance increment verified; live/browser gates remain |

docs/verification/jobs-001-job-discovery.md

@@ -0,0 +1,28 @@
+# JOBS-001 job discovery verification
+
+Updated: 2026-08-10
+
+## Current verified increment
+
+- The authenticated discovery endpoint searches the official NAV feed and now returns an explicit `nav` source key, `NAV Arbeidsplassen` display name, `searched` acquisition type and one request-level retrieval timestamp.
+- Application deadlines are exposed only when NAV supplies the explicit `applicationDue` field. Missing deadline and work-mode data remain absent rather than inferred.
+- The discovery card renders the response source rather than a hardcoded label, links to the original NAV listing and distinguishes listing update, retrieval and deadline dates.
+- The existing reviewed URL-import flow preserves the NAV source and `NO` country code in the create-job request. This is covered with mocked UI data; no NAV request was made.
+- Source filtering is not added while the endpoint has exactly one verified source. Multi-source filtering remains conditional on real source data.
+
+## Evidence
+
+- Focused backend discovery test: 1/1 passed.
+- Focused discovery and reviewed-import UI tests: 2 suites, 4/4 passed.
+- Full backend: 630/630 passed.
+- Full frontend: 50 suites, 198/198 passed; existing Jest force-exit/open-handle warning remains.
+- Production frontend build and TypeScript checks passed.
+- `git diff --check` passed with line-ending notices only.
+- Implementation commit: `511a9f6`.
+
+## Not yet verified
+
+- No live NAV, browser, provider or production request was performed.
+- Required 375/768/1440, light/dark, keyboard, Norwegian/long-content and end-to-end import checks remain.
+- Sorting controls, submitted-search empty state, richer error/retry behavior and unavailable work-mode disclosure remain in JOBS-001.
+

docs/work-programmes/decisions.md

@@ -609,3 +609,13 @@
 - **Consequences:** real-provider re-consent, provider category design, browser gates, SEC-009 deletion and production verification remain explicit blockers before `DONE`. JOBS-001 becomes the sole in-progress item.
 - **User approval required:** No for status correction; any future provider-scope/re-consent rollout needs a separately reviewed package and safe account verification.
 - **Reversible:** Yes. MAIL-001 can return to `IN PROGRESS` when provider mutation authority is approved and testable.
+
+## DEC-062 — Expose only verified discovery provenance
+
+- **Date:** 2026-08-10
+- **Decision:** Treat NAV as verified because the controller itself fetches the official NAV feed; expose a stable source key/display name, label acquisition as `searched`, stamp the request retrieval time and map a deadline only from NAV's explicit `applicationDue` field. Do not infer work mode or add a one-option source filter.
+- **Reason/evidence:** the previous card hardcoded NAV and an update date while the response's source field was unused. Phase 4 requires honest source/type/retrieval/deadline data and explicitly prohibits presenting inference as verification. Focused provenance/import tests and full regressions pass.
+- **Alternatives considered:** derive source from listing hostname; infer remote/hybrid from title/location; add a disabled or single-option source filter; label `date_modified` as retrieval time. These would confuse derived and verified data or add controls without a real choice.
+- **Consequences:** NAV cards now explain where and how the listing was obtained and preserve attribution into tracking. Missing work mode remains visibly absent rather than guessed; source filtering becomes useful only when a second real provider is implemented.
+- **User approval required:** No; this is approved repository work using synthetic fixtures with no external request.
+- **Reversible:** Revert `511a9f6`; no schema or stored data changes are involved.

docs/work-programmes/master-progress.md

@@ -3,7 +3,7 @@
 Updated: 2026-08-10
 
 - **Overall programme status:** Active. Seven packages are locally verified; twenty packages through MAIL-001 are implemented with automated/runtime evidence but blocked from applicable browser/provider/production gates; JOBS-001 is now in progress. Gitea run 609 passes complete pull-request CI in 4m20s; DEP-001 now awaits approved merge-to-main and production verification only.
-- **Current work package:** `JOBS-001` — job-search source and assessment redesign (`IN PROGRESS`); Phase 4/source-provenance inventory and current-behavior reproduction are next.
+- **Current work package:** `JOBS-001` — job-search source and assessment redesign (`IN PROGRESS`); verified NAV provenance/import preservation is committed, and submitted-search state/sort/scanability is next.
 - **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, QA-001, CAREER-001, CAREER-002 and MAIL-001 (`IMPLEMENTED — NOT VERIFIED`). MAIL repository flows are implemented; provider mutation/re-consent, browser, deletion and production gates remain.
@@ -12,7 +12,7 @@ Updated: 2026-08-10
 - **Deferred work:** None. Conditional multi-replica coordination, model deletion, realtime operation delivery and unrelated production changes remain outside current packages.
 - **Next five work packages:** JOBS-001 job-search/application redesign; HOME-001 homepage/Pro promotion; UX-003 authentication/profile polish; PRODUCT-001 homepage/Pro claims; JOBS-002 application workspace redesign. SEC-006/007 resume after package-index permission.
 - **Status counts:** 7 `VERIFIED LOCALLY`; 20 `IMPLEMENTED — NOT VERIFIED`; 1 `IN PROGRESS`; 7 `NOT STARTED`; 5 `BLOCKED`; 0 `DONE`; 0 `DEFERRED`.
-- **Test status:** backend 630/630; frontend 50/50 suites and 198/198 tests; Playwright smoke 4/4; npm audit 0 vulnerabilities; DEP-001 focused router 24/24 and production build pass; MAIL-001 draft/new-message UI 13/13, draft API/idempotency/rotation 10/10, readable draft export 4/4, draft persistence 1/1, Free send 7/7, provider states 9/9, hub unlink 8/8 UI and 2/2 API, shared context 10/10, prior send export/cascade 16/16, recovery/send 10/10, legacy follow-up/backend worker 10/10, legacy UI 2/2, delivery/capability 18/18, provider/correspondence 5/5 and hub detail 5/5. EF model-current and SQLite/MariaDB up/down draft scripts pass; a full blank-chain SQLite apply remains blocked by pre-existing JT-019 drift. Jest open-handle/slow-run behavior is recorded in V-127/V-128/V-130/V-131/V-135/V-142/V-143/V-144/V-150/V-151/V-152.
+- **Test status:** backend 630/630; frontend 50/50 suites and 198/198 tests; Playwright smoke 4/4; npm audit 0 vulnerabilities; production build passes. JOBS-001 provenance backend 1/1 and discovery/import UI 4/4 pass. DEP-001 focused router 24/24; MAIL-001 draft/new-message UI 13/13, draft API/idempotency/rotation 10/10, readable draft export 4/4, draft persistence 1/1, Free send 7/7, provider states 9/9, hub unlink 8/8 UI and 2/2 API, shared context 10/10, prior send export/cascade 16/16, recovery/send 10/10, legacy follow-up/backend worker 10/10, legacy UI 2/2, delivery/capability 18/18, provider/correspondence 5/5 and hub detail 5/5. EF model-current and SQLite/MariaDB up/down draft scripts pass; a full blank-chain SQLite apply remains blocked by pre-existing JT-019 drift. Jest open-handle/slow-run behavior remains 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.
@@ -47,5 +47,6 @@ Updated: 2026-08-10
 - `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/prod-002-ai-evaluation.md`
 - `docs/work-programmes/master-work-plan.md`

docs/work-programmes/master-work-plan.md

@@ -669,9 +669,9 @@ Ordering differences from the suggested list:
 - **Required production verification:** official NAV/safe provider smoke; unavailable providers labeled.
 - **Status:** `IN PROGRESS`.
 - **Blocker:** none for repository inspection and synthetic implementation; official source/browser/production validation remains external.
-- **Evidence:** initial dependency and source-provenance inventory begins at V-154.
+- **Evidence:** `docs/verification/jobs-001-job-discovery.md`; V-154. Verified NAV source name/key, searched acquisition type, request retrieval timestamp, explicit `applicationDue` mapping and reviewed import-source persistence; focused backend 1/1, UI 4/4, backend 630/630, frontend 198/198 and production build pass.
-- **Commit:** none yet.
+- **Commit:** `511a9f6` (honest NAV discovery provenance and import-preservation regression).
-- **Remaining work:** re-read Phase 4, reproduce current discovery/import behavior, inventory source provenance and implement the smallest evidence-backed increment.
+- **Remaining work:** improve submitted-search loading/empty/error/retry behavior, sorting and assessment scanability without inventing missing work-mode data; then perform required browser, live NAV and production gates. Add source filtering only when more than one real source is available.
 
 ### JOBS-002 — Applications table and embedded workspace
 

docs/work-programmes/session-handoff.md

@@ -2,17 +2,17 @@
 
 Updated: 2026-08-10
 
-- **Exact current task:** JOBS-001 — re-read Phase 4 and reproduce current job discovery/source/import behavior before choosing the first change.
+- **Exact current task:** JOBS-001 — improve submitted-search state, sorting and assessment scanability after the verified provenance increment.
-- **Last completed step:** MAIL-001 repository inventory found no safe remaining provider mutation without new consent/scopes; MAIL moved to `IMPLEMENTED — NOT VERIFIED` and JOBS-001 became the sole `IN PROGRESS` item.
+- **Last completed step:** committed and pushed `511a9f6`, which exposes honest NAV source/acquisition/retrieval/deadline metadata and verifies source/country preservation through the reviewed create-job request.
-- **Files currently modified:** authoritative MAIL-001 tracking/evidence only; persistence/export/API code is committed.
+- **Files currently modified:** authoritative JOBS-001 tracking, decision and verification evidence only; application/test code is committed.
-- **Commands already run:** dependency/audit/router/full frontend/build; legacy follow-up/export/recovery/provider suites; full backend; Gitea run inspection; Playwright; MAIL context/unlink/provider-state/Free-policy/draft-persistence focused and full suites/build; EF model-current and dual-provider up/down scripts. See V-126–V-146.
+- **Commands already run:** Phase 4/source/import trace; focused discovery backend test; focused discovery/quick-capture UI tests; full backend/frontend; production frontend build; diff review. See V-154 and prior records.
-- **Test results:** npm audit 0 vulnerabilities; Gitea pull-request CI PASS in 4m20s at run 609; backend 625/625; frontend 50/50 suites and 194/194 tests; Playwright 4/4; production build passes. Draft isolation/cascade 1/1; EF model current; SQLite/MariaDB draft up/down scripts pass. Full blank-chain SQLite apply fails earlier in `AddJobEntityAndProspectStages` on missing `LastReminderEmailSentAt` (JT-019).
+- **Test results:** npm audit 0 vulnerabilities; Gitea pull-request run 609 previously passed; backend 630/630; frontend 50/50 suites and 198/198 tests; JOBS focused backend 1/1 and UI 4/4; Playwright 4/4 from DEP-001; production build passes. Jest retains its known force-exit/open-handle warning.
 - **Services currently running:** none on task-owned ports 3000/5202. Playwright stopped its disposable API/Next servers. Pre-existing Docker services were not changed.
 - **Temporary files or processes:** no task-owned process is running and the failed disposable migration database was removed. Existing synthetic browser evidence/account and startup-created local backup remain documented. No provider account, real email, private content, paid service or production service was accessed.
 - **Production changes currently active:** none. No deployment, migration, provider connection/sync/send or production payload occurred.
 - **Rollback status:** downgrade `20260810080858_AddEmailDraftClientRequestId`, then `20260810075206_AddEmailDrafts`, before reverting draft commits; then follow the existing MAIL rollback order (`ee5ef7e`, `449faeb`, `123fc55`/`e9937ac`, ledger downgrade before `653f011`). No production migration/deploy/provider grant occurred.
-- **Uncommitted changes:** tracking/decision/evidence for MAIL closure and V-153 only; commit and push before JOBS implementation.
+- **Uncommitted changes:** JOBS-001 tracking/decision/evidence for V-154 only; commit and push before the next implementation increment.
 - **Known failures:** live deployment is not verified because PR deploy is intentionally skipped and the active branch is not approved for merge. Draft export/API/UI, full thread/category actions and non-Gmail review remain; existing accounts need re-consent and IMAP stays read-only. A clean full-chain SQLite apply fails in the pre-existing JT-019 migration before the new draft migration. Browser/provider/MariaDB/production unavailable or unverified; recovery scan performance is unmeasured at large ledger scale; Jest open handles; SEC-006 parser dependency work is still separately gated; parser isolation remains SEC-007.
-- **Exact next action:** read `docs/todo/work.md` Phase 4 and inspect `JobDiscoveryPage`, discovery DTO/API/source adapters/import path and tests; reproduce source/filter/import behavior with mocks before editing.
+- **Exact next action:** add an explicit not-yet-searched versus no-results state, bounded client sort and retry behavior to `JobDiscoveryPage`, with loading/error/empty/sort tests; do not add a one-option source filter or infer work mode.
-- **Work that can continue independently:** remaining MAIL-001 repository work and later UX packages. SEC-006/007 await package-index permission; PROD-001/003/004 await production access.
+- **Work that can continue independently:** remaining JOBS-001 repository UX/tests and later UX packages. MAIL provider mutations await scopes/re-consent; SEC-006/007 await package-index permission; PROD-001/003/004 await production access.
 - **Decisions still required from the user:** none for synthetic/code-inspected repository work. Any provider connection or send test, internet/package upgrades, private data, external/paid providers and production actions retain explicit approval/safety gates; SEC-009 retention/legal policy remains unresolved.