dev-wikilisted

# Dev wiki Every question answered twice was work done twice. This skill makes the second answer a lookup. The rule that keeps it useful: **an answer is never written without the evidence it came from**. A wiki page asserting how something works, with no file paths, is indistinguishable from a page describing how it used to work. ## Answering **Check the wiki first.** `docs/agent/wiki/` — an existing answer is read, verified against the code (paths still exist, behaviour still matches), and used. Verification is the cheap part; skipping it is how a wiki starts lying. **Derive from the code, not from general practice.** The question is about *this* repo. `pattern-mine` for how it is done here; `feature-trace` when the answer spans layers; `api-contract-sync` when it concerns the API. **Answer with paths.** Every claim carries a `file:line`. A reader who disagrees can check, and a later run can re-verify. **Say what you did not confirm.** "Auth tokens refresh in the interceptor at `libs/auth/.../token.interceptor.ts:41`; whether the retry queue preserves request order is not obvious from the code and I did not test it." That sentence is worth more than a confident guess, because the next reader knows where the ground stops. ## Writing it back Write the answer to a file when it meets any of these: - The question has now been asked twice - Deriving it took more than a few minutes - The answer is the kind that will be needed again by someone else - A run stalled on it N