StarLedger v1.0.0-beta.3 — #207 5b outcome-contract hardening

Third public beta — the maintenance / freeze checkpoint. Narrowly closes the last deferred item of #207, item 5b (circuit-breaker outcome classification), at the contract level. No change to public data, annotation/meta byte contracts, or executor behaviour; no new runtime subsystem.

#207 item 5b — terminal outcome contract (a classification fix, NOT a new feature)

• plan_summary gains a required deferred_terminal count — a tally of repos skipped as terminally-unavailable (skip-terminal), exactly parallel to the existing deferred_retry. A terminally-unavailable repo's zero-job residual is now machine-readable and can never collapse into the success-like drained-at-base.
• The owner-run P3 completion gate gains a second, independent fail-closed assertion (deferred_terminal === 0) beside the empty_reason precedence, and fails closed on a manifest predating the field.
• No circuit breaker, terminal-state writer, retry engine, or scheduler was added. Both the retry-backoff and terminal failure-bookkeeping paths remain dormant: no runtime code originates attempts > 0 or terminal_unavailable = true (the planner only carries prior state forward). This is forward-compatible scaffolding, so that if such a writer is ever built — or state is seeded externally — its page-the-operator residual is already classified and gated, never mistaken for a drained backlog. The empty_reason enum is unchanged.
• Labeled defensive-contract falsification tests pin the terminal residual at both the planner and the gate; the dormant / no-write-path status is documented consistently across schema, runtime, and the routine spec.

Reviewed across two independent model families (grok-4.7 + gpt-5.6-sol + gpt-5.6-luna); full CI green. Prerelease; tag points at this repository's own canonical main.