You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Lanes skip an issue carrying the session-owned label #17968
A local Claude Code session that files an issue it will work itself cannot keep the software-factory lanes off it. needs-human means an owner decision is needed, so it is the wrong label; attended/unattended say whether a person drives a run, not who owns the work. The owner decided (2026-11-21) on a new label, session-owned: "A local Claude Code session owns this work; factory lanes skip it." It is declared in melodic-software/github-iac#939.
Change
.github/actions/check-born-triaged (routingLabels/routingLabel) treats the binding's session-owned role label (tracker.config.role_labels["session-owned"], default session-owned) as a routing label. That one helper already gates intake triage, the triage sweep, intake re-entry, the WIP cap, check-blockers (the issue lane's admission) and label-unblocked, so all of them skip such an issue.
The work loop's admission gate admits from list-frontier --autonomous (plugins/work-items/tools/work-item-tracker/lib/frontier.sh), which never goes through that step: the autonomous frontier drops an item carrying the session-owned role label. The interactive frontier keeps it, so the owning session can still pick it.
The role is added to the work-items canonical roles (label-taxonomy, schema, binding resolution).
docs/contracts/loop-lane/README.md "Skip an issue" documents the label and when to use it versus the human-gated label.
Acceptance
An issue carrying session-owned (or the binding's remap) gets skip=true from check-born-triaged; one without it does not.
list-frontier --autonomous omits an item carrying the role label; list-frontier keeps it.
Tests cover both, with a remapped label.
Owner decision 2026-11-21. A local session owns this item and works it; lanes should not claim it.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: the born-triaged check, the autonomous frontier in work-item-tracker, the work-items label taxonomy, schema and binding, and the loop-lane README. Every factory lane reads the check.
Reversible: yes; revert the change, and issues already labeled session-owned then go back to lane handling.
Open questions: none
I read this as a request to add a session-owned role label. Factory lanes would skip an issue that carries it, and the autonomous frontier would omit it while the interactive frontier keeps it. The change, the owner decision it cites and the acceptance items are specific, so I am asking nothing further. The admission comment says the body needs confirmed - [ ] acceptance criteria from a listed human, which is separate from this triage. #17969 is related (a filing session marking work session-owned) but asks for a different change, so I did not treat it as a duplicate. I found no merged pull request that already covers this.
Not admitted to the issue lane yet: no trusted-human acceptance criteria: a listed human must put the confirmed - [ ] criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited; intake's refinement of this body is due and may supply them.
melodic-automation-lanes commented on Nov 21, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: Add a session-owned role label that check-born-triaged treats as a routing label and the autonomous frontier drops, with the interactive frontier keeping it, plus roles, docs and tests.
Acceptance criteria
routingLabels in .github/actions/check-born-triaged/check-born-triaged.mjs returns a session-owned label read from tracker.config.role_labels["session-owned"], defaulting to session-owned when absent or empty, and throws on a non-string value like the existing keys
routingLabel returns the session-owned label name when an issue carries it, so check-born-triaged reports skip=true for it and skip=false for an issue without it
A check-born-triaged test passes covering the default and a remapped session-owned label, and ROUTING_DEFAULTS-based assertions in check-born-triaged.test.mjs are updated for the new key
wit_filter_frontier in plugins/work-items/tools/work-item-tracker/lib/frontier.sh with autonomous=true omits an open item carrying the session-owned role label, including a remapped one from the binding
wit_filter_frontier with autonomous=false keeps an item carrying the session-owned label
A frontier test passes covering both modes with a remapped label
The session-owned role is added to the work-items canonical roles: label-taxonomy, schema and binding resolution, with existing role-label tests still passing
docs/contracts/loop-lane/README.md Skip an issue section names the session-owned label and says when to use it versus the human-gated label
Callers of routingLabel (check-wip-cap, intake-reenter, triage-sweep, check-blockers, label-unblocked) still pass their existing tests and receive the session-owned routing value via readRouting
External state: none
Dependencies
melodic-software/github-iac#939 declares the session-owned label in the repository; this change only reads it and does not create it
#17969 (track add marking work session-owned) is a consumer of this label and waits on this issue, not the reverse
.github/actions/check-born-triaged/check-born-triaged.mjs:57-78: ROUTING_DEFAULTS has container and prefix only; routingLabels reads two config keys; routingLabel matches container or prefix
plugins/work-items/tools/work-item-tracker/lib/frontier.sh:33-67: wit_filter_frontier drops container and wayfind items in both modes and human-gated and hold items only when autonomous; no session-owned handling
.github/actions/check-wip-cap/check-wip-cap.mjs:255: consumer of routingLabel
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44930182003, the work-resolve-issue run that agent-ready started, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-21T17:29:32Z. work-unblock has now removed and added agent-ready back to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or the kill-switch wait.
Activity
github-actions commentedon Nov 21, 2026
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: the born-triaged check, the autonomous frontier in work-item-tracker, the work-items label taxonomy, schema and binding, and the loop-lane README. Every factory lane reads the check.
Reversible: yes; revert the change, and issues already labeled
session-ownedthen go back to lane handling.Open questions: none
I read this as a request to add a
session-ownedrole label. Factory lanes would skip an issue that carries it, and the autonomous frontier would omit it while the interactive frontier keeps it. The change, the owner decision it cites and the acceptance items are specific, so I am asking nothing further. The admission comment says the body needs confirmed- [ ]acceptance criteria from a listed human, which is separate from this triage. #17969 is related (a filing session marking worksession-owned) but asks for a different change, so I did not treat it as a duplicate. I found no merged pull request that already covers this.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
Not admitted to the issue lane yet: no trusted-human acceptance criteria: a listed human must put the confirmed
- [ ]criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited; intake's refinement of this body is due and may supply them.melodic-automation-lanes commentedon Nov 21, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: Add a session-owned role label that check-born-triaged treats as a routing label and the autonomous frontier drops, with the interactive frontier keeping it, plus roles, docs and tests.
Acceptance criteria
External state: none
Dependencies
Related work
Sources read
Automated refinement by the lanes App. Intake triages the issue again with it.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"a538e9f5bc53f1f54ea353d603a14938bb2a712827e04f39723fe06d36751df5","body_sha256":"1110817f47288c989d160443187061748fcc7c98c35963c03500517ae02d7f7a"}
melodic-automation-lanes commentedon Nov 21, 2026
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44930182003, the work-resolve-issue run that
agent-readystarted, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-21T17:29:32Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or thekill-switchwait.