@jaypie/mcp 0.8.148 → 0.8.149

package/dist/suites/docs/index.js

@@ -10,7 +10,7 @@ import { gt } from 'semver';
 /**
  * Docs Suite - Documentation services (skill, version, release_notes)
  */
-const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.148#242a2958"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.149#b80d3df3"
     ;
 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.8.148",
+  "version": "0.8.149",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/jaypie/1.2.99.md

@@ -0,0 +1,10 @@
+---
+version: 1.2.99
+date: 2026-09-10
+summary: Pick up @jaypie/kit 1.2.19
+---
+
+## Changes
+
+- `@jaypie/kit` 1.2.19: `placeholders` renders `""`, `0`, `false`, and `null`
+  instead of leaving the handlebar (#526)

package/release-notes/kit/1.2.19.md

@@ -0,0 +1,17 @@
+---
+version: 1.2.19
+date: 2026-09-10
+summary: placeholders renders empty-string, zero, and other falsy values instead of leaving the handlebar
+---
+
+## Changes
+
+- `placeholders()` keeps a `{{ key }}` handlebar only when the resolved value is
+  `undefined`. A present `""`, `0`, `false`, or `null` renders through
+  `String()`. Previously any falsy value left the literal handlebar in the
+  output (#526).
+- The internal path lookup stops only when the path breaks (a non-object or an
+  absent key), so falsy nested values such as `{{ user.count }}` with
+  `{ user: { count: 0 } }` resolve.
+- Whitespace handling is unchanged: `{{ name }}` and `{{name}}` resolve the same
+  key, and a missing key keeps its original spacing.

package/release-notes/mcp/0.8.149.md

@@ -0,0 +1,10 @@
+---
+version: 0.8.149
+date: 2026-09-10
+summary: Document placeholders falsy-value rendering
+---
+
+## Changes
+
+- `skill("placeholders")` documents that only `undefined` keeps the handlebar
+  and that falsy values render (#526)

package/release-notes/testkit/1.2.70.md

@@ -0,0 +1,13 @@
+---
+version: 1.2.70
+date: 2026-09-10
+summary: Remove the orphaned placeholders copy; the mock wraps @jaypie/kit 1.2.19
+---
+
+## Changes
+
+- Removed `src/placeholders.ts` and `src/types/placeholders.d.ts`. Neither was
+  imported nor built, and the copy carried the falsy-value bug fixed in
+  `@jaypie/kit` 1.2.19.
+- The `placeholders` mock continues to wrap the real `@jaypie/kit`
+  implementation, so it picks up the fix.

package/skills/placeholders.md

@@ -30,7 +30,8 @@ function placeholders(
 - Dot notation: `{{user.name}}`
 - Bracket notation: `{{items[0].city}}`
 - Whitespace trimmed: `{{ name }}` resolves same as `{{name}}`
-- Unmatched keys remain: `{{missing}}` passes through unchanged
+- Unmatched keys remain: `{{missing}}` passes through unchanged, spacing intact
+- Only `undefined` counts as missing: `""`, `0`, `false`, and `null` render via `String()`
 
 ## Examples
 
@@ -56,6 +57,10 @@ placeholders(() => `Generated at {{time}}`, { time: "12:00" });
 // Missing keys pass through
 placeholders("{{known}} and {{unknown}}", { known: "yes" });
 // "yes and {{unknown}}"
+
+// Falsy values render
+placeholders("a={{ x }} b={{ n }}", { x: "", n: 0 });
+// "a= b=0"
 ```
 
 ## LLM Integration