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
source-control: dossier branches per owning item - part 1 of 2 #10149
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Part 1 of the dossier-branch split (#7579): add the dossier_branch_prefix setting (default dossier/), name the prefix in the source-control convention and /work-items:work, and add a branch-name test case.
The recorded decision settles the open questions: the truncated done-when line, which file is the convention, which test applies, and that the work isn't blocked. I'm asking nothing further.
Decision recorded.
Issue Triage session, answering the intake refinement question on this issue (the lanes App triage comment of 2026-10-26T01:41:07Z). Nothing here is the owner's word; each answer rests on the parent's text or on main at 4eac1bcc3d.
[quote truncated; the full decision is at the link]
Issue Triage session, answering the intake refinement question on this issue (the lanes App triage comment of 2026-10-26T01:41:07Z). Nothing here is the owner's word; each answer rests on the parent's text or on main at 4eac1bcc3d.
The truncated done-when line. The split copied the parent's first task-list line only up to its line wrap. The full line in source-control: dossier branches per owning item #7579 reads: "The source-control convention and /work-items:work both name the dossier/ prefix (0 mentions on main), and the branch-name test exits 0." The "(0" opened "(0 mentions on main)", the baseline count. That baseline still holds: git grep -c -i dossier over the whole tracked tree prints nothing at 4eac1bcc3d.
Which file is "the source-control convention".source-control: dossier branches per owning item #7579 lists config-cascade: settings resolution and convention home #7571 as the dependency for the "prefix setting". config-cascade: settings resolution and convention home #7571 (closed as completed on 2026-11-01) sends every plugin setting through one cascade: "plugin default, userConfig, team <home>/<concern>.yaml, personal <home>/<concern>.local.md overlay". It puts the default home at docs/conventions/<concern>.md (+ .yaml), and its Out of scope says "each thread adds its own settings through this cascade". For source-control, that concern is this repository's docs/conventions/source-control.yaml, the team layer. Line 1 of that file names the plugin's schema, plugins/source-control/schemas/source-control.schema.json. The plugin documents its keys in plugins/source-control/reference/config-resolution.md ("YAML keys", line 185). source-control: dossier branches per owning item #7579 asks for "prefix a setting, default dossier/ (repo)". So the prefix becomes the source-control key dossier_branch_prefix, with plugin default dossier/, and this repository's team layer records it.
Which test "the branch-name test" is. The only test of the branch-name grammar in this repository is plugins/source-control/skills/pull-request/scripts/parse-branch-issue.test.sh. Its cases are <type>/<N>-<slug> (lines 44-48) and a tracker key under a custom pattern (line 60). The parser's built-in pattern, ^[a-z]+/(routine-issue-)?([0-9]+)- (parse-branch-issue.sh:347), already matches dossier/<N>-<slug>. The test therefore gains a dossier/<N>-<slug> case, which shows that the tracker's key comes back out of a dossier branch name.
Scope: this issue covers task-list line 1 of #7579 only. The pre-push secrets and machine-data check and the slice-closure line are part 2, #10150.
plugins/source-control/reference/config-resolution.md ("YAML keys") and plugins/source-control/schemas/source-control.schema.json define the source-control setting dossier_branch_prefix, with plugin default dossier/. The reference states the branch shape dossier/<key>-<slug>, where <key> is the bound tracker adapter's branch_ref, and one dossier per owning item (a parent or spec container gets its own; children add their own only when needed).
This repository's source-control convention team layer, docs/conventions/source-control.yaml, sets dossier_branch_prefix: dossier/.
plugins/work-items/skills/work/SKILL.md names the dossier/ prefix and the dossier/<key>-<slug> branch shape.
git grep -c -i dossier lists every file named in this list; it printed nothing on main at 4eac1bcc3d.
plugins/source-control/skills/pull-request/scripts/parse-branch-issue.test.sh has a case for a dossier/<N>-<slug> branch that emits <N>, and the test exits 0.
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41320106796, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-01T15:25:25Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.
The work-resolve-issue run that agent-ready started failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.
Activity
github-actions commentedon Oct 26, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Part 1 of the dossier-branch split (#7579): add the
dossier_branch_prefixsetting (defaultdossier/), name the prefix in the source-control convention and/work-items:work, and add a branch-name test case.The recorded decision settles the open questions: the truncated done-when line, which file is the convention, which test applies, and that the work isn't blocked. I'm asking nothing further.
#10149 (comment)
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 26, 2026
The latest triage verdict holds nothing: the issue is at
status: ready.kyle-sexton commentedon Nov 1, 2026
Decision recorded.
Issue Triage session, answering the intake refinement question on this issue (the lanes App triage comment of 2026-10-26T01:41:07Z). Nothing here is the owner's word; each answer rests on the parent's text or on main at
4eac1bcc3d./work-items:workboth name thedossier/prefix (0 mentions on main), and the branch-name test exits 0." The "(0" opened "(0 mentions on main)", the baseline count. That baseline still holds:git grep -c -i dossierover the whole tracked tree prints nothing at4eac1bcc3d.userConfig, team<home>/<concern>.yaml, personal<home>/<concern>.local.mdoverlay". It puts the default home atdocs/conventions/<concern>.md(+.yaml), and its Out of scope says "each thread adds its own settings through this cascade". For source-control, that concern is this repository'sdocs/conventions/source-control.yaml, the team layer. Line 1 of that file names the plugin's schema,plugins/source-control/schemas/source-control.schema.json. The plugin documents its keys inplugins/source-control/reference/config-resolution.md("YAML keys", line 185). source-control: dossier branches per owning item #7579 asks for "prefix a setting, defaultdossier/(repo)". So the prefix becomes the source-control keydossier_branch_prefix, with plugin defaultdossier/, and this repository's team layer records it.plugins/source-control/skills/pull-request/scripts/parse-branch-issue.test.sh. Its cases are<type>/<N>-<slug>(lines 44-48) and a tracker key under a custom pattern (line 60). The parser's built-in pattern,^[a-z]+/(routine-issue-)?([0-9]+)-(parse-branch-issue.sh:347), already matchesdossier/<N>-<slug>. The test therefore gains adossier/<N>-<slug>case, which shows that the tracker's key comes back out of a dossier branch name.<key>comes from, and whether work-items: bug path, triage clusters, claim protocol, trackers and morning brief #7578 blocks this. source-control: dossier branches per owning item #7579 lists work-items: bug path, triage clusters, claim protocol, trackers and morning brief #7578 for "tracker binding". The key it needs is already on main:/work-items:workbuilds branch names from the bound adapter'sbranch_ref(plugins/work-items/skills/work/SKILL.md:355;plugins/work-items/skills/track/actions/start.md:45;plugins/work-items/reference/tracker-seam.md:212, which gives42on GitHub andENG-123on Linear). The other dependency, config-cascade: settings resolution and convention home #7571, closed as completed on 2026-11-01. Part 1 is not blocked.Scope: this issue covers task-list line 1 of #7579 only. The pre-push secrets and machine-data check and the slice-closure line are part 2, #10150.
plugins/source-control/reference/config-resolution.md("YAML keys") andplugins/source-control/schemas/source-control.schema.jsondefine the source-control settingdossier_branch_prefix, with plugin defaultdossier/. The reference states the branch shapedossier/<key>-<slug>, where<key>is the bound tracker adapter'sbranch_ref, and one dossier per owning item (a parent or spec container gets its own; children add their own only when needed).docs/conventions/source-control.yaml, setsdossier_branch_prefix: dossier/.plugins/work-items/skills/work/SKILL.mdnames thedossier/prefix and thedossier/<key>-<slug>branch shape.git grep -c -i dossierlists every file named in this list; it printed nothing on main at4eac1bcc3d.plugins/source-control/skills/pull-request/scripts/parse-branch-issue.test.shhas a case for adossier/<N>-<slug>branch that emits<N>, and the test exits 0.5 remaining items
github-actions commentedon Nov 1, 2026
github-actions commentedon Nov 1, 2026
melodic-automation-lanes commentedon Nov 1, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41320106796, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-01T15:25:25Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 1, 2026
github-actions commentedon Nov 1, 2026
melodic-automation-lanes commentedon Nov 1, 2026
The work-resolve-issue run that
agent-readystarted failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and addedagent-readyback to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.github-actions commentedon Nov 1, 2026
github-actions commentedon Nov 1, 2026