Previously readStoredFramework returned null for both "never set" and
"localStorage unavailable" — consumers couldn't distinguish a fresh
visitor from a private-mode browser. Introduce a tri-state: keep
storedFramework: string | null for the value, and add
storageAvailable: boolean so UIs can branch on "we can't persist
your pick" separately from "you haven't picked yet".
Also subscribe to window `storage` events so that when another tab
clears or changes selectedFramework, this tab's stored state stays
in sync (StoredFrameworkHighlight badge + RouterPivot redirect
react immediately without a reload).
Strengthens the comment above the URL-persistence effect explaining
why `stored` is intentionally excluded from the deps array (prevents
a setState ping-pong loop), and adds behavioral "Covered by:" notes
above each non-trivial fix.
If shell-docs/src/content/{reference,ag-ui,docs} didn't exist the
script silently produced a tiny index with no warning — operators
only found out by noticing Cmd-K search returning nothing.
Warn per missing directory and exit non-zero if ALL scan roots are
missing (that means we're running outside a prepared tree, e.g.
shell-docs didn't emit into the expected layout).
The watch loop logged '[watch] bundle failed' once and then fell
silent — repeat failures looked like success, and recoveries were
invisible (no news = assumed fine). Track the last error in module
scope so we distinguish first-failure from repeat-failure, and log an
explicit 'bundle recovered' note when the next green run clears the
state. Makes dev-mode transitions visible instead of silent.
A malformed docs-links.json was only console.warn'd and treated as
empty — build ran green while the override file silently rotted.
Accept an errors accumulator and push parse failures into it so
main()'s non-zero exit path fires. Missing file and stale-shape
tolerance are unchanged (both are legitimate states).
Without a timeout on the inner fetch, a hung upstream would stall the
entire docs-probe run indefinitely (Node's fetch has no default
timeout). Add a 10s AbortController. The bare catch also left 'error'
states opaque — log URL + error kind so operators can tell an
abort from DNS from TLS.
The bare catch returned 'unknown' with no trace, making it impossible
to distinguish DNS failures from aborts from TLS errors in the unknown
bucket. Log the URL plus a kind:code pair so spikes of 'unknown' are
actually diagnosable.
mockE2E/mockSmoke/mockQA were called unconditionally from main(), so
production dashboards shipped seeded test data in columns that aren't
wired to real CI yet. Gate each behind GENERATE_STATUS_MOCK_*
env vars (default off → emit null / 'unknown'). Print a prominent
banner to stderr naming which columns are mock whenever any gate is
on, so operators can't discover stub data by surprise.
A bare catch swallowed JSON.parse failures, silently returning [] and
making every /<slug> framework redirect disappear. Throw in production
(registry is a required build-time artifact) and console.warn in dev
(so a transient mid-write doesn't kill the dev loop). Also throw if
the file is missing in production for the same reason.
The cross-starter consistency test had two AGENT_URL matchers:
function re8000() {
return new RegExp(AGENT_URL_LOCALHOST_8000_RE.source, flags);
}
function re8123() {
return new RegExp(
AGENT_URL_LOCALHOST_8000_RE.source.replace(/8000\\b/, "8123\\b"),
flags,
);
}
The 8123 variant does regex-source string munging — brittle: the
replacement target `8000\\b` has to stay in lockstep with the
shared regex's literal source, and a future port format change would
snap in a subtle way (the test could keep passing while matching
subtly wrong content, or start failing for reasons unrelated to the
starter it's guarding).
Replace the `.source.replace` hack with an exported factory
`makeAgentUrlLocalhostPortRE(port)` in `generate-starters.ts` and
have both `re8000`/`re8123` use it. The existing
`AGENT_URL_LOCALHOST_8000_RE` constant is preserved (now delegating to
the factory) so any external import stays happy.
Bonus: the factory validates port bounds so a typo can't silently
produce a pattern that never matches.
Two orthogonal bugs in the demo-content bundler:
1) README regions were silently dropped. `collectDemoFiles` pulls the
demo-dir root README out into the `readme` field rather than
appending to `files`, but it STILL wrote any `@region[...]`
slices it found inside the README into `perFileRegions` under the
README's bundled path. The region-collation loop at write time
iterated `fileOrder = files.map(f => f.filename)`, which by
construction never contains the README path — so those regions
went nowhere. Walk any `perFileRegions` keys not in fileOrder
after the main pass, so README regions still land in the public
map. Preserves the stable file-order rule (README contributions
come after source files, alphabetical tiebreak).
2) Binary-like files were being passed through
`fs.readFileSync(abs, "utf-8")` and then stringified into the
bundle. A PNG or font file typically produces a mess of
replacement characters in `demo-content.json` — waste at best,
visible corruption at worst when the Code tab ever tried to
render them. Extend `SKIP_EXTENSIONS` with the usual binary
suspects (images, fonts, archives, media, PDFs) so the walker
drops them at scan time.
The canonical schema in `scripts/generate-registry.ts` + per-package
`docs-links.json` calls the shell path `shell_docs_path`. probe-docs
was still reading ONLY the legacy `shell_docs_url` key, so any
future cleanup of `shared/feature-registry.json` to the canonical
key would silently turn every shell-docs status into 'missing'.
Prefer `shell_docs_path`, fall back to `shell_docs_url` so older
registry snapshots still contribute. Emit a one-shot dev-mode warning
when we see only the legacy key, so a lingering registry stays visible
without spamming CI logs.
Replace the argv-sniffing 'process.argv.includes("build")' check with
process.env.NEXT_PHASE === "phase-production-build", the Next.js
canonical signal for a production build. The argv approach is fragile:
it breaks under wrappers, programmatic invocation, or any tool that
invokes next via a different argv shape.
COMMIT_SHA defaulted to 'unknown', so a caller that forgot to pass
--build-arg COMMIT_SHA would silently ship an image whose footer,
health checks, and error reports all report 'unknown'. Add a guard in
the builder stage that refuses to proceed when COMMIT_SHA is unset or
still the 'unknown' default.
showcase/scripts/ now ships a package-lock.json (committed here for the
first time), so the Docker builder can use 'npm ci' for deterministic
installs instead of 'npm install'. Update the comment to match actual
state and copy the lockfile into the scripts stage.
The runner stage was copying the entire builder node_modules tree,
shipping tailwindcss, postcss, tsx, typescript, and every @types/*
package into the production image. Add 'npm prune --omit=dev' after
the node_modules copy (and also copy package-lock.json so prune runs
deterministically) to strip dev-only packages from the runtime image.
The ag-ui and reference pages each carried their own near-identical
stripImportsFenceAware copy with a TODO(dedup) flag. The canonical
implementation already exists in docs-render.tsx as stripLeadingImports
and has better semantics — it only strips imports that appear in the
top-of-file header region (before the first non-import content line),
rather than any import anywhere outside a fence. That distinction
matters for doc bodies that legitimately discuss imports in prose
outside code fences.
Export stripLeadingImports from docs-render and point both pages at it;
remove the local duplicates.
Card's type accepted icon, className, and children but the component
body never read them — silent prop drop. Render icon above the title,
merge className onto the wrapper, and render children below the
description so MDX authors get the behavior the type signature
promises.
Two Callout components coexisted: a restricted variant in
mdx-components.tsx (info | warn | error only) and the broader-surface
variant in docs-callout.tsx (info | tip | warn | warning | error |
danger | note). reference/[...slug]/page.tsx imported from
mdx-components, silently limiting authors to three types. Collapse to
a single implementation by re-exporting docs-callout's Callout from
mdx-components so existing import paths keep working.
The registry's <Link> shim rendered a plain <a>, forcing a full page
reload on every internal MDX link. next/link was already imported in
this file; now the shim routes through it when href is present, falling
back to a bare <a> only when no href is provided.
The page wrapper renders the extracted title inside its own <h1>.
When no frontmatter title is present the title comes from the MDX
body's first H1 — which MDXRemote then also renders, producing two
stacked h1s at the top of every ag-ui doc. Strip the first leading
`# …` line (after any blank lines) from the MDX content before
rendering so the wrapper provides the single h1 and the body flows
from the first paragraph.
Both sidebar-framework-selector.tsx and the catch-all docs page.tsx
kept local copies of FRAMEWORK_CATEGORY_ORDER that mirrored the
canonical one exported from docs-render. Drift between the copies
would have shown up as divergent category ordering across the UI.
Remove the local duplicates and import the single source of truth.
The non-greedy regex matches through the first same-family close tag,
so nested containers like <Card>outer <Card>inner</Card> rest</Card>
closed at the inner </Card> and left the remaining 'rest</Card>' as
literal text. Capture the opening tag name and bail when the inner
body contains another occurrence of it — renders correctly through
MDX's own JSX handling instead of producing broken markup.
Accept \r?\n in extractFrontmatter so Windows-authored MDX files
don't silently skip frontmatter extraction. In stripLeadingImports,
store the full fence marker (``` or ~~~) rather than its first
character so a stray single backtick inside a fenced block doesn't
prematurely close it.
Replace the hand-rolled frontmatter regex in loadDoc with gray-matter
(already a dep) so quoted values, folded YAML, multiline descriptions,
and malformed frontmatter no longer fall through silently. Wrap every
fs read in readTitle, loadDoc, inlineSnippets, and buildNavTreeFromFilesystem
in try/catch — a single unreadable file / permission error used to
crash the entire page render.
Move parseTableRow, isTableRow, isTableSeparator to module scope
so they aren't recreated on every convertTablesInJSX call. Fixes
eslint-plugin-unicorn(consistent-function-scoping) warnings. No
behavior change.
- Document every SNIPPET_MAP alias inline (AgUI/AGUI,
FrontendTools/FrontEndToolsImpl) so future maintainers can see why
the duplicates exist and don't collapse them blindly. Confirmed
FrontEndToolsImpl is still referenced from live MDX under
integrations/langgraph/*.
- Verified every SNIPPET_MAP target exists on disk with matching
casing (including migrate-to-1.10.X.mdx and migrate-to-1.8.2.mdx).
- Export FRAMEWORK_CATEGORY_ORDER (+ FrameworkCategory type) from
docs-render as the single source of truth. Consumer files
(sidebar-framework-selector.tsx, [[...slug]]/page.tsx) each define
the same constant independently today; a follow-up agent can
retire those duplicates once they pick up the import.
- Log the full Error instance (not just .message/.digest) so the stack
trace actually reaches the server log / browser devtools.
- Include the pathname (via usePathname) in the log message so reports
can be tied back to the page that crashed.
- Replace misleading migration-specific copy ("This page will be fixed
shortly. Some ... components are still being migrated.") with a
generic user-facing message — the error boundary catches errors from
many causes, not just migration gaps.
- Show error.digest explicitly as a reportable "Error ID" so users can
include it when reporting the issue; drop the fallback to
error.message because it can leak internal details in a user-facing
surface.
- Extract duplicated loadItems/getAllItems into @/lib/reference-items so the
/reference index page and the /reference/[...slug] page read the same
tree the same way (same subdirs, same walker, same gray-matter path,
same caching).
- Walker is now recursive: subfolder files like components/inputs/textarea.mdx
are indexed and statically generated. Previously only top-level .mdx
files under components/ and hooks/ were picked up.
- Wrap gray-matter and fs reads in try/catch per file: a single malformed
frontmatter block no longer crashes the whole static-generation pass —
we log the offending path and skip that file.
- Fence-aware import stripper in the slug page so code samples containing
import ... lines inside fences are not corrupted. (Duplicated inline
here and in ag-ui page with a TODO(dedup) marker pointing at a future
shared helper in @/lib/docs-render.)
- loadReferenceItems memoizes in production (module-scope cache keyed by
subdir). Dev bypasses the cache so edits show up without a server
restart.
buildNavTree walks the entire content tree on every page render and
calls readTitle / readMeta O(pages) times per request. Each call
previously reopened and re-parsed the file from disk.
- Process-scoped Map caches keyed by resolved absolute path.
- Null results are cached too — a missing or malformed file still
short-circuits on the second visit.
- Memory footprint is trivial: titles are short strings, meta is a
small JSON object.
- Stale-during-process semantics are acceptable for Next.js build
and server runtime lifetimes; authors re-run the process to pick
up MDX/meta.json edits (same as before in production builds).
- Replace local MDX components map with spread of shared docsComponents
from @/lib/mdx-registry, so AG-UI pages get the full component set
(Tabs, FrameworkTabs, Snippet, Steps from @/components/docs-steps,
etc.) instead of silently rendering raw JSX when MDX uses anything
outside the tiny local subset.
- Use the shared InlineDemo from mdx-registry, whose Open full demo
link uses an absolute NEXT_PUBLIC_SHELL_URL/integrations/... URL.
The prior local copy used a relative /integrations/... URL that 404d
on the docs host (no /integrations route on docs.showcase.copilotkit.ai).
- Parse frontmatter with gray-matter instead of a whole-file title:
regex that could match any title: line buried inside an MDX body.
- Wrap fs.readFileSync in try/catch with meaningful error logs naming
the offending path; fall back gracefully instead of crashing render.
- Fence-aware leading-import stripper so MDX code samples that show
import ... lines are not corrupted (duplicated here; TODO(dedup) in
comment to hoist into @/lib/docs-render next time another route needs
it).
- JSX_CONTAINER_TAGS now covers Callout, Card, Cards, Step, Steps,
Tabs alongside the original Accordion/Tab. Previously a Markdown
table inside e.g. <Callout> silently failed to promote to HTML
and rendered as raw pipes.
- convertMarkdownTableToHtml's parseRow and the row/separator
detection in convertTablesInJSX now accept GFM tables written
WITHOUT outer leading/trailing pipes (valid GFM — previously
rejected because we sliced (1, -1) unconditionally).
- readMeta now logs the offending path + parse error when JSON.parse
fails, replacing the silent catch. Malformed meta.json no longer
collapses to 'no nav ordering' with zero diagnostic signal.
- Clear selection button was hidden on /docs/* because it branched on
framework (URL-derived, always null there). A user landing on /docs
with a stale storedFramework from a previous session had no way to
clear the preference from the selector UI. Show the button whenever
framework OR storedFramework is set; skip the navigation when we're
not on a framework-scoped route (it's a pure preference change).
- router.push -> router.replace on framework change. Picking a backend
is a pivot on the same logical page, not forward navigation. Using
push clutters the back stack with every framework the user clicked
through, making the browser Back button useless.
- Type-guard e.target with instanceof Node before passing to contains,
rather than hard-casting. EventTarget can be non-DOM (e.g. events
against window); the cast silently degrades to contains(null) which
returns false in most engines but is undefined behaviour in spec.
- Document that stripFrameworkPrefix intentionally only inspects
parts[0] and does NOT recurse — /<fw>/<fw>/x must keep the inner
<fw>/x as the feature tail.
- Rename INTEGRATION_CATEGORY_IDS to FRAMEWORK_CATEGORY_ORDER to match
the identically-defined constant in /[[...slug]]/page.tsx (the two
will be consolidated into @/lib/registry in a follow-up owned by the
registry refactor; left a TODO pointing at the canonical home).
- sort_order tiebreak: Array#sort is not guaranteed stable for ties
across engines. When multiple integrations default to 999 the
rendered order shuffles between V8 revisions. Add an explicit
alphabetical-by-slug tiebreak so the rendered panel is
deterministic.
fallbackHref was assigned to href and then immediately overwritten in
every branch of the scope switch — the value was never read. Since
useFramework() returns the URL-derived framework identically during
SSR and post-hydration, the resolved href matches what fallbackHref
was pre-computing server-side, so the 'client takes over on mount'
comment was describing a no-op.
- Remove the dead assignment; resolve href directly from framework.
- Keep fallbackHref as an optional prop (ignored) to avoid churning
call sites that still pass it.
The effect had no dependency array, so it re-ran on every render and
hijacked the user's own sidebar scroll whenever any unrelated re-render
fired (state/context flips, parent rerenders). Key the effect on
pathname so scroll-to-active only runs on route change.
Also:
- behavior: 'instant' is a Chromium non-standard extension; other
engines silently ignore it. Use 'auto' which is the spec-compliant
'no smooth animation' value.
- Wrap scrollIntoView in try/catch — it can throw on detached nodes
and in obscure iframe/security contexts; a sidebar scroll
restoration never justifies taking down the route.
- Replace the global /^import\s+.+$/gm pass with a fence-aware walker
(stripLeadingImports). The old regex silently mangled docs code
samples like 'import os' inside Python fences; the new pass only
drops top-of-file MDX import lines and leaves fence bodies alone.
- Add Set<string> cycle tracking through inlineSnippets' recursion so
a self- or mutually-referencing snippet can't loop until the stack
overflows. On a repeat, emit a warning and inline a comment marker
so the author sees something diagnosable.
- Log warn when a <Component /> reference can't be mapped to a
snippet file (either missing from SNIPPET_MAP or missing on disk);
previously the reference silently rendered nothing.
Jordan Ritter