@jaypie/mcp 0.6.3 → 0.6.5

package/dist/suites/docs/index.js

@@ -8,7 +8,7 @@ import { gt } from 'semver';
 /**
  * Docs Suite - Documentation services (skill, version, release_notes)
  */
-const BUILD_VERSION_STRING = "@jaypie/mcp@0.6.3#291140bb"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.6.5#d73a8800"
     ;
 const __filename$1 = fileURLToPath(import.meta.url);
 const __dirname$1 = path.dirname(__filename$1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaypie/mcp",
-  "version": "0.6.3",
+  "version": "0.6.5",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.23.md

@@ -0,0 +1,43 @@
+---
+version: 1.2.23
+date: 2025-01-26
+summary: Fix shared secrets not injecting env vars across constructs (Issue #158)
+---
+
+# @jaypie/constructs 1.2.23
+
+## Bug Fix
+
+### Shared Secrets Between Constructs (Issue #158)
+
+Fixed an issue where secrets declared in multiple constructs (e.g., `JaypieQueuedLambda` and `JaypieNextJs`) would not properly inject `SECRET_*` environment variables or grant IAM permissions to the second construct.
+
+**Root Cause**: `JaypieLambda` and `JaypieNextJs` were calling `resolveSecrets(scope, ...)` with their parent construct as the scope. This caused secrets to be cached per-construct rather than per-stack, so constructs couldn't share secrets.
+
+**Fix**: Changed both `JaypieLambda` and `JaypieNextJs` to use `Stack.of(this)` as the scope for `resolveSecrets`. This ensures:
+- Secrets are shared at the stack level across all constructs
+- Each construct sets its own `SECRET_*` environment variables
+- Each construct grants IAM permissions to its Lambda function
+
+**Before** (broken):
+```typescript
+// JaypieQueuedLambda created secrets under its own namespace
+// JaypieNextJs couldn't find or use those secrets
+const jobProcessor = new JaypieQueuedLambda(this, "JobProcessor", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Created JobProcessorANTHROPICAPIKEY-xxx
+});
+const nextjsApp = new JaypieNextJs(this, "NextJsApp", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Missing env var and permissions!
+});
+```
+
+**After** (fixed):
+```typescript
+// Both constructs share secrets at stack level
+const jobProcessor = new JaypieQueuedLambda(this, "JobProcessor", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Creates shared secret
+});
+const nextjsApp = new JaypieNextJs(this, "NextJsApp", {
+  secrets: ["ANTHROPIC_API_KEY"],  // Reuses same secret, gets env var + permissions
+});
+```

package/release-notes/mcp/0.6.5.md

@@ -0,0 +1,12 @@
+---
+version: 0.6.5
+date: 2026-01-26
+summary: Added migration guide for class to category refactor in DynamoDB skill
+---
+
+# @jaypie/mcp 0.6.5
+
+## Changes
+
+- Added migration section to `dynamodb` skill documenting the `class` → `category` field rename in @jaypie/dynamodb 0.4.0+
+- Documents table recreation and migration script options for existing tables

package/skills/dynamodb.md

@@ -147,3 +147,19 @@ describe("OrderService", () => {
 });
 ```
 
+## Migration: class to category (v0.4.0)
+
+Version 0.4.0 renamed `class` → `category` and `indexClass` → `indexCategory`.
+
+**If your table was created with an older version:**
+
+1. **Local dev**: Delete and recreate the table using MCP `createTable`
+2. **Production**: See `packages/dynamodb/CLAUDE.md` for migration script
+
+| Old | New |
+|-----|-----|
+| `class` | `category` |
+| `indexClass` | `indexCategory` |
+| `INDEX_CLASS` | `INDEX_CATEGORY` |
+| `queryByClass()` | `queryByCategory()` |
+

package/skills/llm.md

@@ -142,6 +142,27 @@ const greetTool = fabricLlmTool(greetService);
 const toolkit = new Toolkit([greetTool]);
 ```
 
+### Explain Mode
+
+Explain mode adds transparency to tool calling by requiring the LLM to state its reasoning when invoking tools.
+
+```typescript
+// Enable via Toolkit constructor
+const toolkit = new Toolkit([myTool], { explain: true });
+
+// Or via operate options
+const response = await Llm.operate("What's the weather?", {
+  model: "gpt-5.1",
+  tools: myTools,
+  explain: true,
+});
+```
+
+When enabled:
+- Each tool receives an `__Explanation` parameter requiring the model to state why it's calling the tool
+- The explanation is stripped before the tool executes (tools receive clean arguments)
+- Useful for debugging and understanding LLM decision-making
+
 ## Structured Output
 
 ### Natural Schema