Harden M8 trust and guidance workflows

CLAUDE.md

@@ -79,10 +79,16 @@ Tools are YAML configs with:
 - `output`: Template for final output (e.g., `"{response}"`)
 - `input_schema`, `output_schema`: Optional tool-level JSON Schema contracts;
   schemas are validated when tools are loaded or created
+- `deprecated`, `deprecated_message`, `replacement`: Validated migration metadata;
+  replacements may be local names or `owner/tool` registry references
 
 Run `cmdforge inspect <tool> [--registry]` for the shared local preflight
 report. `cmdforge registry publish <path> --dry-run` runs local checks first
 and, when authenticated, the registry's publish-time checks without publishing.
+Normal publication uses the same checks as Stage 1, asks for confirmation in an
+interactive terminal, and then performs the Stage 2 mutation. The registry
+reruns deterministic conformance authoritatively and stores immutable audit and
+quality evidence for the published version.
 Inspect also shows inferred contract proposals and runs deterministic contract
 conformance when both tool schemas are explicit. Prompt outputs are synthesized
 from their schemas; code, nested-tool, and MCP steps are reported as unsupported
@@ -92,6 +98,8 @@ evidence to `conformance.json`. Later inspections and local publish dry-runs
 rerun the stored synthetic inputs and report state, coverage, contract, and
 normalized output changes. ToolStep preflight also compares the values the
 runner supplies with the called tool's input contract.
+Quality headlines exclude categories with missing evidence and are accompanied
+by evidence coverage plus checked/not-tested category states.
 
 ### Step Types