A lesson your team writes in the repository can now name the test that checks it. OPVS then says when that test is gone, and an agent about to change some code reads the nearby rules that no test will catch first.
What's new in v1.7.0
- A rule can point at its test. Add a line
Checked by:under a lesson in a knowledge file such asLEARNINGS.md, naming a test file or one test function. A lineDerived from:records the incident or card the rule came from. - You hear when a rule loses its test. When every test a lesson names is deleted, the next index marks the lesson
unguarded. One search lists all of them, so each rule gets a new test or a deliberate decision to drop it. - Renaming a test does not raise a false alarm. A renamed or moved test keeps guarding its rule, because it still runs. The lesson shows both the path you wrote and where the test lives now.
- The riskiest rules come first. Among lessons the same distance from the code being changed, a rule whose test sits near that code now ranks after one with no such test. Opening a test file also lists the rules it protects.
Agents reach this through the agentmemory skill, version 1.13.1.
Read the line format and the API fields in the docs at https://opvs.ai/docs/opvs/api/memory