Skip to content

fix(public): point brief-requested nav and back links at clean non-307 paths - #97

Closed
nish3451 wants to merge 13 commits into
mainfrom
fix/brief-requested-clean-links
Closed

fix(public): point brief-requested nav and back links at clean non-307 paths#97
nish3451 wants to merge 13 commits into
mainfrom
fix/brief-requested-clean-links

Conversation

@nish3451

@nish3451 nish3451 commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

What

The post-signup surface at /brief-requested (public/brief-requested.html) still carried the redirecting-internal-link fault PR #34 removed from the five public pages: its logo, three nav links and the back link pointed at .html forms that the deployed worker 307-redirects to their clean extensionless twins:

anchor was now
logo index.html → 307 → / /
nav "The appraisal" audit.html → 307 → /audit /audit
nav "The desk" agents.html → 307 → /agents /agents
nav "Pricing" pricing.html → 307 → /pricing /pricing
back link index.html → 307 → / /

Why it slipped past the guard

The "Internal page links (dogfood 996dffe45ef7)" guard in scripts/check-site.mjs only covered the five public pages — brief-requested.html was not in internalLinkPages. This PR fixes the instance and the detector: the guard now includes the brief-requested page, and a negative probe confirmed it fails if any .html page-name anchor returns there.

Validation

  • npm run check passes with the fix; fails on a deliberately re-introduced href="audit.html" (then passes again after restore).
  • npm run test suites green: headings 6/6, sitemap 7/7, worker 53/53, UI 16/16, contract 8/8 (90 tests total).

Files

  • public/brief-requested.html — five anchors pointed at clean paths
  • scripts/check-site.mjs — internal-links guard extended to cover the post-signup page

Summary by CodeRabbit

  • Bug Fixes

    • Updated confirmation page navigation links to use clean, direct routes instead of .html URLs.
    • Improved navigation consistency for logo, appraisal, desk, pricing, and back-to-site links.
  • Tests

    • Expanded site checks to verify confirmation page links do not use redirecting .html addresses.

The post-signup /brief-requested page still linked its logo, nav and back
link at the .html forms (index.html, audit.html, agents.html, pricing.html),
each of which the worker 307-redirects to its clean extensionless twin —
the same redirecting-internal-link fault PR #34 removed from the five public
pages, left unfixed on the sixth surface. Point the five anchors at /,
/audit, /agents, /pricing and extend the check-site.mjs internal-links guard
(dogfood 996dffe45ef7) to cover the brief-requested page so the shape cannot
return.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

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

Next review available in: 28 seconds

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: fbe17329-560c-40d9-b8b5-ca982601ad07

📥 Commits

Reviewing files that changed from the base of the PR and between 167b9fd and 71a2aa8.

📒 Files selected for processing (2)
  • public/brief-requested.html
  • scripts/check-site.mjs
📝 Walkthrough

Walkthrough

The confirmation page now uses root-relative navigation routes. The site checker also scans /brief-requested for redirecting .html links.

Changes

Navigation route cleanup

Layer / File(s) Summary
Update confirmation page navigation
public/brief-requested.html
The logo, primary navigation, and “Back to the site” links now use root-relative routes.
Extend internal-link validation
scripts/check-site.mjs
The regression guard now checks /brief-requested with the existing public navigation pages.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: updating navigation and back links to use clean, non-307 paths.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/brief-requested-clean-links

Comment @coderabbitai help to get the list of available commands.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 90645c2620

ℹ️ 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".

Comment thread scripts/check-site.mjs
["pricing page", read("public/pricing.html")],
["specimen page", read("public/specimen.html")]
["specimen page", read("public/specimen.html")],
["brief-requested page", read("public/brief-requested.html")]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Normalize root-relative HTML targets in the added guard

When a brief-requested link is written in the common root-relative form href="/audit.html", target remains /audit.html, which is not a key in htmlPageTargets; the checker therefore passes even though the link still hits the redirecting .html endpoint. I confirmed this by substituting /audit.html on the newly guarded page and running node scripts/check-site.mjs, which exited successfully, so the detector added here does not reliably prevent the regression it is intended to cover.

Useful? React with 👍 / 👎.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d07d750566

ℹ️ 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".

Comment thread scripts/check-site.mjs
["pricing page", read("public/pricing.html")],
["specimen page", read("public/specimen.html")]
["specimen page", read("public/specimen.html")],
["brief-requested page", read("public/brief-requested.html")]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the confirmation route in redirect targets

When any guarded page contains href="brief-requested.html", adding this page to internalLinkPages still does not report the redirecting link because htmlPageTargets has no brief-requested.html entry. I verified this by replacing one of this page's clean links with that value and running node scripts/check-site.mjs, which still passed; add the confirmation route mapping so the guard covers the .html twin of every included public page.

Useful? React with 👍 / 👎.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@nish3451

Copy link
Copy Markdown
Collaborator Author

Stale duplicate of PR #145 (head branch fix/brief-requested-clean-links-lane1), which re-lands the byte-identical fix (fix commit ad5164e cherry-picked; content verified identical) on current origin/main HEAD (5864e39). #97 sat BEHIND current main since 2026-08-11 with ten main-merge commits. #145 is checked green (npm run check + npm test, 92 tests) and carries the same guard-coverage negative probe. Closing per the repo's reconciliation pattern (docs/evidence/duplicate-open-pr-clusters-residual-2026-08-11.md): one delivery path per surface — #145 survives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant