lib

Core libraries for Radroots
git clone https://radroots.dev/git/lib.git
Log | Files | Refs | README | LICENSE

commit b0526d0ea1514533e4f1a36b20e67cc3fc47f324
parent 4f2ec492696dd2d69da6d65f3026a4e0b264d29a
Author: triesap <tyson@radroots.org>
Date:   Sun, 21 Jun 2026 18:18:07 +0000

coverage: align contract documentation

Diffstat:
Mpolicy/coverage/policy.toml | 4++--
Mspec/README.md | 14++++++++------
2 files changed, 10 insertions(+), 8 deletions(-)

diff --git a/policy/coverage/policy.toml b/policy/coverage/policy.toml @@ -7,8 +7,8 @@ require_branches = true # Heavy-development baseline: required crates must hold at least 98% # coverage across executable lines, functions, regions, and branches. This is -# not a 100% coverage target. Temporary threshold overrides below 98% are not -# part of the active gate. +# not a requirement to reach 100% coverage. Temporary threshold overrides below +# 98% are not part of the active gate. [overrides.radroots_log] require_branches = false diff --git a/spec/README.md b/spec/README.md @@ -183,12 +183,14 @@ Coverage governance is defined under `policy/coverage/`: - human policy notes: `policy/coverage/POLICY.md` - per-crate profiles: `policy/coverage/profiles.toml` -Required Rust crates are gated at `90/90/90/90` (exec lines, functions, -branches, regions), with branch records required unless a crate-specific policy -override marks branch coverage as not applicable because no branch records are -measured. This is not a 100% coverage target. Temporary crate-specific -overrides below 90% or branch-record presence overrides must remain explicit in -the machine-readable policy. +Every non-SimpleX workspace crate is gated at `98/98/98/98` (exec lines, +functions, regions, branches), with branch records required unless a +crate-specific policy override marks branch coverage as not applicable and the +measured report confirms that no branch records exist. Crates are not expected +to reach 100% coverage during heavy development. Temporary crate-specific +threshold overrides below `98/98/98/98` are not part of the active gate, and +branch-record presence overrides must remain explicit in the machine-readable +policy. ## Release Policy