feat(OMN-13025): A-3 evidence-language guard — pre-commit blocks UI/e2e claims in docs/evidence/** without Playwright artifact

[jonahgabriel]

Summary

OMN-13025 (A-3): Adds reject-evidence-ui-claims pre-commit hook that enforces evidence-language honesty in docs/evidence/** markdown files.

OCC receipt PR: OmniNode-ai/onex_change_control#3247

Root Cause

PROCESS_FAILURE_RETRO.md §3.A (top-10 failure #1): the 2026-06-11 19:27Z evidence doc claimed "UI POST → full chain live" when only curl was run. This led to a false "done" declaration.

What This PR Adds

• .pre-commit-hooks/reject-evidence-ui-claims.sh — blocking hook (no warn-only mode per CLAUDE.md Rule Phase 3: Local Template System Implementation #5 + Rule Phase 7: Refinement & Optimization - Complete (10 Streams) #10)
• .pre-commit-config.yaml — wires the hook at pre-commit stage on types: [markdown]
• contracts/OMN-13025.yaml — OCC contract with dod_evidence
• tests/hooks/test_reject_evidence_ui_claims.py — 8 unit tests (TDD-first, all pass before implementation was written)
• tests/hooks/fixtures/evidence_language/ — 6 fixture files covering all reject/accept/ignore cases

Hook Behavior

Blocked claim patterns (case-insensitive) in docs/evidence/**:

• UI POST
• click
• full chain live
• end-to-end / end to end

A claim is allowed only when the document also references a Playwright artifact (playwright or test-results/ appears anywhere in the doc).

DoD Evidence

dod-hook-exists-executable:
  test -x .pre-commit-hooks/reject-evidence-ui-claims.sh
  → PASS (script present and executable)

dod-hook-wired-in-precommit:
  grep -q 'reject-evidence-ui-claims' .pre-commit-config.yaml
  → PASS (hook registered in pre-commit config)

dod-unit-tests-pass:
  uv run pytest tests/hooks/test_reject_evidence_ui_claims.py -v
  → 8 passed in 0.37s

dod-commit-blocked-on-overstatement:
  Hook rejects docs/evidence/*.md with "UI POST" and no Playwright reference
  → EVIDENCE_UI_CLAIM_UNVERIFIED raised (correct behavior)

Evidence-Source: OCC#3247
Evidence-Ticket: OMN-13025
Implementation-Head: db97023cf66d47ae4e97a8a1c6d383980b946d56
OCC-Receipt-PR: OmniNode-ai/onex_change_control#3247

[coderabbitai]

Warning

Review limit reached

@jonahgabriel, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 53 minutes and 49 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d3e97d65-172f-4eb6-a0be-71529f8671d8

📥 Commits

Reviewing files that changed from the base of the PR and between f18ee75 and db97023.

📒 Files selected for processing (10)

• .pre-commit-config.yaml
• .pre-commit-hooks/reject-evidence-ui-claims.sh
• contracts/OMN-13025.yaml
• tests/hooks/fixtures/evidence_language/accept_no_ui_claims.md
• tests/hooks/fixtures/evidence_language/accept_non_evidence_ui_claims.md
• tests/hooks/fixtures/evidence_language/accept_ui_post_with_playwright.md
• tests/hooks/fixtures/evidence_language/reject_click_no_playwright.md
• tests/hooks/fixtures/evidence_language/reject_end_to_end_no_playwright.md
• tests/hooks/fixtures/evidence_language/reject_ui_post_no_playwright.md
• tests/hooks/test_reject_evidence_ui_claims.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-13025-a-3-evidence-language-guard-pre-commit-on-docsevidence

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

⚠️ Hostile Reviewer — DEGRADED (informational)

Blocking findings (critical/error): 0
Total findings: 0
Models succeeded: none

Note: All reviewer models failed or were unavailable. Degraded results are informational during the pilot phase (OMN-8524) and do not block merge. Error: cli_review exited non-zero (all models failed or binary error)

---

Gate semantics (pilot phase)

Verdict	Meaning	Blocks merge?
passed	No critical/error findings	No
blocked	CRITICAL or ERROR findings found	Yes
degraded	All models unavailable (infra)	No (pilot)

Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)