feat(sitemap,indexing): audit indexing, wire dynamic formulation metadata, and complete sitemap inventory

[BigSimmo]

Summary

This PR performs a repository-wide indexing, wiring, linking, and sitemap completeness pass:

1. Robots / Indexing Policy: Standardized \src/app/mockups/layout.tsx\ to use canonical \PRIVATE_APP_ROBOTS_METADATA, applying full
   ocache,
   oimageindex, and
   osnippet\ crawler protections.
2. Dynamic Route Metadata & Discipline:
   • Added dynamic \generateMetadata\ and \�xport const dynamicParams = false;\ to /formulation/[slug]\ (\src/app/(search-app)/formulation/[slug]/page.tsx).
3. Sitemap Completeness & Route Descriptions:
   • Added descriptions for all 25 unannotated page routes and 13 unannotated API endpoints in \scripts/generate-site-map.ts.
   • Added missing mode page index rows for \Calculators, \Therapy Compass, \Factsheets, and \Dictionary.
   • Added dynamic slug inventories for Factsheets, Dictionary terms, and Dictionary topics.
   • Categorized parameterized routes under dynamic route families rather than top-level static product routes in \docs/site-map.md.
4. Test Suite Hardening:
   • Updated \ ests/site-map.test.ts\ with static subroute precedence in
     outePatternForHref\ to prevent false-positive pattern collapsing.
   • Expanded \ ests/site-map.test.ts\ to assert all dynamic slugs across all modes.

Verification

• 
  pm run typecheck\ passed (0 errors)
• 
  pm run sitemap:check\ passed (0 drift)
• \ ests/site-map.test.ts\ passed (11/11 tests)
• \ ests/route-reachability.test.ts\ passed (5/5 tests)
• Focused route, error boundary, and navigation DOM test suites passed (56/56 tests)

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in:22 minutes

Limit details: You’ve used the included review currently available. Your 85 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9ff8c55d-8bdb-4142-9f7a-2579d7cf961a

📥 Commits

Reviewing files that changed from the base of the PR and between 4a792b1 and 37f388d.

📒 Files selected for processing (6)

• docs/site-map.md
• scripts/generate-site-map.ts
• src/app/(search-app)/formulation/[slug]/page.tsx
• src/app/mockups/layout.tsx
• tests/site-map.test.ts
• tests/ui-tools.spec.ts

---

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

[github-actions]

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

• Lighthouse budget — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #12628 (success).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.