docs-site: mobile homepage polish, persistent GitHub link and star count

[lidge-jun]

Summary

The homepage now keeps a GitHub link visible in the fixed header on phones as well as desktop, shows a compact star count when available, and adds a localized GitHub link near the lower documentation map. Mobile command examples wrap, touch targets are larger, and media dimensions reserve space during loading. Existing desktop composition and all eight locales are preserved.

Star counts are fetched once at build time from GitHub's public repository API, without credentials, with a five-second timeout. Offline builds, rate limits and malformed responses render a usable link without a number. Counts remain static until the next deployment. No client polling or third-party badge service was added.

Also records the reviewed recovery plan for the owner-authorized 2.81.0 release train. The plan does not claim release completion.

Verification

• cd docs-site && bun install --frozen-lockfile && bun run build: 569 pages, 79,090 internal links, successful build. The normal request hit the API fallback. A separate scratch build with a synthetic 17092 API response verified the 17k layout; the fixture is not shipped.
• bun test over all 24 test files referencing docs-site: 573 pass, 0 fail. bun run typecheck, bun run structure:check, bun run privacy:scan, and git diff --check passed.
• Chromium rendered English and Korean homepage at 360×740, 360×800, 390×844, 430×932, 768×1024 and 1280×800, plus installation docs at 360 and 1280. Both count and fallback modes: 16 route/viewport rows each, no horizontal overflow; header GitHub remains visible at top, middle and bottom. Screenshots were actually inspected. No Safari-native claim.
• Independent inherited reviewer approved exact head 5c5ec574f0d407a8535b107c7957030d4113c7d2, all four implementation files, with no actionable findings. Separate architect reflection and independent audit approved the recovery roadmap.
• Full local suite was not repeated because concurrent release lanes share this host. PR CI and the coordinator's final integrated lane=all run cover broader execution. Hosted results will be checked against this exact PR head before merge.

Screenshots are stored only on the separate pr-assets branch. The after-count images use the explicitly synthetic 17,092-star response. Before images have DPR 2 and after images DPR 1; CSS viewport sizes match.

Surface	Before	After
390×844 mobile
1280×800 desktop

Scrolled Korean mobile · API failure fallback

Maintainer integration evidence

The owner explicitly authorized this homepage improvement, independent inherited review, merge and release. I am choosing the dev-only maintainer-integration path under MAINTAINERS.md, separately from technical approval. Reviewer Jason approved exact head 5c5ec574f0d407a8535b107c7957030d4113c7d2 with no actionable findings and inspected the saved count/fallback screenshots and reports. Cross-platform CI 37750991759, pull_request event, attempt 1, completed successfully at that head: docs site build, privacy gate and aggregate CI passed. Runtime matrix jobs were correctly excluded by docs-only path filters and are not claimed as tested by this run. The focused local checks above and the later integrated lane=all run provide their separate evidence. git merge-tree --write-tree HEAD origin/dev composed cleanly against the landed picker cleanup.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults. Public unauthenticated build fetch only; no credentials or auth behavior changed.

Summary by CodeRabbit

• New Features
  • GitHub links now display a formatted star count when available.
• Improvements
  • Header controls and links have larger touch targets for easier use on mobile.
  • Landing-page content is easier to read and navigate on smaller screens.
  • The landing-page demo uses a more compact layout.

[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.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: lidge-jun/opencodex/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: c351d747-46d7-4164-9f3e-b8703a289e83

📥 Commits

Reviewing files that changed from the base of the PR and between b6ec62a and 5c5ec57.

📒 Files selected for processing (7)

• devlog/_plan/261008_train_281_recovery/000_plan.md
• devlog/_plan/261008_train_281_recovery/010_integration.md
• devlog/_plan/261008_train_281_recovery/020_publication.md
• docs-site/src/components/Header.astro
• docs-site/src/components/Landing.astro
• docs-site/src/data/github-stars.ts
• docs-site/src/styles/custom.css

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

The changes add build-time GitHub star counts to the documentation header and landing page, adjust homepage layout and touch targets, and document recovery, integration, release publication, and homepage verification procedures for version 2.81.0.

Changes

Recovery and homepage

Layer / File(s)	Summary
GitHub star-count retrieval and display docs-site/src/data/github-stars.ts, docs-site/src/components/Header.astro, docs-site/src/components/Landing.astro, docs-site/src/styles/custom.css	Adds a cached GitHub star-count lookup with offline and error handling, formats counts, and conditionally displays them in localized header and landing-page links.
Homepage layout and touch targets docs-site/src/components/Header.astro, docs-site/src/components/Landing.astro, docs-site/src/styles/custom.css	Updates the demo canvas dimensions and aspect ratios, adds mobile layout rules, and sets minimum touch-target sizes for header and landing-page controls.
Delivery integration and publication procedures devlog/_plan/261008_train_281_recovery/*	Documents delivery review and CI gates, candidate verification, release publication steps, and independent homepage verification.

Priority: ➖ Normal

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant Header as Header.astro
  participant Stars as github-stars.ts
  participant GitHub as GitHub API
  Header->>Stars: getStarCount()
  Stars->>GitHub: Request repository star count
  GitHub-->>Stars: Response with stargazers_count
  Stars-->>Header: Count or null
  Header->>Stars: formatStarCount(count)

Loading

Merge Risk: ⚪ Minimal · up to 5c5ec

The homepage changes appear mergeable after the normal exact-head checks; the GitHub links remain usable when a star count is unavailable.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (6 skipped: 6…	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main docs-site changes: mobile homepage polish, a persistent GitHub link, and GitHub star-count display.

Full details: Docstring Coverage

Explanation

Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (6 skipped: 6 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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