feat(work-items): setup writes the binding to the convention home and migrates the JSON file #11879

Activity

1. kyle-sexton

   added

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   on Nov 1, 2026
2. kyle-sexton

   added the

   Feature

   issue type on Nov 1, 2026
3. kyle-sexton

   marked this as blocked on Nov 1, 2026

   • feat(work-items): the seam reads the tracker binding from the convention home #11872
4. kyle-sexton

   added a parent issue on Nov 1, 2026

   • work-items: bug path, triage clusters, claim protocol, trackers and morning brief #7578
5. melodic-automation-lanes

   added

   agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

   on Nov 1, 2026
6. github-actions commented on Nov 1, 2026

   

   github-actionsBot

   on Nov 1, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   No description provided.
7. github-actions commented on Nov 1, 2026

   

   github-actionsBot

   on Nov 1, 2026 – with GitHub Actions

   Last edited by github-actions

   Contributor

   More actions

   No description provided.
8. melodic-automation-lanes

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   and removed

   agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

   on Nov 1, 2026
9. melodic-automation-lanes commented on Nov 1, 2026

   

   melodic-automation-lanesBot

   on Nov 1, 2026

   Contributor

   More actions

   The work-resolve-issue lane stopped partway through this issue and needs a person.

   Reason: security

   Why, in the run's own words:

   security-risk: deleting .work-item-tracker.json, as this issue's done-when requires, weakens the babysit-prs autonomous merge hold until readers outside setup move to <home>/work-items.yaml. babysit_merge.human_gated_label (plugins/source-control/skills/babysit-prs/scripts/babysit_merge.py:254, via babysit_postmerge._role_label) reads the human-gated label only from .work-item-tracker.json, and when the file is missing it uses the default needs-human. A consumer that remaps human-gated in config.role_labels would lose that merge hold once setup migrates and removes the JSON. babysit_merge_policy.admission_label (line 2319) reads the same file. The removal also breaks functional readers: the work, triage and attend-queue binding preflights (work/SKILL.md:237 and :285, triage/SKILL.md:157, attend-queue/SKILL.md:155, track/SKILL.md:29 and the due, recheck and audit actions) check only .work-item-tracker.json, so a migrated repo would look unbound. plugins/autonomy/skills/setup/scripts/resolve-prerequisites.mjs:209 would report the tracker binding missing. A person needs to decide the order: land the reader migrations (other slices under ＃7578?) before this one, or have this slice keep the JSON file, or refuse to remove it while config.role_labels is set, until they land.

   What the run says it did not do:

   • Removal of the legacy JSON is unsafe to ship until babysit-prs (babysit_merge.py, babysit_merge_policy.py, babysit_postmerge.py), autonomy resolve-prerequisites.mjs and the work, triage, attend-queue and track skills' binding and role-label preflights read <home>/work-items.yaml. Those readers
   • migrate-binding.test.sh was not executed: this lane allows no interpreter or test runner, so 'passes under scripts/run-test-file.sh' is left to the PR's CI. The subagent review traced every assertion by reading.
   • bash plugins/skill-quality/scripts/check-skill.sh plugins/work-items/skills was not run directly: no wrapper exists for it here. check-affected skipped its changed-skills step ('runs the checked tree's own skill-quality code'), so it is left to the PR's CI.
   • tidy: skipped because the change exceeds the 300-changed-line cutoff (225 tracked lines plus three new files).
   • Stale .work-item-tracker.json mentions remain outside the setup skill: reference/label-taxonomy.md:29, tracker-seam.md:167, seeds/gitea/README.md:15, seeds/linear/README.md:15, README.md, and the reader skills listed in the reason. These belong with the reader migration.
   • The working tree also shows untracked .bash_profile, .bashrc, .gitconfig, .idea, .mcp.json, .profile, .ripgreprc, .vscode, .zprofile and .zshrc at the checkout root. This run did not create them (they look like sandbox artifacts), and they are not part of this change.
   • Build and test step (verify) not run beyond the lint checks above, for the same no-interpreter reason.

   Partial work is on the branch work-resolve-issue/issue-11879-41313108155-1. A retry continues from it while it is not behind the default branch, and otherwise starts fresh from the default branch; delete the branch first to always start fresh.

   Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41313108155

   To retry, remove needs-human and add agent-ready again.
10. kyle-sexton commented on Nov 1, 2026

    

    kyle-sexton

    on Nov 1, 2026

    MemberAuthor

    More actions

    Re-scoped after the lane stop on run 41313108155: setup now copies the JSON binding to YAML and keeps .work-item-tracker.json, because babysit-prs, resolve-prerequisites and the work, triage, attend-queue and track preflights still read only the JSON file. Removing the JSON is the held #7578 slice that removes the old file, after the reader migrations. The stop was an ordering question inside the parent's split, not a secret, account or billing risk, so it goes back to the lanes.
11. kyle-sexton

    added

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

    and removed

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

    on Nov 1, 2026
12. github-actions commented on Nov 1, 2026

    

    github-actionsBot

    on Nov 1, 2026 – with GitHub Actions

    Last edited by github-actions

    Contributor

    More actions

    No description provided.
13. github-actions commented on Nov 1, 2026

    

    github-actionsBot

    on Nov 1, 2026 – with GitHub Actions

    Last edited by github-actions

    Contributor

    More actions

    No description provided.
14. melodic-automation-lanes commented on Nov 1, 2026

    

    melodic-automation-lanesBot

    on Nov 1, 2026

    Contributor

    More actions

    This run started fresh from the default branch instead of resuming work-resolve-issue/issue-11879-41313108155-1, which is behind it. That branch keeps the earlier run's commits until the next run on this issue deletes it, when no pull request uses it.
15. melodic-automation-lanes

    closed this as completedin #11947on Nov 1, 2026