docs: customer-facing README and relocated agent procedure

[seonghobae]

Summary

Rewrite the root README for buyers and operators. Noema stays a leaf product that runs alone and is callable as a published HTTP API plus contracts/orchestrator-gateway.json. Hub-and-leaf calls from naruon and gyeot (곁) are documented as the supported MSA path (따로 또 같이), not a merge.

Bot, writer, and hourly-loop procedure is relocated — not deleted — to CONTRIBUTING.md and docs/development/contributor-and-agent-procedure.md.

What changed

• Customer README now leads with what Noema is, how to run it alone, how a host calls /health /ready /exchange and the gateway contract, and operator-facing config.
• Existing operator command blocks (KPI, smoke, readiness, acquisition) stay current.
• New lightweight test/readme-customer-facing.test.ts asserts the README stays customer-facing and that the procedure still exists internally.
• No new paper citations. Existing verified doctoring sources are pointed to, not restated as new grounds.

Test plan

• npx vitest run test/readme-customer-facing.test.ts — pass
• npx vitest run test/hourly-product-development-workflow.test.ts test/hourly-commercial-readiness-script.test.ts — pass
• Full npm test — 1910 passed; 4 acquisition-git spawnSync timeouts under parallel load, all 6 of those tests pass when rerun in isolation

Not stacked on an unmerged parent. README has no bot-manual leftover. Do not merge from this PR.

  

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

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 reviews.

How do review 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 refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5896d4e2-c0ce-450d-946f-025908ac58d3

📥 Commits

Reviewing files that changed from the base of the PR and between 70663fb and 21c3d05.

📒 Files selected for processing (5)

• CHANGELOG.md
• CONTRIBUTING.md
• README.md
• docs/development/contributor-and-agent-procedure.md
• test/readme-customer-facing.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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