/bug-fix-thread

Work a defect in its ONE permanent thread from red to verified-in-production — diagnose and conserve the finding (bug.diagnose), write the fix and propose its merge (dev.merge — a human signs), follow the deploy (hosting.roll or module.publish), then prove the fixed behaviour on the target instance (bug.verify — the only thing that closes). What the fixer may and may not do.

• Instructions: You are on a defect's **permanent thread** (`Hosting/Triage/_Thread/{t}`, main node = the `Hosting/TriageItem` or `Hosting/Issue`). The thread outlives you; the item is the record; every step is a governed activity you PROPOSE. The rules are on `Essentials/BugTriage` — one global queue, one agent, one thread per defect. # 0. One step per round — and record where the bug stands A round is capped at 30 minutes; the estate's Dispatch (`Essentials/BugTriage` → "Dispatch") posts the next round when your thread is at rest. So each round does ONE of the steps below and ends by `patch`-ing the item: - `bugPhase` — `diagnosing` · `fixing` · `awaiting-merge` · `awaiting-deploy` · `verifying` · `blocked` · `done`. The pool re-drives an `awaiting-*` bug only every few hours and never a `blocked` one; `done` (after `bug.verify`) stops it. - `diagnosis` when you have one, `pullRequest` (the PR URL) when you open it, `fixSha` when it is merged, `deployedTag` when it is out — the pool measures the variants on these. `blocked` is for what a person must decide or do; say what on the item. What you cannot fix at all you file to bug triage (`/feedback`) and set `blocked` with the reason. Where the pool supervises its workers, two more fields are yours: `workLastFailure` at the end of every fix round (ONE line naming the test or gate that still fails; empty when none does), and `bugPhase: awaiting-merge` when the pull request is ready — which calls the review by a stronger model (`workReview`: `accept` → on to the merge; `redo` → a stronger fixer takes the work, with the findings). Stay inside the brief's `workScopePaths`; a file outside them stops the attempt. # 0a. What you are working — three kinds, one thread shape The item's `workKind` says which: `bug` (a classified bug issue), `feedback` (a defect a user or an agent reported, filed as a bug issue — same steps as a bug) or `ci-failure` (a red `main` whose triage verdict is `content` or `platform`). For a **red `main`*…
• Auto mount: yes
• Launches sub thread: no