# OpenCode tickets

Grok writes these (see `PLAN.md`). OpenCode takes **one ticket at a time**. Ponytail plugin required. Do not invent tickets. Do not start the next ticket until the current one is done and `cargo test` passes.

Grok does **not** run ponytail-review until every ticket in this phase has been assigned (they all are) **and** the Open list is empty.

## Open

_(none — Phase 1 tickets all assigned and closed. Grok may run ponytail-review now.)_

## Closed

### T1 — format

`cargo fmt`. Done.

### T2 — clippy, only what it names

`cargo clippy --all-targets -- -D warnings`. Done.

### T3 — stop if fmt/clippy/test are already clean

Done (fmt/clippy/test were clean after T1–T2).

### T4 — Video FX click pass-through

Done (`mouse:272`/`273` → `map_click` + cursor + send to source; unit test).

### T5 — log slots when the set changes

Done.

### T6 — empty passthrough can map `e`

Done.

## Out of scope for OpenCode

- Gitea / git remotes (Grok)
- `hyprland-toplevel-export`
- Game addons
- New step kinds
- ponytail-review (Grok, after this phase is accepted)