@jaypie/mcp 0.8.75 → 0.8.77

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.75#7dfeb98d"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.77#1fb6d6fa"
     ;
 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.75",
+  "version": "0.8.77",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.66.md

@@ -0,0 +1,18 @@
+---
+version: 1.2.66
+date: 2026-06-20
+summary: Forward DD_VERSION to the Lambda environment for Datadog version tagging
+---
+
+## Changes
+
+- `jaypieLambdaEnv` now passes `DD_VERSION` through to the Lambda environment
+  when present in `process.env`, alongside the other allowlisted vars. This lets
+  projects tag telemetry with a version derived independently of
+  `PROJECT_VERSION` (e.g. from the latest git tag), which `dd-trace` reads at
+  runtime.
+- `addDatadogLayers` now falls back the `DatadogLambda` `version` to
+  `process.env.DD_VERSION || process.env.PROJECT_VERSION`, keeping the version
+  tag consistent with the env var.
+
+Issue: [#384](https://github.com/finlaysonstudio/jaypie/issues/384)

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/mcp/0.8.76.md

@@ -0,0 +1,15 @@
+---
+version: 0.8.76
+date: 2026-06-20
+summary: Correct the mocks skill to document the real @jaypie/testkit/mock pattern
+---
+
+## Changes
+
+- Rewrote the `mocks` skill, which documented a non-existent
+  `mockJaypie(vi)` / `mockLogger(vi)` / `mockAws(vi)` API. The working pattern
+  is `vi.mock("jaypie", async () => await import("@jaypie/testkit/mock"))`,
+  returning the flat mock namespace directly. Sub-package and export-verification
+  examples updated to match.
+
+Issue: [#385](https://github.com/finlaysonstudio/jaypie/issues/385)

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/testkit/1.2.45.md

@@ -0,0 +1,17 @@
+---
+version: 1.2.45
+date: 2026-06-20
+summary: Drop the deprecated mongoose mock that broke @jaypie/testkit/mock at load time
+---
+
+## Removed
+
+- **Mongoose mock dropped from the `./mock` umbrella.** `@jaypie/testkit/mock`
+  statically imported `@jaypie/mongoose` (a deprecated, undeclared phantom
+  dependency), which threw `Cannot find package '@jaypie/mongoose'` at module
+  load in any project without mongoose installed. The mock is removed entirely;
+  `jaypie` never re-exported mongoose. The `connect`, `connectFromSecretEnv`,
+  `disconnect`, and `mongoose` exports are no longer available from
+  `@jaypie/testkit/mock`.
+
+Issue: [#385](https://github.com/finlaysonstudio/jaypie/issues/385)

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

@@ -22,11 +22,14 @@ In your test setup file:
 import { vi } from "vitest";
 
 vi.mock("jaypie", async () => {
-  const { mockJaypie } = await import("@jaypie/testkit");
-  return mockJaypie(vi);
+  const testkit = await import("@jaypie/testkit/mock");
+  return testkit;
 });
 ```
 
+`@jaypie/testkit/mock` re-exports a vitest mock for every `jaypie` export as a
+flat namespace, so returning it directly mocks the whole package.
+
 Configure in vitest.config.ts:
 
 ```typescript
@@ -43,35 +46,25 @@ export default defineConfig({
 
 ```typescript
 vi.mock("jaypie", async () => {
-  const { mockJaypie } = await import("@jaypie/testkit");
-  return mockJaypie(vi);
+  const testkit = await import("@jaypie/testkit/mock");
+  return testkit;
 });
 
 // Mocked: log, getSecret, sendMessage, etc.
 ```
 
-### Logger
-
-```typescript
-vi.mock("@jaypie/logger", async () => {
-  const { mockLogger } = await import("@jaypie/testkit");
-  return mockLogger(vi);
-});
-```
+### Sub-Packages
 
-### AWS
+To mock an individual `@jaypie/*` package, return the relevant mocks from the
+same flat `@jaypie/testkit/mock` namespace:
 
 ```typescript
-vi.mock("@jaypie/aws", async () => {
-  const { mockAws } = await import("@jaypie/testkit");
-  return mockAws(vi);
+vi.mock("@jaypie/express", async () => {
+  const testkit = await import("@jaypie/testkit/mock");
+  return { expressHandler: testkit.expressHandler };
 });
 ```
 
-### Legacy Mocks
-
-For legacy packages, see `skill("legacy")`.
-
 ## Using Mocks in Tests
 
 ### Verify Logging
@@ -158,20 +151,20 @@ afterEach(() => {
 
 ## Export Verification
 
-When adding exports to packages, update testkit:
+When adding exports to a Jaypie package, add a matching mock to testkit so the
+auto-mock stays complete:
 
 ```typescript
-// packages/testkit/src/mocks/mockJaypie.ts
-export function mockJaypie(vi) {
-  return {
-    log: mockLog(vi),
-    getSecret: vi.fn().mockResolvedValue("mock"),
-    // Add new exports here
-    newFunction: vi.fn(),
-  };
-}
+// packages/testkit/src/mock/<package>.ts
+import { createMockFunction } from "./utils";
+
+export const newFunction = createMockFunction((x) => x);
 ```
 
+Then re-export it from `src/mock/index.ts` (named export and default object) and
+bump the testkit patch version. Missing mocks surface as failures in testkit's
+`mock/__tests__/index.spec.ts` "all exports from original" check.
+
 ## See Also
 
 - **`skill("errors")`** - Error types used in mock assertions

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