Friction log

File durable, recurring pain with a clear owner and a reproducible contract gap: a missing step, a lying type, a broken harness, docs that disagree with the code, a brittle test. The next agent should be able to act on it without your session. One-off confusion and session-only nits stay in the session.

Fix obvious, low-risk friction in the current change when it is in scope, and mention the fix. File what is left over.

Search open friction issues first and comment on a match. Each issue carries what the project's friction form asks for: what happened, what you wanted, how to reproduce, the cost, what you already looked at, and relevant files. Keep secrets and private data out.

Give each issue a priority and, when it needs a human call, the decision marker from the project's triage scheme (autopilot rung 11; default P0–P3 labels plus needs-decision). friction-skipped marks an issue the friction sweep leaves alone until someone removes the label.