[ryota-murakami]

{
  "schema_version": 1,
  "pr": 1,
  "head": "d05ca782a6b47b07325e174555d4ec5dc390bfb6",
  "base": "main",
  "gate": {
    "tests": {
      "exit": 0,
      "tests_ran": "unknown",
      "count": "unavailable"
    }
  },
  "session_kind": "interactive",
  "pregate": "requires-remote cleared @be76e9755c17 (7 checks, current for d05ca782a6b4)",
  "requires_remote": [
    "ci.yml/verify: https://github.com/laststance/react-libraries/actions/runs/40024471693"
  ],
  "issues": {
    "fixes": [],
    "refs": [],
    "flakes": []
  }
}

Summary

Launch an English React Libraries field guide from the complete public Notion collection. Developers can browse purpose-based categories, compare concise descriptions and recommended use cases, or find a task with Cmd/Ctrl K without knowing a library name.

• Reconcile all 612 saved-link occurrences across 201 Notion pages into 561 migrated entries, plus the approved MUI X Data Grid starter: 562 entries, 59 categories, 59 task guides, and 683 searchable content pages.
• Preserve every source occurrence, consolidate repeated projects, correct 26 source links, and clearly label the four unavailable historical sources. Twelve sources have unconfirmed reachability; these are not represented as discontinued.
• Preserve the approved light/dark design, wrap category names, add large-category jump indexes, and support keyboard search and mobile navigation.
• Build static HTML and a local Pagefind index with Blume. Canonical content lives in content/; normal builds have no Notion dependency.
• Configure pinned CI and the Laststance Vercel project with production tracking main.

Validation

• pnpm run check — no errors, warnings, or hints.
• pnpm run doctor — no problems.
• pnpm run validate — no broken internal links.
• pnpm run build — 683 searchable content pages generated and indexed.
• pnpm test — 4 catalog reconciliation tests and 5 Playwright journeys pass. The receipt runner reports tests_ran: unknown; the underlying runner output explicitly reports 4 and 5 passing tests.
• Eight representative routes inspected at desktop, tablet, and mobile sizes; 320px header checked separately. Recorded navigation/search motion was inspected using extracted frames.
• Additional keyboard-only search, ArrowDown/ArrowUp/Enter, reload, and back-navigation smoke passed without browser exceptions.

Review

Parent checklist and independent native adversarial review are complete on unchanged content. Known findings were fixed: category truncation, narrow header crowding, large-list navigation, fresh-checkout Chromium instructions, and removal of transient login-redirect query data from diagnostic snapshots.

Gate edits reviewed with no relaxation findings. The follow-up also rejects untracked generated pages. The new CI timeout and CI server-isolation setting add verification boundaries; there are no existing tests to remove or weaken. The new pregate policy conservatively selects both browser suites for all changes and runs the catalog guard. It uses --policy-from head for initial repository bootstrap and retains the tool's head (unreviewed) label; its contents received independent review.

Claude Code outside reviews timed out and are missing coverage, not passing reviews. Native review is separate. CodeRabbit CLI completed the initial full review with seven findings (one major, six minor); all were fixed in d05ca78. Its fresh follow-up covered all 15 changed files and completed with zero findings and a passing major gate. The GitHub app excludes this new repository and its installation API requires an Organization Owner, so this is CLI evidence, not a formal GitHub approval. Matching-head CI is tracked separately on this PR.

Coverage

Notion snapshot → provenance mapping → canonical catalog → generated pages → Pagefind
                     tested               tested            build/check       browser
Category navigation → detail / theme persistence / mobile drawer             tested
Purpose/name search → results / empty state / Escape / focus                  tested
Large-category index → target card                                           tested
Keyboard selection → task / reload / browser back                            smoke verified

The audit does not independently revalidate all 562 projects' API, maintenance, license, accessibility, or security claims. Historical one-time importer failure branches and exhaustive accessibility coverage remain outside the release smoke scope. Migration coverage and source preservation are mechanically checked for every occurrence.

Exploratory QA

Scope: local static site in owned Chromium; no signed-in state or external mutation. Five-minute bound. The initial keyboard probe assumed no result was preselected; an exact replay and aria-selected inspection established that the first result is selected by default. The corrected behavioral probe passed; no product change or weakened permanent test resulted. Checkpoints and recordings are retained in local release evidence.

Plan and scope

Plan completion audit: not run (no plan is bound to this branch and no docs/designs/ file matches). Fix: add "Plan: " to the PR body, or run /autoplan.

Conversation requirements were checked directly: all Notion entries, English purpose/fit copy, chosen themes, category discovery, command search, Laststance hosting, and source preservation. Plan item counts: 0 audited, 0 verified, 0 dropped.

Deployment

Vercel team/project: laststance/react-libraries. Production branch: main. Node 22.x, pnpm 12.14.0, static output dist/. Initial feature-branch CI was bootstrapped before the final receipt because the base repository was empty.

Production is live at https://react-libraries-five.vercel.app. Vercel deployment dpl_23FUxGevtQbyBGWuBD44yUoogN2g is Ready for production and its githubCommitSha matches merge commit ece3093ac602f2db80fbb41eb0595059fe494262. Main-branch CI passed on that exact commit. All five Playwright journeys also passed against the public production URL; search and mobile-navigation recordings were inspected frame by frame.

The requested ten-minute canary completed with 6 pages, 10 rounds, and 60 navigations. Every navigation returned HTTP 200, with zero console errors and zero internal-link 404s. All six final screenshots are byte-identical to their monitoring-start screenshots. Average page loads were 74–114 ms; the maximum monitored load was 207.9 ms.

Canary result: DEGRADED, one resolved MEDIUM alert. The choosing-a-library page rose from a 63.4 ms monitoring-start reference to 140.2 ms and 157.5 ms in consecutive rounds, exceeding the relative 2x threshold. It returned to 55.4 ms in the next round. There were no critical/high alerts, no active alerts at completion, and four other unconfirmed single-round timing observations. The resolved alert remains in the result; it is not relabeled healthy. This was a post-deployment monitoring reference, not a before/after deployment performance comparison. No baseline was promoted from this run.

The first PR CI attempt was canceled after a slow Ubuntu package download, and its unchanged retry passed. No CI checks were removed or weakened. Local main matches the published commit and has no uncommitted changes.

Screenshots and interaction recording

Documentation

Follow-up at d05ca78: the independent two-pass audit below remains bound to 61c6795. Its full candidate hashes are no longer current after the CodeRabbit repairs. The parent and independent native reviewer inspected the 15-file delta: updated source links/caveats, 26 correction records, English/local-archive wording, Node minimum, generated pages, and the stronger CI guard. Documentation matches this delta; no third document-release audit was claimed.

Status: current — the two README issues from the initial audit are resolved, with no remaining required documentation corrections.

Audited the repaired initial-release candidate at 61c6795 against cfdf00d. All 1,711 selected file hashes match the recorded candidate. The repair pass re-read changed documentation, release configuration, and source-checker behavior, and reused prior semantic inspection of unchanged files after hash verification. Coverage includes five authored documents, canonical schema/categories and generation/presentation contracts, six representative catalog entries, eight generated content pages, migration reconciliation, test configuration, and deployment configuration. This is not a claim-by-claim re-audit of all 562 projects or a production health check.

Documentation health:

• README.md — Current: Node 22.x support and first-run Chromium installation now match package and CI requirements; canonical editing, generation, validation, and migration procedures are documented.
• AGENTS.md — Current: content ownership, validation commands, evidence handling, and Laststance delivery scope match implementation.
• DESIGN.md — Current: approved theme tokens match theme.css; saved design references are clearly distinguished from shipped site assets.
• MIGRATION.md — Current: 201 pages, 1,623 blocks, 612 occurrences, 577 original URLs, 561 migrated entries plus one starter, 562 total entries, 59 categories, and 683 content pages reconcile with saved evidence. Four unavailable and twelve unconfirmed entries remain accurately qualified.
• DEPLOYMENT.md — Current: static build configuration, Laststance ownership, CI/CodeRabbit release procedure, revision verification, and recovery guidance match the candidate. Production URL/SHA and monitoring evidence are explicitly recorded separately on the release PR.
• scripts/build-content.ts and representative generated MDX — Current: category, task, detail, warning, and related-option content follows the documented canonical ownership model.
• ARCHITECTURE.md / CONTRIBUTING.md / CHANGELOG.md / TODOS.md — Skipped: absent from the audited candidate; no files were generated.

Documentation coverage:

Surface	Reference	How-to	Tutorial	Explanation
Category/task/search discovery	README and generated guides	Choosing a library	Brief task walkthrough	Choosing a library
Catalog maintenance	README and typed schema	README maintenance workflow	No complete entry example	Canonical ownership explained
Validation	README and CI	Browser installation and check commands	No standalone tutorial	Test scope described
Migration and provenance	MIGRATION and reconciliation report	Historical process only	Not applicable	Editorial treatment and limits
Deployment and recovery	DEPLOYMENT and configuration	Release/recovery procedure	No standalone tutorial	Static hosting and revision verification

Coverage debt: no changed public surface lacks all documentation. A worked example for adding an entry would improve newcomer guidance; a separate tutorial remains optional. Historical importer documentation intentionally warns against routine replay.

Diagram drift: none found; audited authored documents contain no architecture diagrams.

video.webm

video.webm

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
react-libraries	Ready	Preview	Oct 23, 2026 9:08pm UTC

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	blume@​2.2.4
	@​playwright/​test@​1.64.1

View full report

[ryota-murakami]

@coderabbitai full review

Please review the initial React Libraries launch at the current head. Focus on authored source, migration coverage, generated-content safety, keyboard/navigation behavior, and CI/Vercel configuration. Generated MDX and immutable source snapshots are excluded by the repository configuration; the canonical catalog, importer, generator, and reconciliation tests remain in scope.

[ryota-murakami]

CodeRabbit CLI completed the initial full review at 61c6795 with one major and six minor findings. All seven were addressed in d05ca782a6b47b07325e174555d4ec5dc390bfb6:

• Replaced the Cal-Heatmap and React Chrono domains that redirected to unrelated content with their official repositories, added visible caveats, and preserved the original Notion provenance. Added a regression check for these destinations.
• Pointed Turso to its primary product site and Auth.js/Vike to their current documentation. Kept historical references in the catalog or migration inventory.
• Translated the design approval quotes and described the maintainer-local reference archive without a personal absolute path.
• Made CI reject untracked generated pages as well as changes to tracked pages.
• Required Node 22.19 or later within Node 22, matching the documented TypeScript execution requirement.

Validation after the fixes: type check and production build pass; four catalog tests and five Playwright journeys pass. Independent native review of the entire 15-file follow-up found no new issues. A fresh CodeRabbit review of the follow-up is running.

The CodeRabbit GitHub application currently excludes this new repository. The installation API denied the addition with an Organization Owner permission requirement, so this evidence comes from the authenticated CodeRabbit CLI, not a GitHub review approval or bot check. No human GitHub approval is claimed.

[ryota-murakami]

CodeRabbit follow-up completed on d05ca782a6b47b07325e174555d4ec5dc390bfb6: 0 findings, major-severity gate passed. The follow-up reviewed all 15 files changed by the repairs, against 61c6795.

The initial full review reported seven findings; all seven are addressed. This is CodeRabbit CLI evidence. The GitHub application remains unavailable for this repository, and no formal GitHub approval is implied.

[ryota-murakami]

Merged and deployed to https://react-libraries-five.vercel.app.

• Merge SHA: ece3093ac602f2db80fbb41eb0595059fe494262.
• Vercel production deployment: dpl_23FUxGevtQbyBGWuBD44yUoogN2g, Ready, with matching Git SHA.
• Main CI: https://github.com/laststance/react-libraries/actions/runs/40027263979 — success.
• Production Playwright: 5/5 journeys passed. Search and mobile motion recordings inspected.
• CodeRabbit CLI: all 7 initial findings addressed; fresh follow-up found 0 issues. GitHub application access still requires repository inclusion by an Organization Owner; no formal GitHub approval is claimed.
• Ten-minute canary: 6 pages / 60 successful navigations, zero console errors, zero internal 404s. One relative performance alert was confirmed and then resolved (63.4 ms reference, 140.2–157.5 ms observed, then 55.4 ms). The report preserves DEGRADED for that resolved incident; no critical/high or active alerts remain. Four isolated timing observations did not persist.

The PR description contains production screenshots, interaction recordings, migration reconciliation, and the distinction between deployment success and the canary's relative performance warning.