@jaypie/mcp 0.8.21 → 0.8.23

package/dist/suites/docs/index.js

@@ -9,7 +9,7 @@ import { gt } from 'semver';
 /**
  * Docs Suite - Documentation services (skill, version, release_notes)
  */
-const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.21#a7fd63df"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.23#3db47ebf"
     ;
 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.21",
+  "version": "0.8.23",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",
@@ -39,7 +39,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@jaypie/fabric": "^0.2.2",
+    "@jaypie/fabric": "^0.2.4",
     "@jaypie/tildeskill": "^0.2.0",
     "@modelcontextprotocol/sdk": "^1.17.0",
     "commander": "^14.0.0",

package/release-notes/dynamodb/0.4.4.md

@@ -0,0 +1,20 @@
+---
+version: 0.4.4
+date: 2026-04-10
+summary: Pick up @jaypie/fabric@0.2.4 — query() once again falls back to DEFAULT_INDEXES for unregistered models
+---
+
+# @jaypie/dynamodb 0.4.4
+
+## Changes
+
+- Picks up `@jaypie/fabric@0.2.4`, restoring the deprecated `DEFAULT_INDEXES` fallback inside `getModelIndexes()`
+- `query({ model, scope })` against an unregistered model no longer throws `ConfigurationError`; it auto-detects `indexScope` from the restored `DEFAULT_INDEXES`
+
+## Why
+
+The 0.4.3 behavior surfaced as `ValidationException`/`ConfigurationError` against tables that previously worked, breaking deployed services. The fallback is restored as a deprecated behavior; both the dynamodb fallback and the underlying `@jaypie/fabric` `DEFAULT_INDEXES` export are slated for removal alongside `@jaypie/fabric@0.3.0`.
+
+## Migration
+
+Register model indexes explicitly with `registerModel({ model, indexes })` to be ready for the upcoming removal.

package/release-notes/express/1.2.20.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.20
+date: 2026-04-09
+summary: Integrate log session management in express handlers
+---
+
+## Changes
+
+- `expressHandler` and `expressStreamHandler` now call `log.setup()` / `log.teardown()` for session lifecycle
+- Request status and normalized path are reported via `log.report()` for inclusion in the teardown report
+- Replaced manual `log.tag()` calls with `log.setup(tags)` for invoke/handler tags

package/release-notes/fabric/0.2.4.md

@@ -0,0 +1,20 @@
+---
+version: 0.2.4
+date: 2026-04-10
+summary: Restore DEFAULT_INDEXES export and getModelIndexes fallback removed in 0.2.3; both are deprecated and slated for removal in 0.3.0
+---
+
+# @jaypie/fabric 0.2.4
+
+## Restored
+
+- `DEFAULT_INDEXES` export from `@jaypie/fabric` and `@jaypie/fabric/index` (removed in 0.2.3 via the same PR that added default security headers to `JaypieDistribution`)
+- `getModelIndexes(model)` once again falls back to `DEFAULT_INDEXES` when a model has not been registered, restoring previous DynamoDB GSI behavior for unregistered models
+
+## Why
+
+The 0.2.3 removal was a breaking change that left downstream consumers without a way to populate GSI keys for unregistered models, surfacing as `ValidationException` errors against tables that previously worked.
+
+## Deprecation
+
+Both `DEFAULT_INDEXES` and the implicit fallback inside `getModelIndexes()` are marked `@deprecated`. They are scheduled for removal in 0.3.0. Register model indexes explicitly with `registerModel({ model, indexes })`.

package/release-notes/lambda/1.2.5.md

@@ -0,0 +1,10 @@
+---
+version: 1.2.5
+date: 2026-04-09
+summary: Integrate log session management in lambda handlers
+---
+
+## Changes
+
+- `lambdaHandler` and `lambdaStreamHandler` now call `log.setup()` / `log.teardown()` for session lifecycle
+- Replaced manual `log.tag()` calls with `log.setup(tags)` for invoke/handler tags

package/release-notes/logger/1.2.13.md

@@ -0,0 +1,13 @@
+---
+version: 1.2.13
+date: 2026-04-09
+summary: Add log session management with setup(), teardown(), and report()
+---
+
+## Changes
+
+- `log.setup(tags?)` starts a logging session, applies tags, resets counters
+- `log.teardown()` emits accumulated report as `log.info.var({ report })` with auto-tracked `{ log: { warn, warns, error, errors } }`
+- `log.report({ key: value })` accumulates per-request data; warns on duplicate keys
+- Warn and error calls (including `.var()`) are auto-counted during active sessions
+- `init()` resets session state

package/release-notes/testkit/1.2.28.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.28
+date: 2026-04-09
+summary: Add setup, teardown, report to log mock
+---
+
+## Changes
+
+- Added `setup`, `teardown`, `report` to `mockLogFactory()`, mock types, and `spyLog`/`restoreLog`

package/skills/logs.md

@@ -63,6 +63,23 @@ log.var({ Processing: {
 
 Log any important, even scalar, data and filter with `var` in Datadog
 
+## Session Management
+
+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.
+
+```typescript
+// Manual session (handlers do this automatically)
+log.setup({ handler: "myHandler", invoke: "abc-123" });
+
+// Accumulate report data during the request
+log.report({ userId: "456" });
+log.report({ itemCount: 3 });
+
+// Teardown emits the report with warn/error stats
+log.teardown();
+// => { report: { userId: "456", itemCount: 3, log: { warn: false, warns: 0, error: false, errors: 0 } } }
+```
+
 ## Setting Log Level
 
 Via environment variable: