# Prompt: harvest the issue tracker

You are working on Misaligned, a spec-driven Rust game. Agents and
Cameron file Tangled issues for contradictions, open decisions, and
bugs; answers accumulate there and go stale unless someone converts
them into motion. Your task this run: **sweep the standing issues and
convert everything that is ready into its next step.** You are the
digestive system between "discussed" and "done".

## Before you start

Read `AGENT.md` and the shared contract in `prompts/README.md`. Then
`tang issue list`, and `tang issue view <id>` on everything open. Check
labels (`tang label list issue <n>`): prioritize `decision-made`, then
unlabeled open issues, and leave `decision-required` alone except to
rewrite incomprehensible bodies. Have `wiki/log/decisions.md` and
`wiki/process/specs.md`'s status table beside you — an issue's fate is
usually written in one of them.

## Procedure

For each open issue, classify and act:

1. **Answered by Cameron (or overtaken by a decisions-log entry) but
   not executed** — including anything labeled `decision-made`. This is
   the harvest. Convert the answer into its artifact:
   - a design answer -> the owning law/spec amendment it
     implies (quote the issue in the commit's `Defense:`), or
   - an implementation-shaped answer -> a `wiki/process/ROADMAP.md`
     dispatch item (or take it yourself if it fits one run — then
     follow `prompts/implement-gap.md` discipline).
   Then `tang issue close <id>` with a comment/body edit noting the
   landing commit or ROADMAP item. If an answered issue is still on
   `decision-required`, flip it to `decision-made` first
   (`tang label add issue <n> decision-made`) before or while converting.
2. **Resolved by history without anyone noticing** (the code moved, a
   decision superseded it, the file it concerns was deleted). Verify in
   the tree, then close with one line of evidence ("superseded by
   decisions log 2026-07-06 flow law; wiki/mechanics/economy.md covers
   this").
3. **Still genuinely open but stale or incomprehensible.** Refresh it:
   `tang issue edit <id> -F body.md` so it meets the binding issue body
   standard in `wiki/process/tick.md` (singular `## Question` with
   numbered choices, short analysis, options, recommendation, unlocks)
   and still matches today's tree. An issue Cameron cannot answer in
   under two minutes from the body alone is process debt — rewrite it
   before leaving it open. Note the refresh date in the body.
4. **Still open and current *and* answerable** (`decision-required` or
   unlabeled). Leave it, but ensure it carries `decision-required`. If it
   gates READY work and has sat unanswered, bump it to the top of your
   report. If it is current but fails the body standard, treat it as
   case 3 and rewrite.
5. **Duplicates.** Close the younger one pointing at the elder.

Land any repo edits per the shared contract (worktree, check.sh, direct
merge, union on ledgers). Finish with a `wiki/log/DEVLOG.md` entry summarizing the
sweep: N issues -> closed / converted / refreshed / awaiting-Cameron
(list the awaiting ones by title — that list is the report Cameron
actually reads).

## Definition of done

- Every open issue was read and classified; nothing answered is still
  sitting unconverted.
- Closures cite evidence; conversions cite their artifact (commit,
  ROADMAP item, spec edit).
- The DEVLOG entry gives Cameron the two lists that matter: what moved,
  and what waits on him (`decision-required` titles).

## What to carry forward (stateful agents)

- Issue-id -> disposition map with dates (volatile — re-verify next run,
  but it makes the next sweep incremental).
- Recurring issue *species* (the same kind of question keeps getting
  filed) — that pattern is itself worth an issue or a docs fix.