Mw improve metrics analyis zazz

[zazzcode]

Pull Request

Linked issue

Closes #

Zazz Context

• Spec: .zazz/specifications/mw-improve-metrics-analysis-zazz.md
• Proposal / feature / architecture:
  • .zazz/proposals/code-review-graph-token-efficiency-and-turso-engine.md
  • .zazz/architecture/crg-architecture.md
• Execution notes:
  • .zazz/execution/mw-improve-metrics-analysis-zazz-run-log.md
  • .zazz/execution/pr219-improvements-HANDOFF.md

WHY

CRG review packets need to be more useful for Zazz-style multi-axis review without forcing agents to read broad source files first.

This PR makes review evidence more portable, budgeted, scoped, and standards-aware. It also adds advisory review-quality signals for the kinds of issues that PR-review agents can miss when they only inspect changed files: SQL wrapper/tSQLt contract drift, service-layer DB integration gaps, HTTP route/doc/test status mismatches, applicable standards, and ambiguous review text that needs reconciliation.

WHAT

• Adds compact review projection support and review-context behavior for lower-noise PR analysis.
• Adds advisory contract/standards signals in CRG review output.
• Adds configurable test-gap suppression and clearer context-savings metadata.
• Adds regression coverage for review advisory signals and budget truncation.
• Updates CRG command docs and usage docs.
• Adds .zazz/architecture/crg-architecture.md with Mermaid architecture and flow diagrams.
• Vendors a code-review-graph skill and expands pr-review axis guidance, findings reporting, and axis artifacts.
• Adds execution/spec docs for this Zazz deliverable.
• Updates the PR template to use Zazz context instead of Avaza/Jira tickets.

Instructions for Reviewers

Focus review on:

• Whether the compact review payload remains backward compatible for existing callers.
• Whether the new advisory signals are specific enough to help review without creating noisy false positives.
• Whether budget truncation keeps advisory rows bounded.
• Whether standards matching is useful while staying advisory.
• Whether the Zazz skill/docs changes match the intended CRG-assisted PR-review workflow.
• Whether the PR template fits this fork’s no-ticket Zazz workflow.

For CRG validation, inspect:

uv run code-review-graph review-context --repo . --base main --max-tokens 4000