Regenerate shell-dojo registry at build and expand CI trigger paths

The dojo app was missing items under the langgraph column because
shell-dojo shipped a stale committed registry.json. The generator
only wrote to shell/, the dojo Dockerfile didn't run the generator
at build, and the CI path filter didn't rebuild the dojo when
manifest files changed.

Fix: emit from generate-registry.ts to shell, shell-dojo, and
shell-docs; add the generator step to shell-dojo's Dockerfile;
expand the deploy workflow's path filter to include packages/**
and shared/**; and refresh the committed registry/demo-content
JSON so files on disk match what the generator produces today.

Author: jpr5

.github/workflows/showcase_deploy.yml

@@ -115,7 +115,11 @@ jobs:
             starter_spring_ai: 'showcase/starters/spring-ai/**'
             starter_strands: 'showcase/starters/strands/**'
             aimock: 'showcase/aimock/**'
-            shell_dojo: 'showcase/shell-dojo/**'
+            shell_dojo:
+              - 'showcase/shell-dojo/**'
+              - 'showcase/shared/**'
+              - 'showcase/scripts/**'
+              - 'showcase/packages/*/manifest.yaml'
             shell_dashboard:
               - 'showcase/shell-dashboard/**'
               - 'showcase/shared/**'
@@ -174,7 +178,7 @@ jobs:
             {"dispatch_name":"starter-spring-ai","filter_key":"starter_spring_ai","context":"showcase/starters/spring-ai","image":"showcase-starter-spring-ai","railway_id":"3559ece3-7ba3-41ac-b24c-1f780133ec58","timeout":15,"lfs":false,"build_args":"","dockerfile":"","health_path":"/api/health"},
             {"dispatch_name":"starter-strands","filter_key":"starter_strands","context":"showcase/starters/strands","image":"showcase-starter-strands","railway_id":"06db2bb8-e15d-4c6a-97ad-e14777c92d9f","timeout":15,"lfs":false,"build_args":"","dockerfile":"","health_path":"/api/health"},
             {"dispatch_name":"aimock","filter_key":"aimock","context":"showcase/aimock","image":"showcase-aimock","railway_id":"0fa0435d-8a66-46f0-84fd-e4250b580013","timeout":5,"lfs":false,"build_args":"","dockerfile":"","health_path":"/health"},
-            {"dispatch_name":"shell-dojo","filter_key":"shell_dojo","context":"showcase/shell-dojo","image":"showcase-shell-dojo","railway_id":"7ad1ece7-2228-49cd-8a78-bddf30322907","timeout":10,"lfs":false,"build_args":"","dockerfile":"","health_path":"/"},
+            {"dispatch_name":"shell-dojo","filter_key":"shell_dojo","context":".","image":"showcase-shell-dojo","railway_id":"7ad1ece7-2228-49cd-8a78-bddf30322907","timeout":10,"lfs":true,"build_args_sha":"${{ github.sha }}","build_args_branch":"${{ github.ref_name }}","dockerfile":"showcase/shell-dojo/Dockerfile","health_path":"/"},
             {"dispatch_name":"shell-dashboard","filter_key":"shell_dashboard","context":".","image":"showcase-shell-dashboard","railway_id":"4d5dfd74-be61-40b2-8564-b53b7dd4c15b","timeout":10,"lfs":true,"build_args_sha":"${{ github.sha }}","build_args_branch":"${{ github.ref_name }}","build_args_shell_url":"https://showcase.copilotkit.ai","dockerfile":"showcase/shell-dashboard/Dockerfile","health_path":"/"},
             {"dispatch_name":"shell-docs","filter_key":"shell_docs","context":".","image":"showcase-shell-docs","railway_id":"7badfb8d-4228-414c-9145-b4026803714f","timeout":10,"lfs":true,"build_args_sha":"${{ github.sha }}","build_args_branch":"${{ github.ref_name }}","dockerfile":"showcase/shell-docs/Dockerfile","health_path":"/"}
           ]'

showcase/scripts/bundle-demo-content.ts

@@ -58,13 +58,15 @@ const __dirname = path.dirname(__filename);
 
 const ROOT = path.resolve(__dirname, "..");
 const PACKAGES_DIR = path.join(ROOT, "packages");
-// demo-content is consumed by BOTH shells:
+// demo-content is consumed by ALL shells:
 //   - shell: integration pages + demo drawer read the bundle at runtime
 //   - shell-docs: <Snippet> (docs routes) imports directly at build time
-// so we dual-emit. Paths array is iterated at write time.
+//   - shell-dojo: demo content renders inside the dojo's cell viewer
+// so we multi-emit. Paths array is iterated at write time.
 const OUTPUT_PATHS = [
   path.join(ROOT, "shell", "src", "data", "demo-content.json"),
   path.join(ROOT, "shell-docs", "src", "data", "demo-content.json"),
+  path.join(ROOT, "shell-dojo", "src", "data", "demo-content.json"),
 ];
 
 interface DemoFile {

showcase/scripts/generate-registry.ts

@@ -24,13 +24,19 @@ const FEATURE_REGISTRY_PATH = path.join(
   "shared",
   "feature-registry.json",
 );
-// Registry is consumed by BOTH shells:
+// Registry is consumed by ALL shells:
 //   - shell: home grid, integrations catalog, matrix, middleware
 //   - shell-docs: docs routes (framework lookup, MDX renderer)
-// so we dual-emit. constraints.json is shell-only (integration-explorer).
+//   - shell-dojo: dojo app's integration grid and demo columns
+// so we multi-emit. constraints.json is shell-only (integration-explorer).
 const SHELL_OUTPUT_DIR = path.join(ROOT, "shell", "src", "data");
 const SHELL_DOCS_OUTPUT_DIR = path.join(ROOT, "shell-docs", "src", "data");
-const OUTPUT_DIRS = [SHELL_OUTPUT_DIR, SHELL_DOCS_OUTPUT_DIR];
+const SHELL_DOJO_OUTPUT_DIR = path.join(ROOT, "shell-dojo", "src", "data");
+const OUTPUT_DIRS = [
+  SHELL_OUTPUT_DIR,
+  SHELL_DOCS_OUTPUT_DIR,
+  SHELL_DOJO_OUTPUT_DIR,
+];
 const CONSTRAINTS_PATH = path.join(ROOT, "shared", "constraints.yaml");
 const CONSTRAINTS_OUTPUT_PATH = path.join(SHELL_OUTPUT_DIR, "constraints.json");
 

showcase/shell-docs/src/data/demo-content.json

@@ -1,5 +1,5 @@
 {
-  "generated_at": "2026-04-21T05:02:54.302Z",
+  "generated_at": "2026-04-21T20:03:18.267Z",
   "demos": {
     "ag2::agentic-chat": {
       "readme": "# Agentic Chat\n\n## What This Demo Shows\n\nNatural conversation with frontend tool execution\n\n## How to Interact\n\nTry asking your Copilot to:\n\n- \"Can you change the background color to something more vibrant?\"\n- \"Make the background a blue to purple gradient\"\n- \"What's the weather like in San Francisco?\"\n- \"Set the background to a sunset-themed gradient\"\n\nYou can also chat about other topics — the agent will respond conversationally while having the ability to use your UI tools when appropriate.\n\n## Technical Details\n\n**Frontend tools** are registered using `useFrontendTool`:\n\n- `change_background` — accepts a CSS background value and applies it to the chat container\n- CopilotKit automatically exposes this function to the agent\n- The agent determines when to call the tool based on the user's request\n\n**Backend tool rendering** uses `useRenderTool`:\n\n- `get_weather` — a backend tool that the agent calls; the frontend renders the result as a weather card\n- The render function receives `args`, `result`, and `status` for loading/complete states\n\n**Agent context** is provided via `useAgentContext`:\n\n- Sends the user's name to the agent so it can personalize responses\n\n**Suggestions** are configured with `useConfigureSuggestions`:\n\n- Static suggestions shown as quick-action buttons below the chat\n\n## Building With This\n\nIf you're extending this demo or building something similar, here are key things to know:\n\n### Styling Inside the Chat\n\nContent rendered inside CopilotKit's chat area (via `useRenderTool`, `useHumanInTheLoop`, `useFrontendTool`) runs inside CopilotKit's component tree. Standard Tailwind classes may not work here because Tailwind v4 can't statically detect them.\n\n**Use inline styles** for any UI rendered inside the chat:\n\n```tsx\n// Do this\n<div style={{ padding: \"24px\", borderRadius: \"12px\", background: \"#fff\" }}>\n\n// Not this — Tailwind may purge these classes\n<div className=\"p-6 rounded-xl bg-white\">\n```\n\n### Chat Layout\n\nWrap `CopilotChat` in a constraining div for proper spacing:\n\n```tsx\n<div className=\"flex justify-center items-center h-screen w-full\">\n  <div className=\"h-full w-full md:w-4/5 md:h-4/5 rounded-lg\">\n    <CopilotChat className=\"h-full rounded-2xl max-w-6xl mx-auto\" />\n  </div>\n</div>\n```\n\n### Overriding CopilotKit Styles\n\nCopilotKit uses `cpk:` prefixed classes internally. To override them, create a **separate CSS file** (not in globals.css — Tailwind purges it):\n\n```css\n/* copilotkit-overrides.css */\n.copilotKitInput {\n  border-radius: 0.75rem;\n  border: 1px solid var(--copilot-kit-separator-color) !important;\n}\n```\n\nImport it in `layout.tsx` after `globals.css`.\n\n### Images and Icons\n\n- Don't reference local image files from agent-generated content (they won't exist). Add `onError` fallbacks.\n- Use emoji instead of SVG icons inside chat messages (`fill=\"currentColor\"` renders unpredictably in the chat context).\n\nSee the full [Styling Guide](https://github.com/CopilotKit/CopilotKit/blob/main/showcase/STYLING-GUIDE.md) for more details.\n",