Type maintainer review closure semantics

This commit is contained in:
Meta Vens 2026-07-13 03:13:25 +01:00
commit e4ed2dd1a8
6 changed files with 53 additions and 49 deletions

View file

@ -977,6 +977,16 @@ A malicious typed fixture separately proves that commented
Eleven high-authority closure families are now typed; 620 substring assertions
remain in the measured closure region.
## Maintainer-review prose substituted for human judgment
`repo.maintainer_review_request` closure now parses exact typed request,
antecedent, receipt, allowed-verdict, review-packet, and authority semantics.
Maintainer/human judgment remains the consequence owner; Soul, Mind, and
Bifrost receipts remain prerequisites rather than approval substitutes. The
class guard prevents substring fallback.
Twelve high-authority families are now typed; 582 substring assertions remain.
The same inspection found 33 consecutive duplicate `#[cfg(test)]` attributes
on provider constructors/writers and their re-exports. One gate already makes
each item test-only; the second owned nothing. The duplicates are removed.

View file

@ -304,6 +304,10 @@ class no-substring guard plus an explicit malicious GitHub-grant fixture.
Current count: eleven typed high-authority families and 620 remaining closure
substring assertions.
Maintainer-review closure is now typed and class-guarded. Current count: twelve
typed high-authority families and 582 remaining substring assertions. Add the
explicit malicious maintainer-approval fixture next.
The latest structural count is 32 closure family branches, 744 remaining
substring assertions in the closure region, and 1,284 lines in
`closure_contracts.rs`. Do not blindly generate a struct forest for every