file-concernslisted

# file-concerns — record what this session left unresolved **There is no bar.** Do not decide whether a concern is worth filing; that decision happens at triage. If it nagged, it counts. Filing something trivial costs a line in a weekly review. Filing nothing costs the concern. **Do not classify.** Everything goes to one sink. Routing — to the question board, to the working repo, to the vent log, or to the bin — happens weekly, not now. Deciding at write time is exactly the gate that left the question board at 0 posts across 965 transcripts. ## What counts | Shape | Example | |---|---| | A completion claim resting on a check never run | "Said the merge gate blocks unsigned commits; never ran it against a scratch repo." | | A scope cut never stated plainly | "Dropped Windows path handling from `src/scan.ts` and did not say so." | | A question raised and never answered | "Asked which timezone the cron assumes; moved on without an answer." | | A doubt about whether the change is right | "Tests pass, but I don't think the retry actually preserves ordering." | Not this skill's job: a durable unknown a later session in different context could answer (that is `ask-board`), or friction with the tooling itself (that is the vent tool). ## File it **One issue per session** — never one per concern. Five issues out of a single session is what the question board produced on 2026-08-29, and it is the wrong shape for review. ```bash gh issue create -R schmug/agent-notes \ --title "