@jaypie/mcp 0.8.21 → 0.8.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -9,7 +9,7 @@ import { gt } from 'semver';
9
9
  /**
10
10
  * Docs Suite - Documentation services (skill, version, release_notes)
11
11
  */
12
- const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.21#a7fd63df"
12
+ const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.22#ea37275f"
13
13
  ;
14
14
  const __filename$1 = fileURLToPath(import.meta.url);
15
15
  const __dirname$1 = path.dirname(__filename$1);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jaypie/mcp",
3
- "version": "0.8.21",
3
+ "version": "0.8.22",
4
4
  "description": "Jaypie MCP",
5
5
  "repository": {
6
6
  "type": "git",
@@ -0,0 +1,11 @@
1
+ ---
2
+ version: 1.2.20
3
+ date: 2026-04-09
4
+ summary: Integrate log session management in express handlers
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - `expressHandler` and `expressStreamHandler` now call `log.setup()` / `log.teardown()` for session lifecycle
10
+ - Request status and normalized path are reported via `log.report()` for inclusion in the teardown report
11
+ - Replaced manual `log.tag()` calls with `log.setup(tags)` for invoke/handler tags
@@ -0,0 +1,10 @@
1
+ ---
2
+ version: 1.2.5
3
+ date: 2026-04-09
4
+ summary: Integrate log session management in lambda handlers
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - `lambdaHandler` and `lambdaStreamHandler` now call `log.setup()` / `log.teardown()` for session lifecycle
10
+ - Replaced manual `log.tag()` calls with `log.setup(tags)` for invoke/handler tags
@@ -0,0 +1,13 @@
1
+ ---
2
+ version: 1.2.13
3
+ date: 2026-04-09
4
+ summary: Add log session management with setup(), teardown(), and report()
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - `log.setup(tags?)` starts a logging session, applies tags, resets counters
10
+ - `log.teardown()` emits accumulated report as `log.info.var({ report })` with auto-tracked `{ log: { warn, warns, error, errors } }`
11
+ - `log.report({ key: value })` accumulates per-request data; warns on duplicate keys
12
+ - Warn and error calls (including `.var()`) are auto-counted during active sessions
13
+ - `init()` resets session state
@@ -0,0 +1,9 @@
1
+ ---
2
+ version: 1.2.28
3
+ date: 2026-04-09
4
+ summary: Add setup, teardown, report to log mock
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - Added `setup`, `teardown`, `report` to `mockLogFactory()`, mock types, and `spyLog`/`restoreLog`
package/skills/logs.md CHANGED
@@ -63,6 +63,23 @@ log.var({ Processing: {
63
63
 
64
64
  Log any important, even scalar, data and filter with `var` in Datadog
65
65
 
66
+ ## Session Management
67
+
68
+ Handlers automatically call `log.setup()` and `log.teardown()` to bookend each request. On teardown, a report is emitted as `log.info.var({ report })` containing accumulated data and warn/error counts.
69
+
70
+ ```typescript
71
+ // Manual session (handlers do this automatically)
72
+ log.setup({ handler: "myHandler", invoke: "abc-123" });
73
+
74
+ // Accumulate report data during the request
75
+ log.report({ userId: "456" });
76
+ log.report({ itemCount: 3 });
77
+
78
+ // Teardown emits the report with warn/error stats
79
+ log.teardown();
80
+ // => { report: { userId: "456", itemCount: 3, log: { warn: false, warns: 0, error: false, errors: 0 } } }
81
+ ```
82
+
66
83
  ## Setting Log Level
67
84
 
68
85
  Via environment variable: