comet native is the Native Runtime command entry point. Most users only enter /comet or /comet-native in their Agent; the Skill follows the continuation returned by Runtime.
Command overview
The new Native flow no longer exposes
checkpoint, evidence, or receipt commands; acceptance checks run during Verify and you can re-run them read-only at any time with comet native check. Results are stored in portable state and the user report.
Create and inspect
new creates the brief, Specs, and comet-state.yaml; local execution lives under .comet/runtime/native/. status and show are read-only and do not switch selection as a side effect.
Progress and Verify
next does not accept a self-reported pass. It confirms Shape, accepts or revises a Verify result, retries an allowed Verifier, or accepts the Runtime-defined handoff, check-plan, and Verifier response through --runner-input:
--accept-result, --revise-implementation, and --revise-requirements for the user decision after Verify. --confirmed only confirms Shape or an explicit verifier-unavailable fallback; it does not accept a passing result. When the Verifier is unavailable, the two choices are:
--retry-verifier keeps the current candidate and completed checks and starts a new acceptance attempt. For Supervisor parallel progress, next also accepts --coordination-mode and --max-parallel (default 2); recovery calls can guard stale responses with --expected-state-version / --expected-action.
Use continuation.inputOptions.template from comet native status <name> --details --json as the current input schema. Only the current Verifier can request checks through request-checks; a Builder self-report cannot enter Archive.
Archive
Read the archive-ready continuation, then preview or execute as needed:verification.md, moves the change, and cleans local Runtime; the normal path does not rerun Verify. For branch/worktree isolation, specify the delivery with --finish keep|merge|push|pull-request (the option semantics are described in Archive and delivery). For a capability conflict, choose the serial order first with --serial-first.
Diagnose, migrate, and recover
doctor --repair only performs deterministic migration, transaction finalization, and local overlay rebuild. It does not rewrite requirements, Specs, or code. A missing verification.md does not block Shape/Build recovery; a wrong branch/worktree or mixed active/archive layout pauses and waits for you to resolve it.
The user-readable artifacts are the brief, Specs, comet-state.yaml, and verification.md. .comet/runtime/native/ contains only local state, logs, locks, and transactions.