feat(triage): stamp current prompt provenance as v3

[Chris0Jeky]

Problem

The capture-date prompt semantics changed, while provider-backed triage records still used llm-triage.v2. That made current and historical provenance indistinguishable.

Change

• Stamp every current provider-backed triage outcome, including deliberate empty extraction, as llm-triage.v3.
• Preserve explicit v2 parse, validate, serialize, schema, fixture, and frontend-classification support for stored history.
• Add the strict v3 schema with the existing v2 JSON shape, and require v3 in current packaged Windows evidence.
• Correct the archive-contract test command so it runs from scripts/ci, where its local harness is importable.

Validation

• dotnet test backend/Taskdeck.sln -c Release -m:1 (green: 8,973 passed; 5 expected skips)
• npm run typecheck, npm run build, and npx vitest run --maxWorkers=2 with VITE_API_BASE_URL removed (379 files, 6,119 passed, 3 skipped)
• Focused contract/API checks, archive contract tests (49 passed), and doc links (663 files) passed.

Not verified

• A real packaged Windows/OpenAI acceptance journey and hosted CI were not run. The packaged journey remains release-proof work.

Refs #2211

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-07T22:41:58.917982Z	8e7fd25	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Chris0Jeky]

Coordinator cleanup: author/reviewer released head 8e7fd25, tracked tree was clean and remote matched. Ignored inventory contained only disposable backend bin/obj, frontend dist/node_modules, and Python pycache; no evidence/runtime files required copying. Worktree removed normally without force. Full-suite counts and direct exit-status evidence remain in the PR; hosted packaged/live-provider acceptance is still unverified.

[Chris0Jeky]

Control-plane review correction (2026-09-08): I merged PR #2787 at 0cebd93 after independent Terra review and green hosted checks, but missed the ADR-0066 amendment's maintainer-review requirement. The September 6 SC-10 delegation named twelve PRs and did not include this one. This was my error; no acknowledgement or post-hoc approval is inferred. The change includes the Windows archive acceptance script and tests alongside the atomic prompt-v3 producer/frontend/docs update. Validation remains recorded on the PR; a live packaged Windows/OpenAI run was not claimed.

Please review #2787 post hoc. I have preserved the merged work and recorded the open checkpoint in OUTSTANDING_TASKS.md via PR #2791. New CI-control PRs #2791 and the #2335 test slice will complete independent review and exact-head hosted checks, then remain open pending your review. No settings, release, or selective-execution approval is inferred.