vance

flue: add generic code review alongside style-guide review (#31562) * flue: add generic code review alongside style-guide review Adds a bonk-style generic engineering review that runs in the same orchestrator run as the existing style-guide review and posts findings in the same bot comment, now split into "### Code Review" and "### Style Guide Review" sections. - New code-review skill: reviews all changed files (including code examples in MDX) for bugs, error handling, security, dead code, and maintainability. No style/prose checks; defers CI-caught issues. - New in-process fan-out (lib/code-review-inproc.ts) mirroring the style-guide one: per-file sessions, concurrency 5, cap 20 files. - Code findings add a `critical` severity above warning/suggestion and use the CR- id namespace; reconcile skill preserves it. - Code-review agent gets full-file context via GitHub-API-backed tools (read_repo_file defaults to the PR head SHA, search_repo). - The repo root AGENTS.md is fetched at the head SHA and injected as agent instructions every run, since the Worker has no repo checkout to discover it from. - Orchestrator runs both reviews concurrently (one failing degrades to empty rather than aborting), reconciles per stream, persists { code, style } findings to R2 (legacy bare-array tolerated), and renders one unified comment. Cadence is unchanged: this rides the existing code-review-orchestrator triggers (auto on PRs, /review, /full-review). * flue: address code-review self-review findings Fixes surfaced by the bot reviewing its own PR (#31562): - getRepoFileContent: decode base64 as UTF-8 via TextDecoder (atob alone produced mojibake for non-ASCII content such as em dashes in AGENTS.md); URL-encode path segments; return null only on 404 and throw on other non-2xx so "absent" is distinct from "failed to load". - Fetch the root AGENTS.md from the PR base ref instead of the head SHA. The content is injected into agent instructions, so reading it from the head let a PR poison AGENTS.md to inject instructions into the reviewer. - Render: a degraded (failed) review section now shows a failure note instead of "No issues found", and the status line notes the partial failure; carried-forward findings still render. Orchestrator passes the per-stream failure flags into renderComment. - Render: match acknowledged findings by stable id, not path:line:rule, so two findings sharing those fields are not both dropped. - github-repo-tools.ts: update stale file header (now shared by the Dependabot and code-review agents). * flue: run review fan-outs sequentially to fix DO memory resets Running the code-review and style-guide fan-outs concurrently kept ~10 model sessions live in a single Durable Object isolate and over-ran its 128 MB limit, producing repeated "isolate exceeded its memory limit and was reset" errors (and downstream event-stream append failures). - Run the two fan-outs sequentially instead of via Promise.all, so one fan-out's sessions are reclaimed before the next starts (roughly halves peak heap). Per-stream failure isolation is preserved. - Lower code-review concurrency from 5 to 3, since its sessions are heavier (full-file reads + injected AGENTS.md) than style-guide ones. Trade-off: review wall-clock is now the sum of the two fan-outs rather than the max — acceptable for a background review bot. * flue: split reviewers into separate specialist workflows Move the code-review and style-guide fan-outs out of the orchestrator DO into their own discovered workflows, so each runs in its own Durable Object isolate (own 128 MB budget). This removes the shared-isolate memory contention that caused "isolate exceeded its memory limit and was reset" errors and restores parallel execution. - New workflows code-review-specialist + style-guide-specialist (FlueCodeReviewSpecialistWorkflow / FlueStyleGuideSpecialistWorkflow). Each self-fetches its own diff once (no per-file fetch, no R2 diff staging), stages it into its own workspace, runs the existing in-process fan-out (reused verbatim), and returns findings as its run result. - Orchestrator now decides diff mode only (no file fetch), admits both specialists via admitWorkflow and polls them concurrently via pollRun (the spam-filter pattern). A timed-out/errored specialist degrades to an empty section with its failure flag set; both failing -> failure comment. - Specialists self-heal incremental -> full diff if the base SHA is gone. - Code-review concurrency restored to 5 (own isolate now). - New shared lib/review-specialist.ts: payload contract + helpers. - writeDiffToWorkspace accepts a minimal DiffPullRequest shape. - wrangler v5 migration adds the two new SQLite DO classes. Supersedes the sequential-fan-out workaround; the fan-outs no longer run in the orchestrator DO at all. * flue: remove unused DiffMode import in code-review-specialist * flue: add beta disclaimer note under Code Review heading * flue: lower code-review specialist concurrency to 3 to stay under DO memory limit * flue: cap code review at 10 files and raise specialist poll timeout The code-review specialist timed out on large PRs. AI Gateway showed all model calls succeeding (0 failures) but slow (p90 ~47s, p99 ~103s), so the cause was DO memory pressure plus total wall-clock, not model errors: - A 13-file run at concurrency 5 hard-OOM'd the specialist isolate ("SQL query failed: ... memory limit") and never reached run_end. - Even without OOM, 13 multi-turn file sessions exceeded the orchestrator's 10-minute poll deadline. Fixes: - CODE_REVIEW_MAX_FILES 20 -> 10. Each code-review file is a multi-turn agent session, so this bounds both peak isolate memory and wall-clock. Covers virtually all docs PRs; larger PRs review their 10 largest files. - Orchestrator specialist poll timeout 10m -> 20m, since a legitimate large review is many slow model calls and the specialist runs durably in its own DO. - Concurrency stays at 3 (memory). * flue: free per-file review sessions to fix specialist DO OOM Delete each per-file agent session as soon as it finishes so harness memory is bounded to ~concurrency live sessions instead of growing with the changed-file count. With the leak fixed, restore the code-review cap to 20 files and concurrency to 5, and drop the dead reserveTokens hint. * enable tracing * flue: document code-review architecture in AGENTS.md * flue: reduce review turns, add watchdog, per-file abort, env-overrides Pre-stage added lines + file content into skill args (code-review-inproc.ts, code-review-specialist.ts, SKILL.md): trusted TypeScript now parses the diff and fetches the full file at head SHA before each session opens, eliminating the mandatory setup turns (read manifest → read patch → parse lines → read_repo_file). Cross-file tools remain available for optional lookups. Removes diff workspace staging from the code-review path entirely. Add external cron watchdog (review-watchdog.ts, review-watchdog-decide.ts, run-state.ts): a scheduled handler fires every 2 minutes, detects reviews stuck past a deadline via inflight R2 markers, and re-drives them. Workflows are non-resumable after DO interruptions; the watchdog is the only reliable recovery path. Inflight markers are written at review start and cleared on completion (code-review-state.ts, code-review-orchestrator.ts). Per-file hard timeout now aborts the CallHandle before deleting the session (code-review-inproc.ts, style-guide-inproc.ts): session.delete() rejects while an operation is active, so abort must settle the operation first. Fixes zombie session leak on timeout. Env-overridable concurrency and file timeout (lib/env.ts): both specialists read CODE_REVIEW_CONCURRENCY, CODE_REVIEW_FILE_TIMEOUT_MS, STYLE_GUIDE_CONCURRENCY, STYLE_GUIDE_FILE_TIMEOUT_MS so local dev can run lower values without touching prod defaults. Staged-diff cleanup in style-guide-specialist.ts: removeWorkspacePath in try/finally so the run-scoped SQLite rows are freed after each review. Added removeWorkspacePath to connectors/cloudflare-shell.ts. Wrangler: cron trigger every 2 min, DOCS_FLUE_BASE_URL var for watchdog. Tooling: flue:reset:local script, NODE_OPTIONS on flue:dev, fixed clear-r2-pr-data.ts to cover both state paths and inflight/ prefix. * flue: remove watchdog (never ran; reviews healthy without it) The scheduled watchdog was never functional in prod: Flue drops non-HTTP handlers from app.ts (they require cloudflare.ts), so the cron fired every 2 minutes and logged "Handler does not export a scheduled() function" 30 times per hour without ever invoking runReviewWatchdog(). Reviews stopped getting stuck independently — the skill rewrite + per-file session.delete() + concurrency limits reduced orchestrator interruptions to near-zero. The watchdog's run-state detection and re-admission path were also untested end-to-end, so enabling it carried real risk. Removes: review-watchdog.ts, review-watchdog-decide.ts, run-state.ts, all inflight marker API from code-review-state.ts, all marker call sites from code-review-orchestrator.ts, triggers.crons + vars.DOCS_FLUE_BASE_URL from wrangler.jsonc. Reverts app.ts to canonical export default app. Keeps: markAutoReviewCompleted, renderFailureComment, bypassReviewLimit (all used independently). bin/clear-r2-pr-data.ts inflight/ handling kept for one-time cleanup of orphaned prod R2 markers. * flue: explicitly clear crons in wrangler config An absent triggers key leaves existing cron triggers intact on deploy; triggers.crons=[] forces wrangler to PUT an empty schedule list, actually deregistering the leftover */2 cron. * flue: address ask-bonk review findings (items 1-4) 1. Extract withConcurrency to lib/inproc-utils.ts; import from both code-review-inproc.ts and style-guide-inproc.ts instead of duplicating. 2. Fix read_repo_file tool UTF-8 decoding: use TextDecoder instead of bare atob() so non-ASCII content (em dashes, CJK, smart quotes) is not mojibake. Also encode path segments with encodeURIComponent, matching the getRepoFileContent fix already applied to github.ts. 3. Fix parseAddedLines: skip lines starting with backslash ('\ No newline at end of file') instead of treating them as context lines. Previously this incremented newLine, producing off-by-one line numbers for every subsequent added line in files without a trailing newline. 4. Fix stale comments: code-review-diff.ts, style-guide-inproc.ts, and wrangler.jsonc v4 comment still described the old in-orchestrator-DO architecture; updated to reflect the specialist-DO split. * flue: add holistic code review mode with size-based routing and forced-mode commands Routes code review to one of two strategies based on combined diff size: Fan-out (≤50 KB): per-file sessions, concurrency 5, cap 20 files. Good for smaller PRs; maximum per-file detail, parallel sessions, per-file degradation. Holistic (>50 KB): single session over the entire PR diff in one pass, cap 50 files (lib/code-review-holistic.ts). Enables cross-file reasoning, no per-file setup overhead, faster and more reliable on large PRs where fan-out wedges. New code-review-holistic skill: rich substance from the per-file skill, reframed for whole-PR review, model-owned navigation. Comment heading reflects which ran: 'Holistic Code Review' or 'Fan Out Code Review'. Both paths log inputTokens/totalTokens for calibration. Two new codeowner slash commands: /fan-out-review — forces fan-out regardless of diff size (with warning in the comment that it may be slow/fail on large PRs) /holistic-review — forces holistic regardless of diff size forceReviewMode threads through orchestrate → orchestrator → review-specialist → code-review-specialist, overriding size-based routing when set. Also: selectCodeReviewFiles takes an optional maxFiles param (holistic passes 50, fan-out uses the existing 20 default); per-file usage logging (inputTokens, totalTokens) added to reviewSingleFile; progress logs committed from the previous session also included here. * flue: fix Dependabot routing for /fan-out-review and /holistic-review; fix partial run consuming auto-review slot /fan-out-review and /holistic-review now check getPullRequest().user.login for dependabot[bot] before dispatching, matching the /review and /full-review pattern. Dependabot PRs route to /workflows/dependabot-review without forceReviewMode; regular PRs keep the forced mode. markAutoReviewCompleted now only fires when both codeOutcome.ok and styleOutcome.ok are true. Previously a partial run (one specialist degraded) still consumed an auto-review slot, which blocked the retry the comment promised would happen on the next push. * [Flue] Replace orchestrator poll with R2 rendezvous + finalize-review workflow Remove the 20-minute specialist poll from the code-review orchestrator (root cause of stuck reviews when the orchestrator DO was interrupted mid-wait). Replace with an event-driven finalize pattern: - Orchestrator is now dispatch-only: limit check, placeholder, diffMode, write context.json to R2, admit both specialists fire-and-forget, return. - Each specialist wraps its review in try/catch (degraded result on error), writes its stream result to R2, then races for a conditional-PUT finalize lock (If-None-Match: *). Exactly one specialist wins. - New finalize-review workflow (FlueFinalizeReviewWorkflow, v6 migration): reads context + stream results from R2, head-guards against newer pushes, idempotency-guards against double-finalize, reconciles both streams, persists review JSON, renders and posts the comment, swaps reactions, marks auto-review slot consumed, cleans up the pending namespace. - reviewMode is carried through context.json so finalize always uses the same mode the orchestrator decided on (fixes log-vs-comment split in local dev where DO env views can differ). - dispatchId scoping isolates concurrent same-head dispatches (e.g. auto-review + /full-review arriving simultaneously). - Zero new custom Durable Object bindings beyond the standard Flue workflow class (FlueFinalizeReviewWorkflow in wrangler.jsonc v6). * [Flue] Use kimi-k2.7-code for reconciliation (drop glm-4.7-flash) * [Flue] Write degraded placeholder before review to prevent stuck finalize A specialist DO that is hard-evicted mid-review never reaches the writeStreamResult call at the end, leaving no code.json/style.json for the other specialist to detect and claim the finalize lock — exactly the stuck-review scenario seen on PR #31736. Fix: each specialist now writes { ok: false, degradedResult } to R2 BEFORE starting its review. If the DO is evicted, the placeholder is already there. The placeholder is overwritten with the real result on success. Either way finalize always has two stream results and will run, posting a degraded-section comment rather than staying stuck forever. Also fixes the unused FinalizeContext import lint error. * [Flue] Fix premature finalize: add final:boolean to stream results The placeholder writes added in the previous commit caused a race: both specialists write their degraded placeholders within ~1-2s, the first to write checks the sibling's placeholder (which looks like a valid result), claims the lock, and finalize fires immediately with two ok:false results before either review ran — posting an instant failure comment. Fix: - Add final:boolean to StreamResultPayload (false=placeholder, true=real) - tryClaimFinalize now checks final:true on the sibling — a placeholder (final:false) is not treated as 'done', preventing premature triggering - Orchestrator writes both crash-protection placeholders (final:false) BEFORE admitting specialists so a key exists even if a specialist DO is evicted immediately after admission - Specialists write final:true in their rendezvous tail (removed the redundant per-specialist placeholder writes added previously) * [Flue] Address AI review findings — robustness, safety, correctness, refactors A. Robustness (stuck-review fixes): - Wrap all specialist setup (token, diff fetch) + review in one try/catch; any setup failure now writes a final:true degraded result and triggers finalize rather than throwing and leaving the placeholder stuck at final:false. Extract shared reportSpecialistResult() helper into lib/finalize-rendezvous.ts to eliminate the duplicated rendezvous tail across both specialists. - Orchestrator admit failures overwrite the placeholder with final:true degraded; if both fail, orchestrator itself claims the finalize lock and admits finalize. Drop redundant type casts on the narrowed admit union. - finalize-review post-comment failure now returns {finalized:false} and skips markAutoReviewCompleted and cleanupPending so the next push can retry without burning an auto-review slot on an undelivered comment. - Degraded streams (ok:false) skip reconciliation and carry previous findings forward as active, preventing false resolution of prior issues. B. Defensive R2 / JSON: - Wrap obj.json() in try/catch in readContext, readStreamResult, and tryClaimFinalize; treat corrupted/partial writes as null/not-final. C. Safety: - Guard req in orchestrator with an explicit throw instead of req!. - safeOrigin() helper returns '' on URL parse failure in both specialists. - parseReviewSpecialistPayload validates pr field shapes and DiffMode union (incremental requires fromSha+toSha strings); normalizes baseUrl to a valid absolute http(s) origin via new URL().origin, dropping invalid values. D. Correctness: - Holistic reviewedFiles now built from patched files only, matching the diff actually sent to the model. - clearTimeout called immediately after await handle resolves in both holistic and per-file reviewSingleFile, preventing a late timer from mislabeling a post-resolve error as a timeout. - Finding ID hash widened from 6 to 12 hex chars (24→48 bit) in both CR-/SG- namespaces; line number deliberately kept excluded for cross-commit stability. - withConcurrency clamps limit to Math.max(1, Math.floor(limit)). E. Dev script (bin/clear-r2-pr-data.ts): - WHERE clause tightened to 'diffs/pr-%' and 'inflight/pr-%' (was 'diffs/%'). - Switch execSync string interpolation to execFileSync with argument arrays. - Freshen stale header comment. F. Refactors: - Collapse four near-identical /review /full-review /fan-out-review /holistic-review handlers in orchestrate.ts into one shared helper. - Merge duplicate cloudflare-shell imports in style-guide-specialist.ts. G. Docs: - AGENTS.md: add finalize-review row to workflow table; rewrite request flow to describe dispatch-only orchestrator, R2 rendezvous, final:bool flag, and finalize-review steps; add v6 migration; update slash-command list. * [Flue] v7+v8 migrations: clear specialist DO storage to break OOM death spiral The FlueCodeReviewSpecialistWorkflow and FlueStyleGuideSpecialistWorkflow DOs accumulated SQLite state from previous crashed runs. Each OOM leaves orphaned session data in the DO's storage. After several crashes the accumulated state is large enough that even the Flue alarm recovery handler OOMs on startup (~900ms, repeating every ~30-60s), creating a death spiral where no future review can complete. Fix: two-step migration to reset the storage: v7 — rename bloated instances to *Old (abandons their storage) v8 — recreate the classes with empty storage under the original names The wrangler bindings still point to the original names (FlueCodeReview- SpecialistWorkflow / FlueStyleGuideSpecialistWorkflow), so no code changes are needed. Run history prior to v7 is lost. * Revert "[Flue] v7+v8 migrations: clear specialist DO storage to break OOM death spiral" This reverts commit fa5e960052398ec7520d3804f145948b1edf6c5e. * [Flue] Specialist split: conventions + redirect specialists, N-stream rendezvous, style-guide rule additions - Generalise finalize rendezvous from 2 streams to N streams (EXPECTED_STREAMS constant; tryClaimFinalize loops all siblings in parallel; stream type widened to string; expectedStreams threaded through context, payload, and options) - Add conventions specialist (light AI session, conventions-check skill): checks PR title format, Summary content against fetched template, and redirect checklist when docs files are renamed/deleted - Add redirect specialist (pure TypeScript, no model): derives old+new URLs from file paths, skips format-only moves (foo.mdx → foo/index.mdx), splat-aware __redirects matching, degrades gracefully if file unreadable - Redirects reconcile deterministically in finalize (no LLM); conventions force full diff mode; bothFailed gate remains code+style only - Add previous_filename to PullRequestFile for correct rename handling - Add marketing-language and time-sensitive-content suggestions to style-guide core-content reference; add component should-use suggestions to code-blocks - Render: 4 sections (Code → Conventions → Style → Redirects); pr path renders as PR label; no-findings messages use <sub> (smaller, no emoji); top-level status line unchanged - wrangler.jsonc v7: new_sqlite_classes for both new DO classes - Fix idempotency guard to skip in log mode (guard is comment-mode only) * [Flue] Add /disable-auto-review command Codeowners can comment /disable-auto-review on a PR to stop push-triggered reviews from running. The flag is stored in R2 at diffs/pr-<n>/auto-review-disabled.json (same pattern as ignore-review-limit). Manual /review and /full-review commands (bypassReviewLimit=true) still work normally. The command is acknowledged with a thumbs-up reaction. * [Flue] Remove holistic code review — always fan-out Holistic mode timed out on large PRs (>50 KB diff, single model pass, 15-min hard timeout) producing zero findings. Fan-out is strictly better: bounded per-file sessions, graceful per-file degradation, guaranteed completion on any diff size. - Delete lib/code-review-holistic.ts and .agents/skills/code-review-holistic/ - code-review-specialist.ts: always fan-out; remove routing logic, holistic imports, env reads, forceReviewMode handling - lib/code-review-inproc.ts: remove CODE_REVIEW_HOLISTIC_* constants and re-export; remove reviewMode from both return sites - lib/code-review-results.ts: remove reviewMode field from CodeReviewResult - lib/review-specialist.ts: remove forceReviewMode from payload type + parser - code-review-orchestrator.ts: remove forceReviewMode from payload + specialistBody - orchestrate.ts: remove /fan-out-review and /holistic-review commands - code-review-render.ts: heading always 'Code Review'; remove codeMode from RenderReviewInput; remove /fan-out-review and /holistic-review command rows - finalize-review.ts: remove codeMode from renderComment call - AGENTS.md: remove holistic routing description and command bullets * [Flue] Remove unused CODE_REVIEW_MAX_FILES import in specialist * [Flue] Relax conventions checks — semantic over format Replace rigid format rules (title must start with [Product] or type:, description must have a ### Summary section) with lenient semantic checks: 1. Product/area identified — title OR description names the area; no tag required 2. Description explains the work — any human prose passes; only flag truly empty/placeholder descriptions 3. Scope accuracy — only flag material misrepresentation, not missing details Default to no finding in all three. Only flag clear, significant violations. * [Flue] Tighten scope accuracy check — flag any unmentioned core change * flue: remove unused-imports rule from style guide review * [Flue] Fix 7 bot-review findings 1. Diff parser: use '+++ '/'--- ' (trailing space) so source lines like '++i;' (patch: '+++i;') are not skipped as file headers. Previously any added line beginning with '++' was silently dropped from args.addedLines. 2. admitWorkflow outside catch-all in reportSpecialistResult: if admitWorkflow threw after tryClaimFinalize won the lock, the exception was swallowed, the lock stayed claimed, and finalize was never admitted for that dispatch. Now the R2 write + lock claim are in the try/catch but the admit call is outside it, so admission errors propagate and can be retried. 3. req guard before placeholder post in orchestrator: the 'if (!req)' check was after the GitHub comment mutation, leaving a stuck 'review pending' comment if req was unexpectedly absent. Moved before the placeholder post. 4. Unhandled getPullRequest failure in finalize: a GitHub API error aborted finalize without running cleanupPending, leaving a stale pending namespace. Wrapped in try/catch with cleanup and graceful return. 5. getIssueComments called unconditionally in log mode: botComment is only used in comment mode (idempotency check + post/update). Moved the fetch inside the 'reviewMode === comment' block to avoid a needless GitHub call and failure surface in log mode. 6. markAutoReviewCompleted read-modify-write race: two concurrent finalizes for the same PR could both read the same state, both pass the headSha dedupe check, and overwrite each other, double-incrementing the count. Fixed with an ETag-based conditional PUT (If-Match / If-None-Match: *) with up to 3 retries on conflict. 7. AGENTS.md stale: updated to reflect 4 specialists (added conventions + redirect rows to workflow table, updated description, request flow, R2 state shape, rendered sections, migration history); added /disable-auto-review to slash commands list. * [Flue] Remove redirect specialist from review pipeline The redirect check added noise without enough signal. Removes the entire stream from the 4-specialist pipeline, leaving code, conventions, and style. - Delete workflows/redirect-specialist.ts - EXPECTED_STREAMS: ['code','style','conventions','redirects'] → 3 streams - Remove degradedRedirectsResult() from finalize-rendezvous.ts - Orchestrator: drop redirects placeholder write, specialist admission, admit-results entry, log fields, and return value - finalize-review: drop redirectsPayload read, missing-results guard term, previousRedirectsFindings, reconcileRedirects helper, reconciledRedirects calls, persisted 'redirects' key, renderComment args, and totalActive/ totalIgnored/totalResolved terms - code-review-render: remove redirects/redirectsFailed from RenderReviewInput, drop redirects from counts and anyFailed, remove Section 4 renderSection call, remove Redirects from acknowledged-by-author block - wrangler.jsonc: v8 migration deletes FlueRedirectSpecialistWorkflow DO class - AGENTS.md: update to 3 specialists throughout; remove redirect rows from workflow table, state shape, rendezvous namespace, and render sections; add v8 migration note; remove stale CI policy note about missing redirects - conventions-check SKILL.md + conventions-specialist.ts: remove stale references to redirect checklist in descriptions/comments * [Flue] Address 16 bot-review findings (W1-W16, S1-S8) W1: Wrap session.skill() reconcile call in finalize-review.ts — a thrown rejection now degrades to current findings instead of crashing finalize. W2+S6: Guard handle.abort() in both inproc timer callbacks with Promise.resolve().catch(() => {}) so abort errors don't produce unhandled rejections from setTimeout. W3: Add allExpectedStreams.includes(myStream) guard in tryClaimFinalize so only legitimate expected streams can trigger finalization. W6: Move parseReviewSpecialistPayload inside the try block in all three specialists (code, style, conventions) so a malformed payload degrades gracefully instead of rejecting the workflow. W7: typeof input.pr === 'object' && input.pr !== null guard in parseReviewSpecialistPayload so non-null non-object values don't cause a TypeError before the intended validation error. W8: Validate every expectedStreams element is a string before passing to downstream rendezvous logic. W9: Wrap isAutoReviewDisabled JSON parse in try/catch — corrupt file now returns false instead of propagating. W10: Validate count and shas shapes in markAutoReviewCompleted before arithmetic and array operations to guard against corrupt data. W11: Rewrite AGENTS.md placeholder description — clarify that final:false placeholders guarantee keys exist in R2 but do NOT trigger finalize; tryClaimFinalize still requires every stream to be final:true. W12+S8: Replace getPullRequest API call in orchestrate.ts slash-command handler with body.issue.user.login from the webhook payload, removing a failure mode that could silently misroute Dependabot PRs. W13+W14: Wrap setReviewLimitIgnored and setAutoReviewDisabled in try/catch in orchestrate.ts — R2 write failure now returns a structured error response instead of propagating a 500 that may trigger webhook retries. W16: Guard NaN in withConcurrency — Math.floor(NaN) passes through Math.max and causes Array.from({ length: NaN }) to throw RangeError. Now clamps to 1 when limit is not finite. S1: Use existing GitHubIssueComment type import in finalize-review.ts instead of inline import() expression. S2: Paginate R2 list in cleanupPending — loop while truncated so all keys under the pending prefix are deleted, not just the first page. S3+S4: Fix stale 'four' in orchestrator header comment; renumber duplicate step-4 labels (context write is now 3, placeholders 4). S7: Preserve original error as cause when converting abort into timeout error in style-guide-inproc.ts. * [Flue] Remove conventions section note from rendered comment * [Flue] Address second-round bot findings (8 fixes) W1: Wrap getIssueComments in finalize-review.ts — API failure now treats the run as not-yet-finalized and continues rather than crashing. W2: Wrap cleanupPending at end of success path — cleanup failure no longer rejects the workflow after the comment is already posted; S1: log markAutoReviewCompleted failure instead of silently swallowing it. W3: More precise git file-header skip in diff parser — match on '+++ b/', '+++ a/', '+++ /dev/null', '--- b/', '--- a/', '--- /dev/null' exactly so source lines like '++ something' (patch: '+++ something') inside a hunk are not incorrectly skipped. W6: Count critical findings from conventions and style in the status-line criticalCount so they surface in '🚨 N critical' even though their renderSection calls still use includeCritical=false. W7: Add pr.body, pr.author, and pr.labels element type checks to parseReviewSpecialistPayload — aligns validation with the declared ReviewSpecialistPrMeta contract. W8+W9: Wrap addReactionToComment after setReviewLimitIgnored and setAutoReviewDisabled — reaction failure no longer masks a successful state write; handler returns acted:true and logs the reaction error. S3: Log when myStream is not in allExpectedStreams in tryClaimFinalize so a misconfigured stream name is visible in logs. * [Flue] Fix two bot findings: quoted diff paths + conventions scope input S: Skip git-quoted file headers in diff parser (paths with spaces/special chars produce headers like '+++ "b/my file.ts"' which the previous prefix checks did not match, causing them to be recorded as added lines). W: Pass changedFiles to conventions-check skill so Rule 3 (scope accuracy) can actually evaluate the full set of changed files, not just renamedDocFiles. Builds a compact {filename,status,additions,deletions} list from the already-fetched PR file list; no extra API call needed. Skill updated to document the new input and use it in Rule 3. * [Flue] Separate 'Acknowledged by author' from last review section with hr * [flue] bump wrangler to 4.107.0; regenerate lockfiles via public npm - .flue/package.json: wrangler 4.97.0 → 4.107.0 (required by @cloudflare/vite-plugin@1.43.0) - Cleared ~/.npmrc Cloudflare internal registry redirect; all @cloudflare/* packages now resolve from public npm, fixing 401 noise and broken workerd@1.20260630.1 binary - Regenerated root and .flue lockfiles against public registry * [flue] fix C1/W1/W2/S3 from code review C1 (style-guide-specialist): guard diffDir before cleanup in finally — without the check, a parse failure would rm -rf / on the DO's SQLite filesystem. W1 (finalize-review + code-review-render): add <!-- status: failure --> to renderFailureComment; update idempotency check to treat both pending and failure as retryable states so /review is not permanently blocked after a both-failed run on the same head SHA. W2 (conventions-specialist): hoist session variable and add finally block calling session?.delete() — matches the pattern in the other two specialists and prevents SQLite event-stream data from accumulating across workflow runs. S3 (clear-r2-pr-data): remove dead OR key LIKE 'inflight/pr-%' branch; no code writes under that prefix. * [flue] fix S2/N1/N2 from re-review S2: renumber orchestrator step comments 3,3,4,4 → 3,4,5,6 N1: style-guide-inproc degraded-file error log: event code_review_orchestrator → style_guide_specialist N2: code-review-inproc degraded-file error log: event code_review_orchestrator → code_review_specialist * [flue] fix N4: delete reconciliation session in finalize-review Session created for the three reconcileStream calls was never deleted, leaving its SQLite event-stream data to accumulate across reviews. Matches the session.delete() pattern from the specialist DOs (W2).

feat: Add flue style guide review bot (#31072) * first pass * fix: pass reviewedFiles to reconciler so incremental reviews correctly resolve fixed findings * [flue] Add wrangler dev script and orchestrator improvements * [flue] Refactor style guide references, improve review quality and speed - Restructure style guide references into always/, conditional/, components/ subdirectories - Update manifest to use granular per-component reference files - Add stale file cleanup to sync-agents script - Improve style-guide-review SKILL.md: add patch parsing, no-enumeration, and no-absence-reasoning instructions - Preserve existing bot comment body when posting pending review update - Add clear-r2-pr-data.ts utility script - Minor orchestrator and spam filter improvements * [flue] Add commands section to code review comment * [flue] Remove import-only component refs, add commands section, fix pending comment body * [flue] Fix duplicate pending status when /full-review is triggered on existing pending comment * [flue] Add /review command for on-demand incremental or full review * [flue] Cap automatic reviews at 2 per PR, bypass for codeowner commands * [flue] Skip spam filter for codeowner-opened issues and PRs * [flue] Remove PR allowlist gating — ready for production * fix: Address PR review feedback — label bug, comment pagination, table cell escaping, wrangler-config example * chore: format flue agent files with prettier * [flue] Restrict code review to codeowner PRs; reduce log noise * fix: prefix unused reviewResponse vars with underscore to satisfy ESLint * [flue] Remove codeowner gate — auto-review all PRs * [flue] Fix duplicate paused message in review limit comment * [flue] Fix duplicate paused message — skip update if already paused * fix: address PR review feedback — section numbers, no-op replace, table sanitization, JSDoc * chore: bump @flue/cli and @flue/runtime to 0.7.1

fix: flue - harden style-guide fan-out, replace wait=result with Durable Streams polling, and refactor domain logic into lib/ (#31436) * [flue] Reduce style-guide fan-out concurrency and scope child hydration by filename - Lower STYLE_GUIDE_CONCURRENCY from 10 to 5 to reduce concurrent DO memory pressure - When a filename is specified, hydrate only manifest.json, pr.json, comments, and the single patch file instead of listing every object in the diffDir prefix - Re-enable and improve fan-out structured logs in code-review-orchestrator: style_guide_fanout_start, style_guide_complete, and per-child dispatch events - Add filename to all style-guide-review log events for per-child observability - Add hydration_start/hydration_complete logs with object counts * [flue] Avoid redundant R2 GETs for manifest.json and pr.json in targeted hydration manifest.json and pr.json are already fetched earlier in the run function (for the fast-fail check and PR metadata read). Reuse their in-memory text instead of re-fetching from R2 inside the targeted diffKeysToLoad branch. Only comments and the patch file are fetched fresh in targeted mode. * style: format * [flue] Fix Body already used error in targeted hydration manifestObj.text() was called at parse time (step 1) and then again inside the cachedDiffResults block. Same for prObj.json() then prObj.text(). R2 response bodies are single-use streams — reading twice throws TypeError. Fix: capture manifestText and prText as strings on first read, reuse them for both parsing and workspace write. * [flue] Log actual error before Flue swallows it as generic 500 Wrap the style-guide-review run body in a top-level try/catch that logs the error message and stack with full context (PR number, filename, diffDir, runId) before rethrowing. Previously any unhandled throw was caught by Flue and surfaced to the parent orchestrator only as a generic 500 internal_error with no child-side log, making the root cause invisible in Workers Observability. * style: format * [flue] Replace ?wait=result fan-out with accepted mode + Durable Streams polling Previously each style-guide child dispatch used ?wait=result, holding a synchronous HTTP request open to the child DO until it completed. If that response path dropped (child finished but parent never received the result), the parent's Promise.all would hang indefinitely. Observed in PR #31422: all 11 child runs completed on the child side, but one parent-side style_guide_child_dispatch_complete was never logged. New approach: - Invoke each child in accepted mode (no ?wait=result); receive runId in 202 - Poll /runs/:runId via Durable Streams long-poll until run_end is observed - Each long-poll subrequest has a bounded lifetime (<=30s per Flue protocol) - Resume from offset after each response so no events are missed - If run_end.isError, throw with the actual error message - If deadline (5 min) exceeded without run_end, return empty result with a timeout log rather than hanging the parent forever New log actions: - style_guide_child_run_admitted - style_guide_child_run_observe_start - style_guide_child_run_observe_complete - style_guide_child_run_observe_failed - style_guide_child_run_observe_timeout - style_guide_child_run_observe_fetch_error - style_guide_child_run_observe_error * style: format * [flue] Apply accepted-mode + Durable Streams polling pattern everywhere Extract shared admitWorkflow() and pollRun() helpers into lib/poll-run.ts so the pattern is consistent across all orchestrators. orchestrate.ts: - Dependabot PR events (3a): fire-and-forget admitted mode — result is not needed by the orchestrate workflow; the dependabot-review workflow handles its own GitHub output - /full-review and /review slash commands (3, 4): same — fire-and-forget; result discarded in original code too - Spam filter (5): admit + poll, since the closed boolean determines whether to run code review. Timeout treated as 'not spam' to avoid blocking review - Code review orchestrator (6): fire-and-forget admitted mode — it posts its own GitHub comment when done; orchestrate does not need to wait code-review-orchestrator.ts: - Replace inline dispatchStyleGuideReview / pollStyleGuideRun with a thin wrapper over the shared admitWorkflow() + pollRun() helpers - Keeps all existing structured log actions intact lib/poll-run.ts (new): - admitWorkflow(): POST to any workflow pathname, return runId from 202 - pollRun<T>(): poll /runs/:runId via Durable Streams long-poll until run_end, with configurable timeout and transient error retry * style: format * [flue] Upgrade model to kimi-k2.7-code across all workflows * [flue] Extract model constants into lib/models.ts Add lib/models.ts with PRIMARY_MODEL and RECONCILIATION_MODEL. Replace hardcoded model strings in all four workflow files. * Revert "[flue] Extract model constants into lib/models.ts" This reverts commit 23ab445bfeb550adeb5f1f719286261c596c8368. * [flue] Extract style-guide result types/schemas into lib/style-guide-results.ts Move StyleGuideFindingFromModelSchema, StyleGuideResultFromModelSchema, StyleGuideFinding, StyleGuideResult, and assignFindingIds out of the workflow file into a shared lib. style-guide-review.ts re-exports the public types; code-review-orchestrator.ts imports directly from lib. * style: format * [flue] Extract style-guide workspace hydration into lib/style-guide-hydration.ts * style: format * [flue] Extract style-guide fan-out mechanics into lib/style-guide-fanout.ts * style: format * [flue] Extract code-review diff/state helpers into lib/code-review-diff.ts and lib/code-review-state.ts * style: format * [flue] Extract code-review comment rendering into lib/code-review-render.ts * style: format * [flue] Extract GitHub webhook parsing helpers into lib/github-webhook.ts * style: format * [flue] Extract spam-filter domain helpers into lib/spam-filter.ts * style: format * [flue] Extract Dependabot review helpers into lib/dependabot-review.ts * style: format * [flue] Fix redundant R2 GETs in full hydration mode and misleading acted:true on dispatch failure --------- Co-authored-by: cloudflare-docs-bot[bot] <cloudflare-docs-bot[bot]@users.noreply.github.com>

feat: add /rebase command to cloudflare-docs-bot (#32121) * feat: add /rebase and /rebaseWithConflicts slash commands to cloudflare-docs-bot * chore: fix lint errors (unused imports, misleading emoji char class) * fix: address code review findings on rebase workflow * fix: address second round of code review findings on rebase workflow * fix: address third round of code review findings on rebase workflow * fix: address fourth round of code review findings on rebase workflow * fix: handle production-side renames in AI conflict resolution path * fix: separate conflict read/write paths and deduplicate tree updates * fix: address sixth round of code review findings on rebase workflow * fix: distinguish permanent vs transient errors in polling, remove duplicate JSDoc * fix: address human reviewer findings (binary files, conflict assertion, fork detection, dead code) * fix: address final review polish (fork null, JSON parse, rename prompt, commit msg, mode, confidence) * fix: fall back to previousPath for mode lookup on renamed conflict files * feat: drop raw API error from halted-conflict, react 👍/👎 based on outcome * feat: improve AI confidence prompt, surface model reason on downgrade * feat: convert /rebaseWithConflicts resolver to Flue agent with bounded tools and skill * fix: address code review findings on rebase agent and tools * fix: extract paginateCompare, fix rate-limit 403, 300-file guard, in-progress error handling, backtick strip, groot-preview, stale JSDoc * fix: token error handling, Retry-After clamping, marker regex, SHA validation, confidence reason * Fixed SHA regex; reviewed PR #32121. Co-authored-by: mvvmm <mvvmm@users.noreply.github.com> * fix: guard fetch errors, binary conflicts, production file cap, duplicate marker, JSDoc * feat: collapse /rebase and /rebaseWithConflicts into a single /rebase command * chore: remove mode field from rebase workflow payload * fix: integer validation for payload IDs, strip stale metadata in render fallback --------- Co-authored-by: ask-bonk[bot] <ask-bonk[bot]@users.noreply.github.com> Co-authored-by: mvvmm <mvvmm@users.noreply.github.com>

chore: upgrade Flue to 0.9.1 and isolate into its own workspace (#31240) * chore: upgrade Flue bot to 0.9.1 * regenerate pnpm lock * fix: pin Vite for Astro checks * fix: remove unused Flue workflow id * chore: isolate Flue into its own pnpm workspace * chore: move flue.config.ts into .flue/ and ignore generated vite cache * chore: remove root flue.config.ts * chore: format eslint.config.js

feat: add Dependabot review workflow to docs bot (#31258) * feat: add Dependabot review workflow with GitHub API-backed repo tools * fix: remove stale junk from wrangler.jsonc * chore: empty stale R2 keys list * fix: summary table at top, per-package details collapsed * style: format * fix: address PR review — reaction swap, empty packages guard, dedup fetchPrAuthor, fix JSDoc --------- Co-authored-by: cloudflare-docs-bot[bot] <cloudflare-docs-bot[bot]@users.noreply.github.com>

feat: add unit tests for trusted flue functions (#32186) * feat: add unit tests for trusted flue functions * fix: resolve typecheck and eslint issues in test files * fix: correct malformed hunk headers in diff fixtures * docs: add Testing section to .flue/AGENTS.md

feat: add Flue spam and off-topic filter agent (#30832) * chore: ignore .worktrees/ directory * Revert "chore: ignore .worktrees/ directory" This reverts commit 4c311f351c244e78bb448e8df9407b289a92ad9f. * feat: add Flue spam-filter agent for GitHub issues and PRs * chore: rename Flue spam and off-topic filter * fix: address Flue filter review feedback * just-bash is needed by flue * add observability * deploy should sync skills * add logging to spam agent * add more loggings * disable invocation logs * enable traces * better log messages * disable traces * fix eslint * ignore flue dist in eslint * add urls to more logs * fix: isolate Flue filter sessions * fix: improve Flue orchestrator verdict logs * chore: migrate Flue to 0.7, add flue.config.ts, fix local dev * [Flue] Handle reopened and ready_for_review events in spam filter * chore: fix prettier formatting in orchestrate.ts * [Flue] Comment out low-value webhook received/ignored logs * [Flue] Add spam/off-topic labels when closing issues and PRs * chore: remove unused agents dependency * chore: restore agents dependency (required by Flue generated entry)

fix: self-heal Flue incremental review diff on rebase and upstream merges (#32070) * fix: self-heal flue incremental review diff on rebase and upstream merges The code-review and style-guide specialists computed their incremental diff as a three-dot compare of the last-reviewed head SHA against the current head. That is only correct when the branch is a clean forward extension of the last-reviewed SHA. After a rebase/force-push the old SHA is orphaned, so the compare's merge-base regresses to the old fork point and the delta sweeps in every upstream commit the branch absorbed — the review then flags findings in files the PR never touched. A production->PR merge ("Update branch") has the same effect while still reporting status: ahead. The prior self-heal only fired on a 404 (base SHA garbage-collected), so neither the rebase nor the merge case was covered. Add fetchFilesForDiffMode (lib/diff-fetch.ts), shared by both specialists, which trusts the incremental delta only when the compare succeeds, its status is ahead/identical, and every file in the delta belongs to the PR's net diff. Any violation self-heals to the full PR diff. comparePullRequestHeads now returns the compare status/ahead_by/ behind_by to support this. * fix: paginate GitHub file/compare lists and encode compare refs Address review findings on the diff self-heal: - getPullRequestFiles now follows Link-header pagination instead of fetching a single per_page=100 page, so the PR net-diff set used by fetchFilesForDiffMode's containment check is complete for PRs with more than 100 changed files. - comparePullRequestHeads paginates the compare file list (deduping by filename, since the compare endpoint paginates over commits and can repeat files across pages) and captures status/ahead_by/behind_by from the first page. This keeps the incremental delta and the upstream-file self-heal decision from being based on a truncated first page. - The compare base/head refs are URL-encoded (preserving '/') so refs with special characters produce a well-formed request.

[flue] In-process review fan-out, native skill bundling, and R2 reduction (#31516) * [flue] Replace style-guide child-workflow fan-out with in-process sessions Collapse the per-file style-guide review from N child workflows (admitted over HTTP + Durable Streams long-poll) into concurrent sessions within the code-review orchestrator's own Durable Object. One harness over a single shared workspace, hydrated once, with one session per file fired via a concurrency pool; a single file's failure degrades to an empty result instead of aborting the whole review. This removes the separate child-workflow DOs that were the unit getting evicted mid-poll (the interruption that failed PR #31514), and deletes the admit/poll plumbing (lib/poll-run.ts retained for the spam-filter gate). - Add lib/style-guide-inproc.ts (hydrate-once + per-file session fan-out) - Rewrite orchestrator fan-out to call runStyleGuideReviewInProcess - Delete lib/style-guide-fanout.ts (only the orchestrator used it) - Retire the style-guide-review workflow + its DO class (v4 deleted_classes migration) * [flue] Bundle skills + references in build; stage diff in Workspace; shrink R2 to per-PR state Adopt Flue's native skill mechanism instead of fetching skill/reference content from R2 at runtime, and stage the per-run PR diff directly in the shared Workspace now that review runs in-process. - Import all four skills (style-guide-review, reconcile-code-review, spam-and-off-topic-filter, dependabot-review) with { type: "skill" } and register them on their agents; drop the runtime R2 SKILL.md fetches and workspace writes. - Move the style-guide reference rules into the skill directory so they ship as packaged skill resources; rewrite SKILL.md to read them via the read tool at the advertised packaged paths (patch parsing stays on the code tool). Manifest file paths updated to skill-root-relative. - Replace writeDiffToR2 with writeDiffToWorkspace: the orchestrator writes manifest/pr/patches straight into the shared Workspace; delete the R2 hydration (lib/style-guide-hydration.ts) and the comments.json round-trip (comments already reach reconcile via in-memory args). - Remove the obsolete content-sync tooling (bin/sync-agents.ts, bin/sync-skills.ts) and drop the sync step from flue:deploy. R2 is retained only for cross-run per-PR state (review-{sha}.json snapshots and the auto-review counter); no content is pushed to R2 on deploy anymore.

chore: add contributing router skill, consolidate authoring skills (#31501) * [Chore] Add contributing router skill, consolidate authoring skills Introduce .agents/skills/contributing as the single entry point for contributing to the docs. It routes to task-specific references and absorbs the pr, changelog, docs-review, and code-review skills. - Add SKILL.md router with ground rules, intake, task index, validation - Add writing-docs, content-types, choosing-components, and information-architecture references - Move pr/changelog/docs-review/code-review into contributing/references - Remove the changelog, pr, review-code-examples, and styleguide commands and their dangling symlinks; adopt a skill-first approach - Update AGENTS.md to document the contributing skill * style: format * [Chore] Broaden contributing skill description to trigger on PR actions * [Chore] Add PR-sync guidance to pr.md; keep ground rules minimal * [Chore] Tighten contributing skill: delegate style rules, refine safety wording * [Chore] Make component selection exhaustive; add Type/MetaInfo, Icon, RSSButton, Example to catalog * style: format * [Chore] Align component catalog with styleGuide.component sync check --------- Co-authored-by: cloudflare-docs-bot[bot] <cloudflare-docs-bot[bot]@users.noreply.github.com>

chore: consolidate agent skills and create shared style guide references (#30735) * chore: consolidate agent skills and create shared style guide references - Add .agents/references/style-guide.md — canonical writing and formatting rules - Add .agents/references/components.md — full MDX component catalog with props - Add .agents/references/procedures.md — step-writing rules for how-tos and tutorials - Update changelog, docs-review skills to reference shared style guide - Remove content-rules.md (content merged into shared reference) - Fix changelog skill code examples section (WranglerConfig/TypeScriptExample rules) - Fix docs-review quick-reference table (adds PackageManagers row, removes duplicates) - Rename verify-dependabot-pr → dependabot-review - Remove npm-to-pnpm skill (outdated) - Update AGENTS.md: remove duplicated component docs, add skills/references index, fix description field annotation * chore: add missing components to agent reference (Badge, Card, YouTube, Stream, APIRequest, CURL, WranglerCommand, Markdown) * chore: add prebuild check to keep components.md in sync with style guide pages * chore: document all remaining components in agent reference, remove exclusion list from check script * chore: move component docs check to CI pre-build step, not package.json prebuild * fix: format check-component-docs.ts, add formatting reminder to AGENTS.md * chore: remove circular reference from components.md * chore: add bidirectional sync check for component docs, add missing styleGuide.component to badges.mdx * fix: remove confusing WranglerConfig carve-out from code-review skill

feat: improve copy button UX with checkmark feedback and tippy tooltips (#30441) * feat: replace copy button feedback tooltip with checkmark icon, add tippy tooltips to copy buttons - Swap 'Copied!' feedback tooltip on EC code blocks for a checkmark icon - Add tippy.js tooltips to EC copy buttons and PackageManagers copy button - Standardize copy/check icons to Phosphor Regular across EC and PackageManagers - Extract tippy.css overrides from Head.astro into src/styles/tippy.css - Consolidate agent-setup components to use addTooltip() util - Migrate AgentsToolkit tooltips from custom portal impl to tippy * adjust font size * add important to tippy css properties * copy agent-toolkit list styles from TOC * icon button fixes * chore: clean up AgentsToolkit list item and icon button styles - Match TOC link style (sidebar-text colors, py-1.5, leading-snug) - Remove pointless div wrapper from IconButton - Replace sr-only span with aria-label, add aria-hidden to icon - Fix Prettier formatting * fix: guard against double init of tippy instances on page load * fix: remove copy button click listeners on cleanup to prevent accumulation

chore: clean up Flue routing and workflow state (#31409) * chore: clean up Flue routing and workflow state * chore: share Flue internal auth helpers

perf: reduce Workers AI model page HTML payload size (#30350) * perf: reduce Workers AI model page HTML size - Add ModelCardData type: slim projection of ResolvedModel that excludes schema, apiModes, codeSnippets, examples, and metadata fields - Strip ~1.76 MB of unused JSON Schema data from ModelCatalog island props on /workers-ai/models/ and /ai/models/ index pages (catalog only needs name, task, description, properties, and a handful of scalars for filtering/rendering — never the full schema) - Change client:load to client:visible on SchemaTree/SchemaVariantSelector islands so React hydration is deferred until the schema section scrolls into view (it is below the fold on every detail page) - Deduplicate input schema serialisation on multi-mode model pages: when sync and streaming modes share identical input, render the input schema once and show per-mode output sections, eliminating ~145 KB of duplicate SchemaRowData props per affected detail page * perf: serve model JSON schemas as static files, remove Code bloat Replace the 'API Schemas (Raw)' section's syntax-highlighted <Code> blocks with static .json endpoints and a compact link UI. The <Code> components were inflating 227 KB of raw JSON into ~1.95 MB of syntax-highlighted HTML (8.6x ratio) via Expressive Code span wrapping. On models with multiple API modes (sync/streaming/batch), the same schema was rendered multiple times, pushing detail pages to ~3.1 MB. Changes: - Extract detectApiModes() from model-resolver.ts into model-schema.ts so it can be shared without pulling in Astro's getCollection - Add src/pages/workers-ai/models/[...schema].json.ts: generates static JSON endpoints per model per schema (sync-input.json, sync-output.json, streaming-input.json, etc.) for all legacy models (~220 files) - Add src/pages/ai/models/[...schema].json.ts: same for catalog models, handling multi-segment slugs (e.g. /ai/models/openai/gpt-5.4-mini/schema-input.json) - Replace Code blocks in ModelDetailPage.astro with a 2-column card grid linking to the .json endpoints, each card having square open/download icon buttons Expected result: ~3.1 MB -> ~1.15 MB on gemma detail page * chore: fix prettier formatting in model-properties.ts

feat: add agent setup prompt for AI agent onboarding (#30281) * feat: add agent setup prompt for AI agent onboarding - Add src/content/agent-setup/prompt.md as single source of truth for agent instructions (install Skills, MCP servers, and find next steps) - Serve prompt as text/markdown at /agent-setup/prompt.md via Astro API endpoint - Override Starlight SkipLink slot to inject hidden data-agent-instructions div as first child of <body> on /agent-setup/ only - Add Accept: text/markdown content negotiation to worker for /agent-setup route, proxying to /agent-setup/prompt.md - Inject HTML stop directive as preamble in the hidden div only, keeping the markdown prompt clean * feat: global skills install and restart prompt for MCP servers * feat: per-agent MCP config paths, global skills, fix OAuth note * feat: improve agent setup prompt UX and fix opencode mcp install * feat: add restart and auth instructions to setup completion block * feat: move restart notice inside ascii block * feat: add per-agent MCP auth commands inline with install steps * fix: remove claude mcp auth, OAuth triggers on first tool call for Claude Code * feat: update agent setup with plugin installs, new MCP servers, and refreshed prompts * feat: include remaining agent setup component and page changes * [agent-setup] revamp homepage copy block and /agent-setup index page - Add PromptCopyBlock component with dark terminal-style UI, copy button, and icon swap on success - Add two-path card layout to /agent-setup/ (Quick setup vs Manual setup) with orange border on quick path card - Remove agent directive hidden div from SkipLink.astro - Remove content negotiation for /agent-setup from worker/index.ts - Update homepage agent section: copy block, secondary link, drop SVG on small screens, rework CTA text * [agent-setup] polish copy block, homepage logos, and path cards - Two-path card layout on /agent-setup/: Quick setup (orange border) vs Manual setup, responsive with flex wrap at 1000px - PromptCopyBlock: remove animation, fix copy button click handler, no-select on text, copy/copied label swap, overflow/truncation fixes - Homepage: smaller logos (60px), gap spacing, remove justify-between, tighten secondary link spacing, pcb-root margin overrides * fix: prettier formatting and homepage agent section margin * [agent-setup] light mode fixes and copy block polish - PromptCopyBlock: theme-aware colors for light mode (no more hardcoded dark) - Remove glow, add subtle orange box-shadow that increases on hover/copied - Fix copy button colors, green copied state, text color via CSS vars - Homepage: even section margin, normal text size/color for secondary link * [agent-setup] increase homepage agent section top/bottom margin * [agent-setup] copy block light/dark mode background and dot polish * chore: remove unnecessary SkipLink override and astro.config registration

chore: consolidate astro-config.ts into root astro.config.ts (#32258)

chore: tail-end Starlight->Nimbus migration cleanup (#32250) * chore: tail-end Starlight->Nimbus migration cleanup Small cleanup pass identified after the Starlight->Nimbus migration and the src/nimbus->src promotion: - .github/CODEOWNERS: fix dead /src/nimbus/pages/agent-setup path (no longer exists post-promotion) to /src/pages/agent-setup. That team had zero CODEOWNERS coverage on the real directory. - style-guide/how-we-docs/metadata.mdx: fix dead GitHub link to src/nimbus/schemas (now src/schemas). - Batch content fix across 11 style-guide pages that still described the site as running on Starlight, or referenced now-removed Starlight/community packages (starlight-package-managers, starlight-links-validator) instead of their Nimbus/local equivalents: - our-site.mdx: framework description now points to nimbus-docs.com instead of starlight.astro.build (and no longer misattributes a Hugo->Starlight blog post to a "choosing Nimbus" claim it doesn't make). - links.mdx: replaces the removed starlight-links-validator reference and a dead <GitHubCode> snippet (pinned to an ancient commit's now-nonexistent line numbers) and a phantom CI env var link with an accurate description of Nimbus's nimbus/internal-link rule. - icons.mdx: replaces a genuinely broken example (`import { StarlightIcon } from "~/components"` — this export doesn't exist) with the real Card/LinkCard `icon` string-prop API, and notes the legacy seti:/bare-name compat mapping for existing content. - badges.mdx: removes an instruction to apply a `sl-badge` CSS class that no longer exists on the ported Badge component (styling is now computed inline via Tailwind, not exposed as a class). - cards.mdx, file-tree.mdx, package-managers.mdx, rss-button.mdx, frontmatter/index.mdx, frontmatter/custom-properties.mdx, directory-listing.mdx, content-types/overview.mdx: swap Starlight framework/package attributions and dead starlight.astro.build links for the real Nimbus component/docs equivalents. - ai-consumability.mdx: the claim that Cloudflare's Markdown-for- Agents network layer transforms a `starlight-tabs` custom element is no longer accurate — Nimbus's Tabs component doesn't render that custom element at all (confirmed: it's a plain `<div data-nb-tabs>`). Generalized the wording since verifying/fixing that external transform pipeline is out of scope here; flagging this as worth a cross-team follow-up separately. Verified: pnpm run check/lint/format:check/test all clean, full build succeeds (8709 pages), test:postbuild passes. * style: address style-guide bot findings (drop 'please', split semicolon sentence) - frontmatter/index.mdx: remove 'please' per style guide (avoid please) - components/icons.mdx: split a semicolon-joined sentence into two Skipped 2 code-review findings about the nimbus-docs.com link possibly being dead/unverified — confirmed live and correct, posted reasoning as a PR comment.

flue: add /ignore-review-limit command for codeowners (#31541)

chore: post-Nimbus migration cleanup (#32229) - Delete dead Starlight-leftover src files (middleware, analytics scripts, explain-code, mermaid, MERMAID.md) and the stale starlight-docsearch patch - Rewrite 13 content files off @astrojs/starlight/components and astro-expressive-code/components -> ~/components; remove those two alias entries from astro-config.ts - Remove 33 unused packages: full Starlight/EC ecosystem plus orphaned rehype/remark/hast/unist plugins deleted with the old plugin tree - Fix vitest.config.ts: remove vite-tsconfig-paths (no test file uses ~/ imports); fix post-pr-ci-failure-comment to not check for 'Nimbus Build' job that no longer exists; delete orphaned bin/post-preview-url-comment/ - Remove Starlight rollback safety-nets: theme toggle no longer dual-writes starlight-theme key, BaseLayout no longer migrates from it, PageHead generator now says 'Nimbus v0.2.2', remove experimental.contentIntellisense - Fix sitemap.serializer.ts git log path (src/pages -> src/nimbus/pages) - Update AGENTS.md, agent references, src/nimbus/README.md, MIGRATION.md (deleted), and two content pages with broken GitHub links to deleted paths - Remove dist-nimbus/ from .prettierignore and eslint.config.js