repo-mailbox v0.36.1 — release. Catalog ref now pins the v0.36.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ms-ai-architect v1.18.2 — release. Catalog ref now pins the v1.18.2 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ms-ai-architect v1.18.1 — release. Catalog ref now pins the v1.18.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Remove claude-design from the marketplace manifest and its catalog
README entry, and remove the playground-design-system entry from the
README. The catalog now lists 11 plugins.
Add scripts/check-public-links.mjs: fails when README.md or the
manifest links to an open/<name> repository missing from a tracked
PUBLIC_REPOS list. Chosen over the local retired-terms list because
that gate scans every tracked file, and historical docs plus
CONVENTIONS.md (which keep naming these repos on purpose) would hold
it red; a live visibility check could not be red before the repos
change visibility. Red on 5ba4a7a (6 hits), green after (0 of 36).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
okr v1.10.1 — release. Catalog ref now pins the v1.10.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
voyage v5.11.1 — release. Catalog ref now pins the v5.11.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.36.0 — release. Catalog ref now pins the v0.36.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Mirrors repo-mailbox's own badge (selftest_checks-1006 at 4fd1955, the
0.36.0 release commit). release-plugin.mjs refused the 0.36.0 dry-run on
the stale stat line before tagging; it now passes that pre-flight and
stops only at the not-yet-minted v0.36.0 tag.
check-versions shows 1 ERROR on repo-mailbox until the release moves the
ref: the gate reads the badge at the pinned v0.35.0 (978). That finding
is kind=stat for the plugin being released, which preflightErrors()
exempts - measured: preflightErrors(gate, 'repo-mailbox') -> [].
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
llm-security v8.1.3 — release. Catalog ref now pins the v8.1.3 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
voyage v5.11.0 — release. Catalog ref now pins the v5.11.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
llm-security v8.1.2 — release. Catalog ref now pins the v8.1.2 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
llm-security v8.1.1 — release. Catalog ref now pins the v8.1.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
claude-design 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>
Phase 9 la til 05-critique-iterate.md, saa foundation-referansene gikk fra
fem til seks. Maalt ved f596c83: 14 filer under references/ - seks foundation
(00-05) + aatte per-preset. Badgen leser references-14.
To steder, fordi stat-linja ellers ville motsi prosaen to linjer over:
:217 prosa five foundation -> six foundation (ugatet)
:220 stat-linje 13 -> 14 reference files (gatet)
Prosaen var korrekt for v0.1.0. Ugatede tall rotner naar ref-en flytter seg.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
repo-mailbox v0.35.0 — release. Catalog ref now pins the v0.35.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pluginens badge leser selftest_checks-978 ved 0.35.0 (fem suiter:
coord 257 + board 478 + route 73 + orders 116 + guard 54 = 978).
Katalogen sa 927. Badgen er kilden; katalogen rettes til den.
Ett tall paa README.md:235; resten av raden er urort.
Ordre 20260917T221924Z-6958712598-from-repo-mailbox, steg 2.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
llm-security v8.0.0 — release. Catalog ref now pins the v8.0.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ms-ai-architect v1.18.0 — release. Catalog ref now pins the v1.18.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
`claude plugin marketplace add` records no `autoUpdate` key, and Claude Code
only defaults it on for Anthropic's own catalogs. A release published here
therefore never reaches an already-registered machine on its own.
Adds a "Staying up to date" section after Install with the manual commands
(`claude plugin marketplace update`, `claude plugin update`) and a paste-ready
`extraKnownMarketplaces` settings block that turns auto-update on.
Measured on Claude Code 2.1.260 in an isolated CLAUDE_CONFIG_DIR profile:
- `marketplace add` writes {source:{source,url}} with no autoUpdate
- `autoUpdate: true` in extraKnownMarketplaces propagates to
plugins/known_marketplaces.json on next start
- negative control: `false` propagates too, so the probe discriminates
One place only; the 12 plugin READMEs are untouched.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Also correct the repo-mailbox stat line: catalog said 529 selftest
checks, plugin's own badge at v0.33.0 says 868 (check-versions.mjs
caught the drift as an ERROR before this commit).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
repo-mailbox v0.32.1 — release. Catalog ref now pins the v0.32.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.32.0 — release. Catalog ref now pins the v0.32.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
voyage v5.10.1 — release. Catalog ref now pins the v5.10.1 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.31.0 — release. Catalog ref now pins the v0.31.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.30.0 — release. Catalog ref now pins the v0.30.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.29.0 — release. Catalog ref now pins the v0.29.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-mailbox v0.28.0 — release. Catalog ref now pins the v0.28.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
config-audit v6.0.0 — release. Catalog ref now pins the v6.0.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
voyage v5.10.0 — release. Catalog ref now pins the v5.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.27.0 — release. Catalog ref now pins the v0.27.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Completes the two-repo release: v0.25.0 was tagged + pushed in the plugin
repo, and the catalog ref moves v0.24.0 -> v0.25.0. Before this, plugin.json
said 0.25.0 while the catalog still pinned v0.24.0 — a public unreleased bump
(check-versions WARN), leaving `board.sh --dispatch` written but uninstallable.
Stat line mirrored to the plugin's own badges at v0.25.0 (release-plugin.mjs
bumps ref + label but not stats, so the post-write gate ERRORed on both axes):
skills 3 -> 4 and selftest checks 433 -> 529. Both measured with
check-versions' own extractStatBadges/extractCatalogStats against
`git show v0.25.0:README.md`, with config-audit as a known-positive control;
skills=4 cross-checked against skills/*/SKILL.md at the tag. The new
`dispatch` bullet keeps the block's one-bullet-per-skill pattern intact.
check-versions: 12 OK, 0 WARN, 0 ERROR (was 11 OK, 1 WARN).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A4uewAg3byV6Z3TuaQfR7G
repo-mailbox v0.24.0 — release. Catalog ref now pins the v0.24.0 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
repo-standard removed both numbers from its own README prose to stop an
ungated figure going stale again, and gave a corrected unit for checks
(check-table rows, not exported functions). Self-measured at the pinned
v0.11.2 tag per the catalog's own badge-less-axis convention: checks =
table rows (README.md:68-87, 20 — their own grep recipe overcounts by
hitting a second table in the file), tests = `node --test` (245/245).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WPstjCdfFm5dUWFC3pFTNE
repo-standard v0.11.2 — release. Catalog ref now pins the v0.11.2 tag so `claude plugin update` resolves the release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Post-write gate caught the selftest-check stat line stale again (412 -> 433,
read from the plugin's own badge at v0.23.0). Tag minted+pushed on bf11cbf.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RQPdPvk1pnB1MNdsvUanFD
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
A visitor could see that this repository has tests but not how to run them.
Adds a Tests section naming the command, and states that the migration test
files under docs/ are an archive rather than part of the suite.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0141o7P9gFCDxURKyc2cW7mc
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
The ref bump in 2b38c27 moved graceful-handoff v3.1.0 -> v3.2.1, and that MOVED
this axis out of the gate's reach. At v3.1.0 the plugin carried a `tests-30`
shields badge, so `30 tests` was mirrored and enforced. At v3.2.1 the badge set
is version / platform / skill-1 / STATE--helper-deterministic / license -- no
tests badge -- so the claim became ungated in the same commit that made it wrong.
Measured at the pinned tag per the calibrated rule in CLAUDE.md (`ℹ tests` from
`node --test`, in a `git archive v3.2.1` extract, never the sibling worktree):
48 tests. The catalog understated by 18.
Badge coverage therefore moves 27 gated / 15 ungated -> 26 / 16 across the same
42 axis-claims; `1 pipeline` was already ungated (it is alt-text over a
deterministic-helper badge, not a count). This is the re-measurement pass
CLAUDE.md requires whenever a ref moves -- not a hand-edit to silence the gate,
which stays silent on an axis it cannot see.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XPz4FNKSn2QwoMhRFn4WNo
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>
The catalog understated repo-mailbox's selftest count. Source of truth is the
plugin's own badge at the PINNED ref: `git show v0.20.3:README.md` line 17 says
`selftest_checks-406` (coord 191 + board 142 + route 73 = 406). The catalog said
398, measured at v0.20.2 before coord-selftest went 183 -> 191.
Flagged by repo-mailbox via coord; check-versions.mjs had it as the only ERROR
in the gate. That mattered beyond the stale number: release-plugin.mjs:200 calls
the gate through execFileSync, which throws on exit 1 -- AFTER writing
marketplace.json and README.md but BEFORE committing. Any `--write` run would
have landed a half-state, so this had to be green first.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XPz4FNKSn2QwoMhRFn4WNo
