From 6f07fb9edf58dce67a02ab31a49e36f27a71681b Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Wed, 4 Nov 2026 10:49:08 -0500 Subject: [PATCH 1/2] docs(loop-lane): cite owner decision Q-host-run on the host-run row Co-Authored-By: Claude Opus 5.5 --- docs/contracts/loop-lane/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contracts/loop-lane/README.md b/docs/contracts/loop-lane/README.md index 0ccf88d4ab2..46486277889 100644 --- a/docs/contracts/loop-lane/README.md +++ b/docs/contracts/loop-lane/README.md @@ -419,7 +419,7 @@ Three labels take work off the unattended path, and each means one thing (owner |---|---|---| | human-gated role label (`needs-human`) | An owner decision: one of the reasons above | A listed human, by answering | | `attended` | The owner must be present: a manual step on external state an agent cannot safely run or test, of a class [`pr-pipeline.yaml`](../../conventions/pr-pipeline.yaml) `attended.classes` lists, such as a DNS or registrar change, a cloud resource outside an IaC repository's preview and deploy flow, a new key or secret, an elevated pass, or a network registration. It asks no decision | Only a listed human, once the step is done | -| `host-run` | Work an agent run or builder session on a host takes, which the issue lane cannot make: an unattended host run, or a change to a path the lane cannot push | Removed, with `agent-ready` added again, to hand the work back to the lane | +| `host-run` | Work an agent run or builder session on a host takes, which the issue lane cannot make: an unattended host run, or a change to a path the lane cannot push. Builder items are worked one at a time: interview, plan, implement (owner decision Q-host-run, 2026-11-04) | Removed, with `agent-ready` added again, to hand the work back to the lane | `needs-session` is the session-builder queue, not an owner stop: a pr-unblock stop on a change the lane cannot make (a protected path, a weakened required check, a check the `fix-ci` rung-up could From 053d4bb20698b0f71b3e421b70ee415f5dede576 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Wed, 4 Nov 2026 11:02:15 -0500 Subject: [PATCH 2/2] docs(loop-lane): record the host-run builder rule as contract 18.1.0 Co-Authored-By: Claude Opus 5.5 --- docs/contracts/loop-lane/CHANGELOG.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/contracts/loop-lane/CHANGELOG.md b/docs/contracts/loop-lane/CHANGELOG.md index 10b4a3207ed..8752edaf4d1 100644 --- a/docs/contracts/loop-lane/CHANGELOG.md +++ b/docs/contracts/loop-lane/CHANGELOG.md @@ -5,6 +5,15 @@ topology, the escalation contract, the capability-tier vocabulary, or any loop-l major bump, and additive guidance is a minor bump. A new model release re-audits the capability-tier table (§3); drift found by that audit is recorded here. +## [18.1.0] - 2026-11-04 + +Minor: additive guidance. + +- **`host-run` covers builder work, one item at a time.** The label marks work an agent run or a + builder session on a host takes, a change to a path the issue lane cannot push included + (#13261). Builder items are worked one at a time: interview, plan, implement (owner decision + Q-host-run, 2026-11-04). + ## [18.0.0] - 2026-11-04 Major: the escalation contract changes (§2).