@jaypie/mcp 0.8.65 → 0.8.67

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.65#58028ec6"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.67#266d669f"
     ;
 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.65",
+  "version": "0.8.67",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.61.md

@@ -0,0 +1,18 @@
+---
+version: 1.2.61
+date: 2026-06-11
+summary: Lambda serviceTag now sets the PROJECT_SERVICE environment variable
+---
+
+## @jaypie/constructs 1.2.61
+
+### Added
+
+- **`serviceTag` sets `PROJECT_SERVICE`** (`JaypieLambda` and the
+  `JaypieQueuedLambda`, `JaypieBucketQueuedLambda`, `JaypieExpressLambda`,
+  `JaypieWebSocketLambda` constructs built on it). When a `serviceTag` is
+  provided, its value is now injected as the `PROJECT_SERVICE` environment
+  variable on the Lambda in addition to the existing service tag. Precedence is
+  explicit `environment.PROJECT_SERVICE` > `serviceTag` > `process.env.PROJECT_SERVICE`,
+  so a service no longer needs `PROJECT_SERVICE` set in the deploy environment to
+  identify itself at runtime.

package/release-notes/jaypie/1.2.50.md

@@ -0,0 +1,12 @@
+---
+version: 1.2.50
+date: 2026-06-11
+summary: Pick up @jaypie/logger 1.2.16 (data field in JSON output) and @jaypie/llm 1.2.38 peer (google provider naming)
+---
+
+## jaypie 1.2.50
+
+### Changes
+
+- **Dependencies**: `@jaypie/logger` ^1.2.16 — trailing log object split into `data` field in JSON output
+- **Peer dependencies**: `@jaypie/llm` ^1.2.38 — provider name standardized on `"google"` with deprecated `"gemini"` aliases

package/release-notes/llm/1.2.38.md

@@ -0,0 +1,15 @@
+---
+version: 1.2.38
+date: 2026-06-11
+summary: Standardize provider name on "google"; PROVIDER.GEMINI and GeminiProvider remain as deprecated aliases
+---
+
+## @jaypie/llm 1.2.38
+
+### Changes
+
+- **Provider naming**: "Google" is the provider; Gemini is the model family
+  - `PROVIDER.GOOGLE` replaces `PROVIDER.GEMINI` (deprecated alias kept, same object)
+  - `GoogleProvider` replaces `GeminiProvider` (deprecated alias export kept)
+  - `new Llm("gemini")` and fallback `{ provider: "gemini" }` still resolve to `"google"` with a deprecation warning (unchanged)
+- **Model constants**: Added `MODEL` export with named model constants; Google `TINY` is now `gemini-3.1-flash-lite`

package/release-notes/logger/1.2.16.md

@@ -0,0 +1,26 @@
+---
+version: 1.2.16
+date: 2026-06-11
+summary: Split trailing object into structured data field in JSON output
+---
+
+## Changes
+
+- `log.warn("message", { details })` (and all level methods) now emits `{ "message": "message", "data": { "details": ... } }` in JSON format instead of concatenating the stringified object into the message
+- Applies when the final argument is an object (or array) and all preceding arguments are scalars; preceding scalars are joined into `message`
+- Falls back to the previous space-joined concatenation when the object is not last, when multiple objects are passed, or when the trailing object does not serialize to JSON (e.g., `Error` instances)
+- Text format output is unchanged
+
+## Migration
+
+JSON output for `log.warn("Processing", { id: "my-id" })` changes from:
+
+```json
+{"message":"Processing {\"id\":\"my-id\"}"}
+```
+
+to:
+
+```json
+{"message":"Processing","data":{"id":"my-id"}}
+```

package/release-notes/mcp/0.8.66.md

@@ -0,0 +1,14 @@
+---
+version: 0.8.66
+date: 2026-06-05
+summary: Document request envelope in skill("api") — requests use the same { data } object-vs-array rules as responses
+---
+
+## Changed
+
+- **`api` skill** now documents the **request envelope**. Request bodies follow
+  the same `{ data }` convention as responses: `{ data: {} }` for a single record
+  (object), `{ data: [] }` for an array of records. The request rule was
+  previously undocumented in every skill file — only response format was covered.
+- Retitled the skill to **API Request and Response Format** and added a request
+  rule to the shared rules list.

package/release-notes/mcp/0.8.67.md

@@ -0,0 +1,12 @@
+---
+version: 0.8.67
+date: 2026-06-11
+summary: Update skill("logs") for logger data field and skill("llm") for Google provider naming
+---
+
+## @jaypie/mcp 0.8.67
+
+### Changes
+
+- **skill("logs")**: Document trailing-object split into `data` field in JSON log output
+- **skill("llm")**: Provider for Gemini models is named `"google"` (`"gemini"` deprecated); refresh provider default-model table to current constants

package/release-notes/testkit/1.2.41.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.41
+date: 2026-06-11
+summary: Add GoogleProvider mock; GeminiProvider remains as deprecated alias
+---
+
+## @jaypie/testkit 1.2.41
+
+### Changes
+
+- **LLM mocks**: `GoogleProvider` mock added following the `@jaypie/llm` rename; `GeminiProvider` remains as a deprecated alias

package/skills/api.md

@@ -1,11 +1,27 @@
 ---
-description: API response format and conventions
+description: API request and response format and conventions
 related: express, handlers, style
 ---
 
-# API Response Format
+# API Request and Response Format
 
-All API responses follow a consistent envelope format.
+All API requests and responses follow a consistent envelope format.
+
+## Request Envelope
+
+Request bodies follow the same `{ data }` envelope as responses.
+
+```json
+// Single record
+{ "data": { "name": "Example" } }
+
+// Array of records
+{ "data": [{ "name": "First" }, { "name": "Second" }] }
+```
+
+- `{ data: {} }` — single record (object)
+- `{ data: [] }` — array of records (even if zero or one result)
+- No other top-level keys at the root
 
 ## Response Envelope
 
@@ -39,8 +55,9 @@ Every response body is a JSON object with one top-level key:
 
 ### Rules
 
-1. A response contains either `data` or `errors`, never both
-2. Single records use an object: `{ data: {} }`
-3. Multiple records use an array: `{ data: [] }`
-4. Errors always use an array: `{ errors: [] }`
-5. No other top-level keys (no `status`, `message`, `meta` at the root)
+1. Requests and responses both use the `{ data }` envelope
+2. A response contains either `data` or `errors`, never both
+3. Single records use an object: `{ data: {} }`
+4. Multiple records use an array: `{ data: [] }`
+5. Errors always use an array: `{ errors: [] }` (responses only)
+6. No other top-level keys (no `status`, `message`, `meta` at the root)

package/skills/llm.md

@@ -21,11 +21,13 @@ console.log(response.content); // "4"
 
 | Provider | Match Keywords | Default Model |
 |----------|----------------|---------------|
-| OpenAI | "openai", "gpt", /^o\d/ | gpt-5.2 |
-| Anthropic | "anthropic", "claude", "haiku", "opus", "sonnet" | claude-sonnet-4-5 |
-| Google | "google", "gemini" | gemini-3-pro-preview |
-| OpenRouter | "openrouter" | z-ai/glm-4.7 |
-| xAI | "xai", "grok" | grok-4-1-fast-reasoning |
+| OpenAI | "openai", "gpt", /^o\d/ | gpt-5.4 |
+| Anthropic | "anthropic", "claude", "haiku", "opus", "sonnet" | claude-sonnet-4-6 |
+| Google | "google", "gemini" | gemini-3.1-pro-preview |
+| OpenRouter | "openrouter" | anthropic/claude-sonnet-4-6 |
+| xAI | "xai", "grok" | grok-latest |
+
+The provider name for Gemini models is `"google"` — `"gemini"` is accepted as a deprecated alias.
 
 ```typescript
 // Provider auto-detected from model
@@ -317,7 +319,7 @@ const review2 = await llm.operate(code2);
 
 ```bash
 ANTHROPIC_API_KEY   # Required for Anthropic
-GOOGLE_API_KEY      # Required for Gemini
+GOOGLE_API_KEY      # Required for Google (Gemini models)
 OPENAI_API_KEY      # Required for OpenAI
 OPENROUTER_API_KEY  # Required for OpenRouter
 XAI_API_KEY         # Required for xAI (Grok)

package/skills/logs.md

@@ -30,17 +30,19 @@ log.fatal("Fatal error"); // only used internally in jaypie
 
 ## Logging Data
 
-DO NOT use multiple parameters when logging:
-<BAD>
+A trailing object becomes the structured `data` field; preceding scalars join into `message`:
+
 ```typescript
-log.info("Processing", { id: "my-id" });
+log.warn("Processing failed", { id: "my-id" });
+// => { "message": "Processing failed", "data": { "id": "my-id" } }
 ```
-</BAD>
 
-Use `log.var` to log single-key objects that parse in Datadog:
+This only splits when the object is last and everything before it is scalar. An object mid-call, multiple objects, or a non-serializable object (e.g., `Error`) falls back to space-joined stringification — keep objects last and singular.
+
+Prefer `log.var` to log single-key objects that parse in Datadog:
 <GOOD>
 ```typescript
-log.trace("Processing", { id: "my-id" });
+log.trace("Processing");
 log.var({ id: "my-id" });
 ```
 </GOOD>