@jaypie/mcp 0.8.146 → 0.8.148

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.146#5d742935"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.148#242a2958"
     ;
 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.146",
+  "version": "0.8.148",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/jaypie/1.2.98.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.98
+date: 2026-09-05
+summary: Pick up @jaypie/logger 1.2.24 and @jaypie/llm 1.3.40
+---
+
+## Changes
+
+- `@jaypie/logger` 1.2.24: `log.sessionActive` reports whether a report session
+  is open
+- `@jaypie/llm` 1.3.40: no tally attempt outside an active logger session

package/release-notes/llm/1.3.40.md

@@ -0,0 +1,13 @@
+---
+version: 1.3.40
+date: 2026-09-05
+summary: Skip the operate tally when no logger session is active
+---
+
+## Changes
+
+- `tallyOperate` returns before building a payload when `log.sessionActive` is
+  `false`, so `operate()` and `stream()` outside a Jaypie handler no longer
+  produce `[logger] tally() called without active session` at trace (issue #522)
+- Behavior inside a handler is unchanged; the guard compares against `false`, so
+  a logger predating `@jaypie/logger` 1.2.24 still tallies

package/release-notes/llm/1.3.41.md

@@ -0,0 +1,16 @@
+---
+version: 1.3.41
+date: 2026-09-07
+summary: Repoint MODEL.FIREWORKS.DEEPSEEK at the dated deepseek-v4-pro-0813 id
+---
+
+## Changes
+
+- `MODEL.FIREWORKS.DEEPSEEK` is now
+  `accounts/fireworks/models/deepseek-v4-pro-0813`. Fireworks renamed the model;
+  the undated `accounts/fireworks/models/deepseek-v4-pro` stopped responding
+  entirely, which is why the live capability matrix excluded it on 2026-08-31
+- `COST` prices the new id at $1.32 input, $3.96 output, $0.044 cached input
+  read per million tokens (Fireworks Standard tier). The retired undated id
+  keeps its `COST` entry per policy, so historical tallies still resolve
+- The model runs the live capability matrix again; `minimax-m2p7` stays excluded

package/release-notes/logger/1.2.24.md

@@ -0,0 +1,24 @@
+---
+version: 1.2.24
+date: 2026-09-05
+summary: Expose log.sessionActive so libraries can guard optional report and tally calls
+---
+
+## Changes
+
+- `JaypieLogger` exposes a read-only `sessionActive` getter, `true` between
+  `setup()` and `teardown()`
+- Libraries that tally opportunistically guard on it rather than calling
+  `tally()` unconditionally and having the logger trace
+  `[logger] tally() called without active session`
+
+## Usage
+
+```typescript
+if (log.sessionActive !== false) {
+  log.tally({ llm: { operates: 1, turns: 2 } });
+}
+```
+
+Compare against `false` rather than testing truthiness: a logger predating this
+release reports `undefined`, where the tally should still be attempted.

package/release-notes/mcp/0.8.147.md

@@ -0,0 +1,14 @@
+---
+version: 0.8.147
+date: 2026-09-05
+summary: Release notes for @jaypie/logger 1.2.24, @jaypie/llm 1.3.40, @jaypie/testkit 1.2.69, and jaypie 1.2.98
+---
+
+## Changes
+
+- Added release notes for `@jaypie/logger` 1.2.24, `@jaypie/llm` 1.3.40,
+  `@jaypie/testkit` 1.2.69, and `jaypie` 1.2.98
+- `skills/logs.md` documents `log.sessionActive` and the guard pattern for
+  optional tally calls
+- `skills/llm.md` records that the operate tally is skipped outside a handler
+  session rather than no-oping inside the logger

package/release-notes/mcp/0.8.148.md

@@ -0,0 +1,9 @@
+---
+version: 0.8.148
+date: 2026-09-07
+summary: Release notes for @jaypie/llm 1.3.41
+---
+
+## Changes
+
+- Added release notes for `@jaypie/llm` 1.3.41

package/release-notes/testkit/1.2.69.md

@@ -0,0 +1,12 @@
+---
+version: 1.2.69
+date: 2026-09-05
+summary: Mock log reports sessionActive
+---
+
+## Changes
+
+- `mockLogFactory` sets `sessionActive: true` on the mock log, matching
+  `@jaypie/logger` 1.2.24, so code guarding a tally on the session runs under
+  test
+- Tests exercising the unguarded path set `log.sessionActive = false`

package/skills/llm.md

@@ -676,7 +676,7 @@ Inside a Jaypie handler (`expressHandler`, `lambdaHandler`, and stream variants)
 - `operates` counts loop executions; repeated calls sum every number
 - `usage` is keyed `provider:model` — fallback providers appear as separate keys
 - `tools` appears only when tools were called
-- Outside a handler session the tally is a silent no-op
+- Outside a handler session the tally is skipped entirely (guarded on `log.sessionActive`), so a CLI or script calling `operate()` directly emits nothing
 
 ## LLM Observability (Datadog)
 

package/skills/logs.md

@@ -132,6 +132,16 @@ log.tally({ llm: { operates: 1, turns: 3 } });
 
 Outside an active session `tally()` silently no-ops, so libraries can tally unconditionally. `@jaypie/llm` tallies an `llm` key (turns, tool calls, usage by model) automatically.
 
+`log.sessionActive` reports whether a session is open. A library that assembles a tally payload guards on it, skipping the work when nothing will collect the result:
+
+```typescript
+if (log.sessionActive !== false) {
+  log.tally({ llm: { operates: 1, turns: 2 } });
+}
+```
+
+Compare against `false` rather than testing truthiness: an older logger without the accessor reports `undefined`, and the tally should still be attempted there.
+
 ## Setting Log Level
 
 Via environment variable: