Submit a Launch v1.8.0

Submit a Launch v1.8.0

Version 1.8.0 adds Universal Admission V1 as one project-agnostic Applicant admission protocol for hooks, tokens,
apps, games, services, hybrids, no-market projects, and novel designs without a project-type or capability allowlist.

What changed

• Added one bounded public Submission V2 admission envelope that preserves unknown capabilities as analysis-pending
  instead of rejecting a project because its category is unfamiliar.
• Separated semantic admission from transport authentication, replay protection, quotas, leases, fencing, retry,
  dead-letter retention, snapshots, and garbage collection.
• Added authenticated command and event receipts plus an owner-private, single-host SQLite reference implementation
  with store-conformance, recovery, integrity, and adversarial tests.
• Published an exact, digest-bound Universal Admission discovery contract covering the closed schemas and reference
  runtime while keeping the existing Application V3.1 GitHub Draft intake and launch policy unchanged.
• Documented that launch-route requirements, including the disabled Programmable production profile, are not universal
  Applicant admission requirements.

Authority boundary

The Universal Admission contract remains reference-only-disabled: its endpoint, audience, and trust snapshot are
unset; every authority flag is false; and the SQLite adapter is not a distributed production service. Admission does
not grant review, acceptance, approval, audit, deployment, discovery, routing, funds, safety, or launch authority.

Verify locally

Use Node.js 24.12 or newer:

npm ci --ignore-scripts
npm test