Submit a Launch v1.6.0

Version 1.6.0 adds the generic Application V3.1 protected draft intake. Complete no-market, tradable, hook, token,
app, game, service, and hybrid projects can use one project-agnostic contract without a project-type or capability
allowlist.

What changed

• Added the central public-pr-application-v3 contract version 3.1.0 and its closed JSON Schema.
• Added add-only revision packages under
  submissions/<application-id>/v3/revisions/<positive-decimal-revision>/.
• Added protected-base validation for bounded canonical data, exact Git and applicant identity, immutable lineage,
  source closure, evidence bindings, package digests, and public-data safety without executing applicant code.
• Preserved novel capability evidence through pinned source records and additional review records instead of filtering
  projects through a category allowlist.
• Made legacy Fee V2 bindings conditional. Projects that did not select Fee V2 use the explicit not-selected state
  and an all-null fee tuple without fabricated fee artifacts.

Compatibility and authority

Legacy V2 and hidden Workflow Canary intake remain separate supported transports. V3.1 does not rewrite their bytes,
move their pull requests, inherit their status, or satisfy Canary or Website eligibility.

A valid V3.1 package is only an official draft eligible for review. Validation does not mean the project has been
reviewed, accepted, approved, audited, deployed, listed, made available, launched, or authorized to handle funds.
Registry promotion and every production fact remain separately evidenced maintainer actions.

Verify locally

Use Node.js 24 or newer:

npm ci --ignore-scripts
npm test