Bug triage
Declares Essentials/Agent/bug-triage standing: the ONE agent on the ONE global bug queue (Essentials/BugTriage).
- Agent path: Essentials/Agent/bug-triage
- Purpose: Works each defect from red to verified in production in one permanent thread — diagnoses, fixes with a test, proposes the merge, follows the deploy and proves the fix on the target instance.
- Triggers: A classified bug recorded by the pooled inbox (Hosting/PlatformBuilds/_Inbox) — an issue opened or filed with `bug` + one `sev:` by a member or a fleet bot, including the triage agent's own FileIssue coming back through the organisation webhook, Triage's LabelIssue classifying an opened issue as a bug, A reopened bug issue — a new round on the same thread, A red `main` (a signed ci-failure event) whose triage verdict is `content` or `platform` — Dispatch hands the run to ONE worker per repository's red episode; later red runs join it; `transient` gets its single re-run and no worker, A feedback whose triage verdict is `defect` — filed as a bug issue, which gets the worker when it comes back through the organisation webhook (held when it was submitted outside the trusted instances), The estate's Dispatch (Hosting/BugFix, BugFixPool) — every 10 minutes it re-drives each open bug thread at rest, restarts a round that died with its process, and starts queued bugs
- Runs on: the control instance
- Wired: yes
- Ledger path: Hosting/Triage/Status
- Activity fields: lastBugThreadStartedAt, lastBugRedriveAt, lastBugPoolAt
- Queue path: Hosting/Triage
- Thread namespace: Hosting/Triage/_Thread
- Doc path: Essentials/BugTriage
- Note: One thread per defect at Hosting/Triage/_Thread/bug-{repo}-{number}, recorded on the issue's item as bugThreadPath (TriageIntake.EnsureBugThread). The estate's pool (Hosting/BugFix) spreads bugs over model variants (EU-routed and served, at most N open each — policy bug-fix-eu-only: with none served, a bug stays queued and no round runs on any other model) and re-drives every open thread at rest — one step per round, never one long round. A red main's worker is at Hosting/Triage/_Thread/ci-{repo}-{ledger issue}, recorded on the red run's item; every item records its workKind (bug · ci-failure · feedback) and the model the pool's table chose for its kind and difficulty (workModel, workModelReason, workRung). Hosting/Agent/triage still classifies and files; a stranger's issue, and a feedback defect from outside the trusted instances, is never handed to this agent. The comparison of the variants is the Comparison area of Hosting/BugFix.