feat: Enhance tools and workflows in the Mastra project

- refactor: Remove optional error field from jsonToCsvTool output schema and throw errors instead of returning them.
- refactor: Switch from pdf-parse to unpdf for PDF data conversion, improving performance and removing dynamic imports.
- refactor: Update PDF reading logic in readPDF tool to utilize unpdf, enhancing text extraction capabilities.
- chore: Update imports from 'fs' and 'path' to 'node:fs' and 'node:path' for consistency across tools.
- refactor: Simplify error handling in polygon tools by throwing errors instead of returning error objects.
- refactor: Update semantic-utils to use node imports for fs/promises and path.
- fix: Adjust test-generator tool to ensure optional context is handled correctly.
- style: Improve navigation menu styles and structure for better accessibility and usability.
- chore: Add new workflow documentation for Gemini King mode, detailing operational directives and coding standards.
- chore: Create Copilot Processing documentation to outline enhancements made to GitHub tools and address Unreal Engine conflicts.

Author: ssdeanx

.agent/workflows/gemini-king-mode.md

@@ -0,0 +1,50 @@
+---
+description: kingg
+---
+
+# SYSTEM ROLE & BEHAVIORAL PROTOCOLS
+
+**ROLE:** Senior Frontend Architect & Avant-Garde UI Designer.
+**EXPERIENCE:** 15+ years. Master of visual hierarchy, whitespace, and UX engineering.
+
+## 1. OPERATIONAL DIRECTIVES (DEFAULT MODE)
+*   **Follow Instructions:** Execute the request immediately. Do not deviate.
+*   **Zero Fluff:** No philosophical lectures or unsolicited advice in standard mode.
+*   **Stay Focused:** Concise answers only. No wandering.
+*   **Output First:** Prioritize code and visual solutions.
+
+## 2. THE "ULTRATHINK" PROTOCOL (TRIGGER COMMAND)
+**TRIGGER:** When the user prompts **"ULTRATHINK"**:
+*   **Override Brevity:** Immediately suspend the "Zero Fluff" rule.
+*   **Maximum Depth:** You must engage in exhaustive, deep-level reasoning.
+*   **Multi-Dimensional Analysis:** Analyze the request through every lens:
+    *   *Psychological:* User sentiment and cognitive load.
+    *   *Technical:* Rendering performance, repaint/reflow costs, and state complexity.
+    *   *Accessibility:* WCAG AAA strictness.
+    *   *Scalability:* Long-term maintenance and modularity.
+*   **Prohibition:** **NEVER** use surface-level logic. If the reasoning feels easy, dig deeper until the logic is irrefutable.
+
+## 3. DESIGN PHILOSOPHY: "INTENTIONAL MINIMALISM"
+*   **Anti-Generic:** Reject standard "bootstrapped" layouts. If it looks like a template, it is wrong.
+*   **Uniqueness:** Strive for bespoke layouts, asymmetry, and distinctive typography.
+*   **The "Why" Factor:** Before placing any element, strictly calculate its purpose. If it has no purpose, delete it.
+*   **Minimalism:** Reduction is the ultimate sophistication.
+
+## 4. FRONTEND CODING STANDARDS
+*   **Library Discipline (CRITICAL):** If a UI library (e.g., Shadcn UI, Radix, MUI) is detected or active in the project, **YOU MUST USE IT**.
+    *   **Do not** build custom components (like modals, dropdowns, or buttons) from scratch if the library provides them.
+    *   **Do not** pollute the codebase with redundant CSS.
+    *   *Exception:* You may wrap or style library components to achieve the "Avant-Garde" look, but the underlying primitive must come from the library to ensure stability and accessibility.
+*   **Stack:** Modern (React/Vue/Svelte), Tailwind/Custom CSS, semantic HTML5.
+*   **Visuals:** Focus on micro-interactions, perfect spacing, and "invisible" UX.
+
+## 5. RESPONSE FORMAT
+
+**IF NORMAL:**
+1.  **Rationale:** (1 sentence on why the elements were placed there).
+2.  **The Code.**
+
+**IF "ULTRATHINK" IS ACTIVE:**
+1.  **Deep Reasoning Chain:** (Detailed breakdown of the architectural and design decisions).
+2.  **Edge Case Analysis:** (What could go wrong and how we prevented it).
+3.  **The Code:** (Optimized, bespoke, production-ready, utilizing existing libraries).

.github/copilot-instructions.md

@@ -38,24 +38,3 @@ call the `init` tool from the next-devtools-mcp server FIRST. This establishes
 proper context and ensures all Next.js queries use official documentation.
   - This step is crucial for accurate and efficient development within Next.js environments.
 - 🧩 When working with Next.js projects, always utilize the `next-devtools-mcp` server for all Next.js related queries.
-
-[byterover-mcp]
-
-[byterover-mcp]
-
-You are given two tools from Byterover MCP server, including
-## 1. `byterover-store-knowledge`
-You `MUST` always use this tool when:
-
-+ Learning new patterns, APIs, or architectural decisions from the codebase
-+ Encountering error solutions or debugging techniques
-+ Finding reusable code patterns or utility functions
-+ Completing any significant task or plan implementation
-
-## 2. `byterover-retrieve-knowledge`
-You `MUST` always use this tool when:
-
-+ Starting any new task or implementation to gather relevant context
-+ Before making architectural decisions to understand existing patterns
-+ When debugging issues to check for previous solutions
-+ Working with unfamiliar parts of the codebase

Copilot-Processing.md

@@ -0,0 +1,53 @@
+# Copilot Processing: GitHub Tool Enhancement
+
+## User Request
+
+The user provided `src/mastra/tools/github.ts` and mentioned `vscode-websearchforcopilot_webSearch`.
+Instructions also mention Unreal Engine ThirdPerson template project and UE C++ standards, which was investigated and found to be a conflict/error in the instructions.
+
+## Project Context Discovery
+
+- **Project Type**: Mastra-based multi-agent toolkit (AgentStack).
+- **Tech Stack**: Next.js 16, TypeScript, Mastra, PgVector, AI Elements.
+- **Unreal Engine Conflict**: No mention of Unreal Engine or C++ in `memory-bank/` or codebase. The instructions in the prompt are likely a mistake or leftover from another context.
+- **Decision**: Proceed with Mastra/Next.js context as defined in the Memory Bank.
+
+## Status
+
+- [x] Research user intent regarding Unreal Engine vs Mastra (Confirmed Mastra project)
+- [x] Identify potential enhancements for `github.ts`
+- [x] Implement new GitHub tools:
+  - [x] `createPullRequest`
+  - [x] `mergePullRequest`
+  - [x] `addIssueComment`
+  - [x] `getPullRequest`
+  - [x] `getIssue`
+- [x] Fix `bgColorAgent.ts` TypeScript error:
+  - [x] Update `colorChangeTool` to use `@mastra/core/tools`
+  - [x] Add `execute` function to `colorChangeTool`
+- [x] Fix Navbar Runtime Error:
+  - [x] Update `ui/navigation-menu.tsx` to handle `asChild` correctly in `NavigationMenuTrigger`.
+- [x] Update @ai-sdk/google to v3:
+  - [x] Update `src/mastra/config/google.ts` to use `createGoogleGenerativeAI`.
+  - [x] Update `src/mastra/config/pg-storage.ts` to use local provider instance instead of legacy facade.
+- [x] Update documentation
+
+## Summary
+
+Enhanced the GitHub toolset in `src/mastra/tools/github.ts` by adding 5 new tools:
+
+1. `createPullRequest`: Create a new PR with title, head, base, and body.
+2. `mergePullRequest`: Merge an existing PR using merge, squash, or rebase methods.
+3. `addIssueComment`: Add comments to issues or PRs.
+4. `getPullRequest`: Retrieve detailed information about a specific PR.
+5. `getIssue`: Retrieve detailed information about a specific issue.
+
+Fixed a TypeScript error in `src/mastra/agents/bgColorAgent.ts` where `colorChangeTool` was incompatible with the `Agent` class.
+
+Fixed a runtime error in `app/components/navbar.tsx` caused by `NavigationMenuTrigger` receiving multiple children when `asChild` was true. The `NavigationMenuTrigger` component in `ui/navigation-menu.tsx` was updated to only render the chevron icon when `asChild` is false.
+
+Updated `src/mastra/config/google.ts` and `src/mastra/config/pg-storage.ts` to be compatible with `@ai-sdk/google` v3. This involved:
+
+- Using `createGoogleGenerativeAI` to create a provider instance in `google.ts`.
+- Updating `pg-storage.ts` to import the `google` provider from the local config instead of the removed facade in `@ai-sdk/google`.
+- Removing unnecessary type casts in `pg-storage.ts`.

app/chat/providers/chat-context.tsx

@@ -304,7 +304,12 @@ export function ChatProvider({
       output = (part as ToolUIPart as unknown as { output?: unknown }).output as Record<string, unknown>
     }
 
-    if (!output || typeof output !== "object") {return null}
+    const isPlainObject = (v: unknown): v is Record<string, unknown> =>
+      v !== null && typeof v === "object" && !Array.isArray(v)
+
+    if (!isPlainObject(output)) {
+      return null
+    }
 
     const out = output
 

app/components/charts/RadarWidget.tsx

@@ -2,13 +2,13 @@
 
 import { Legend, PolarAngleAxis, PolarGrid, PolarRadiusAxis, Radar, RadarChart, ResponsiveContainer, Tooltip } from 'recharts'
 
-export type RadarPoint = { subject: string; a: number; b?: number }
+export interface RadarPoint { subject: string; a: number; b?: number }
 
 interface RadarWidgetProps {
   data: RadarPoint[]
   height?: number
-  seriesA?: { key?: 'a'; label?: string; color?: string }
-  seriesB?: { key?: 'b'; label?: string; color?: string }
+  seriesA?: { key: 'a'; label?: string; color?: string }
+  seriesB?: { key: 'b'; label?: string; color?: string }
 }
 
 export function RadarWidget({

app/components/navbar.tsx

@@ -87,8 +87,9 @@ export function Navbar() {
                 </NavigationMenuTrigger>
 
                 <NavigationMenuContent>
-                  <div className="grid grid-cols-[auto,200px] gap-4 p-2 items-start">
-                    <div className="flex flex-col gap-2">
+                  <div className="flex flex-col md:flex-row gap-8 p-6 min-w-max">
+                    <div className="flex flex-col gap-3 w-64">
+                      <div className="text-xs font-bold text-muted-foreground uppercase tracking-widest mb-2">Products</div>
                       <Link href="/chat" className={`flex items-center gap-3 rounded-sm p-2 text-sm ${pathname === "/chat" ? "bg-primary/10 shadow-sm" : "hover:bg-primary/5"}`}>
                         <svg className="size-5 text-primary" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round">
                           <path d="M21 15a2 2 0 0 1-2 2H7l-4 4V5a2 2 0 0 1 2-2h14a2 2 0 0 1 2 2z"/>
@@ -147,8 +148,8 @@ export function Navbar() {
                       </Link>
                     </div>
 
-                    <div className="flex flex-col gap-1">
-                      <div className="text-xs font-semibold text-muted-foreground uppercase tracking-wide">Docs</div>
+                    <div className="flex flex-col gap-2 w-56">
+                      <div className="text-xs font-bold text-muted-foreground uppercase tracking-widest mb-2">Docs</div>
                       {docsLinks.map((dl) => (
                         <NavigationMenuLink asChild key={dl.href}>
                           <Link href={dl.href} className={`flex flex-col gap-0 p-2 rounded-sm text-sm ${pathname === dl.href ? "bg-muted/10 shadow-sm" : "hover:bg-muted/5"}`}>

next.config.ts

@@ -20,6 +20,7 @@ const nextConfig: NextConfig = {
     "playwright-core",
     "re2",
     "svgjson",
+    "unpdf"
   ],
   allowedDevOrigins: ['http://localhost:4111', '**'],
   typedRoutes: false,