v0.9: Stage 1 Verify — runtime/verify + audit recorder + lifectl info/run wiring (#121)

[devin-ai-integration]

Summary

Second PR of the v0.9 epic (#119). Implements the seven sub-steps of docs/LIFE_RUNTIME_STANDARD.md §2.1–§2.5 + v0.8 Part B §B.1 row 1 (lifecycle gate / withdrawal pre-flight / audit-chain integrity). Stage gating is fail-close (D6): any sub-step failure aborts Stage 1, emits assembly_aborted{stage="verify", reason}, and refuses to mount.

Closes #121.

What landed

• runtime/verify/ modules — one per sub-step:
  • _structural.py (§2.1: zip safe-open + path-traversal rejection + descriptor parse)
  • _schema.py (§2.1 cont.: life-package.schema.json re-validation + binding-spec §7 forbidden_uses namespace check; x- extensions accepted as advisory, unknown non-x- keys fail-close)
  • _time.py (§2.2: created_at not in future / expires_at not past / expires_at > created_at, with 30s clock-skew tolerance)
  • _inventory.py (§2.3: per-entry sha256 + size match, plus rejection of any zip entry not in contents[])
  • _audit_chain.py (§2.4: v0.4 hash-chain prev_hash walk + canonical re-hash of every event + audit_event_ref resolves to a package_emitted event whose metadata.package_id matches)
  • _consent.py (§2.5: in-archive consent_evidence_ref readability + HTTP GET of withdrawal_endpoint with 4xx/5xx/network-failure rejection + status:"withdrawn" rejection)
  • _lifecycle.py (Part B §B.1 row 1: withdrawn and tainted states refused; absent lifecycle/lifecycle.json treated as active for pre-v0.8 packages, with a warning)
• runtime/verify/__init__.py — public verify(life_path, *, audit, withdrawal_policy) -> VerifyResult entry point. Always returns a VerifyResult (with package_id, lifecycle_state, audit_chain_length, inventory_entries_verified, errors[], warnings[]) so the caller can present a structured rejection reason — no opaque "Failed to load".
• runtime/audit/recorder.py — minimal in-memory AuditRecorder used by Stages 1–4 until v0.9 sub-issue v0.9 sub-issue #6: Stage 5 Guard (withdrawal / lifecycle / expiry watchers + clean teardown + audit emitter) #125 ships the full v0.4 hash-chain emitter that links the runtime's session log back to the bundled audit/events.jsonl. Records mount_attempted, withdrawal_poll, assembly_aborted{stage="verify"} events.
• runtime/cli/lifectl.py — info and run wired:
  • lifectl info <pkg> prints a structured §2.1–§2.5 + lifecycle report (human-readable by default, JSON via --json); exit 0 on PASS / 1 on FAIL.
  • lifectl run <pkg> runs Stage 1; on PASS exits 2 with Stage 2+ pending sub-issues #122-#126 to stderr; on FAIL exits 1.
  • Both subcommands accept --withdrawal-mock {not-revoked|revoked|unreachable|malformed} for test-only short-circuit of the §2.5 HTTP poll. Production runtimes MUST omit this flag — spec mandates a real HTTP GET per §2.5.
• tools/test_runtime_verify.py — 15 sanity-test cases:
  • Happy path with a real local http.server driving the §2.5 urllib.request.urlopen end-to-end
  • Negative fixtures constructed by mutating a freshly-built .life zip (_rebuild_zip_with): bad zip / missing descriptor / inventory hash mismatch / unlisted entry / audit chain break / expired package / lifecycle=withdrawn
  • Withdrawal endpoint returning HTTP 403, returning status:"withdrawn", or being unreachable (port-rebind trick)
  • assembly_aborted audit event emission
  • CLI surface: lifectl info exit 0 + PASS print, --json structured errors, lifectl run exit 2 with Stage 1 ✓
• .github/workflows/validate.yml — runtime-scaffold job now runs both v0.9 sub-issue #1: runtime/ package scaffold + lifectl CLI entrypoint #120 + v0.9 sub-issue #2: Stage 1 Verify (zip / schema / time / identity / integrity / audit chain / consent / withdrawal pre-flight / lifecycle gate) #121 test drivers, installs tools/requirements.txt so jsonschema is available.
• CHANGELOG.md + runtime/README.md — sub-issue v0.9 sub-issue #2: Stage 1 Verify (zip / schema / time / identity / integrity / audit chain / consent / withdrawal pre-flight / lifecycle gate) #121 entry; Quickstart refreshed for the new info/run surface.

Hard-rule invariants enforced for Stage 1

• D6 = fail-close — any sub-step failure aborts Stage 1, emits assembly_aborted{stage="verify", reason}, and the runtime refuses to proceed (no degraded mount).
• §2.5 withdrawal pre-flight — 4xx, 5xx, network failures, malformed bodies, and status:"withdrawn" all reject the mount.
• Lifecycle gate — withdrawn and tainted packages refused; frozen (memorial) flagged for read-only enforcement at sub-issue v0.9 sub-issue #6: Stage 5 Guard (withdrawal / lifecycle / expiry watchers + clean teardown + audit emitter) #125 (Stage 5 Guard).

Review & Testing Checklist for Human

(Risk: yellow — first stage with real assembly logic, but every sub-step is covered by both Python unit tests and a CLI subprocess test. CI is the primary gate.)

• CI runtime-scaffold job passes on both py3.11 and py3.12.
• Smoke test on the bundled fixture:

  pip install -e .
  lifectl info examples/minimal-life-package/out/*.life --withdrawal-mock not-revoked
  

  should print verification: PASS and exit 0.
• --json output is parsable (lifectl info <pkg> --withdrawal-mock revoked --json | jq).
• lifectl run <pkg> --withdrawal-mock not-revoked prints Stage 1 Verify ✓ + the package metadata, then exits 2 with Stage 2+ pending sub-issues #122-#126 to stderr.

Notes

• This PR intentionally does NOT yet exercise Stage 2 (Resolve), so lifectl run always stops with the "Stage 2+ pending" message after Stage 1 PASS. Stages 2–5 land in v0.9 sub-issue #3: Stage 2 Resolve (Provider Registry + LifeCapabilityProvider + tier-aware resolution + bundled refusal) #122–v0.9 sub-issue #6: Stage 5 Guard (withdrawal / lifecycle / expiry watchers + clean teardown + audit emitter) #125; the e2e echo Provider in v0.9 sub-issue #7: Built-in echo Provider + end-to-end conformance harness + Quickstart docs #126.
• The --withdrawal-mock flag is test-only and should be removed (or moved behind a hidden debug entry point) before v1.0. Until then it is the only way for CI / sandboxes without external network access to exercise the §2.5 path deterministically.

Link to Devin session: https://app.devin.ai/sessions/ff7322e18fd94887875daa2c1c75f87d
Requested by: @LING71671

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring