Highlight user-defined tools + the 'still Galaxy, web-accessible' frame

site/src/pages/index.astro

@@ -93,6 +93,11 @@ const grounded = [
     body: "The agent works from Galaxy's actual catalog — thousands of containerized, version-pinned tools — through Galaxy MCP. What it runs is installed and reproducible, not a name it made up.",
     icon: '<rect x="4" y="4" width="7" height="7" rx="1"/><rect x="13" y="4" width="7" height="7" rx="1"/><rect x="4" y="13" width="7" height="7" rx="1"/><rect x="13" y="13" width="7" height="7" rx="1"/>',
   },
+  {
+    title: "No tool for the job? It builds one.",
+    body: 'When nothing in the catalog fits, the agent authors a User-Defined Tool right in Galaxy — guided by a curated skill — instead of dropping to ad-hoc local scripts. Even bespoke steps run through Galaxy\'s job system, so they stay reproducible and shareable.',
+    icon: '<rect x="3" y="3" width="18" height="18" rx="2"/><path d="M12 8v8M8 12h8"/>',
+  },
   {
     title: 'Community workflows, not reinvented',
     body: 'When a curated IWC workflow fits the task, the agent finds and runs it instead of assembling a pipeline from scratch — decades of best-practice, tested methods as the default.',
@@ -130,6 +135,10 @@ const faqs = [
     q: "Won't the AI just hallucinate tools and parameters?",
     a: `That's the failure mode Galaxy grounding is built to avoid. Instead of inventing a pipeline from text, the agent works through Galaxy MCP against your server's real tool catalog and the curated <strong>IWC</strong> workflow collection — so the tools it runs actually exist, are version-pinned, and are containerized. It drafts the plan with the exact tools and parameters for you to approve <em>before</em> anything runs, and the run itself is a real Galaxy job with full provenance. The output is grounded in Galaxy's contracts, not a plausible-looking guess.`,
   },
+  {
+    q: "What if the tool I need isn't in Galaxy?",
+    a: `<strong>It builds one.</strong> When no catalog tool fits the task, the agent authors a <strong>User-Defined Tool</strong> right in Galaxy — guided by a curated skill — rather than dropping to ad-hoc local scripts. The new tool runs through Galaxy's job system like any other, so even bespoke steps stay reproducible and shareable. Full agentic reach, still inside Galaxy.`,
+  },
   {
     q: 'Can I drive Galaxy from Claude Desktop or another agent — not just Orbit?',
     a: `Yes. <a href="${url('/docs/galaxy-mcp')}">Galaxy MCP</a> (<code>uvx galaxy-mcp</code>) is a standalone Model Context Protocol server — point any MCP-capable client (Claude Desktop, Orbit, others) at a Galaxy instance and it can search and run tools, drive workflows, and manage histories. Orbit and Loom use it under the hood.`,
@@ -330,6 +339,11 @@ const faqs = [
           ))
         }
       </div>
+      <p class="grounded-foot">
+        <strong>Full agentic driving on top of the reproducible, transparent, web-accessible
+        Galaxy platform</strong> — your analysis runs in the browser, on the Galaxy servers you
+        and your collaborators already use. It's still Galaxy.
+      </p>
     </div>
   </section>
 
@@ -573,7 +587,9 @@ loom</code></pre>
 
   /* ---- grounded (built on Galaxy) ---- */
   .grounded { background: var(--color-light-bg); padding: clamp(4rem, 8vw, 6.5rem) 0; }
-  .grounded-grid { display: grid; grid-template-columns: repeat(3, 1fr); gap: 1.2rem; }
+  .grounded-grid { display: grid; grid-template-columns: repeat(2, 1fr); gap: 1.2rem; }
+  .grounded-foot { text-align: center; margin: 2.25rem auto 0; max-width: 52rem; color: var(--color-galaxy-grey); line-height: 1.65; font-size: 1.02rem; }
+  .grounded-foot strong { color: var(--color-galaxy-dark); }
 
   /* ---- code card ---- */
   .codecard { background: #1b2030; border: 1px solid rgba(255, 255, 255, 0.1); border-radius: 0.7rem; overflow: hidden; box-shadow: 0 30px 60px -30px rgba(0, 0, 0, 0.6); margin: 0; }