code-standardslisted

# Code standards — the change workflow You are making a code change in the Parler Protocol repo. The full contract is [`docs/engineering-guidelines.md`](../../../docs/engineering-guidelines.md) — read it once per session (it's short). This skill is the execution order. ## Steps 1. **Orient.** Read `tasks/lessons.md` (hard-won traps; obey them). Find the subsystem's doc in `AGENTS.md`'s index and read only that one. 2. **Plan if non-trivial** (3+ steps or an architectural choice): short plan in `tasks/todo.md` — files touched, tests to add, risks. Going sideways → stop and re-plan. 3. **Baseline:** `scripts/verify.sh --rust-only` green *before* touching anything. A pre-existing red is the first task. 4. **Implement** the smallest root-cause change. Hand-match the surrounding style. **Never `cargo fmt`.** 5. **Test:** new behavior gets a test that fails without the change; security gates get negative-assertion tests (wrong token → 401, cursor unchanged, no leak). 6. **Verify:** run `make ci` until green before "done". 7. **Self-review** your own diff against `docs/code-review-guidelines.md` (or invoke `parler-review`). Fix findings before presenting. 8. **Close out:** docs updated in the same change; append to `tasks/lessons.md` if you were corrected or surprised; conventional commit message (`feat|fix|docs(scope): …`). ## Tripwires — stop and check the guidelines when you're about to… - change anything in `crates/parler-protocol/` → ripple rules + add