@jaypie/mcp 0.7.21 → 0.7.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.7.21#ca417bad"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.23#49c71f6f"
     ;
 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.21",
+  "version": "0.7.23",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.31.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.31
+date: 2026-02-18
+summary: Add Cache-Control and Cross-Origin-Embedder-Policy security headers to JaypieDistribution
+---
+
+# @jaypie/constructs 1.2.31
+
+## Fixes
+
+- **JaypieDistribution**: Added `Cache-Control` (`no-store, no-cache, must-revalidate, proxy-revalidate`) and `Cross-Origin-Embedder-Policy` (`unsafe-none`) to the default security response headers, resolving ZAP baseline scan warnings [90004], [10015], and [10049].

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/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.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/cdk.md

@@ -173,12 +173,14 @@ new JaypieNextJs(this, "App", {
 
 `JaypieDistribution` ships with default security response headers via a `ResponseHeadersPolicy` (analogous to `helmet` for Express):
 
+- Cache-Control (no-store, no-cache, must-revalidate, proxy-revalidate)
 - HSTS (2-year max-age, includeSubDomains, preload)
 - X-Content-Type-Options (nosniff)
 - X-Frame-Options (DENY)
 - Referrer-Policy (strict-origin-when-cross-origin)
 - Content-Security-Policy (conservative defaults)
 - Permissions-Policy (camera, microphone, geolocation, payment disabled)
+- Cross-Origin-Embedder-Policy (unsafe-none)
 - Cross-Origin-Opener-Policy (same-origin)
 - Cross-Origin-Resource-Policy (same-origin)
 - Server header removed

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: