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
track add: let a filing session mark work session-owned #17969
/work-items:track add has no way for a session filing work it will do itself to say so. The owner decided (2026-11-21) on a session-owned label for that ("A local Claude Code session owns this work; factory lanes skip it."), declared in melodic-software/github-iac#939; the lanes skip it once the companion claude-code-plugins change lands.
Change
/work-items:track add gets an ownership choice: --session-owned applies the session-owned role label, resolved from the tracker binding (config.role_labels["session-owned"], default session-owned) the way the human-gated role label is. It cannot be combined with --agent-ready, and an item filed this way skips the needs-triage floor, since intake would not see it.
Acceptance
track add --session-owned files the item with the resolved role label and without the needs-triage floor.
--session-owned with --agent-ready stops before anything is created.
A missing live label stops the action, as any missing --label does.
Owner decision 2026-11-21. A local session owns this item and works it; lanes should not claim it.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: the work-items track add action doc, label taxonomy reference, SKILL.md, CHANGELOG and evals; read by sessions that file work with /work-items:track.
Reversible: yes; revert the doc and eval edits.
Open questions: none
I understood this as: add a --session-owned flag to /work-items:track add. It applies the resolved session-owned role label, is refused together with --agent-ready, skips the needs-triage floor, and stops on a missing live label. The design and done-when are exact. The companion change is #17968, which is independent of this one.
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:/work-items:track add accepts --session-owned, which applies the session-owned role label resolved from config.role_labels (default session-owned), skips the needs-triage floor, is refused with --agent-ready, and stops on a missing live label.
Acceptance criteria
plugins/work-items/skills/track/actions/add.md lists --session-owned in the Usage line and the Flags list, saying it applies the session-owned role label.
add.md says the label resolves from config.role_labels\["session-owned"\] with default session-owned, by the same resolution as the human-gated role label.
add.md's Build labels step says an item filed with --session-owned gets no needs-triage floor, beside the existing --priority and --agent-ready exceptions at add.md:54, and the Defaults bullet at add.md:7 agrees.
add.md says --session-owned together with --agent-ready stops the action before anything is created, and the message names both flags.
add.md says the resolved session-owned label must exist in the live set, and a missing one stops the action before anything is created, as a missing --label does at add.md:30.
plugins/work-items/reference/label-taxonomy.md Canonical roles table and binding-shape JSON (around lines 32-59) list the session-owned role with default session-owned and a description that a local session owns the item and lanes skip it; the intro's role count is updated.
plugins/work-items/skills/track/SKILL.md mentions the new flag wherever it describes the add flags and role resolution (around line 29), and the work-items CHANGELOG has an entry.
A new eval under plugins/work-items/evals (modeled on tk-empty-role-label-stops) covers --session-owned with --agent-ready stopping before create-item, and one covers the item created without needs-triage; the work-items test suite passes.
External state: none
Dependencies
melodic-software/github-iac#939 declares the session-owned label in the live label set; until it is live, track add --session-owned stops on the missing-label check, which is the intended behavior.
#17968 is the companion change that makes lanes skip the label. It is independent and neither blocks nor is blocked by this change.
plugins/work-items/skills/track/actions/add.md:7: the needs-triage floor is applied when the live set has it and no priority is given.
plugins/work-items/skills/track/actions/add.md:15: the Usage line has no ownership flag.
plugins/work-items/skills/track/actions/add.md:28: --agent-ready applies the autonomous-eligible role label.
plugins/work-items/skills/track/actions/add.md:30: a missing --label stops the action before anything is created, naming the missing set.
plugins/work-items/skills/track/actions/add.md:54: the Build labels step drops the floor for --priority, --agent-ready, --parent and container labels; this is where the session-owned exception goes.
plugins/work-items/reference/label-taxonomy.md:32-59: four canonical roles resolved from config.role_labels with defaults; session-owned is not among them yet.
plugins/work-items/reference/label-taxonomy.md:61-66: roles resolve at the start of each invocation; an absent entry falls back silently to the default, and a malformed entry is an error.
plugins/work-items/skills/track/SKILL.md:29: role resolution from config.role_labels of the binding.
Automated refinement by the lanes App. Intake triages the issue again with it.
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44935459237, 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-21T18:28:13Z. 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: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: the work-items
track addaction doc, label taxonomy reference, SKILL.md, CHANGELOG and evals; read by sessions that file work with /work-items:track.Reversible: yes; revert the doc and eval edits.
Open questions: none
I understood this as: add a
--session-ownedflag to/work-items:track add. It applies the resolvedsession-ownedrole label, is refused together with--agent-ready, skips theneeds-triagefloor, and stops on a missing live label. The design and done-when are exact. The companion change is #17968, which is independent of this one.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
Not admitted to the issue lane yet: blocker #17968 is not closed by a listed human or a merge.
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:
/work-items:track addaccepts--session-owned, which applies thesession-ownedrole label resolved fromconfig.role_labels(defaultsession-owned), skips theneeds-triagefloor, is refused with--agent-ready, and stops on a missing live label.Acceptance criteria
--session-ownedin the Usage line and the Flags list, saying it applies the session-owned role label.config.role_labels\["session-owned"\]with defaultsession-owned, by the same resolution as the human-gated role label.--session-ownedgets noneeds-triagefloor, beside the existing--priorityand--agent-readyexceptions at add.md:54, and the Defaults bullet at add.md:7 agrees.--session-ownedtogether with--agent-readystops the action before anything is created, and the message names both flags.--labeldoes at add.md:30.session-ownedrole with defaultsession-ownedand a description that a local session owns the item and lanes skip it; the intro's role count is updated.addflags and role resolution (around line 29), and the work-items CHANGELOG has an entry.--session-ownedwith--agent-readystopping before create-item, and one covers the item created withoutneeds-triage; the work-items test suite passes.External state: none
Dependencies
session-ownedlabel in the live label set; until it is live,track add --session-ownedstops on the missing-label check, which is the intended behavior.Related work
Sources read
--agent-readyapplies the autonomous-eligible role label.--labelstops the action before anything is created, naming the missing set.--priority,--agent-ready,--parentand container labels; this is where the session-owned exception goes.config.role_labelswith defaults;session-ownedis not among them yet.config.role_labelsof the binding.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":"53fa1bb8f0370257e5c6e31d2de5df7337ddd71f2711e795a63deee07bde89f6","body_sha256":"ec5a6c25ad1e2158fe83be8266ff18180571c6f820b57efb1cbd9bc108948d69"}
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 44935459237, 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-21T18:28:13Z. 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.github-actions commentedon Nov 21, 2026