@jaypie/mcp 0.8.169 → 0.8.171

package/dist/assets.js

@@ -55,11 +55,11 @@ function getMcpAssetPaths() {
  */
 function getMcpBuildInfo() {
     return {
-        commit: "74f2d649"
+        commit: "e1bbf2ee"
             ,
-        version: "0.8.169"
+        version: "0.8.171"
             ,
-        versionString: "@jaypie/mcp@0.8.169#74f2d649"
+        versionString: "@jaypie/mcp@0.8.171#e1bbf2ee"
             ,
     };
 }

package/package.json

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

package/release-notes/jaypie/1.2.108.md

@@ -0,0 +1,10 @@
+---
+version: 1.2.108
+date: 2026-09-24
+summary: Pulls @jaypie/logger 1.2.25
+---
+
+## Changes
+
+- **`@jaypie/logger` 1.2.25**: `log.report()` merges nested objects
+  recursively; a changed leaf logs its dotted path at debug (#585).

package/release-notes/llm/1.3.49.md

@@ -0,0 +1,16 @@
+---
+version: 1.3.49
+date: 2026-09-24
+summary: COST prices nemotron-lightning-3p5-30b-a3b; the model is not cataloged because it does not support tools or structured output
+---
+
+## Changes
+
+- `COST` prices `accounts/fireworks/models/nemotron-lightning-3p5-30b-a3b` at $0.05 input, $0.20 output, $0.01 cache read per million tokens (Fireworks standard serverless rates)
+- `MODEL.FIREWORKS.NEMOTRON_LIGHTNING` is deliberately absent. The model does not support tools or structured output: a `json_schema` `response_format` hangs with no response, and after a tool call it answers in prose. A caller can still pass the id directly
+- `MODEL.FIREWORKS.NEMOTRON` remains `nemotron-3-ultra-nvfp4`, the newest serverless Nemotron Ultra
+
+## Testing
+
+- `npm run test -w packages/llm`: unit suite passes; Google hot specs failed on provider "high demand" 503s
+- Live, 2026-09-24 (`APP_MODELS=accounts/fireworks/models/nemotron-lightning-3p5-30b-a3b npm run test:llm:matrix`, twice): plain and temperature passed; tools, structured, and both timed out at 180s

package/release-notes/logger/1.2.25.md

@@ -0,0 +1,24 @@
+---
+version: 1.2.25
+date: 2026-09-24
+summary: log.report() merges nested objects recursively instead of shallow-overwriting top-level keys
+---
+
+## Changes
+
+- `log.report()` merges plain objects recursively (#585). Two calls that
+  write different children of the same key keep both
+- Arrays and scalars are leaves where the last write wins. A changed leaf logs
+  `[logger] Overwriting report key: <dotted.path>` at debug; rewriting the
+  same value logs nothing
+
+## Usage
+
+```typescript
+log.report({ agentModel: { agent_notes: { chain: "Fast" } } });
+log.report({ agentModel: { agent_evidence_list: { chain: "Fast" } } });
+// => teardown report includes both agent_notes and agent_evidence_list
+```
+
+Use `log.tally()` for values that accumulate; `report()` is for data
+recorded once, including nested data filled in across several calls.

package/release-notes/mcp/0.8.171.md

@@ -0,0 +1,11 @@
+---
+version: 0.8.171
+date: 2026-09-24
+summary: logs skill describes report() recursive merge and debug-level leaf overwrite
+---
+
+## Changes
+
+- **`logs` skill**: `log.report()` merges plain objects recursively and logs
+  a changed leaf at debug, not warn; `log.tally()` is for values that
+  accumulate (#586).

package/skills/logs.md

@@ -122,7 +122,7 @@ log.teardown();
 // => { report: { userId: "456", itemCount: 3, log: { warn: false, warns: 0, error: false, errors: 0 } } }
 ```
 
-`log.report()` warns when a key is written twice. Use `log.tally()` for data written repeatedly — keys combine instead: numbers sum, strings collect into an array of strings, booleans AND, and objects merge recursively.
+`log.report()` records values once. Plain objects merge recursively, so separate calls can fill sibling keys under one parent (`report({ agent: { a: {...} } })` then `report({ agent: { b: {...} } })` keeps both). Arrays and scalars are leaves: the last write wins, and a changed leaf logs `[logger] Overwriting report key: <dotted.path>` at `debug`. Use `log.tally()` for data that accumulates — keys combine instead: numbers sum, strings collect into an array of strings, booleans AND, and objects merge recursively.
 
 ```typescript
 log.tally({ llm: { operates: 1, turns: 2 } });