Oko/Docs

Command reference

oko defects completion

Declares or replaces the complete-repair measure on a historical defect, including a class previously called repaired by one commit.

Invocation#

Command
oko defects completion <id> (--criterion RESULT | --class --probe-program PROGRAM --probe-scope TEXT --probe-format lines|json --probe-arg ARG...) [--probe-pointer /PATH] [--json]

Inputs and options#

  • The same criterion or inventory declaration as `record`. The inventory must receive {revision}; each successful output row names a still-present instance. `--probe-format json` also requires --probe-pointer to an array of strings.

Output and state effect#

  • Rechecks any earlier repair or claim at its own revision. An empty successful class inventory on main qualifies the claim; a failed probe, remaining instances or missing evidence leaves it claimed and open, with the revision and diagnostic retained. An old off-main repair migrates to a claim. `show`, `list --counts` and Desktop expose it; `list --unrepaired` includes it.
  • Example for a product that commits its class inventory: `oko defects completion <id> --class --probe-program git --probe-scope 'committed product inventory' --probe-format lines --probe-arg show --probe-arg '{revision}:inventory.txt'`. Each line of that committed file is an unresolved instance; an empty file is a complete sweep. A failed inventory command does not mean zero.

Refusals and safe exits#

  • A missing class probe, criterion, scope, program, revision argument, JSON pointer or invalid output format names what to declare. If a repair or closing revision changes during the measurement, the command refuses without writing a stale result.

CLI reference#