Grace Verification

<skill>

<purpose>

Strengthen deterministic verification for modules and changes. Verification state lives in .grace/verification/index.xml and routed verification documents. Each durable module should have deterministic V-M-* coverage unless an explicit exception is planned.

</purpose>

<workflow>

• Read relevant .grace/graph anchors and current V-M-* entries.
• Identify scenarios, commands, test files, required log markers, and trace assertions.
• Ensure commands are deterministic and runnable from the project root or documented cwd.
• Update or propose .grace/verification changes through the active change plan.
• Run the commands and record fresh evidence in the response.

</workflow>

<cwd_contract>

When verification commands run from a workspace or package directory, add one direct <Cwd>relative/project/path</Cwd> child to the owning V-M-* entry. Keep declared <TestFiles><File>...</File></TestFiles> paths project-root-relative; the CLI uses Cwd only to compare them with cwd-relative command arguments.

</cwd_contract>

<evidence_contract>

Use <Marker> when module health must prove a runtime log or trace emission from linked implementation code. Use <TraceAssertion> for deterministic test or trace evidence that does not require runtime logging, such as pure functions, type-level modules, and core libraries. A non-empty marker or trace assertion satisfies the module-health evidence requirement; only authored markers require matching runtime emission and BLOCK_* evidence.

</evidence_contract>

</skill>