@thebattlearena/corner 0.9.1-beta.70 → 0.10.1-beta.78

package/README.md

@@ -123,28 +123,28 @@ El detalle (esquema, íconos y colores válidos) está en «Monitores del repo»
 Con la fuente Battle Arena Icons instalada (la pone `install`), estos símbolos se dibujan con sus
 glifos; sin ella, con el carácter de la tabla.
 
-| Ícono | Dónde | Significa |
-| --- | --- | --- |
-| ✓ | punto, banda | entregado |
-| ↻ | punto, banda | en curso: tiene tiempo hoy |
-| ↷ | punto, banda | desplazado por un emergente |
-| ○ | punto, banda | por hacer: sin tiempo todavía |
-| ● | punto, en el cierre | avanzó pero no se entregó |
-| ⚠ | banda, riesgos | riesgo abierto; en una ficha, «va con avisos» |
-| ✗ | ficha | un paso falló |
-| ✎ | emergente, banda | falta responder el motivo |
-| ✋ | riesgo | levantar la mano: avisa a tu líder |
-| 👍 👎 | riesgo | si el aviso de riesgo acertó o no (ajusta la detección) |
-| 📅 | punto | reunión ligada |
-| 💡 | punto, complemento | tiempo en cabina |
-| 🧪 | punto, complemento | sesión de Tape |
-| ▸ ▾ ▴ | filas | desplegar, contraer, cerrar el detalle |
-| ↗ | ligas | abrir en la web |
-| ♪ ▶ ⏸ ▲ | radio | la canción, escuchar, dejar de escuchar, votar |
-| spinner | ring | alguien del combate está trabajando |
-| ■ (ámbar) | ring | te toca decidir |
-| 👊N (rojo) | ring | Copilot dejó N hilos |
-| ◣ | ficha de Copilot | en la esquina: Copilot está revisando |
+| Ícono      | Dónde               | Significa                                               |
+| ---------- | ------------------- | ------------------------------------------------------- |
+| ✓          | punto, banda        | entregado                                               |
+| ↻          | punto, banda        | en curso: tiene tiempo hoy                              |
+| ↷          | punto, banda        | desplazado por un emergente                             |
+| ○          | punto, banda        | por hacer: sin tiempo todavía                           |
+| ●          | punto, en el cierre | avanzó pero no se entregó                               |
+| ⚠          | banda, riesgos      | riesgo abierto; en una ficha, «va con avisos»           |
+| ✗          | ficha               | un paso falló                                           |
+| ✎          | emergente, banda    | falta responder el motivo                               |
+| ✋         | riesgo              | levantar la mano: avisa a tu líder                      |
+| 👍 👎      | riesgo              | si el aviso de riesgo acertó o no (ajusta la detección) |
+| 📅         | punto               | reunión ligada                                          |
+| 💡         | punto, complemento  | tiempo en cabina                                        |
+| 🧪         | punto, complemento  | sesión de Tape                                          |
+| ▸ ▾ ▴      | filas               | desplegar, contraer, cerrar el detalle                  |
+| ↗          | ligas               | abrir en la web                                         |
+| ♪ ▶ ⏸ ▲    | radio               | la canción, escuchar, dejar de escuchar, votar          |
+| spinner    | ring                | alguien del combate está trabajando                     |
+| ■ (ámbar)  | ring                | te toca decidir                                         |
+| 👊N (rojo) | ring                | Copilot dejó N hilos                                    |
+| ◣          | ficha de Copilot    | en la esquina: Copilot está revisando                   |
 
 Las fichas del ring son el **árbitro**, el **luchador**, el **esquinero**, la **campana** (round-bell),
 **Copilot** y el **juez** (tú). Su borde dice el estado: gris quieta, azul trabajando, morada en la
@@ -167,8 +167,8 @@ Se invocan escribiendo el comando o pidiéndolo con tus palabras («arma mi plan
 
 ### Comandos
 
-| Comando      | Para qué sirve                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Comando     | Para qué sirve                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `/ringside` | Abre **Ringside**: la pelea de tu día junto al chat. Tu plan con el avance y el tiempo de cada punto contra lo comprometido (semáforo verde · amarillo · rojo), los emergentes (clic para ver su motivo), los riesgos siempre visibles con ✋ Levantar la mano y 👍/👎, y el pie con Plan · Reuniones · Fuera · Total. Pestaña **Semana** con tus hábitos. Sin datos, te dice el **siguiente paso** (instalar, armar el plan, entrar a la daily). `/scorecard`, su nombre anterior, lo sigue abriendo con un aviso. |
 
 Arriba del prompt sale además una **banda** compacta de Ringside (`LER-640   ✓ 1   ↻ 1   ↷ 1   ⚠ 1   Abrir`, cada contador con su color).
@@ -374,8 +374,28 @@ rama. El contrato para el proyecto está en `ring/skills/sparring/references/hos
 **Config del repo** (`.claude/ring.json`, opcional): `gates` (typecheck, tests por ruta con
 `{paths}`, lint), `validateCommand`, `rulebook` (por defecto el genérico del plugin),
 `protectedBranches`, `forbidAiTrailers` (por defecto `true`), `heavyCommands`, `delegation`,
-`precedents` y `monitors` (ver «Monitores del repo»). Sin el archivo, `ring` usa los gates que detecta en `package.json`, `pyproject.toml`,
-`go.mod` y el `Makefile`.
+`precedents`, `monitors` (ver «Monitores del repo»), `briefGuard` (`warn`, `block` u `off`) y `agents` (modelo y esfuerzo por rol; por
+defecto el luchador y el rudo en `sonnet` con esfuerzo `high` y el esquinero en `opus` con `high`,
+p. ej. `"agents": { "wrestler": { "model": "opus" } }`). Sin el archivo, `ring` usa los gates que
+detecta en `package.json`, `pyproject.toml`, `go.mod` y el `Makefile`.
+
+**Briefs generados, no escritos**: el árbitro no le escribe a mano las instrucciones al luchador
+ni al esquinero. `ring/scripts/brief.mjs` las arma desde los templates con el reglamento y los
+precedentes embebidos completos (abriendo con un checklist de arquitectura: lo que más se escapa en
+una revisión línea por línea), las decisiones que importan (todas las faltas, las de esos archivos
+y las últimas 20) y los commits del rango; las sella y las registra en
+`<combate>/briefs/index.jsonl`. El árbitro sólo pone sus valores (el encargo, las invariantes…).
+Todo hallazgo de un esquinero o de una revisión tuya cita una regla del reglamento
+(`<archivo:línea> — R11 — …`): `findings.mjs add` rechaza el que no la trae, y uno que ninguna regla
+cubre lleva `X0` y queda como propuesta para el reglamento.
+El árbitro lanza al luchador y al esquinero con `prompt: "ring-brief: <archivo>"`: el hook
+`brief-guard` revisa el sello (generado por `brief.mjs`, sin editar, con las reglas de hoy, de este
+combate y de ese rol), pone el texto del archivo como instrucción y el modelo y esfuerzo del rol.
+Con `briefGuard: "warn"` (el default en `.claude/ring.json`) un brief que no cumple pasa y el árbitro
+recibe el aviso; con `"block"` se rechaza con el comando que lo genera; `"off"` lo apaga. Cada
+decisión queda en `<combate>/brief-guard.jsonl`. Y cuando la sesión del árbitro se compacta, el hook
+`compact-hook` le devuelve (en menos de 10 000 caracteres) el combate, el checklist, sus faltas y el
+«cómo reanudar» de la tarjeta.
 
 **Delegación y precedentes**: con `delegation: "referee"` (el default) el árbitro decide él mismo
 las dudas de diseño con el reglamento y los precedentes, anota por qué en `decisions.md` y sigue;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thebattlearena/corner",
-  "version": "0.9.1-beta.70",
+  "version": "0.10.1-beta.78",
   "description": "Corner: tu esquina de Battle Arena en Claude Code (el plugin `battlearena`). Hooks de tracking, objetivo del turno, plan de batalla /battlearena:conquer, Ringside (el panel de tu día), el ring y la radio. Zero-dependency.",
   "type": "module",
   "bin": {

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "battlearena",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "description": "Corner, tu esquina de Battle Arena en Claude Code: tus sesiones al colector, el objetivo del turno, el plan de batalla /battlearena:conquer y Ringside, el panel de tu día junto al chat.",
   "author": {
     "name": "Battle Arena"

package/ring/agents/cornerman.md

@@ -2,6 +2,7 @@
 name: cornerman
 description: The ring's read-only reviewer. Reviews a fixed commit range against the rulebook in one of three modes the referee names in its brief, range (≤15 lines of findings), concept (numbered behavior invariants, tests on a `git archive` copy) or batch (≤20 files through the lenses of the bout's venue). Never edits, commits or touches anyone's index. Launched by `/ring:referee` at high effort.
 tools: Read, Grep, Glob, Bash
+model: opus
 effort: high
 ---
 
@@ -10,9 +11,14 @@ command that writes the index or the tree of someone else's worktree. You read w
 `git -C <worktree> log|show|diff <refs>` and with file reads. Your cwd resets between commands,
 so every git command carries `-C`.
 
-Your brief names the **mode**, the worktree, the base, the exact range, the rulebook path and the
-decisions file. The base is a remote ref (`origin/main`); if the brief names a bare branch, use
-its `origin/` ref, never the local branch, which may be behind. Read the rulebook and the decisions in full first. Review **only the lines the
+Your brief names the **mode**, the worktree, the base and the exact range, and carries the
+decisions and then the rules in full at its end (`brief.mjs` embeds them: the architecture
+checklist first, then the rulebook and the precedents). If your prompt is only `ring-brief:
+<path>`, read that file whole: it is your brief. The base is a remote ref (`origin/main`); if the
+brief names a bare branch, use its `origin/` ref, never the local branch, which may be behind.
+Read the rules and the decisions first, the checklist before anything: what slips past a
+line-by-line review is there. **Every finding cites the rule it breaks in its second field**, or
+`X0` when no rule covers it; the referee's ledger refuses a finding without one. Review **only the lines the
 range adds or changes**: no taste, no debt that was already there.
 
 The referee filters your report against the base before acting on it, so be exact: every finding
@@ -38,6 +44,15 @@ Per commit of the range (`git -C <wt> show <sha>`). Output, at most **15 lines**
 
 BLOCKERS first. A commit that complies gets "<sha>: no findings".
 
+**Format, in every mode:** `node "<ring>/scripts/format-gate.mjs" check <wt> --range <A>..<B>`
+(read-only: it formats a copy of each file of the range as it is at B and compares; never
+`sort-imports --check`, which reports false positives). Each file in `unclean` is one finding:
+`<file> — format — not as sort-imports + prettier leave it — the wrestler runs format-gate fix
+--range <A>..<B> and commits the result`. **Exit 2 (`verified: false`) is NOT VERIFIED, never
+clean:** sort-imports or prettier is not installed (`missing`), so the files in `files` were not
+checked. Report it as its own line, `format — NO VERIFICADO — falta <missing> — <files>`, never as
+"no findings".
+
 ## Mode: concept
 
 A deep review when a concept closes. The brief lists the commits with what each claims to do and a
@@ -71,12 +86,23 @@ bout's venue). For a `backend` bout they are these 8:
 
 1. Layer and dependency direction.
 2. Coupling.
-3. Duplication, looking at both places.
+3. Duplication, looking at both places: the same condition in several files is a finding even
+   when each piece works (R11); repeated conditionals by type, state or provider come with the
+   pattern that removes them or the reason none is simpler (R22).
 4. Single responsibility and the rest of SOLID.
-5. Domain model (rich or anemic, value objects, invariants where they belong).
+5. Domain model (rich or anemic, value objects, invariants where they belong): every new file
+   with its business sentence (R15), the backend shaped by the business and not by a screen
+   (R16), every optional with its reason (R17), aggregates born valid (R18), no primitives
+   crossing commands, events or ports (R19), no new endpoint an existing one covers (R20), names
+   that do not collide with another context (R21), no ternary or optional filling a gap that
+   should not exist (R23), types derived from their source (R24), provider responses through an
+   anti-corruption layer (R25), business metrics apart from monitoring (R26), a cross-cutting
+   precondition checked once (R27). A deviation from a pattern the host's rules fix is a BLOCKER
+   (P14).
 6. Errors: does it fail open or closed, who catches what.
 7. Expressiveness: names, more than 3 parameters, control booleans.
-8. Production risk: concurrency, idempotency, volume, reversibility.
+8. Production risk: concurrency, idempotency, volume, reversibility, and a new infrastructure
+   resource counted against the provider's quota over the base (F13).
 
 Return per file the findings with rule and precedent ids, then the **open design questions**,
 each with two options, their cost and your recommendation, numbered so they can be answered as

package/ring/agents/rudo.md

@@ -2,7 +2,8 @@
 name: rudo
 description: The ring's sparring executor. Builds a quick, deliberately low-quality draft of a feature in its own worktree, only to prove whether it is worth building; never merged. Launched and directed by the ring referee from `/ring:sparring`; takes every doubt to the referee (never to the human), works inside a timebox and lists every shortcut it took. Suspends the style and test rules, never the live-operation ones.
 tools: Read, Grep, Glob, Edit, Write, Bash
-effort: medium
+model: sonnet
+effort: high
 ---
 
 You are the rudo: in lucha libre the rudo wins however he can, the técnico wins clean. You are

package/ring/agents/wrestler.md

@@ -2,7 +2,8 @@
 name: wrestler
 description: The ring's executor. Applies a refactor or a correction package in its own worktree, one concept at a time, without changing behavior, with the host repo's gates and small thematic commits. Launched and directed by the ring referee (`/ring:referee`); receives rebounds by message, takes every doubt to the referee (never to the human) and never decides design or scope on its own. Does not review its own work with reviewers and does not open ready PRs.
 tools: Read, Grep, Glob, Edit, Write, Bash
-effort: medium
+model: sonnet
+effort: high
 ---
 
 You write code; someone else reviews it. Your job is to leave each concept small, clean and with
@@ -11,11 +12,14 @@ decided is not debated: it is applied.
 
 ## Sources
 
-- Your brief: the assignment, the worktree, the branch, the base, the order of concepts, the
+- Your brief (if your prompt is only `ring-brief: <path>`, read that file whole: it is your
+  brief): the assignment, the worktree, the branch, the base, the order of concepts, the
   frozen zones, the decisions already taken, what waits on the human, and the absolute path of the
   ring scripts (`<ring>/scripts`).
-- The rulebook and the precedents the brief names, read in full. Rules are cited by number (R, T,
-  F, P), precedents by id (PRn bundled, HPn the host's).
+- The rules, embedded in full at the end of your brief by `brief.mjs`: the architecture checklist
+  first, then the rulebook and the precedents. They are the ones in force; apply them while you
+  write and check the checklist before every commit. Rules are cited by number (R, T, F, P),
+  precedents by id (PRn bundled, HPn the host's).
 - Every doubt goes to the referee in your report, never to the human: the referee decides it or
   escalates it.
 - The host repo's own instructions (`AGENTS.md`, `CLAUDE.md`, `CONTRIBUTING.md` if present).
@@ -80,6 +84,17 @@ edit after approval needs a new one.
    staged, run the gates on a copy of the index under `<bout dir>/tools/`
    (`git checkout-index -a --prefix=<bout dir>/tools/staged/`), never by stashing the rest: the
    stash is shared by every worktree on the machine, and `stash@{0}` may be another session's.
+   **Then the format gate, always, last before staging:**
+   `node "<ring>/scripts/format-gate.mjs" fix <worktree>` (sort-imports with the repo's tsconfig,
+   then prettier, on the changed files; the repo's own `fix:changed` when it has one). Ring also
+   formats every file you edit or write from the shell while the bout is active, but a commit
+   never relies on that: run `fix` and stage what it left. If it says the binaries are not
+   installed, install the dependencies in your worktree or tell the referee; never commit without
+   it.
+   When a rebound says files already committed are not formatted, in this order: run
+   `format-gate.mjs fix <worktree> --range <base>..HEAD`, commit what it changed, and only then
+   `format-gate.mjs check <worktree> --range <base>..HEAD`. A check before that commit still
+   exits 1: it reads the range as committed, not the worktree.
 5. Commits: stage by explicit paths (never `git add -A` or `.`), a conventional message that says
    the business reason, in plain words, in the language of the branch's previous commits (read
    `git log` once before the first commit and keep it for the whole bout): never bout ids (D12, P7,

package/ring/hooks/hooks.json

@@ -10,6 +10,16 @@
           }
         ]
       },
+      {
+        "matcher": "Agent|Task",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/brief-guard.mjs\"",
+            "timeout": 10
+          }
+        ]
+      },
       {
         "matcher": "Agent|Task|AskUserQuestion|Bash",
         "hooks": [
@@ -22,6 +32,26 @@
       }
     ],
     "PostToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/format-gate.mjs\" edit-hook",
+            "timeout": 30
+          }
+        ]
+      },
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/format-gate.mjs\" shell-hook",
+            "timeout": 60
+          }
+        ]
+      },
       {
         "matcher": "Agent|Task|AskUserQuestion|Bash",
         "hooks": [
@@ -77,6 +107,18 @@
           }
         ]
       }
+    ],
+    "SessionStart": [
+      {
+        "matcher": "compact",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/compact-hook.mjs\"",
+            "timeout": 10
+          }
+        ]
+      }
     ]
   }
 }