Complete the ProDocs 1.0 roadmap

[boyeesu]

What

Completes every published ProDocs roadmap phase and promotes the project to the 1.0 production contract.

• adds authored claims, decisions, invariants, features, runbooks, evidence coverage, contradiction/supersession state, and SQLite-backed incremental indexing
• adds git impact analysis, documentation policies, reviewed proposal application, provider-backed cited narratives, and opt-in pre-push checks
• adds bounded agent context, MCP tools/resources, Codex/Claude Code/OpenCode recipes, prompt-injection boundaries, and retrieval evaluation
• adds product, technical, support, security, operations, and coding-agent views; feature/customer maps; history; runbook verification; and an authenticated local collaboration API
• publishes graph/context v2 plus impact/proposal schemas and marks all roadmap phases complete
• updates the README, architecture, compatibility, security, operations, maturity, validation, release, and changelog documentation for 1.0.0

Why

ProDocs needs one deterministic, evidence-backed knowledge layer that humans and coding agents can trust, query, review, and keep current from inside the repository. This closes the launch roadmap without leaving partially implemented phases.

Security impact

Repository content remains untrusted data. The deterministic core has no network egress; provider egress is explicit, redacted, bounded, and citation-validated. Plugins are declarative and capability-bounded. Proposal writes require exact approval hashes and are restricted to authored documentation. Runbooks do not invoke a shell. The collaboration server is loopback-first and requires a strong bearer token for non-loopback exposure.

GitHub main protection was verified active: force pushes and deletions are disabled, admin enforcement and conversation resolution are enabled, and all CI/CodeQL/dependency checks are required.

Validation

• 67/67 tests pass
• coverage: 93.15% lines, 80.17% branches, 95.84% functions
• documentation sync/check passes
• documentation policy: 0 errors, 0 warnings
• evaluation: 2/2 cases, recall 1.000, precision 1.000
• declarative plugin conformance passes
• release metadata and packed-package installation pass
• npm audit --omit=dev: 0 vulnerabilities
• 6 dependency registry signatures and 3 attestations verified
• npm pack --dry-run passes for prodocs@1.0.0

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 56 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: b196c680-e0c9-4e80-8598-33153850498e

📥 Commits

Reviewing files that changed from the base of the PR and between 9d4e280 and f836afe.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (72)

• .github/workflows/ci.yml
• .gitignore
• CHANGELOG.md
• CODEOWNERS
• README.md
• SECURITY.md
• docs/ARCHITECTURE.md
• docs/COLLECTORS.md
• docs/COMPATIBILITY.md
• docs/MATURITY.md
• docs/OPERATIONS.md
• docs/RELEASING.md
• docs/ROADMAP.md
• docs/VALIDATION.md
• docs/knowledge/claims/local-first.md
• docs/knowledge/decisions/deterministic-core.md
• docs/knowledge/features/agent-interface.md
• docs/knowledge/features/change-intelligence.md
• docs/knowledge/features/evidence-kernel.md
• docs/knowledge/features/product-views.md
• docs/knowledge/invariants/untrusted-repository.md
• docs/knowledge/runbooks/production-verification.md
• docs/prodocs/CODE_MAP.md
• docs/prodocs/FEATURE_MAP.md
• docs/prodocs/KNOWLEDGE_HEALTH.md
• docs/prodocs/SYSTEM_OVERVIEW.md
• docs/prodocs/knowledge.json
• docs/prodocs/manifest.json
• docs/prodocs/views/coding-agents.md
• docs/prodocs/views/operations.md
• docs/prodocs/views/product.md
• docs/prodocs/views/security.md
• docs/prodocs/views/support.md
• docs/prodocs/views/technical.md
• fixtures/evaluation/core.json
• fixtures/plugins/service.prodocs-plugin.json
• package.json
• prodocs.config.json
• schemas/context-packet.schema.json
• schemas/impact.schema.json
• schemas/knowledge.schema.json
• schemas/prodocs-config.schema.json
• schemas/proposal.schema.json
• scripts/verify-release.js
• src/cli.js
• src/collectors/artifacts.js
• src/collectors/index.js
• src/config.js
• src/constants.js
• src/context.js
• src/evaluate.js
• src/history.js
• src/hooks.js
• src/impact.js
• src/index-store.js
• src/integrations.js
• src/knowledge.js
• src/mcp.js
• src/plugins.js
• src/policy.js
• src/proposals.js
• src/providers.js
• src/render.js
• src/runbooks.js
• src/safe-fs.js
• src/scanner.js
• src/security.js
• src/server.js
• test/cli-roadmap.test.js
• test/config.test.js
• test/package.test.js
• test/roadmap.test.js

---

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