@jaypie/mcp 0.8.92 → 0.8.93

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.92#ea103a82"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.93#ff14510f"
     ;
 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.92",
+  "version": "0.8.93",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/express/1.2.28.md

@@ -0,0 +1,12 @@
+---
+version: 1.2.28
+date: 2026-07-04
+summary: Include route parameters in the automatic session report
+---
+
+# @jaypie/express 1.2.28
+
+## Changes
+
+- `expressHandler` and `expressStreamHandler` now include a `parameters` field (mirroring `req.params`) in the automatic `log.report()` call when the matched route defines params, e.g. `path: "/workflows/:id/messages"` now also reports `parameters: { id: "..." }`.
+- `parameters` is omitted entirely when the route has no params.

package/release-notes/jaypie/1.2.62.md

@@ -0,0 +1,14 @@
+---
+version: 1.2.62
+date: 2026-07-04
+summary: Pick up @jaypie/express 1.2.28 (report parameters) and @jaypie/logger 1.2.20 (exported JaypieLogger)
+---
+
+## Changes
+
+- `@jaypie/express` dependency raised to `^1.2.28` — `expressHandler` and
+  `expressStreamHandler` now include a `parameters` field (mirroring
+  `req.params`) in the automatic session report when the matched route
+  defines params
+- `@jaypie/logger` dependency raised to `^1.2.20` — `JaypieLogger` is now a
+  named export, and `report()`/`setup()`/`teardown()` gained TSDoc comments

package/release-notes/logger/1.2.20.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.20
+date: 2026-07-04
+summary: Export JaypieLogger class and document setup/report/teardown session management
+---
+
+## Changes
+
+- Exported `JaypieLogger` as a named export from `@jaypie/logger` so its class members are visible to API Extractor and appear in generated API docs
+- Added TSDoc comments to `report()`, `setup()`, and `teardown()`
+- Documented the `log.setup()` / `log.report()` / `log.teardown()` session management pattern on jaypie.net (previously only covered in the internal `logs` skill)

package/release-notes/mcp/0.8.93.md

@@ -0,0 +1,11 @@
+---
+version: 0.8.93
+date: 2026-07-04
+summary: Document expressHandler/expressStreamHandler automatic parameters field in session report
+---
+
+## Changes
+
+- `skill("express")` documents the automatic `log.report()` session report,
+  including the new `parameters` field (mirrors `req.params`)
+- Release notes for `@jaypie/express` 1.2.28

package/release-notes/testkit/1.2.52.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.52
+date: 2026-07-04
+summary: Re-export JaypieLogger from @jaypie/testkit/mock to match @jaypie/logger 1.2.20
+---
+
+## Changes
+
+- `@jaypie/testkit/mock` re-exports `JaypieLogger` alongside the existing
+  `Logger`, `FORMAT`, `LEVEL`, `redactAuth`, `sanitizeAuth` mocks, matching
+  `@jaypie/logger@1.2.20`'s new named export

package/skills/express.md

@@ -162,6 +162,24 @@ The Lambda adapter provides Express-compatible request properties:
 | `req._lambdaContext` | Original Lambda context |
 | `req._lambdaEvent` | Original Lambda event |
 
+## Session Report
+
+`expressHandler` and `expressStreamHandler` automatically call `log.report()` with request metadata before the session's `log.teardown()` (see `skill("logs")`):
+
+```typescript
+{
+  method: "GET",
+  path: "/workflows/:id/messages", // UUID segments normalized to :id
+  query: "limit=10",
+  contentType: "",
+  contentLength: 0,
+  status: "200",
+  parameters: { id: "123e4567-e89b-12d3-a456-426614174000" }, // req.params, only when non-empty
+}
+```
+
+`parameters` mirrors Express's `req.params` so the original route parameter values survive path normalization for aggregation.
+
 ## CDK Integration
 
 Deploy with `@jaypie/constructs`: