fix(site): derive current state from source metadata - #281
Conversation
The production homepage still presented the August 7 launch as its latest material change after the August 11 source and dependency updates. A browser review also found a missing favicon request and field-run accessibility coverage tied to one hard-coded run. The changelog frontmatter now owns homepage metadata. Both layouts declare a pinned SVG favicon. The site regression test verifies asset presence and metadata. Accessibility coverage discovers every field run. Verified with Astro check and build, site and field-run tests, markdown lint and diff validation, exact 375 and 1440 pixel browser checks, and mobile and desktop Lighthouse audits. The local accessibility script reached browser launch, but macOS denied Chromium access to its Mach port. The required GitHub accessibility check remains the merge gate.
|
Warning Review limit reached
Next review available in: 35 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
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. Comment |
1 participant
rationale
the homepage latest-change block was hard-coded to the august 7 launch, so it drifted after the august 11 source and dependency work. the same production review found a browser request for a missing favicon and accessibility coverage tied to one field-run filename.
what changed
verification
bun run checkandbun run buildbun run test:siteandbun run check:field-runsrollout
required github checks remain the merge gate. the local accessibility runner reached chromium launch, where macos denied the child process access to its mach port. github actions provides the authoritative browser result before merge.