release: v0.10.4

[Rome-1]

Unblocks rf-f5is. #250 merged to a public main on 2026-09-11 and the registries have served 0.10.3 ever since — a fix disclosed and not shipped, for an externally reported finding. Cutting the disclosure line from that PR body didn't undo the disclosure: merging to a public repo publishes a diff naming exactly which key shapes were undetected and at what lengths.

Contents

commit	PR
6839663	#250	rf-f5is — OpenAI + Supabase rules in the regex engine
14eb1c6	#246	rf-3n1i — allowed_patterns in Python under the policy floor, plus two allowlist bypasses

Scope of the bump

Four files, found by searching for the current version rather than trusting the validator's list — #238 exists precisely because a partial bump passed validation once:

node/package.json
python/pyproject.toml
node/resources/rafter-security-skill.md                  (gated ClawHub manifest)
python/rafter_cli/resources/rafter-security-skill.md     (gated ClawHub manifest)

Deliberately not bumped. The repo carries six other SKILL.md files with their own frontmatter versions — rafter-code-review at 0.7.0, rafter-secure-design / rafter-skill-review / rafter at 0.1.0–0.7.0. Those are independently versioned skill resources, not package-version mirrors; moving them to 0.10.4 would be wrong. "Every manifest" is not "every file with a version" — the two that are package mirrors are the two validate-release gates.

Verification

Ran validate-release's own checks locally rather than trusting the edit:

• node and python versions match at 0.10.4 ✅
• both gated skill manifests match the package version ✅
• and the check validate-release does not do, which is the one that actually bites: 0.10.4 is not already on the registry ✅

main's version equalling the published version is what made the last two gaps unpublishable — validation passes and the publish job fails later, at the registry, with an error that doesn't say "you forgot the bump". Worth adding that check to validate-release separately; it's one npm view call and would have caught all three occurrences before the prod push rather than after.

Not included

se-u7c2 and se-riqb are Stage 0 items the mayor asked to fold in. I've asked diffie which of us writes se-riqb (it touches secret_patterns.py, the file #250 just changed) rather than both of us editing it. If they land before this merges they ride along; if not, they go in the next cut rather than hold a public disclosure any longer.

Does not push prod. PR #251 (main → prod) is open and is Rome's to merge.