@jaypie/mcp 0.7.20 → 0.7.22

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.7.20#3704c7bc"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.22#e20270cd"
     ;
 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.7.20",
+  "version": "0.7.22",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/jaypie/1.2.13.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.13
+date: 2026-02-18
+summary: Update @jaypie/llm peer dependency to ^1.2.10
+---
+
+## Changes
+
+- Update `@jaypie/llm` peer dependency to `^1.2.10`

package/release-notes/jaypie/1.2.14.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.14
+date: 2026-02-18
+summary: Bump for @jaypie/logger 1.2.2 Datadog log forwarding transport
+---
+
+## Changes
+
+- Bump `@jaypie/logger` to 1.2.2 with opt-in Datadog log forwarding transport

package/release-notes/llm/1.2.10.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.10
+date: 2026-02-18
+summary: Add retry for transient network errors across all LLM providers
+---
+
+## Changes
+
+- Add `isTransientNetworkError` utility that detects low-level Node.js/undici network errors (ECONNRESET, ETIMEDOUT, etc.) by inspecting error codes, messages, and the `error.cause` chain
+- Integrate transient network error detection into all four provider adapters (Anthropic, Gemini, OpenAI, OpenRouter) so network errors are classified as retryable instead of unknown
+- Add retry logic to `StreamLoop` for connection-level failures before any chunks are yielded; mid-stream failures emit an error chunk instead of throwing

package/release-notes/logger/1.2.2.md

@@ -0,0 +1,15 @@
+---
+version: 1.2.2
+date: 2026-02-18
+summary: Add opt-in Datadog log forwarding transport for non-Lambda environments
+---
+
+## Changes
+
+- Add `DatadogLogTransport` that ships logs directly to Datadog's Logs API via HTTPS when enabled by env vars
+- Transport activates when `DATADOG_LOCAL_FORWARDING=true` and `DATADOG_API_KEY` is set — zero application code changes needed
+- Batches logs (flush every 5s or at 100 entries) with atomic buffer swap and best-effort flush on process exit
+- Auto-tags entries with `ddsource`, `service`, `env`, and `hostname` from DD_* and PROJECT_* env vars
+- Transport errors are silently swallowed and never affect stdout logging
+- Export `isDatadogForwardingEnabled()` and `_resetDatadogTransport()` for inspection and Lambda lifecycle
+- `init()` now resets the Datadog transport so env vars are re-read between Lambda invocations

package/release-notes/mcp/0.7.21.md

@@ -0,0 +1,10 @@
+---
+version: 0.7.21
+date: 2026-02-18
+summary: Add release notes for @jaypie/llm 1.2.10 and jaypie 1.2.13
+---
+
+## Changes
+
+- Add release notes for `@jaypie/llm` 1.2.10 (transient network error retry)
+- Add release notes for `jaypie` 1.2.13

package/release-notes/mcp/0.7.22.md

@@ -0,0 +1,10 @@
+---
+version: 0.7.22
+date: 2026-02-18
+summary: Add logger release notes for Datadog log forwarding transport
+---
+
+## Changes
+
+- Add release notes for `@jaypie/logger` 1.2.2
+- Add release notes for `jaypie` 1.2.14

package/skills/datadog.md

@@ -50,6 +50,37 @@ log.error("Payment failed", {
 });
 ```
 
+## Direct Log Forwarding (Non-Lambda)
+
+For local dev, eval runs, and CI where CloudWatch subscription filters aren't available, enable direct HTTP forwarding to Datadog's Logs API:
+
+```bash
+DATADOG_LOCAL_FORWARDING=true DATADOG_API_KEY=your-key npm run dev
+```
+
+This activates automatically in `@jaypie/logger` — zero code changes needed. Logs are batched (flush every 5s or 100 entries) and shipped via HTTPS to `http-intake.logs.{DD_SITE}/api/v2/logs`.
+
+### Environment Variables
+
+| Variable | Description | Default |
+|----------|-------------|---------|
+| `DATADOG_LOCAL_FORWARDING` | Enable forwarding (`true`/`false`) | `false` |
+| `DATADOG_API_KEY` | Datadog API key (required) | — |
+| `DD_SITE` | Datadog intake site | `datadoghq.com` |
+| `DD_SERVICE` / `PROJECT_SERVICE` | Service tag | `unknown` |
+| `DD_ENV` / `PROJECT_ENV` | Environment tag | `local` |
+| `DD_HOST` / `PROJECT_HOST` | Hostname tag | `os.hostname()` |
+
+### Inspection
+
+```typescript
+import { isDatadogForwardingEnabled } from "@jaypie/logger";
+
+if (isDatadogForwardingEnabled()) {
+  // Transport is active
+}
+```
+
 ## @jaypie/datadog Package
 
 The `@jaypie/datadog` package provides utilities:

package/skills/dynamodb.md

@@ -112,6 +112,34 @@ const table = new JaypieDynamoDb(this, "myApp", {
 
 ## Local Development
 
+Use docker-compose for local DynamoDB. The `@jaypie/dynamodb` MCP tool can generate a `docker-compose.yml` with custom ports.
+
+### Suggested package.json Scripts
+
+```json
+{
+  "scripts": {
+    "dynamo:init": "docker compose up -d && npm run dynamo:create-table",
+    "dynamo:create-table": "AWS_ACCESS_KEY_ID=local AWS_SECRET_ACCESS_KEY=local aws dynamodb create-table --table-name jaypie-local --attribute-definitions AttributeName=pk,AttributeType=S AttributeName=sk,AttributeType=S --key-schema AttributeName=pk,KeyType=HASH AttributeName=sk,KeyType=RANGE --billing-mode PAY_PER_REQUEST --endpoint-url http://127.0.0.1:9060 2>/dev/null || true",
+    "dynamo:remove": "docker compose down -v",
+    "dynamo:start": "docker compose up -d",
+    "dynamo:stop": "docker compose down"
+  }
+}
+```
+
+| Script | Description |
+|--------|-------------|
+| `dynamo:init` | Start containers and create the default table |
+| `dynamo:create-table` | Create the local table (idempotent) |
+| `dynamo:remove` | Stop containers and delete data volumes |
+| `dynamo:start` | Start containers (data persists) |
+| `dynamo:stop` | Stop containers (data persists) |
+
+Adjust the `--endpoint-url` port and `--table-name` to match your `docker-compose.yml`.
+
+### Manual Setup
+
 ```bash
 # Start local DynamoDB
 docker run -p 8000:8000 amazon/dynamodb-local