Nits

The friction ledger: small annoyances, paper cuts, and papercuts-adjacent behaviors picked up while delegating real work to Factory Droid. A nit without a repro is a vibe; vibes live in the The Log, not here.

Structure per nit:

1. What I did (the exact delegation or command)
2. What happened (observed, not interpreted)
3. What I expected
4. The workaround, if one survived
5. Verdict: still-broken | fixed | lived-with

Rules:

• Real observed behavior only. Session link, transcript excerpt, or it didn't happen.
• One nit per page. Small pages are the point.
• Nits that turn out to be documentation gaps get a link to the doc and a note on where the doc lost the plot, not just "RTFM."
• When Factory fixes a nit, the page gets re-checked and the verdict flips. Updates get dated.

Filing: nits get noticed in The Log entries first; promotion to a page happens when the nit deserves its own file and will be re-checked.