Writing a bug report

DISRESPEC-SPINE: One fact once. No filler, repeated source material, empty sections, or chat restatement; after successful creation return only clickable artifact links, except for blockers, failed creation, incomplete verification, or irreversible-action confirmation.

Artifact placement

Place the file under ~/.agents/artifacts/<workspace>/, resolving ~ to the absolute home path and deriving <workspace> from the repository or working-directory basename. Keep it out of the repository and carry its absolute path forward. If the workspace name or target path conflicts with unrelated work, stop for a structured human choice; never overwrite. If the root is unwritable, offer grant access and retry, another agent-neutral user directory, or cancel. Never fall back to vendor storage, the repository, or a temporary directory.

A bug report is a defect record, not a remedy: symptom, reproduction, root cause, and the requirement the defect violates. The fix is a separate, later task. The report must preserve enough state that a fixer can rerun the reproduction and evaluate the diagnosis without reconstructing unrecorded conditions. A bug report has these sections: Symptom · Reproduction · Root cause · Affected requirements; do not reinvent them. These rules are conventions backed by review — nothing in this repository enforces them automatically.