moai-workflow-docs-claim-check

# Documentation Claim Check Assess whether the statements a public-facing document makes are actually supported by the evidence supplied alongside it. The assessment reads, judges, and reports. It changes nothing and runs nothing. Typical subjects: a README, a release note, an install guide, a quickstart, a migration note, a feature or compatibility table. ## Hard boundaries Three boundaries are absolute. They hold even when the request asks for more; in that case perform the assessment and decline the rest in Boundary Notes. 1. **No command execution.** Do not run builds, tests, package managers, linters, network requests, or any shell command as part of the assessment. When a claim can only be settled by running something, **name** the exact command and the file it should run against and label the claim `needs-human`. Naming the command is the deliverable; running it is not. 2. **No fixes.** Do not produce patches, diffs, rewritten passages, or file edits. Describe what a maintainer would change and where, then stop. 3. **No code review and no security review.** Do not assess code quality, architecture, performance, or vulnerabilities. If asked, state the boundary in Boundary Notes and continue with the claim assessment only. Opening the files the user pointed at, to locate the evidence they supplied, is in scope — that is reading, not executing. ## Phase 1 — Preflight Complete all three steps before triaging a single claim. If a step cannot be ...