docs: align public repo naming with v95 surfaces#42
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✅ Files skipped from review due to trivial changes (4)
🚧 Files skipped from review as they are similar to previous changes (3)
📝 WalkthroughWalkthroughThis PR refreshes product positioning terminology by replacing "ZERO-hosted control plane" with "ZERO-hosted app" throughout documentation, README, and UI, while renaming "cockpit" references to "Control." It also adds a surface-limited validation helper to the public readiness gate to enforce boundary compliance. ChangesTerminology refresh and boundary validation updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cffe25cc2f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/public_readiness_gate.sh`:
- Around line 31-48: current_surface_search() must fail closed on file errors:
after running rg or grep, capture the command's exit code and if it indicates an
error (for rg/grep an exit code >1 or ==2), write an explanatory message to
stderr and exit the script (or return a distinct non-zero code) so the gate
fails instead of silently treating the error as “no match”; otherwise
preserve/return the original exit code so callers can distinguish “no match” (1)
from an actual error. Reference the current_surface_search function and update
both the rg and grep branches to implement this exit-code check and error
handling.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e9a9e82b-173d-4bca-832d-b3f308a7d601
📒 Files selected for processing (7)
AGENTS.mdREADME.mddocs/llms-full.txtdocs/llms.txtdocs/open-core-boundary.mddocs/positioning.mdscripts/public_readiness_gate.sh
896d2e1 to
93830da
Compare
Summary
getzero.dev/developersandgetzero.dev/proof.docs/llms-full.txtso agent retrieval stops carrying stale publiccontrol planeand product-page wording.public-readinessto catch stale current-surface wording in README/AGENTS/high-visibility docs.Guardrails
/cockpit-mode,/live/cockpit, andlive-cockpitremain documented where they are actual current CLI/API names.Validation
just public-readinessjust public-proofjust registry-readinessscripts/generate_llms_full.py --checkSummary by CodeRabbit
Documentation
Style