Oko
Oko/Docs

Command reference

oko defects classes remaining

A class's completion probe: every instance of the shape recorded after all its class's mechanisms were installed, as the install records say, and after the repair's commit, open or closed. One closed on its own repair still came back and is listed; one withdrawn as recorded in error is not.

Invocation#

Command
oko defects classes remaining --shape SHAPE --after REPOSITORY@COMMIT [--json]

Inputs and options#

  • The commit's time is read from Git in the checkout REPOSITORY names.
  • The completion probe measures from the install records: a hook was installed when the Tama hook registry carrying it was written, which every install does whole; a refusal or test since the oldest installation of its product's command line, in the unbroken run up to the current one, whose source revision contains the mechanism's (`stado product status <product> --surface cli`). The first reading that finds every layer standing (`show`, `check`, or the closing gate) keeps that moment as `installedAt`, which the listing shows; a change to a cause or a mechanism clears it.

Output and state effect#

  • Prints `<id> open|closed <product> <found at> <title>` per instance, nothing when none came after, so the probe stays unpassed while any is listed; --json prints `{remaining: [{defect, open}…]}`. The native API answers `classes {verb: "remaining", shape, after}` the same and OkoKit's `remaining(shape:after:)` reads it.

Refusals and safe exits#

  • `--after <value> names no <repository>@<commit>`; a commit Git cannot read refuses with Git's own answer; `git gave <value> a commit time that is not one (…)`.
  • `no class holds the shape "<shape>"; `oko defects classes` lists them`; `class <id> has <landed> of <needed> layer mechanisms landed, so nothing they stop has been measured; `oko defects classes show <short id>` names what each still lacks`; `the mechanisms of class <short id> have not all acted yet: <cause>`, the cause being what the install records say: `the cli installation of <product> Stado records here does not carry <mechanism>`, Stado's own refusal, or why the hook registry's install time cannot be read.

CLI reference#