docs(lane1): reverify growth/ops exporters --help item — already fixed on main (PR #135) - #187
Conversation
…d on main (PR #135) The 7 growth/ops exporters that overwrite tracked ACTIVE_OPERATOR_ARTIFACTS (live-metrics, proof-library, market-benchmark, sender-setup-guide, market-proof-run, market-parity-readiness, internal-dashboard) honor --help/-h via commit d4f3ef4 (PR #135): handleHelp() runs before any work, --output/--ops/--html are routed through resolveOutputPath(), and scripts/test-active-operator-surfaces.mjs enforces exit 0 + usage + no artifact rewrite for both flags. Re-verified live against fresh origin/main (4b8e240): both named probes exit 0 with usage and leave tracked artifacts byte-identical (md5 unchanged); the full operator-surface test passes. No source change is possible or needed; this report documents the verification.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 49 minutes Limit details: You’ve used all 1 included review currently available under your plan. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (1)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
1 participant
Item
Verdict
Already fixed and merged on main (PR #135, commit
d4f3ef4). No code change is possible or needed; this run reverified the shipped fix against fresh origin/main (4b8e240). A prior report (PR #165) documented the same verdict; this PR is a fresh re-verification of the current mainline.Evidence
d4f3ef4(fix(ops): honor --help in the 7 growth/ops exporters that overwrite tracked ACTIVE_OPERATOR_ARTIFACTS #135, 7 growth/ops exporters),3d1a956(fix(ops): honor --help in the remaining 8 export scripts so retired growth/ops artifacts stay untouched #99),fc44b42(fix(ops): honor --help in the 4 recording-batch exporters #145) are all ancestors of fresh origin/main:git merge-base --is-ancestor d4f3ef4 HEAD→ true.handleHelp(process.argv.slice(2), "Usage: ...")as their first statement and route--output=/--ops=/--html=throughresolveOutputPath()(scripts/lib/operator-cli.mjs:14-19, 30) — which also refuses repo-escaping paths.scripts/test-active-operator-surfaces.mjs(trackedOpsHelpSurface, lines 144-152) asserts exit 0 +Usage:for both--helpand-h, byte-identical tracked/private-runtime artifacts afterward, no retired artifact recreation, and refusal of escaping output paths.Live re-verification (branch off origin/main @ 4b8e240)
node scripts/test-active-operator-surfaces.mjs→Active operator surface checks passed.(exit 0)node scripts/export-growth-metrics.mjs --help→ usage, exit 0;growth-brain/ops/live-metrics.mdmd5 unchanged (fd9e1d45...)node scripts/export-proof-library.mjs -h→ usage, exit 0;growth-brain/ops/proof-library.mdmd5 unchanged (d1a764c1...)git statusclean after the probes — no tracked ops artifact overwritten.No source change is possible or needed; this report documents the verification.