Harden Lumin operation reconciliation

[silverstein]

Summary

• require a content-bound acknowledgement of the durable one-use claim before Lumin request entry
• distinguish terminal unreconcilable outcomes from retry-safe status and artifact reads
• preserve consumed authority when an outcome was not retained, without allowing another create attempt
• recover crash-orphaned staging safely through private quarantine with exact file, link, owner, and time checks
• enforce same-user ownership through the effective POSIX uid
• keep source and packaged-share implementations byte-identical
• keep all Lumin lifecycle modules internal and unregistered

Verification

• exact implementation commit: a8b04ff4b43376d27efc14e9c2547d4b5220a975
• independent adversarial review: GO, no P0, P1, or P2 findings
• focused and adjoining VM tests: 137/137
• focused and adjoining macOS tests: 137/137
• full macOS Vitest inventory with one worker: 180 files passed, 2,929 tests passed, 107 intentional skips
• macOS native partition: 62 passed, 9 intentional skips
• reproducible MCPB build: 068bca3ac896534bf5e3e85f0334dc2b21238b1f6028ac14fabdf406c0365dee, 74,447,961 bytes, 3,036 files
• packaged macOS arm64 smoke: 51 tools, 14 prompts, native raster rendering, verified extraction workspace
• source and share lifecycle files are byte-identical

The first unconstrained aggregate Vitest process was killed by macOS resource pressure near completion. The exact same commit then passed the complete 3,036-test inventory with one worker.

Boundaries

This is internal lifecycle hardening only. It does not register a public Lumin tool, read production credentials, call Lumin, create or sign a request, alter external data, publish a release, or make a public capability claim. Polling remains the current public PKCE reconciliation path. Webhook verification remains future-server-only because Lumin app webhooks require a private server application.