Skip to content

0.8.1 — Adoption Proof + Friction Diet

Choose a tag to compare

View all tags
@qwerfunch qwerfunch released this 05 Jul 17:05
· 281 commits to main since this release
v0.8.1
a633378
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Parallel work stops conflicting, every save gets ~12× faster, and the numbers stop lying.

Heads-up: everything migrates on its own — the attestation file at your first green gate, sync stamps at the next sync, the CLAUDE.md section at the next clad update. Just update the npm engine and the editor plugin together: an older plugin reads the new attestation file as "missing entries" until it catches up. Noisy, harmless, gone after the update.

Added

  • An adoption verdict. clad measure --sessions now answers a question we couldn't: does the agent actually pull context, or does it just receive what we push? Pushes score nothing, empty lookups score nothing, and silence is shown rather than hidden. Our own first number: 64 cycles, 0 pulls — embarrassing, and exactly what decides 0.9.
  • Mid-merge guards. A half-merged tree can never be stamped as verified — clad done refuses, the gate holds its write until the merge settles.
  • One merge rule. Conflict in a derived file? Keep either side, finish the merge, run the gate. The gate rewrites the truth; your hands never should.

Changed

  • The verification record keys one line per file, not per feature. Branches that touch different files now merge clean — in the GitHub PR view too. This was the root of most conflicts.
  • Every save: ~6s → ~0.5s. The two subprocess scanners moved to turn-end and commit gates. Nothing skipped, just later.
  • The README promises only what the record keeps — corrected in all four language variants.
  • One name per concept. Old docs deleted or shrunk to abstracts; the glossary settles the confusions that kept coming back — check vs gate, the card family, slice vs working set.

Fixed

  • Sync no longer stamps a date nobody reads into spec.yaml — and no longer causes a merge conflict with it.
  • No message recommends a removed command anymore, and a tripwire keeps it that way.

Shipped only after A/B-testing the whole cycle against the published 0.8.0 — same violations, same merges, live agents on both engines. The old engine really did stamp a half-merged tree; this one refused. Full verdict: docs/ab-evaluation/case-081-cycle-conformance.md.

Assets 2
Loading