git:20261022.e2220d6 to git:20261023.95dc2aa

+ **Capybara Toolbox** is a Claude Code plugin marketplace (`.claude-plugin/marketplace.json`, name `capybara-toolbox`). Each plugin lives in `plugins/<name>/` and is self-contained. The first plugin is **ar-board**: a local approve/reject web panel; the second is **publish-check**: a read-only scan of a git repository for leaks before it goes public; the third is **tidy-board**: stale branches, worktrees and stashes as cards on the ar-board engine, deleted only on approval; the fourth is **housekeeping**: small tools (doc-truth, handoff and todo-sweep) that keep a repository and a work session honest without editing tracked files (handoff and todo-sweep write only to their own `.handoff/` and `.todo-sweep/` folders); the fifth is **header-footer**: a hook-computed header line at the top of every Claude reply and a configurable status-line footer. All are Python stdlib only (publish-check, tidy-board and housekeeping also need `git`; header-footer uses `git` only for its branch and repository fields), with no build step, no package manager and no linter. Docs are English with Portuguese counterparts; the skills (`SKILL.md`) are English, while everything the user sees is English by default and pt-BR on request: the panel UI, the cards and reports the tools generate, handoff's notes, header-footer's weekday and the CLI messages of every script (`lang` in a batch or in `header-footer.json`, `--lang` on every command, the `CAPYBARA_LANG` environment variable, an EN/PT toggle in the panel's header; publish-check prints English only). `base` is the main branch.

+ One plugin, one version, several skills added one release at a time; every script of the plugin carries the plugin's `VERSION` and a release bumps them together, which `plugins/housekeeping/tools/sync.py` enforces. The scripts are standalone (`python3 -I` does not put their folder on the path), so the few helpers they share (git wrapper, fingerprint, config loader) are duplicated on purpose. **doc-truth** (`plugins/housekeeping/skills/doc-truth/scripts/doc_truth.py`) reads every git-tracked `.md` and reports cited paths that are not in the git tree, broken links and anchors, EN/PT-BR heading-level drift, and versions or plugin lists that disagree with the manifests; it is read-only, never runs a documented command and never uses the network. The repository's own `.doc-truth.json` excludes history (`docs/plans`, `docs/refinements`, CHANGELOGs, `backlog.md`) and the generated `dist/`, and lists run-time file names in `ignore_paths`. **handoff** (`plugins/housekeeping/skills/handoff/scripts/handoff.py`) writes `.handoff/<date>-<time>.md`: the git facts come from `collect`, and every typed citation in the agent's draft (`commit:`, `branch:`, `file:`; an untyped backtick is prose) is checked, kept and marked `[not verified]` (pt-BR `[nao verificado]`) when it fails; the note ends with a JSON data block that `resume` compares with the repository. `.handoff/` is git-ignored, and `collect` leaves it out of the facts so that writing a note does not change the state it records. **todo-sweep** (`plugins/housekeeping/skills/todo-sweep/scripts/todo_sweep.py`) finds `TODO`/`FIXME` inside comments of tracked text files, ages each with `git blame` (a repository's root commit is a blame boundary but has a real age; only a shallow clone's boundary does not), writes an ar-board batch (labels Resolve, Discard, Keep; pt-BR Resolver, Descartar, Manter) plus a `scan.json` sidecar, and `report` (which needs a concluded board of the current round) writes a read-only report and remembers Discard and Keep in `.todo-sweep/ledger.json` by a hash of file, text and occurrence; it never edits a source file. `capy_board.py` next to it is a **generated byte copy of the ar-board engine** (the panel); `plugins/housekeeping/tools/sync.py` regenerates it, so after editing or releasing `ar_board.py` run the ar-board sync and then this one. `.handoff/` and `.todo-sweep/` are git-ignored, and both tools refuse such a folder when it is a symlink.

+ One script, `plugins/header-footer/skills/header-footer/scripts/header_footer.py`, is the header hook (`header-hook`), the status-line command (`footer`) and the CLI; its `VERSION` is the version source, kept in sync by `plugins/header-footer/tools/sync.py`. It is the only plugin that ships hooks: `hooks/hooks.json` registers `header-hook` on `UserPromptSubmit`, whose output (the `<reply-header>` line plus the instruction to copy it) becomes turn context, and `state-hook` on five events to feed the footer's `state` field. `hooks/hooks.json` must equal the script's `PLUGIN_HOOKS` table (a test enforces it), which is also what `wire-hooks` writes into `settings.json` for installs without the plugin system. A plugin cannot set `statusLine`, so `on footer` copies the script to `<claude config dir>/header-footer/header_footer.py` (the plugin cache path changes on every update) and points `statusLine` there; `status` reports a copy older than the plugin. The config is `header-footer.json` in the Claude config directory and every path honours `CLAUDE_CONFIG_DIR`, which is how the tests isolate themselves; its optional top-level `lang` (the `lang` command) chooses the language of the messages and of the `weekday` field, while the footer and the instruction sent with the header line are the same in both languages. Two header hooks for one prompt (the plugin's and an older `settings.json` entry) print once, through an `O_EXCL` marker keyed by session and prompt. The footer is a port of a Node status line and must stay byte-identical to it: `half_up` reproduces JavaScript's `Math.round`, which Python's `round` does not.

+ - Every user-visible string of the panel lives in the `I18N` table of `ar_board.py` (`en` and `pt-BR`, the latter with accents; a test pins equal keys and placeholders and another flags any literal left in `PAGE`). The tool tables (`TEXT` and `LABELS` in the tidy-board and todo-sweep scripts) carry both languages too; everything a script parses (ids, proofs, decisions, ledger words, JSON keys, `age_reason` codes) stays language independent. The CLI messages of every script but publish-check live in a `MSG` table per script (`en` and `pt-BR`, both plain ASCII, so the pt-BR side stays accent-free; a test per script pins the parity and an AST guard flags any Portuguese literal left in the functions that print); the language resolves `--lang`, then the batch's or scan's `lang`, then `CAPYBARA_LANG`, then `en`, and only `main()` sets it. Card content may be any Unicode.