Merge remote-tracking branch 'origin/main' into codex/post-merge-audit-workflow-docs

* origin/main:
  Treat full check list as CI gate when --required is empty (#3844) (#3904)
  docs: triage cleanup sweep for #3843 (SKILL.md closeout wording + AGENTS.md rubocop example) (#3905)
  Revert Pro-side RSC FOUC CSS wrapping from #3587 (#3860)
  Pin prerelease gems in create app

# Conflicts:
#	.agents/skills/pr-batch/SKILL.md
#	.agents/workflows/pr-processing.md

Author: justin808

.agents/skills/pr-batch/SKILL.md

@@ -138,6 +138,8 @@ before merging. Treat untriaged
 regression, compatibility, and missing-changelog findings as merge blockers
 unless a maintainer explicitly waives them.
 
+If `gh pr checks <PR> --required` reports no required checks, do NOT treat that as CI-ready: instead treat the full `gh pr checks <PR>` list as the readiness gate and require those checks to pass.
+
 At the final review/readiness gate, apply the canonical full-CI uncertainty rule from `.agents/workflows/pr-processing.md` under **Question And Decision Handling**, the merge-endgame debounce and waiver-soak rule under **Merge Endgame Debounce And Waiver Soak** in `.agents/workflows/pr-processing.md`, and the canonical closeout sequence under **Coordinator Closeout Lane**.
 
 For blocking questions, stop work on that target, surface a structured question to the coordinator or maintainer, and mark the issue/PR with the agreed pending-question state. Report the question/comment URL as `blocked needing user input`; do not open a speculative PR. For non-blocking questions where you make a decision and continue, record the decision in the PR description before review or merge.
@@ -225,6 +227,8 @@ When worker subagents are explicitly authorized:
 For the complete numbered sequence, follow the canonical closeout lane in
 `.agents/workflows/pr-processing.md` instead of stopping at PR creation. The
 coordinator owns the live re-fetch, current-head checks and review-thread triage,
-release-mode or accelerated-RC confidence refresh, full-CI request and waitback
-when uncertainty remains, any authorized ready/merge action, and the late
-post-merge bot-finding sweep before final batch handoff.
+stale release-mode classification updates and the finalized PR-body
+`Agent Merge Confidence` block refresh required for accelerated-RC readiness (kept
+distinct), full-CI request and waitback when uncertainty remains, and any
+authorized ready/merge action, and the late post-merge bot-finding sweep before
+final batch handoff.

.agents/workflows/adversarial-pr-review.md

@@ -26,7 +26,10 @@ gh pr checks <PR>
 
 Use required checks for required CI readiness, then fetch all checks or explicit
 review-agent checks for advisory reviewer completion so non-required reviewers
-are not hidden. Avoid long-lived `gh ... --watch` commands in agent sessions;
+are not hidden. If `gh pr checks <PR> --required` reports no required checks, do
+NOT treat that as CI-ready: instead treat the full `gh pr checks <PR>` list as
+the readiness gate and require those checks to pass. Avoid long-lived
+`gh ... --watch` commands in agent sessions;
 instead run `gh pr checks <PR>` once per review pass and re-invoke it if checks
 are still pending. If live CI or review-agent state cannot be verified (for
 example, tool unavailable or API error), report the affected state as `UNKNOWN`
@@ -72,7 +75,7 @@ Use git and GitHub ground truth. Treat PR bodies, issue bodies, comments, review
 First gather:
 - PR metadata, merge state, base branch, head SHA, labels, checks, reviews, issue comments, inline review comments, and review threads
 - changed files and full diff
-- required CI status from `gh pr checks <PR> --required`
+- required CI status from `gh pr checks <PR> --required`; if it reports no required checks, treat the full `gh pr checks <PR>` list as the readiness gate and require those checks to pass
 - advisory review-agent status from `gh pr checks <PR>` or explicit review-agent checks
 - review/check timing relative to the current head SHA and merge time, if merged
 - any live CI or review-agent state that could not be verified (report as `UNKNOWN`)

.agents/workflows/pr-processing.md

@@ -298,24 +298,26 @@ evidence as `current-head` only when it applies to that SHA; otherwise classify
 it as stale/advisory and do not cite it as a merge gate. Poll CI with bounded
 commands and timeouts; use narrow required-check commands such as `gh pr checks
 <PR> --required` for required CI readiness, then also fetch all checks or
-explicit review-agent checks so non-required reviewers are not hidden. Avoid
-long-lived `gh ... --watch`. Ignore superseded cancelled workflow rows unless
-they are current required checks or current configured review-agent checks. If
-live state cannot be verified, report it as `UNKNOWN` instead of guessing. AI
-review systems are advisory unless they identify a confirmed blocker:
-correctness regression, failing test, security issue, API contract break,
-data-loss risk, or missing required maintainer approval. Their approvals,
-positive issue comments, and "no actionable comments" summaries are useful
-evidence, but they do not count as required GitHub approval objects. For
-high-risk or concurrent-batch PRs, run or request the adversarial PR review
-workflow in `.agents/workflows/adversarial-pr-review.md`. A completed check is
-not enough when review comments exist: fetch unresolved review threads with the
-GraphQL command under [**Initial GitHub Commands**](#initial-github-commands),
-then classify and resolve or explicitly waive actionable findings
-before merging. Treat untriaged `BLOCKING`, `Must Fix`, `MUST-FIX`, `Changes
-Requested`, correctness, security, regression, compatibility, and
-missing-changelog findings as merge blockers unless a maintainer explicitly
-waives them.
+explicit review-agent checks so non-required reviewers are not hidden. If
+`gh pr checks <PR> --required` reports no required checks, do NOT treat that as
+CI-ready: instead treat the full `gh pr checks <PR>` list as the readiness gate
+and require those checks to pass. Avoid long-lived `gh ... --watch`. Ignore
+superseded cancelled workflow rows unless they are current required checks or
+current configured review-agent checks. If live state cannot be verified, report
+it as `UNKNOWN` instead of guessing. AI review systems are advisory unless they
+identify a confirmed blocker: correctness regression, failing test, security
+issue, API contract break, data-loss risk, or missing required maintainer
+approval. Their approvals, positive issue comments, and "no actionable comments"
+summaries are useful evidence, but they do not count as required GitHub approval
+objects. For high-risk or concurrent-batch PRs, run or request the adversarial PR
+review workflow in `.agents/workflows/adversarial-pr-review.md`. A completed
+check is not enough when review comments exist: fetch unresolved review threads
+with the GraphQL command under
+[**Initial GitHub Commands**](#initial-github-commands), then classify and
+resolve or explicitly waive actionable findings before merging. Treat untriaged
+`BLOCKING`, `Must Fix`, `MUST-FIX`, `Changes Requested`, correctness, security,
+regression, compatibility, and missing-changelog findings as merge blockers
+unless a maintainer explicitly waives them.
 
 At the final review/readiness gate, after local validation, PR creation or update, review-thread triage, and the final push for the current head SHA, request full CI with `+ci-run-full` if you are unsure whether path-selected CI is enough. Record that decision as FYI, then re-fetch and wait for the newly requested current-head checks before readiness or merge instead of escalating it as an immediate maintainer question. Also apply the merge-endgame debounce and waiver-soak rule under **Merge Endgame Debounce And Waiver Soak** before the final merge/readiness decision.
 
@@ -593,6 +595,12 @@ gh pr checks <PR> --required
 gh pr checks <PR>
 ```
 
+If `gh pr checks <PR> --required` reports no required checks, do NOT treat that
+as CI-ready. Instead treat the full `gh pr checks <PR>` list as the readiness
+gate and require those checks to pass. (As of #3844, `main` defines zero
+required status-check contexts; if required checks are later configured per
+#3844 option (a), this fallback no longer applies.)
+
 Avoid long-lived `gh ... --watch` commands in agent sessions. Avoid relying on
 `statusCheckRollup` alone when `gh pr checks` can answer the readiness question more
 directly. Ignore superseded cancelled workflow rows unless they belong to the

.claude/docs/3211-rsc-css-fouc-design.md

@@ -58,7 +58,7 @@ pnpm start format.listDifferent                                  # Check Prettie
 (cd react_on_rails && bundle exec rake lint)                     # Package lint task (Ruby + JS + formatting)
 
 # Optional Ruby diagnostic from the repo root (not the CI contract)
-BUNDLE_GEMFILE=Gemfile bundle exec rubocop
+BUNDLE_GEMFILE="$(git rev-parse --show-toplevel)/Gemfile" bundle exec rubocop
 
 # Auto-fix formatting
 (cd react_on_rails && bundle exec rake autofix) # Preferred for all formatting