This release includes 2 breaking changes for platform teams planning a safe upgrade.
Published 5d
Developer Productivity
✓ No known CVEs patched
✓ No known CVEs patched in this version
Topics
ai-coding-assistant
archetype
ast-analysis
claude-code
claude-plugin
code-conventions
+12 more
code-review
code-style
developer-tools
javascript
linter
mcp
mcp-server
prompt-engineering
python
ruby
rails
typescript
Summary
AI summaryPlan steps now require -> verify: clauses and unexecuted steps are listed under "Not verified".
Full changelog
Changed
- The ladder line carries two counts, so padding is unwritable. v4.5.12 told the model to
count rather than recall; a graded Rails re-fire then wrote "I read everyapp/file" over
15 of 19 — with its own 19-filefindoutput in context — proving exhortation inside a slot
does not hold where shape does. The line is now the fixed form "Ladder: used ... | skipped
... - reason | read N of M source files": "every file" cannot be rendered in it, and the
whole-read shortcut is judged against the real M, not the read subset. - Every plan step needs its
-> verify:clause, including the last ones — the steps that
lose the clause are empirically the ones that later go undone. - Unexecuted plan steps belong in "Not verified". The plan is a promise; a silently dropped
step (hostile-input probes that never ran) is a broken one unless it is named. - Numbers in evidence cells must come from a tool result — a plausible count written from
memory ("4 tests" for a 5-test file) is the same defect as a fabricated action.
Breaking Changes
- Every plan step must include a `-> verify:` clause, including the final steps.
- Unexecuted plan steps must be recorded in a "Not verified" section.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Chameleon
All releases →Beta — feedback welcome: [email protected]