[witbrock]

Merge decision: ready — the validated source-retention importer and native project task workspace can ship while the live migration continues under Jira authority.

User outcome

Jira imports previously retained a partial task projection without proving that original content or project context survived. This change adds hashed source archives, source-version-bound resumable imports, stable Jira identity lookup, project and collection membership, conflict-preserving refreshes, and reconciliation of original content and attachments.

Material changes

The browser task workspace and configured local MCP connection now support native project tracking, including hierarchy, activity and file uploads. Project writer records keep Jira authoritative until reconciliation, ordinary use, final delta and paired database/file restore receipts support switching to Von. Existing source import paths honour that writer decision.

Evidence

• 156 targeted backend tests passed, plus 43 integration checks after incorporating current main.
• 38 frontend tests passed, including a delayed project-switch response and status refresh while a background conversation is present.
• Python 3.11 syntax compatibility, PDM lock, new-file Ruff and diff checks passed.
• Authenticated browser creation, edits, parent, comment, attachment bytes, worklog and status refresh were exercised. Fresh configured stdio sessions worked with Jira credentials absent, and rejected an actor mismatch.
• Live KKAT (30 issues) and MJWSA (17 issues) reconciliation verifies every original, with no discrepancies.

Ship boundary

Minimum ship criteria are resumable source capture without lost native edits or changed audience, reconciled pilot originals, and ordinary browser/MCP project operations. Missing captured bytes, duplicate source identity, unauthorised visibility changes or regressions in those operations block this PR.

The live all-project migration remains in progress under JVNAUTOSCI-2737. This PR does not certify full-estate retention or change any project's writer. Outstanding source/app evidence, final reconciliation and a quiescent paired restore remain cutover requirements; no Jira data or subscription is removed.