P2: Prove managed semantic artifacts and offline runtime provenance

[tomdps]

Parent

Tracking parent #251; epic #243. This is one vertical delivery slice. Do not close or bypass the parent tracker from this child.

Goal

Bind each managed Python semantic artifact from source revision through packaged checksum and offline installed launch, with no ambient fallback.

Dependency contract

• P1 — Add truthful Python LSP semantic inspection and navigation #248
• P2: Make Python setup dry-run-first, exact, reversible, and manager-aware #270 (P2: Make Python setup dry-run-first, exact, reversible, and manager-aware)

Required behavior

1. Map descriptor artifact reference to per-platform package/file, checksum, license/source revision/build recipe, installed path, version/protocol launch, and runtime capability row.
2. Resolve only declared packaged/acquired artifacts; missing/corrupt/wrong-version/unsupported targets degrade explicitly with no PATH, sibling checkout, workspace build, current-tool, or hidden download fallback.
3. Separate explicit approved acquisition/setup from validation. Instrument offline validation so package-manager/install/network activity is undeclared and fails the receipt.
4. Update managed/ASP descriptors, package staging/packlists, provenance/license validators, installed smoke, and negative fixtures together without granting ASP host authority.
5. Maintainer/subagent-owned. Do not launch Zeroshot unless the user explicitly re-delegates this slice after its JIT review.

Acceptance criteria

• Present/verified/launchable, absent, checksum mismatch, source/license missing, unsupported target, crash/protocol mismatch, timeout, and offline cases map to exact ledger rows.
• Installed binary/file hash and launch transcript bind to the packed tarball and declared source revision.
• Validation process ledger contains only declared interpreter/checker/test/semantic commands and no acquisition/install/network path.

Observable outcomes

• Clean success carries positive execution/provenance evidence; zero diagnostics alone is never proof.
• Findings and every unavailable/invalid/timeout/crash/resource/stale/unsupported state are machine-readable and fail or degrade exactly as the capability contract says.
• No implicit fallback, partial result, or skipped execution is reported as a pass.
• Target source, configuration, lockfiles, environments, and caches remain unchanged except where this issue explicitly owns a validation-gated atomic edit; every temporary resource/process is cleaned.

Non-goals

• installing a project language server
• public readiness text
• OS matrix aggregation
• new ASP authority

Verification

Run focused behavior first, then the configured repository proof only after the acceptance matrix works:

• npm run build
• npm run pack:check
• npm run provenance:check
• managed artifact/descriptor/negative installed tests
• Attach exact real-tool/artifact versions, argv/config/cwd/source, normalized result examples, before/after cleanliness evidence, and packed-install proof where the slice changes public package behavior.

Execution rule

Implement only after a just-in-time review against current dev. Keep exactly one implementation run active. PR base is dev; require green checks, clean scoped diff, merged PR, closed child, parent checklist update, focused reproductions, and opcore-ci proof before starting the next child. Do not claim Python readiness/parity, ASP authority, old-tool replacement, security/SAST, all-stack support, automatic fixes, or a blended score.