@jaypie/mcp 0.8.61 → 0.8.63

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.61#9515fd89"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.63#4149aed3"
     ;
 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.61",
+  "version": "0.8.63",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/dynamodb/0.6.3.md

@@ -0,0 +1,34 @@
+---
+version: 0.6.3
+date: 2026-05-31
+summary: transactWriteEntities supports conditional writes (conditionalCreate / condition) and throws ConflictError on a conditional-check failure
+---
+
+## Added
+
+- **Conditional `transactWriteEntities`**. The transaction writer now accepts
+  two optional params so callers can express the canonical DynamoDB
+  uniqueness / atomic-create pattern in a single transaction:
+
+  - `conditionalCreate: true` guards **every** `Put` with
+    `attribute_not_exists(id)` — mirroring `createEntity` for the multi-item
+    case (e.g. writing an entity **and** its uniqueness-sentinel row atomically).
+  - `condition: string` supplies a custom `ConditionExpression` applied to
+    every `Put` (takes precedence over `conditionalCreate`).
+
+  ```ts
+  await transactWriteEntities({
+    conditionalCreate: true, // attribute_not_exists(id) on every Put
+    entities: [organization, aliasLock],
+  });
+  ```
+
+- **Distinct conflict signal**. When a conditional write causes DynamoDB to
+  cancel the transaction (`ConditionalCheckFailed`), `transactWriteEntities`
+  now throws a `ConflictError` (409, from `@jaypie/errors`) instead of a raw
+  `TransactionCanceledException`, so callers can map the conflict to a 4xx.
+  Non-conditional cancellations propagate unchanged.
+
+The default (no condition) remains an unconditional write — fully additive.
+
+Issue: [#357](https://github.com/finlaysonstudio/jaypie/issues/357)

package/release-notes/errors/1.2.2.md

@@ -0,0 +1,20 @@
+---
+version: 1.2.2
+date: 2026-05-31
+summary: Add ConflictError (409) for uniqueness / state-conflict responses
+---
+
+## Added
+
+- **`ConflictError` (409)**. Jaypie previously had no 409, so callers had to
+  reach for a generic `BadRequestError` (400) for uniqueness violations and
+  other state conflicts. `ConflictError` fills the gap and is wired into
+  `jaypieErrorFromStatus(409)`.
+
+  ```ts
+  import { ConflictError } from "jaypie";
+
+  throw new ConflictError("Alias already claimed");
+  ```
+
+Issue: [#357](https://github.com/finlaysonstudio/jaypie/issues/357)

package/release-notes/jaypie/1.2.49.md

@@ -0,0 +1,12 @@
+---
+version: 1.2.49
+date: 2026-05-31
+summary: Re-export the new ConflictError (409) via the @jaypie/errors 1.2.2 bump
+---
+
+## Changed
+
+- Bumped `@jaypie/errors` to `^1.2.2`, so `ConflictError` (409) is now
+  available from the `jaypie` entrypoint.
+
+Issue: [#357](https://github.com/finlaysonstudio/jaypie/issues/357)

package/release-notes/mcp/0.8.62.md

@@ -0,0 +1,14 @@
+---
+version: 0.8.62
+date: 2026-05-31
+summary: Document conditional transactWriteEntities and ConflictError in the dynamodb and errors skills
+---
+
+## Changed
+
+- **`dynamodb` skill** documents `transactWriteEntities`' new
+  `conditionalCreate` / `condition` params and the atomic conditional-write
+  pattern.
+- **`errors` skill** lists the new `ConflictError` (409).
+
+Issue: [#357](https://github.com/finlaysonstudio/jaypie/issues/357)

package/release-notes/mcp/0.8.63.md

@@ -0,0 +1,15 @@
+---
+version: 0.8.63
+date: 2026-05-31
+summary: Fix the dynamodb skill's Atomic Conditional Writes example to import ConflictError from jaypie, not @jaypie/dynamodb
+---
+
+## Fixed
+
+- **`dynamodb` skill**. The "Atomic Conditional Writes" example imported
+  `ConflictError` from `@jaypie/dynamodb`, which does not re-export it — the
+  import threw at runtime. `ConflictError` lives in `@jaypie/errors` (and the
+  `jaypie` umbrella); the example now imports it from `jaypie` while keeping
+  `transactWriteEntities` from `@jaypie/dynamodb`.
+
+Issue: [#357](https://github.com/finlaysonstudio/jaypie/issues/357)

package/release-notes/testkit/1.2.40.md

@@ -0,0 +1,18 @@
+---
+version: 1.2.40
+date: 2026-05-31
+summary: Mock the new ConflictError and the conditional transactWriteEntities signature
+---
+
+## Added
+
+- **`ConflictError` mock**. Re-exported from `@jaypie/testkit/mock` and mapped
+  in the mocked `errorFromStatusCode(409)`, matching the new
+  `@jaypie/errors` export.
+
+## Changed
+
+- **`transactWriteEntities` mock signature** now accepts the optional
+  `conditionalCreate` and `condition` params added in `@jaypie/dynamodb` 0.6.3.
+
+Issue: [#357](https://github.com/finlaysonstudio/jaypie/issues/357)

package/skills/dynamodb.md

@@ -175,6 +175,30 @@ await destroyEntity({ id: "abc-123" });
 | `deleteEntity({ id })` | Soft delete (`deletedAt`, `#deleted` suffix on GSI pk) |
 | `archiveEntity({ id })` | Archive (`archivedAt`, `#archived` suffix on GSI pk) |
 | `destroyEntity({ id })` | Hard delete (permanent) |
+| `transactWriteEntities({ entities, conditionalCreate?, condition? })` | Write many entities atomically; `conditionalCreate: true` guards every `Put` with `attribute_not_exists(id)` (`condition` for a custom expression), throwing `ConflictError` (409) when a conditional check fails |
+
+### Atomic Conditional Writes
+
+Use `conditionalCreate` to write an entity **and** a uniqueness-sentinel row in a single transaction -- both commit or neither does:
+
+`ConflictError` is thrown from `@jaypie/errors` (re-exported by the `jaypie` umbrella); `@jaypie/dynamodb` does not re-export it.
+
+```typescript
+import { ConflictError } from "jaypie"; // or "@jaypie/errors"
+import { transactWriteEntities } from "@jaypie/dynamodb";
+
+try {
+  await transactWriteEntities({
+    conditionalCreate: true, // attribute_not_exists(id) on every Put
+    entities: [organization, aliasLock],
+  });
+} catch (error) {
+  if (error instanceof ConflictError) {
+    // alias already claimed -- map to 409
+  }
+  throw error;
+}
+```
 
 ### Scope and Hierarchy
 

package/skills/errors.md

@@ -29,6 +29,7 @@ throw new ConfigurationError("Missing API key");
 | UnauthorizedError | 401 | Authentication required |
 | ForbiddenError | 403 | Authenticated but not permitted |
 | NotFoundError | 404 | Resource doesn't exist |
+| ConflictError | 409 | Request conflicts with current state (e.g. uniqueness violation) |
 | ConfigurationError | 500 | Missing or invalid config |
 | InternalError | 500 | Unexpected server error |