qstack-reflectlisted

# /qstack-reflect Report how this project is being worked, using only facts that can be counted and re-checked. Read-only: never edit tracked files, never commit, never change a branch or working tree. This is a mechanical evidence pass. Do not interpret motive, diagnose the reader, or write anything you cannot cite a number for. A finding is a count plus its location. If a category lacks evidence, say so and move on. ## Arguments `/qstack-reflect [plan-dir ...]` Every argument is a directory holding plan documents, relative to the repository root or absolute. Supplied paths are authoritative: use exactly those and skip plan discovery entirely. This is the escape hatch for any project whose plans live somewhere this skill would not think to look: a `docs/` tree, an `rfcs/` directory, a path outside the repository. With no arguments, fall back to discovery (category E). Discovery is a convenience for projects using a known layout, not a claim to know where a given project keeps its plans. When it finds nothing, say where it looked and name this argument, rather than concluding the project has no plans. ## Scope 1. Resolve the repository root with `git rev-parse --show-toplevel`. Outside Git, say the skill needs a Git repository and stop. 2. Take the checkout set from `git worktree list --porcelain`. Git maintains this list itself, so it is an answer rather than a guess: no directory convention to match, no candidate to verify, and nothing to exclude. 3. State