Repository navigation
Fixes found by evaluating a real NestJS and Next.js remaster with Evaris 0.4.0
and Invaris 0.5.0.
-
Fixed: an
allowedChangesorprotectedPathsentry always matches the
identical path. 0.4.0 read literal paths as patterns, so a listed Next.js
route such asapp/products/[id]/page.tsxno longer matched itself and an
unchanged experiment failed source authorization on a correct delivery. -
A failed
source-authorizationcriterion now has a catalogue message and
writesevidence/source-authorization.json, listing each unauthorized path,
how it changed and which rule it broke. Before, it failed with no message or
evidence. -
With verification,
allowedChanges: ["**"]is accepted whenprotectedPaths
also coversinvaris.json, so the deny-list form works with Invaris. Pattern
errors name the case, field and pattern instead ofPATH_UNSAFE: experiment. -
verification.dependencieslinks directories such asnode_modulesinto the
verification scratch root, so an Invaris campaign whose harnesses declare
workspace dependencies can run against the imported tree. Before, such a
campaign was refused withworkspace_prepare_failed. -
Campaign verification checks the complete frozen experiment and repeat set,
recomputes the native decision, and shows each experiment verdict in reports.
The real-binary CI matrix now includes tagged Invaris 0.5.0. -
Comparisons check verifier executable and input digests. Use
--left-preparationand--right-preparationto pair explicit trials. -
Import can derive observed Claude Code session metadata and confirmed
instruction reads from a retained stream JSON transcript.