docs: close remaining current-state drift

[Abiorh001]

Goal

Complete the already-approved WS-DOCS-001 documentation modernization by removing the remaining stale current-state and retired-process wording.

What changed

• records the merged AUTH/ART guide-source binding and read path as implemented
• replaces the stale README claim that guide binding and reputation projection are active v0.1 work
• describes the remaining ART custody chain from the merged PR docs(art): reconcile remaining v0.1 plan #247 plan
• removes retired signed-loop machinery from active contributor, agent, and engineering-policy guidance
• replaces remaining calendar framing in active ADR outcomes
• aligns AGENTS with the deferred runtime reputation boundary

Scope

Documentation only. This implements the merged WS-DOCS-001 direction; it does not create a new planning initiative and changes no runtime, tests, CI, migration, action, grant, or product behavior.

Verification

• python3 scripts/check_markdown_links.py
• python3 scripts/check_stale_workstream_wording.py
• python3 scripts/check_stale_authorization_docs.py
• python3 scripts/check_stale_artifact_contracts.py
• git diff --check

All passed. No local sheet export exists in the clean worktree, so XLSX validation was not applicable.

Internal review

• Documentation: PASS after aligning AGENTS process and reputation wording
• Product/operations: PASS; current guide-binding, ART remainder, contribution, compensation, and deferred reputation claims align with merged evidence

Human review focus

• current main capability accuracy after PRs feat(auth): activate guide binding and read #245 and docs(art): reconcile remaining v0.1 plan #247
• removal of retired engineering-loop terminology from active entry docs
• preservation of historical records without presenting them as current authority

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 53 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7dd5f52a-63bb-45b7-aab5-a81c0c705321

📥 Commits

Reviewing files that changed from the base of the PR and between 2c24c91 and 81c686b.

📒 Files selected for processing (8)

• .agent-loop/README.md
• .agent-loop/policies/repository-engineering-policy.md
• AGENTS.md
• CONTRIBUTING.md
• README.md
• docs/decision_0001_core_scope.md
• docs/decision_0002_db_first_not_blockchain_first.md
• docs/roadmap_status.md

---

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