@jaypie/mcp 0.8.14 → 0.8.16

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.14#03cb149b"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.16#67e5307b"
     ;
 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.14",
+  "version": "0.8.16",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.40.md

@@ -0,0 +1,11 @@
+---
+version: 1.2.40
+date: 2026-04-05
+summary: Add managedRuleOverrides to JaypieWafConfig for overriding specific WAF rule actions
+---
+
+## Changes
+
+- Add `managedRuleOverrides` prop to `JaypieWafConfig` for overriding actions on specific rules within AWS managed rule groups
+- Enables downgrading rules like `SizeRestrictions_BODY` to count mode so large webhook payloads (e.g., GitHub) are not blocked
+- Closes #272

package/skills/cdk.md

@@ -341,6 +341,18 @@ new JaypieDistribution(this, "Dist", {
   handler,
   waf: { logBucket: myWafBucket },
 });
+
+// Override specific managed rule actions (e.g., allow large request bodies)
+new JaypieDistribution(this, "Dist", {
+  handler,
+  waf: {
+    managedRuleOverrides: {
+      AWSManagedRulesCommonRuleSet: [
+        { name: "SizeRestrictions_BODY", actionToUse: { count: {} } },
+      ],
+    },
+  },
+});
 ```
 
 Cost: $5/month per WebACL + $1/month per rule + $0.60 per million requests. Use `waf: false` to opt out.

package/skills/dynamodb.md

@@ -1,6 +1,6 @@
 ---
 description: DynamoDB runtime package, key design, entity operations, and queries
-related: apikey, aws, cdk, models
+related: apikey, aws, cdk, models, vocabulary
 ---
 
 # DynamoDB Patterns
@@ -220,7 +220,7 @@ All GSIs use `sequence` (Number) as the sort key for chronological ordering.
 | `indexScope` | `{scope}#{model}` | List entities by parent | You need hierarchical queries |
 | `indexAlias` | `{scope}#{model}#{alias}` | Human-friendly slug lookup | You need slug-based lookups |
 | `indexCategory` | `{scope}#{model}#{category}` | Category filtering | You need to filter by category |
-| `indexType` | `{scope}#{model}#{type}` | Type filtering | You need to filter by type |
+| `indexType` | `{scope}#{model}#{type}` | Type filtering | You need to filter by type (note: vocabulary discourages `type` in favor of `category`; `indexType` is retained as a legacy GSI pattern) |
 | `indexXid` | `{scope}#{model}#{xid}` | External ID lookup | You need cross-system ID lookups |
 
 ### Query Functions

package/skills/vocabulary.md

@@ -1,6 +1,6 @@
 ---
 description: Definitions, naming conventions, ontology, and pedantry
-related: fabric, models, services
+related: dynamodb, fabric, models, services
 ---
 
 # Vocabulary
@@ -49,7 +49,7 @@ Arguably composition, identity, instance, and relation would form a more complet
 - name: most common way to clearly reference the entity
 - related: array of id strings, complex "{model}#{id}" strings, or `{ id, model }` objects
 - scope: organizes entities, usually a reference to a parent entity
-- sequence: computed scalar, usually normalized createdAt or name
+- sequence: computed scalar, usually `Date.now()` for chronological ordering
 - state: mutable data the entity tracks
 - status: canceled, complete, error, pending, processing, queued, sending
 - updatedAt: timestamp
@@ -66,7 +66,7 @@ Arguably composition, identity, instance, and relation would form a more complet
 - key => alias; make api or secret keys explicit in name
 - ou => scope
 - output => state
-- type => category, tags; reserved
+- type => category, tags; reserved (exception: `indexType` GSI exists in DynamoDB as a legacy pattern; prefer `category` for new work)
 
 Avoid words defined elsewhere (services, terminology)