Admit capacity-only user project preflight

[8Dionysus]

Problem

The storage preflight path treated ordinary user-owned project capacity as if it needed per-task host write orchestration. That made a capacity-only check depend on route orchestration and obscured the boundary between accounting and filesystem mutation.

Result

The source path now admits ordinary user project capacity through the shared reservation ledger while retaining a capacity-only boundary: the route records ownership and available capacity, but does not grant write permission or cleanup authority. Runtime errors still fail the gate, Vault archive handling remains separate, and the existing coverage and forecast paths stay intact.

The change is limited to the storage reservation/planning contract, CLI projection, public command contract, generated ABI, and focused tests.

Validation

• Focused owner tests: 140 passed.
• Owner validation graph instant contract check: passed with the pinned aoa-sdk source.
• Compile, diff, ABI, manifest, public-boundary, scaffold, and release checks: passed.
• Shared default ledger proof: real 1 MiB acquire/release against the ToS source-witness target on dev 66312; release succeeded and no payload was written.
• Signed artifact trust loop: public_source_seed sidecars built; ABI control verified; durable isolated registry promotion succeeded; exact record/subject/source/ref/host_managed/agent trust gate returned allow with no blockers, warnings, or manual review.

Delivery boundary

The artifact receipt is recorded in work/automatic-capacity-artifact-delivery-20260907.json. Installed delivery remains code-only and is gated on merged source parity; it does not expand policy, add owner-write routes, or claim public release trust.