You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The skill proviso-mutate measures whether your tests have
teeth. A new agent, proviso-mutator, reads the spec tree and the
code, never the tests, and writes one small slip per rule (a guard
inverted, a refusal skipped, a boundary moved by one), plus a few in
code no rule covers. The skill runs your tests against each slip in a
worktree of its own, reports the share caught and every survivor, and
proposes for each whether it is a hole in the tests, a hole in the
tree or a change nobody could observe. You decide each: holes in the
tests go to the testing agent, holes in the tree become a request for proviso-integrate. Records of runs are kept only in a folder you
name in .proviso/build.md. proviso update installs the skill and
the agent.
proviso pack --element <identifier> writes the context pack of
one element as the tree holds it, under a new heading # Element,
for a test written outside any amendment. It derives no element diff
and reads neither the amendment note nor git history.
Changed
proviso diff --json and proviso pack list the text of each added
or changed part as it stands now (text, and a Now block before
each Former block), so an added Examples row can be told from the
others, not only by its fingerprint.
The checking agent never reads the coherence file, so that a fresh
check does not lean on earlier runs.
The testing agent can also be started by proviso-mutate, with the
pack of one rule whose tests miss a case.
The notes for the skills, .proviso/build.md, now also ask where the
tests are and where records of mutation runs are kept. init never
overwrites your notes; add the lines yourself if you want them.
Fixed
proviso diff --since and proviso pack --since no longer run on a
spec tree whose manifest.sum names another model version: like
every other command, they now exit 2 where lint refuses the tree.
The tree at the revision gets the same check. A merge conflict after
the manifest's first line still does not stop them.
With --since, a symbolic link in the spec tree at the revision now
refuses the comparison, as lint refuses a link on disk; it used to be
skipped silently.