What problem does it solve? Changes to the telic seam and ontology surface can silently fail because OntologyRegistry.create_object() returns (None, [errors]) instead of raising, so broken schema changes look green unless tests assert on the created object. This Skill provides a disciplined test procedure that proves provenance actually persists. ## Core Features & Use Cases - Targeted test sequencing: Runs focused pytest files for telic_seam, task_board, and telos_graph before a full-suite regression sweep diffed against a same-session baseline. - Enum round-trip validation: Enforces updating both the code-level whitelist and the ontology schema enum, with an explicit assertion that create_object() does not return None. - Adversarial test patterns: Provides fixture construction rules and adversarial patterns (topology round-trip, orphan proposals, method existence) plus a structured PASS/FAIL verdict block. - Use Case: After adding a new action_type enum value to ActionProposal, use this Skill to verify the dispatch is stored with the new value rather than silently falling back to "dispatch". ## Quick Start Verify my changes to telic_seam.py and ontology.py by running the targeted provenance tests and the enum round-trip check, then report the verdict block.
