@ampless/backend 1.0.0-alpha.20 → 1.0.0-alpha.21

package/dist/functions/mcp-handler.d.ts

@@ -1,10 +1,10 @@
 /**
- * MCP HTTP endpoint Lambda. Phase 5: Bearer validation + JSON-RPC 2.0
- * tool dispatch over AppSync IAM auth, including `upload_media`.
+ * MCP HTTP endpoint Lambda. Bearer validation + JSON-RPC 2.0 tool
+ * dispatch over AppSync IAM auth, including `upload_media`.
  *
  *   1. Reads KvStore directly (PK = 'mcp-tokens', SK = SHA-256 hex)
- *      to validate `Authorization: Bearer amk_...`. Same narrow IAM
- *      grant as Phase 3 (`dynamodb:GetItem` on the KvStore table).
+ *      to validate `Authorization: Bearer amk_...`. The Lambda has a
+ *      narrow IAM grant: `dynamodb:GetItem` on the KvStore table.
  *   2. Parses the incoming JSON-RPC envelope by hand (no MCP SDK
  *      stdio transport in a Lambda runtime — overkill for the three
  *      verbs we actually need).

package/dist/index.d.ts

@@ -18,10 +18,8 @@ interface DefineAmplessBackendOpts {
 }
 type AmplessBackend = any;
 /**
- * The end-to-end ampless backend wiring: identical to the 251-line
- * `backend.ts` that used to live in `templates/_shared/amplify/`,
- * but parameterised on the resource objects so users only have to
- * compose the imports.
+ * The end-to-end ampless backend wiring, parameterised on the resource
+ * objects so users only have to compose the imports.
  *
  * What it does, in order:
  *   1. Calls `defineBackend` with every Ampless resource.
@@ -201,8 +199,8 @@ interface AmplessSchemaAuthorizationOpts {
      * destructure `resource` out of their `allow` parameter), so this
      * grant applies broadly — every model the Lambda calls is reachable.
      * That's wider than strictly necessary; the MCP tools' GraphQL
-     * operations narrow the effective surface to Post / PostTag in
-     * Phase 4 and Media in Phase 5.
+     * operations narrow the effective surface to Post / PostTag for
+     * content tools and Media for `upload_media`.
      *
      * Typed as `unknown` for the same reason `userAdminFunction` /
      * `mcpHandlerFunction` are in other helpers — `defineFunction`'s

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ampless/backend",
-  "version": "1.0.0-alpha.20",
+  "version": "1.0.0-alpha.21",
   "description": "Amplify Gen 2 backend factories for ampless: auth, data, storage, event processors, API key renewer",
   "license": "MIT",
   "type": "module",
@@ -65,8 +65,8 @@
     "@smithy/protocol-http": "^5.3.0",
     "@smithy/signature-v4": "^5.4.0",
     "fflate": "^0.8.2",
-    "ampless": "1.0.0-alpha.10",
-    "@ampless/mcp-server": "1.0.0-alpha.11"
+    "ampless": "1.0.0-alpha.11",
+    "@ampless/mcp-server": "1.0.0-alpha.12"
   },
   "peerDependencies": {
     "@aws-amplify/backend": "^1",