Skip to content

feat(work-items): the seam reads the tracker binding from the convention home #11872

New issue
New issue
Closed
Feature
#11925
Closed
feat(work-items): the seam reads the tracker binding from the convention home#11872
Feature
#11925
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.

Description

@kyle-sexton
kyle-sexton
opened on Nov 1, 2026

Problem

The tracker binding is .work-item-tracker.json at the repo root. ADR 0075 (fix 11) supersedes ADR
0015: the binding moves to <home>/work-items.yaml, schema-checked, and no plugin keeps its own
convention file.

Origin: Q534, Q551; ADR 0075 fix 11.

Fix

Expand step of an expand, migrate, contract set. The seam's binding reader resolves the convention
home and reads the binding keys from <home>/work-items.yaml, with the personal overlay
<home>/work-items.local.yaml, checked against the work-items schema, using the repository's
existing YAML subset reader (plugins/work-items/skills/triage/scripts/yaml-subset.awk, as
parse-concern-value.sh does), not a new parser dependency. While the migration runs it
still reads .work-item-tracker.json when the YAML has no binding, with a one-line notice. When
neither resolves, it stops and points at /work-items:setup.

Done when

  • The work-items schema declares the binding keys; the tracker CONTRACT documents the new location, the overlay and the fallback.
  • binding.test.sh covers: YAML binding, YAML plus overlay, JSON fallback with notice, neither (stop), invalid YAML (named file, key, value); it passes under scripts/run-test-file.sh, as does work-item-tracker.test.sh.
  • A work-items changelog fragment passes bash scripts/check-changelog-fragments.sh.

Parent: #7578

Activity

  1. kyle-sexton
    added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 1, 2026
  2. kyle-sexton
    added the
    Feature
    issue type on Nov 1, 2026

  3. github-actions commented on Nov 1, 2026

    @github-actions
    github-actionsBot
    on Nov 1, 2026 – with GitHub Actions
    Contributor
    No description provided.
  4. kyle-sexton
    marked this as blocking 6 issues on Nov 1, 2026
  5. kyle-sexton
    added a parent issue on Nov 1, 2026

  6. github-actions commented on Nov 1, 2026

    @github-actions
    github-actionsBot
    on Nov 1, 2026 – with GitHub Actions
    Contributor
    No description provided.

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

    @melodic-automation-lanes
    melodic-automation-lanesBot
    on Nov 1, 2026
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41281678773, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-01T07:32:35Z. 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.

  8. melodic-automation-lanes
    added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 1, 2026

  9. github-actions commented on Nov 1, 2026

    @github-actions
    github-actionsBot
    on Nov 1, 2026 – with GitHub Actions
    Contributor
    No description provided.

  10. github-actions commented on Nov 1, 2026

    @github-actions
    github-actionsBot
    on Nov 1, 2026 – with GitHub Actions
    Contributor
    No description provided.
  11. melodic-automation-lanes
    closed this as completedin #11925on Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.

    Type

    Feature

    Fields

    No fields configured for Feature.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions