Tag v0.22.0 created and pushed to repo-mailbox. Also corrects the
catalog's stale selftest-check count for repo-mailbox (402 -> 412)
to match the plugin's own badge, caught by the post-write gate.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QugnZfg8Jpi7tHNmoT7Uqp
repo-standard v0.11.1 — release. Catalog ref now pins the v0.11.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-standard v0.11.0 — release. Catalog ref now pins the v0.11.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
okr v1.10.0 — release. Catalog ref now pins the v1.10.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Two stat corrections plus a ref bump, together because release-plugin.mjs left a
half-state that could only be closed with the gate green.
repo-standard v0.5.0 -> v0.9.0 (operator-approved). Approved as "bump to the
latest tag, v0.8.1", but v0.8.1 became unreachable while the session ran:
plugin.json had moved to 0.9.0, and the helper refuses a target its plugin.json
does not match ("asked to release 0.8.1 — bump plugin.json first"). v0.9.0 was
tagged at 22:05 today (1dfd408), plugin.json == README badge == 0.9.0, so it is
a consistent released version and the faithful reading of the approval. Same
breaking v0.8.0 boundary that was already accepted, one minor further.
Ungated axes re-measured at the new ref, per CLAUDE.md: tests 135 -> 170
(`node --test` on a `git archive v0.9.0` extract), checks 14 -> 14 (the README
check table still has 14 rows; v0.6.0-v0.9.0 re-levelled finding CODES under
existing rows). Badges at v0.9.0 are version/platform/skills-1/license, so
both numbers stay ungated and rot silently — they were measured, not carried.
repo-mailbox 406 -> 402. This reverses the refusal sent from here 20 minutes ago
(and d60ad40's 406), and the reversal is legitimate rather than a flip-flop: 402
was wrong then and is right now because the REF MOVED underneath it. When
repo-mailbox asked, v0.21.0 did not exist as a tag and the catalog pinned
v0.20.3, whose badge says 406 — writing 402 then would have produced a hard
ERROR and a dangling ref. A parallel session has since bumped the ref to
v0.21.0 (9d04179), and the badge AT that ref says 402. The catalog documents
what installs, so the number follows the tag.
That parallel commit knowingly landed a red gate for the catalog to clean up;
this commit is that cleanup. Gate now: 12 OK, 0 WARN, 0 ERROR, 0 SKIP.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XPz4FNKSn2QwoMhRFn4WNo
repo-mailbox removed route.sh's --opus-xhigh-failed flag and Fable rows
5-6 as a rubric outcome (operator policy decision) - a hand-written
override now, never produced by the calculator.
Known gate result: check-versions.mjs reports 1 expected ERROR for
repo-mailbox (catalog stat line still says 406 selftest checks, plugin's
own badge now says 402 - the release dropped three checks that tested a
command shape row_advisor() can no longer produce). repo-mailbox already
sent a coord-send correction superseding its earlier 406 notice with the
current 402; that stat-line prose is catalog's to update, not committed
here per the repo boundary. repo-standard's pre-existing WARN (v0.5.0 ref
vs 0.9.0 plugin.json, untagged) is unrelated and untouched.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ap1WKHCDPcSfpjo4ds2dQX
graceful-handoff v3.2.1 — release. Catalog ref now pins the v3.2.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
release-plugin.mjs wrote the ref + version-label bump; committing by
hand because the closing check-versions.mjs gate blocked on repo-mailbox's
own stale stat-line prose (398 -> 406 selftest checks), which is not this
script's job to edit. Correction queued to catalog via coord message
20260809T191518Z-4678230575-from-repo-mailbox.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CHmf1VfCvaYXamJxe5y6Vt
Ref bump requested by repo-standard (two coord messages: v0.4.0 then
v0.5.0, superseding). Stat line re-measured at the v0.5.0 tag per the
badge-mirroring rule: checks table unchanged at 14, tests 111 -> 135
(node --test on a git-archive extraction of the tag, "ℹ tests" not
"ℹ pass"). check-versions.mjs: 12 OK / 0 WARN / 0 ERROR / 0 SKIP.
okr 1.9.0 "Styringssloeyfa lukkes" -- release. Catalog ref now pins the v1.9.0
tag so `claude plugin update` resolves the release.
Stat-linja rettet i samme slag: 14 -> 16 commands. Driften ble skapt av denne
releasen selv -- fase D la til /okr:rapport og /okr:arkivklar -- og
release-plugin.mjs flagget den som ERROR i stedet for aa gjette, som er riktig
oppfoersel. Tallet er verifisert mot disk (`ls commands/*.md | wc -l` = 16) og
mot pluginens egen badge, ikke lest fra prosa. Agenter (7) og hooks (3) uendret.
check-versions: 12 OK, 0 WARN, 0 ERROR, 0 SKIP.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EQ9kk8ZewiXsv5N98XFNwN
repo-standard v0.3.0 — release. Catalog ref now pins the v0.3.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-standard v0.2.2 — release. Catalog ref now pins the v0.2.2 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-standard v0.2.0 — release. Catalog ref now pins the v0.2.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-standard v0.1.1 — release. Catalog ref now pins the v0.1.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-standard was tagged and pushed in its own repo but never pinned here, so
its documented install command could not resolve for anyone (its own gate
reported ERROR INSTALL-NOT-IN-CATALOG against us).
Manifest entry added by hand (release-plugin.mjs rewrites an existing entry,
it cannot create one); the ref was written by release-plugin.mjs, not by hand.
README block written to catalog house style from the text repo-standard
proposed, with one correction: the gate composes TWELVE checks, not fourteen
(classifyRepo spreads 12 check* calls at v0.1.0, and their own README table
has 12 rows). Stats measured in an extraction of the v0.1.0 tag: 1 skill
(badge), 12 checks, 84 tests (node --test: tests 84 / pass 84).
check-versions.mjs: 12 plugins — 12 OK, 0 WARN, 0 ERROR, 0 SKIP.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01THEvHPWM11RupX24wBGKLu
repo-mailbox v0.20.1 — release. Catalog ref now pins the v0.20.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.19.0 — release. Catalog ref now pins the v0.19.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ai-psychosis v1.2.2 — release. Catalog ref now pins the v1.2.2 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.18.0 — release. Catalog ref now pins the v0.18.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.17.0 — release. Catalog ref now pins the v0.17.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.16.0 — release. Catalog ref now pins the v0.16.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.15.0 — release. Catalog ref now pins the v0.15.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.14.0 — release. Catalog ref now pins the v0.14.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
route.sh now writes --advisor opus into the startup command it emits,
per row and on a need: always on the Sonnet rows (capability lift, which
is what makes the quota fallback safe to take), on the Opus rows only at
costly/one-way stakes, never on Fable (the CLI rejects it).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X8N8hQEJSWWtieWUx37txT
repo-mailbox v0.12.1 — release. Catalog ref now pins the v0.12.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The voyage entry was 625 chars against a field where the second-longest is
linkedin-studio at 274 and the median is 163 (measured 2026-07-31, n=11).
Roughly half of it was annotation-HTML implementation detail — scripts/annotate.mjs,
"modelled on claude-code-100x", pencil-toggle mode, Fiks/Endre/Spørsmål, Copy Prompt.
That belongs in the plugin's own docs; README.md:66 already carries the one-sentence
catalog-level version of it. Kept: the six phases, agent swarms, external research
triangulation, the adversarial-vs-independent-review distinction, and multi-session
resumption — the parts that distinguish voyage from any other pipeline in the list.
No gate covers this: check-versions.mjs does not inspect description length, so a bad
rewrite would still go green. Three variants were measured (189/237/328) and the
operator picked 237.
Verification: JSON parses, 11 plugins intact; check-versions 11 OK / 0 WARN / 0 ERROR
(exit 0); check-versions + release-plugin tests 28 pass / 0 fail; diff is 1 line.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wsm9DJmoiL5g9M8JXjFTE1
okr v1.8.2 — release. Catalog ref now pins the v1.8.2 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
config-audit v5.13.0 — release. Catalog ref now pins the v5.13.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.12.0 — release. Catalog ref now pins the v0.12.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.11.0 — release. Catalog ref now pins the v0.11.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.10.0 — release. Catalog ref now pins the v0.10.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.9.0 — release. Catalog ref now pins the v0.9.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.8.0 — release. Catalog ref now pins the v0.8.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.7.0 — release. Catalog ref now pins the v0.7.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
linkedin-studio v0.8.0 — release. Catalog ref now pins the v0.8.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.6.0 — release. Catalog ref now pins the v0.6.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.5.0 — release. Catalog ref now pins the v0.5.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
okr v1.8.1 — release. Catalog ref now pins the v1.8.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.4.0 — release. Catalog ref now pins the v0.4.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
okr v1.8.0 — release. Catalog ref now pins the v1.8.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The plugin repo moved from open/coord to open/repo-mailbox. Bumps the
entry name, source URL and ref together, and updates the README heading,
link and label to match.
Also corrects the per-plugin stat line: it claimed 48 selftest checks;
the actual count has been 70 since v0.2.2.
check-versions.mjs: 11 plugins, 10 OK, 1 WARN (pre-existing okr), 0 ERROR.
coord v0.2.1 — release. Catalog ref now pins the v0.2.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
coord v0.2.0 — release. Catalog ref now pins the v0.2.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Local inter-repo coordination mailbox — directed messages and broadcasts
between Claude Code sessions, injected as context at session start.
New plugin repo: open/coord, pinned at v0.1.0. check-versions: 11/11 OK.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HBbjgS5A55RVavoyjJC4FX
linkedin-studio v0.7.0 — release. Catalog ref now pins the v0.7.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
