-
v3.3.0 - the record you plan from
StableSome checks are pendingtest / node-test (git, 22) (push) Waiting to runtest / node-test (git, 24) (push) Waiting to runtest / node-test (other, 22) (push) Waiting to runtest / node-test (other, 24) (push) Waiting to runtest / node-test (planning, 22) (push) Waiting to runtest / node-test (planning, 24) (push) Waiting to runtest / node-test (prose, 22) (push) Waiting to runtest / node-test (prose, 24) (push) Waiting to runtest / node-test (review, 22) (push) Waiting to runtest / node-test (review, 24) (push) Waiting to runtest / node-test (routing, 22) (push) Waiting to runtest / node-test (routing, 24) (push) Waiting to runtest / self-verify (push) Waiting to runtest / typecheck (push) Waiting to runreleased this
2026-08-15 13:59:28 +00:00 | 789 commits to main since this releaseThe evidence Cadence plans and reports from is itself checked this cycle: the
capture queue that silently dropped filed work, the run record that could not
join a provider call to the fire that made it, and the claims the docs make
about the code.Fixed
-
/cad-captureno longer writes where recall cannot see it. Five items
filed after the 2026-08-08 archive block landed below a heading the corpus
walk does not visit and were invisible to/cad-plan's recall until they
were lifted by hand, one of them a[high]finding that a tuning rule can
never fire. The writer lands inside the walk, the tag reader admits every
shape the writer emits,/cad-healthreports any bullet outside the walk,
and a concurrent append can no longer lose an update. -
The run record joins.
corris fire-scoped rather than phase-scoped, so
a provider call attributes to the fire that made it; a terminal event's
--roleis validated against its paired dispatch, so a role with zero
dispatches can no longer render carrying a token total; andrecordedcounts
matched dispatches rather than token-bearing events, so a replayed terminal
stops hiding a missing report. -
String-form
protected_branchesis honored by all four readers, the
fence-blind## Phasesand## Activescanners are guarded, and a blank
--rootis refused consistently rather than linting the cwd and returning
ok:true. -
Fourteen stale claims are corrected at their source.
README.md,
METHOD.mdandcadence-core/workflows/plan.mdstated aplanreview as
advisory atshippedwhereroute-table.jsonresolvesoff;
/cad-new-projectand/cad-adoptreported the config they had just copied
as turning plan check on when the template ships it off;
config-catalog.mdpublished aRiskknob category with zero rows behind
it;recall.mdnamed two callers where the code makes three; and
METHOD.mdandINTERNALS.mdstill described the dispatch-time risk floor
and its per-surface waivers, both retired in v2.7.0.
Added
-
A second
/cad-docs-verifysweep, transcribed and dated.
.planning/DOCS-CLAIMS.mdnow carries 933 rows over 32 files, each with a
generatedruncolumn and a live line cite, 373 line re-pins, and the seven
rows phase 4'strace closeinvalidated rewritten to the live call rather
than silently re-pinned. -
Two prose assertions that derive both sides from the tree, in
cadence-core/bin/prose-agreement.test.mjs: README's skill, role and
rung-file counts measured againstskills/andagents/, and a check that
PROJECT.md's### Activedeclares its milestone before naming any other
version. Both were shown to redden on a pre-fix input. -
planning.mjs criteria-size, so the 3-7 acceptance-criteria ceiling
/cad-contextstates is counted rather than merely written down.
Changed
-
One
trace closesubcommand replaces eight workflow files' restated close
prose,trace renderis bounded by default, and the round-trips measured
as unbatched now issue as one call. -
The
REQ_IDdocumentation states the asymmetry that is live rather than
the head-anchored limitPRS-02removed:REQ_ID_EXACTadmits a
digit-leading category whileREQ_ID_TOKENkeeps its letter head, so an
unbolded2FA-01remains invisible to the prose scan.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-