docs(evidence): re-verify brief-requested clean-links survivor PR #145 on current main and live (2026-08-14) - #188
Conversation
…on current main and live (2026-08-14) The post-signup surface still carries the redirecting-.html fault the item names (verified live: all four .html hrefs 307 to their clean twins). The fix lives on the sole surviving delivery path PR #145, open and MERGEABLE against current origin/main with CI green; this receipt records the authoritative re-verify of that tree (check + 117 tests + negative probe) so the surface closes when #145 merges. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
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: 21 minutes 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 (2)
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 |
…8-14) PR #145 merged to main as f9214c1 (2026-08-14T09:42:02Z): brief-requested now serves the clean anchors and the internal-links guard covers the page. Update the receipt and lane report from "survivor verified, awaiting merge" to the landed closeout. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
1 participant
What
Item 599374f838 (
[unreviewed-by-opus]): point/brief-requestednav and back links at clean non-307 paths. The post-signup surface still carries the fault on main and live (verified 2026-08-14:https://tinystudio.io/brief-requestedservesindex.html/audit.html/agents.html/pricing.html, each 307-redirecting to its clean twin).The fix itself is already implemented and CI-verified on the sole surviving delivery path — PR #145 (
fix/brief-requested-clean-links-lane1) — the survivor kept open by the fleet's duplicate-cluster reconciliation (docs/evidence/duplicate-open-pr-clusters-residual-*-2026-08-11/12.mdclosed #60 and #97 as stale duplicates and declared #145 "must be merged for the surface to be closed"). Opening a byte-identical duplicate here would recreate that cluster, so this lane's delivery is the authoritative re-verify + closeout receipt instead.Verification (2026-08-14)
origin/main(60958fc), checks green (verify, Gitleaks, CodeRabbit completed).3459a9d(fresh worktree):npm run checkpasses;npm testexit 0 — 117 tests, 0 failures.href="*.html"anchors onpublic/brief-requested.html.href="audit.html"makescheck-site.mjsexit 1 withInternal page link on brief-requested page must point at the clean destination "/audit"; restore passes./brief-requestedserves 200 with all four.htmlhrefs; each.htmlpath 307s to its clean twin.Files
docs/evidence/brief-requested-clean-links-rereverify-2026-08-14.md— evidence receipt (the lane's claimed file).lane/reports/chore-brief-requested-clean-links-rereverify-2026-08-14.md— lane reportThe actual fix lands by merging PR #145, which this receipt declares the single delivery path for the surface.