debugsolid

# debug Select this owning procedure for a root-cause investigation, whether requested in plain language or through `/debug`. The command spelling is not a prerequisite. Investigation and implementation remain separate: this procedure never changes code. It closes the reproduce, evidence, and regression-test handoff loop through `/fix`. ## Entry boundaries - A known bug with a named regression test belongs to `/fix` directly. - A design discussion without failing behavior belongs to `/adr`; attribution is still required before authoring an ADR. New behavior belongs to `/feature`. - An explanation-only question stays in the non-mutating question-answer path; it does not require a debug invocation or a command spelled by the user. - Do not re-enter from an active `/fix` or `/adr` invocation. Complete that invocation before a separate investigation; do not create a routing cycle. - The phase gates below own symptom precision, evidence, and the one named exit. A no-action close uses the board helper in Phase 5, never a direct file append. ## Pre-flight Read these, or STOP and surface the gap — never guess a log path, trace tool, or test runner: - `<project-root>/.codearbiter/tech-stack.md` — log paths, trace tooling, test runner conventions. The evidence sources. - `<project-root>/.codearbiter/CONTEXT.md` — domain vocabulary, system structure, and the `stage:` frontmatter (the maturity value; higher demands more rigorous evidence before exit). - `<project-root>/.cod