coder · S1M0N38 · Feb 24, 2026 · Feb 24, 2026 · Feb 25, 2026 · Feb 25, 2026
diff --git a/.agents/skills/balatrobot/SKILL.md b/.agents/skills/balatrobot/SKILL.md
@@ -0,0 +1,68 @@
+---
+name: balatrobot
+description: Launch Balatro with the BalatroBot mod and interact via the CLI. Use when you need to manually test, reproduce issues, or inspect game state through the JSON-RPC API.
+---
+
+# BalatroBot CLI
+
+Four commands: `serve`, `api`, `list`, `stop`. Explore any with `--help`.
+
+## Workflow
+
+```bash
+# Start server in background (ports are ephemeral, auto-allocated)
+nohup balatrobot serve --render headless --settings turbo --debug > /tmp/bb.log 2>&1 &
+sleep 5
+balatrobot api health           # auto-discovers port via state file — no --host/--port
+
+# Call endpoints or replay a trace
+balatrobot api gamestate
+balatrobot api --requests path/to/trace.req.jsonl      # --requests also auto-discovers
+
+balatrobot stop                                     # always use stop, never kill/pkill
+```
+
+## `serve`
+
+```bash
+balatrobot serve --render headless --settings turbo --debug
+```
+
+Key flags: `--render [headfull|headless|ondemand]` (default headfull), `--settings` (default "default"), `--debug`, `--num`. Blocks until Ctrl+C — background it with `&`/`nohup` before running other commands.
+
+## `api`
+
+```bash
+balatrobot api <method> [JSON_PARAMS]       # params default {}
+balatrobot api --requests PATH              # replay JSONL trace
+balatrobot api --requests PATH --responses PATH  # verify against recorded
+```
+
+Reads the running instance from the state file — **never pass `--host`/`--port` manually** (ports are ephemeral). For multi-instance, use `-i`/`--index`.
+
+```bash
+balatrobot api health
+balatrobot api start '{"deck":"RED","stake":"WHITE"}'
+balatrobot api play '{"cards":[0,1,2,3,4]}'
+balatrobot api buy '{"pack": 0}'
+balatrobot api gamestate | jq '.state'
+```
+
+See `docs/api.md` for methods, params, and state machine.
+
+## `list`
+
+```bash
+balatrobot list                                     # human-readable
+balatrobot list --json | jq '.instances[0].port'    # extract port/log_path
+```
+
+## `stop`
+
+```bash
+balatrobot stop              # SIGTERM + 5s poll, cleans state file
+```
+
+## Logs
+
+Session directory `logs/<timestamp>/` contains `<port>.log`, `<port>.req.jsonl`, `<port>.res.jsonl`. Find paths via `balatrobot list --json`.
diff --git a/.agents/skills/git-commit/SKILL.md b/.agents/skills/git-commit/SKILL.md
@@ -0,0 +1,36 @@
+---
+name: git-commit
+description: 'Conventional commit creator with auto-staging and message generation.'
+license: MIT
+allowed-tools: Bash
+---
+
+# Git Commit
+
+1. **Context:** `git log -n 5` to match repo style.
+
+2. **Review:** `git status` and `git diff`.
+
+3. **Stage & Group:** If many files changed, group them into **multiple logical commits** (`git add <files>`). No secrets.
+
+4. **Message:** ALL commits should be multiline. (No `!` for breaking changes because we are still in early alpha). Format:
+
+   ```text
+    <type>(<scope>): <title>
+
+    <body>
+   ```
+
+   where `<title>` ≤ 72 characters (ideal ≤ 50) and `body` wrap at 72 characters. The best commit messages help someone six months later answer "Why was this change made?".
+
+5. **Commit:** Execute using heredoc:
+
+   ```bash
+   git commit -F - <<'EOF'
+   <message here>
+   EOF
+   ```
+
+6. **Iterate:** Repeat steps 3-5 until all logical groups are committed.
+
+7. **Safety:** No `--force`, `reset --hard`, config changes, or `--no-verify`.
diff --git a/.agents/skills/triage-issue/REFERENCE.md b/.agents/skills/triage-issue/REFERENCE.md
@@ -0,0 +1,61 @@
+# HTML Report Reference
+
+## Palette (Tokyo Night)
+
+Include this `<style>` block in the report. It provides a dark theme with semantic color variables. Compose the rest of the report freely — choose whatever sections, layout, and HTML elements best explain the issue.
+
+```css
+:root {
+  --bg: #1a1b26; --surface: #24283b; --border: #3b4261;
+  --text: #c0caf5; --muted: #565f89; --accent: #7aa2f7;
+  --green: #9ece6a; --red: #f7768e; --yellow: #e0af68; --purple: #bb9af7;
+}
+body {
+  font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif;
+  background: var(--bg); color: var(--text); line-height: 1.65;
+  padding: 2.5rem; max-width: 860px; margin: 0 auto; font-size: 0.9rem;
+}
+h2 { color: var(--accent); margin: 2rem 0 0.5rem; }
+code { background: var(--surface); border: 1px solid var(--border); border-radius: 4px; padding: 0.1rem 0.35rem; }
+pre { background: var(--surface); border: 1px solid var(--border); border-radius: 8px; padding: 1rem; overflow-x: auto; font-size: 0.82rem; }
+a { color: var(--accent); }
+hr { border: none; border-top: 1px solid var(--border); margin: 1.5rem 0; }
+```
+
+## Verdict badges
+
+```css
+.badge { display: inline-block; padding: 0.2rem 0.65rem; border-radius: 20px; font-size: 0.78rem; font-weight: 600; }
+.badge-green  { background: rgba(158,206,106,0.15); color: var(--green);  border: 1px solid rgba(158,206,106,0.3); }
+.badge-red    { background: rgba(247,118,142,0.15); color: var(--red);    border: 1px solid rgba(247,118,142,0.3); }
+.badge-yellow { background: rgba(224,175,104,0.15); color: var(--yellow); border: 1px solid rgba(224,175,104,0.3); }
+```
+
+| Verdict | Class | Color |
+|---------|-------|-------|
+| Reproduced / bug confirmed | `badge-red` | `--red` |
+| Already fixed / no action needed | `badge-green` | `--green` |
+| Needs manual review / inconclusive | `badge-yellow` | `--yellow` |
+
+## Required header
+
+Every report must start with:
+
+```html
+<h1>{issue title}</h1>
+<p class="meta">
+  <code>{scope}</code> &middot;
+  <a href="https://github.com/coder/balatrobot/issues/{NNN}">#{NNN}</a> &middot;
+  coder/balatrobot &middot;
+  <span class="badge badge-{color}">{VERDICT}</span>
+</p>
+```
+
+The link to the original issue on GitHub is mandatory.
+
+## Guidelines
+
+- **Compose freely.** The LLM decides which sections (`<h2>`) to include based on what best explains the issue. There is no fixed template beyond the header.
+- **Use the palette variables** for all colors. Use `--red`/`--green` for diff highlights, `--accent` for headings and links, `--muted` for secondary text.
+- **Keep it simple.** Plain HTML. No frameworks, no JavaScript. The report is a static file opened in a browser.
+- **Save to** `/tmp/balatrobot/issues/{NNN}/report.html`
diff --git a/.agents/skills/triage-issue/SKILL.md b/.agents/skills/triage-issue/SKILL.md
@@ -0,0 +1,77 @@
+---
+name: triage-issue
+description: Triage and reproduce GitHub issues for the coder/balatrobot repo. Fetches issue data, downloads attachments, creates a branch, reproduces the bug, and generates an HTML investigation report. Use when the user says "/triage-issue NNN" or asks to reproduce a specific issue by number.
+---
+
+# Triage Issue
+
+Reproduce and investigate a GitHub issue end-to-end, producing an HTML report.
+
+## Quick start
+
+User provides a GitHub issue URL. Extract the issue number and run the full workflow below.
+
+## Workflow
+
+### 1. Fetch & download
+
+```bash
+mkdir -p /tmp/balatrobot/issues/NNN
+gh issue view NNN --repo coder/balatrobot --json title,body,comments,labels,state \
+  | tee /tmp/balatrobot/issues/NNN/issue.json
+```
+
+Extract attachment URLs from body + comments and download:
+```bash
+gh issue view NNN --repo coder/balatrobot --json body,comments -q '.body, (.comments[].body)' \
+  | grep -oE 'https://github.com/user-attachments/files/[^ )]+' \
+  | xargs -I{} curl -sLo /tmp/balatrobot/issues/NNN/$(basename {}) '{}'
+```
+
+### 2. Read before executing
+
+**Before running anything**, read all downloaded files:
+- **`script.py`** — reproduction script. Read fully before running.
+- **`*.req.jsonl`** — replayable via `balatrobot api --requests`.
+- **`*.res.jsonl`** — response log for comparison.
+- **`*.log`** — Balatro log output for error context.
+
+Choose reproduction method: `script.py` if present (adapt port), else replay `.req.jsonl`.
+
+### 3. Create branch
+
+Derive prefix from issue title (`fix(...)` → `fix/`, `feat(...)` → `feat/`, etc., fallback `fix/`):
+```bash
+git checkout <current-active-branch>
+git checkout -b <prefix>/issue-NNN
+```
+
+### 4. Reproduce
+
+```bash
+balatrobot serve --render headless --settings turbo --debug
+```
+
+Wait for ready, then reproduce using the chosen method. Run **≥3 times** to confirm consistency.
+
+### 5. Report & cleanup
+
+Generate HTML report at `/tmp/balatrobot/issues/NNN/report.html`. See [REFERENCE.md](REFERENCE.md) for template. Must include: issue title, verdict badge (`REPRODUCED`/`ALREADY FIXED`/`NEEDS MANUAL REVIEW`), summary, reproduction steps, results table, analysis, conclusion.
+
+Then:
+- `balatrobot stop`
+- If already fixed → delete branch, switch back.
+- If reproducible → keep branch.
+- `open /tmp/balatrobot/issues/NNN/report.html`
+
+## Checklist
+
+Before reporting done, verify:
+- [ ] Issue data fetched and saved to `/tmp/balatrobot/issues/NNN/`
+- [ ] All attachments downloaded
+- [ ] Attachments read and understood before execution
+- [ ] Branch created from active branch
+- [ ] Issue reproduced (or confirmed already fixed) with ≥3 runs
+- [ ] HTML report generated at `/tmp/balatrobot/issues/NNN/report.html`
+- [ ] Report opened in browser
+- [ ] Server stopped, branch cleaned up if no fix needed
diff --git a/.claude/settings.json b/.claude/settings.json