What's new

This page sums up the last three RCF Lite releases, newest first.

0.42.1, 12 November 2026

Security and fixes

• A frozen tree with nothing pending reads ready: right after rcf define freeze, with no document changed, added or removed, rcf define readiness and the viewer's Readiness tab no longer block on it.

0.42.0, 10 November 2026

Features

• rcf audit test-strength judges Python sources: a symbol-level Code Node on a .py file is read through your machine's own python3, 3.9 or later, with nothing installed and none of your code imported.
• rcf define validate resolves a Code Node #symbol on a Python def or async def, so a renamed function reads as stale code.

0.41.0, 7 November 2026

Features

• Test strength is a report, not a gate: rcf build finalise and rcf build verdict test with --result PASS no longer refuse a failing or blocked test-strength record.
• rcf build finalise refuses a test-strength record that is not a valid TestStrengthReport v1 for the reviewed head.
• The managed agent-instructions block states the twelve rules of the build cycle, and rcf doctor reports a 0.40.1 block stale until rcf doctor --fix or rcf init rewrites it.
• rcf guidance build-cycle carries the twelve rules, and the rcf build bundle runbook follows them.
• The help for rcf build finalise, rcf build verdict test, rcf audit test-strength and rcf audit separation follows these changes.
• Removed: the package no longer ships its own rcf/ folder, which nothing read at run time; the README's link to the repository's own chain now points at GitHub instead.
• Removed: the package ships no development-chain material. Source comments, guidance, the package changelog and the release feed no longer name the people who reviewed the work or carry internal tracking ids, and src/ruleset/ruleset.json loses its unread provenance block.

Every release, with its full notes and any action needed, is on the Changelog.