Dotfiles

Appearance

Queue workflow ​

GitHub Issues are the durable queue state for autonomous work in this repo. TODO.md and TODO_COMPLETED.md are legacy/manual queue material kept for historical context while old items are migrated or explicitly touched.

Use AGENTS.md as the authoritative policy for labels, decision gates, validation, and commit behavior.

Durable queue ​

Queue state lives in GitHub Issues through gh. If gh, GitHub auth, the GitHub remote, or the required queue labels are unavailable, stop and ask for that setup to be fixed. Do not fall back to local queue files.

Use the repo label families from AGENTS.md:

  • status:* for workflow state;
  • type:* for work category;
  • scope:* for host or subsystem;
  • risk:* for expected blast radius.

Each issue should carry enough context for another agent to continue the work: the concrete task, affected lane or subsystem, validation command, blockers, and any legacy TODO.md pointer that supplied historical context.

Work an item ​

When a worker is assigned a GitHub Issue:

  1. Run git status --short --branch.
  2. Read the assigned issue and any linked legacy notes.
  3. Make the smallest coherent source edit.
  4. Run the issue validation or the closest lane-native equivalent.
  5. Update the issue with validation results, blockers, or follow-up context.
  6. Close the issue only after the requested work is complete and validated.

If a task cannot be completed because it needs another host lane, elevated commands, or a decision, record the blocker in the issue and use the matching status:* label. Keep the final answer explicit about the remaining manual action.

Legacy TODO handling ​

TODO.md is no longer the source of truth for autonomous continue work. Treat it as manual queue context and historical notes.

When a legacy TODO item is migrated or touched:

  1. Create or update a GitHub Issue with the durable task state.
  2. Preserve the legacy context until the issue references the old item clearly.
  3. Leave a small pointer in TODO.md, such as a GitHub Issue number or a short migrated note.
  4. Avoid moving new issue-based completions into TODO_COMPLETED.md; use the closed issue as the durable completion record.

Do not delete or rewrite queue history wholesale as part of ordinary queue work. Reduce legacy material only in small follow-up changes after the durable issue has enough context.