@jaypie/mcp 0.8.76 → 0.8.78

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.76#d4ee8b15"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.78#17b14d70"
     ;
 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.76",
+  "version": "0.8.78",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.67.md

@@ -0,0 +1,19 @@
+---
+version: 1.2.67
+date: 2026-06-20
+summary: Add serviceTag to JaypieDistribution for CloudFront metric and log attribution
+---
+
+## Changes
+
+- `JaypieDistribution` now accepts an optional `serviceTag` prop, parallel to
+  `roleTag` and matching `JaypieLambda`. When set:
+  - The distribution is tagged with `CDK.TAG.SERVICE`, so Datadog metrics carry
+    `service:<value>` instead of `service:N/A`.
+  - The created access-log and WAF-log buckets are tagged with the same value,
+    so the Datadog forwarder attributes their forwarded logs to the service
+    instead of the generic `cloudfront`/source default.
+- Omitting `serviceTag` preserves current behavior. External/imported log
+  buckets are not tagged (the construct does not own them).
+
+Issue: [#387](https://github.com/finlaysonstudio/jaypie/issues/387)

package/release-notes/constructs/1.2.68.md

@@ -0,0 +1,14 @@
+---
+version: 1.2.68
+date: 2026-06-21
+summary: Grant Datadog role trustedadvisor:ListRecommendations
+---
+
+## Changes
+
+- `extendDatadogRole` now adds `trustedadvisor:ListRecommendations` (Resource
+  `*`) to the custom Datadog policy, alongside the existing
+  `budgets:ViewBudget` and `logs:DescribeLogGroups` grants. This lets the
+  Datadog AWS integration role surface Trusted Advisor recommendations.
+- Applies wherever `extendDatadogRole` runs (e.g. `JaypieDatadogForwarder` with
+  role extension enabled and `CDK_ENV_DATADOG_ROLE_ARN` set).

package/release-notes/mcp/0.8.77.md

@@ -0,0 +1,13 @@
+---
+version: 0.8.77
+date: 2026-06-20
+summary: Lead LLM structured-output docs with natural schema syntax over Zod
+---
+
+## Changes
+
+- Reordered the `llm` and `models` skills to present Jaypie's natural schema
+  syntax first for structured output, with JSON Schema and Zod as alternatives.
+- Fixed the `llm` skill's `format` type signature to include `NaturalSchema`.
+- Added a natural-schema validation example to the `models` skill so its
+  Validation Patterns section is no longer Zod-only.

package/release-notes/mcp/0.8.78.md

@@ -0,0 +1,10 @@
+---
+version: 0.8.78
+date: 2026-06-21
+summary: Add constructs 1.2.68 release notes
+---
+
+## Changes
+
+- Added release notes for `@jaypie/constructs` 1.2.68 (Datadog role gains
+  `trustedadvisor:ListRecommendations`).

package/skills/api.md

@@ -60,4 +60,4 @@ Every response body is a JSON object with one top-level key:
 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)
+6. No other top-level keys (no `status`, `message`, `meta` at the root) except `metadata`

package/skills/llm.md

@@ -455,7 +455,7 @@ describe("LLM Integration", () => {
 interface LlmOperateOptions {
   data?: Record<string, any>;           // Placeholder substitution data
   fallback?: LlmFallbackConfig[] | false; // Fallback provider chain
-  format?: JsonObject | ZodType;        // Structured output schema
+  format?: NaturalSchema | JsonObject | ZodType; // Structured output schema (natural syntax preferred)
   history?: LlmHistory;                 // Previous conversation
   hooks?: LlmHooks;                     // Lifecycle callbacks
   instructions?: string;                // Additional instructions

package/skills/models.md

@@ -83,6 +83,27 @@ const createUser = fabricService({
 
 ## Validation Patterns
 
+Prefer Jaypie's natural schema syntax — it validates and types inline without a schema library. Reach for Zod only when you need refinements the natural form can't express.
+
+### Natural Schema
+
+The fabric `input` object is itself a natural schema: each field declares a `type` (a constructor like `String`/`Number`, or a `const` tuple of allowed values), `required`, and `description`. Input is validated and typed before `service` runs.
+
+```typescript
+const createUser = fabricService({
+  alias: "user_create",
+  input: {
+    email: { type: String, required: true, description: "User email address" },
+    name: { type: String, required: true, description: "User display name" },
+    role: { type: ["user", "admin"] as const, required: false },
+  },
+  service: async ({ email, name, role }) => {
+    // email, name, role are validated and typed here
+    return createUserInDatabase({ email, name, role: role || "user" });
+  },
+});
+```
+
 ### Zod Schemas
 
 ```typescript