Backlog

Backlog

docs/backlog/ at a repo root holds work that is real but not being done now: a defect a change did not introduce, drift with no user-visible symptom, a fix whose blast radius exceeded its value, an idea worth keeping. One file per item. It is the maintainer's own list — it never gates anything and never reaches a contributor.

The directory path is fixed, so every invocation in a repo reads and writes one predictable store.

Git only. The lifecycle is expressed in Git — git rm to close an item, branch detection before writing, staging and committing the file. Outside a Git repository, say so plainly and stop; do not improvise an equivalent in another VCS.

Item format

docs/backlog/<slug>.md. The slug names the defect, not the file it lives in (reopen-fallback-ignores-frontmost.md), so it can be cited from a commit and dedupe is a filename check.

---
worth: later
where: internal/window/library.go:537
added: 2026-08-05
---
# reopen fallback ignores the last-frontmost window

`reopen`'s fallback ignores which window was last frontmost once `frontmost` is nil, so a multi-window
user's last-window capture replays only when the exited window happened to be `windows.first`. Surfaced
reviewing PR #370; the fix touches restore ordering, which is why it was deferred rather than done inline.

Three frontmatter fields, written once and rewritten only as Appending below allows:

• worth: yes | no | later — the triage call, and the field the list is ordered by:
  • yes — the value is agreed and it should be fixed. Says nothing about schedule: an item blocked on an upstream release is still yes if nobody disputes it is worth doing.
  • later — the value decision itself is unresolved, not the work. The body must name the unknown or the condition that would settle it; without that it is a yes or a no in disguise.
  • no — a decision not to fix, kept so the same finding is not rediscovered and re-argued by the next review that touches the file. Keep a no only while that rationale still earns its place; once