docs(readme): surface readiness check, domain guidance, and offline-deterministic core

[madara88645]

What

The README predated several shipped capabilities. This refresh adds them without restructuring the document:

• Readiness Check added to What It Does, Key Features, and as a step in How To Use (the traffic-light banner honoring the compiled safety policy — feat(web): make ReadinessBanner a self-describing traffic light #894/[codex] prevent unsafe readiness-policy contradictions #910)
• Domain-aware guidance in the Expanded Prompt description: hand-curated Key considerations for recognized scenarios (SQL performance, uploads, auth, timezones, downloads, payments) and decisive follow-up questions (feat(compile): domain expertise that makes compile genuinely useful (0/6 -> 4/6 ADDS_VALUE) #906 and follow-ups)
• Coordinated-task decomposition noted on the Execution Plan bullet (feat(compiler): decompose coordinated tasks into plan steps (conservative) #903)
• Trust facts stated once: offline deterministic compilation with no API key, 1,700+ tests with QA regression gates, optional cloud path is OpenRouter-only

Scope

README.md only — 1 file, +14/−9. No code changes.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
compiler	Ready	Preview, Comment	Jul 2, 2026 9:55am

[cursor]

PR Risk Assessment

Risk level: Very Low

Code review required: No

Reviewers assigned: None (not required)

Approval: Not applicable — PR is already merged. Would have been eligible for automation approval under Very Low rules.

---

Evidence (diff-based)

Signal	Finding
Files changed	1 (README.md)
Lines	+14 / −9
Production code	None
Tests / CI config	None
Infra / auth / DB	None

What changed

Documentation-only refresh of the public README:

• Documents Readiness Check, domain-aware guidance, and coordinated-task decomposition in feature descriptions
• Adds trust facts (offline deterministic core, test count, OpenRouter-only cloud path)
• Adds a readiness-banner step to the “How To Use” flow

No executable logic, configuration, prompts used as model instructions, or shared runtime surfaces were modified.

Decision

• Very Low → safe to merge without dedicated review
• No CODEOWNERS file in repo; no codeowner gate
• 0 reviewers currently assigned; none added (below Medium threshold)

CI

All checks passed (Smoke, CodeQL, Snyk, PR Tests, Vercel).

  

_{Sent by Cursor Automation: Assign PR reviewers}