Tier-1 supported surface

This is the Tier-1 list for CLI package trust remediation (release contracts and tests). Only these workflows are candidates for release blocking and tight docs accuracy until explicitly expanded.

Commercial / marketing Tier‑1 (merge-signal wedge) is narrower: Next.js App Router + GitHub PRs + shipgate next — see the repo’s supported-matrix.md and support-levels.md. Do not use this page alone to justify enterprise positioning for verify / gate as the same product promise as shipgate next.

Everything else in shipgate --help is best-effort: it may be useful, but it is not held to the same bar for docs accuracy and contract tests.

Tier-1 matrix

Workflow	Command(s)	What “green” means	Contract tests (shipgate package)
ISL parse / typecheck	shipgate check [files...]	Exit 0; specs parse and typecheck	spec.test.ts, linter.test.ts, smoke.test.ts
Verify implementation	shipgate verify <path>	Exit 0 when result.success	verify.test.ts, smoke.test.ts, e2e*.test.ts
Spec gate (SHIP/NO_SHIP)	shipgate gate <spec> -i <impl>	Exit from getGateExitCode(result) (typically 0 = SHIP, 1 = NO_SHIP)	smoke.test.ts, e2e*.test.ts (integration coverage)
Next.js App Router gate	shipgate next [path]	Exit 0 when result.success; optional golden-path artifacts	next-gate.test.ts, next-golden-evidence-schema.test.ts
Packaging / npm tarball	(release process)	Tarball includes dist/cli.cjs, schemas/, declared package.json files	packaging.test.ts
Consumer install smoke	GitHub Action	pnpm install + shipgate build → npm pack → clean npm install tarball → next + gate on tests/fixtures	.github/workflows/shipgate-consumer-smoke.yml (also Run workflow / workflow_dispatch)
CLI surface manifest	(regression)	Commander registrations match snapshot	cli-contract.test.ts — when adding/removing commands, update snapshots: pnpm exec vitest run tests/cli-contract.test.ts -u (review diff in PR)

Not Tier-1 (examples)

These remain best-effort until promoted with tests + docs:

• shipgate go, shipgate vibe, shipgate scan — often depend on AI keys, network, or heuristics.
• Most nested commands under gen, packs, proof, compliance, auth, etc.
• ShipGate monorepo: required Tier‑1 shipgate next jobs cover two internal Next roots today (see dogfooding-status.md); the multi-app shipgate-next-all sweep is not the same as those required checks.

Promoting a command to Tier-1

1. Add or extend automated tests in packages/cli/tests/ (or consumer fixture job) that assert exit codes and stable outputs.
2. Add a CLI reference page (or extend an existing one) on this docs site.
3. Update this matrix and the exit codes page.
4. Record the change in shipgate CHANGELOG under [Unreleased] / release notes.

Related

• Reliability contract — guarantees vs non-guarantees
• Exit codes — Tier-1 exit behavior
• Internal: docs/internal/TRUST_CRACK_REGISTER.md — full trust crack register