@ampless/backend 1.0.0-beta.91 → 1.0.0-beta.93

package/README.ja.md

@@ -64,7 +64,7 @@ amplessAuthConfig({                                            // カスタム
 amplessAuthConfig({ postConfirmation, webAuthn: false })      // パスワードのみのサインイン
 ```
 
-Amplify Hosting パイプラインビルドでは、テンプレートが `cms.config.ts` の `site.url` から `resolveWebAuthn({ override, siteUrl, isPipeline })` を通じて Relying Party ID を自動導出します。最も一般的なケースでは手動設定不要です。`ampx sandbox` では RP ID は `localhost` のまま（Amplify が自動解決）です。管理画面を `site.url` と**異なるサブドメイン**で配信している場合は、`amplify/auth/resource.custom.ts` でオペレーターがアクセスする bare domain を `relyingPartyId` に固定してください。パスキー登録後に RP ID を変更すると、登録済みの認証情報がすべて無効化されます。[docs/passkeys.ja.md](https://github.com/heavymoons/ampless/blob/main/docs/passkeys.ja.md) を参照してください。
+Amplify Hosting パイプラインビルドでは、テンプレートが `cms.config.ts` の `site.url` から `resolveWebAuthn({ override, siteUrl, isPipeline })` を通じて Relying Party ID を自動導出します。最も一般的なケースでは手動設定不要です。`ampx sandbox` では RP ID は `localhost` のまま（Amplify が自動解決）です。管理画面を `site.url` と**異なるサブドメイン**で配信している場合は、`amplify/auth/resource.custom.ts` でオペレーターがアクセスする bare domain を `relyingPartyId` に固定してください。パスキー登録後に RP ID を変更すると、登録済みの認証情報がすべて無効化されます。[passkeys.ja](https://github.com/heavymoons/ampless/wiki/passkeys.ja) を参照してください。
 
 ### `amplify/data/resource.ts`
 

package/README.md

@@ -64,7 +64,7 @@ amplessAuthConfig({                                            // pin the Relyin
 amplessAuthConfig({ postConfirmation, webAuthn: false })      // password-only sign-in
 ```
 
-In Amplify Hosting pipeline builds the template auto-derives the Relying Party ID from `site.url` in `cms.config.ts` via `resolveWebAuthn({ override, siteUrl, isPipeline })` — no manual configuration needed for the common case. In `ampx sandbox` the RP ID stays `localhost` (auto-resolved by Amplify). If the admin is served from a **different subdomain** than `site.url`, pin `relyingPartyId` to the bare domain operators visit in `amplify/auth/resource.custom.ts`. Changing the RP ID after passkeys exist invalidates every registered credential. See [docs/passkeys.md](https://github.com/heavymoons/ampless/blob/main/docs/passkeys.md).
+In Amplify Hosting pipeline builds the template auto-derives the Relying Party ID from `site.url` in `cms.config.ts` via `resolveWebAuthn({ override, siteUrl, isPipeline })` — no manual configuration needed for the common case. In `ampx sandbox` the RP ID stays `localhost` (auto-resolved by Amplify). If the admin is served from a **different subdomain** than `site.url`, pin `relyingPartyId` to the bare domain operators visit in `amplify/auth/resource.custom.ts`. Changing the RP ID after passkeys exist invalidates every registered credential. See [passkeys](https://github.com/heavymoons/ampless/wiki/passkeys).
 
 ### `amplify/data/resource.ts`
 

package/dist/events/processor-trusted.js

@@ -334,7 +334,7 @@ function createProcessorTrustedHandler(opts) {
       for (const plugin of privilegedHookedPlugins) {
         if (plugin.hooks?.[parsed.type]) {
           console.warn(
-            `[trusted-processor] privileged plugin "${plugin.name}" declares ${parsed.type} hook but no privileged Lambda is provisioned yet \u2014 hook will not execute. See docs/architecture/08-plugin-architecture.md.`
+            `[trusted-processor] privileged plugin "${plugin.name}" declares ${parsed.type} hook but no privileged Lambda is provisioned yet \u2014 hook will not execute. See https://github.com/heavymoons/ampless/wiki/architecture-08-plugin-architecture.`
           );
         }
       }

package/dist/events/processor-untrusted.js

@@ -30,7 +30,7 @@ function createProcessorUntrustedHandler(opts) {
       for (const plugin of privilegedHookedPlugins) {
         if (plugin.hooks?.[parsed.type]) {
           console.warn(
-            `[untrusted-processor] privileged plugin "${plugin.name}" declares ${parsed.type} hook but no privileged Lambda is provisioned yet \u2014 hook will not execute. See docs/architecture/08-plugin-architecture.md.`
+            `[untrusted-processor] privileged plugin "${plugin.name}" declares ${parsed.type} hook but no privileged Lambda is provisioned yet \u2014 hook will not execute. See https://github.com/heavymoons/ampless/wiki/architecture-08-plugin-architecture.`
           );
         }
       }

package/dist/functions/mcp-handler.js

@@ -857,7 +857,7 @@ function getSchema() {
     ],
     formats: ["tiptap", "markdown", "html", "static"],
     notes: {
-      editorTrust: 'editor stores arbitrary HTML/JS verbatim \u2014 same trust shape as WordPress unfiltered_html capability. See docs/architecture/04-access-layer-mcp.md \xA7"editor \u306E\u4FE1\u983C\u30E2\u30C7\u30EB".',
+      editorTrust: 'editor stores arbitrary HTML/JS verbatim \u2014 same trust shape as WordPress unfiltered_html capability. See https://github.com/heavymoons/ampless/wiki/architecture-04-access-layer-mcp \xA7"editor \u306E\u4FE1\u983C\u30E2\u30C7\u30EB".',
       tiptapBody: 'When format=tiptap, body is the tiptap document JSON: { type: "doc", content: [...] }. The renderer expects this shape.',
       noLayout: "metadata.no_layout=true serves the post as bare HTML with no theme chrome \u2014 middleware rewrites the public /<slug> request to the internal bare-HTML handler, which renders the body verbatim with no wrapping <html>/<head>/layout. Use this for landing pages, embeds, or any post whose body is a full HTML document. Only meaningful with format=html (the other formats need the theme renderer).",
       staticFormat: "A fourth format value `static` exists on the underlying data model for posts whose body is a JSON manifest pointing to a pre-uploaded HTML/CSS/JS bundle in S3 at public/static/<slug>/. Public URL pattern: /<slug>/ for the entrypoint and /<slug>/<file> for every bundle file (middleware rewrites both to an internal static-bundle handler). Static posts are created/edited through the dedicated tools `upload_static_bundle` (zip in one shot), `upload_static_file` / `delete_static_file` (incremental per-file ops), and `commit_static_post` (rebuild the manifest from the current S3 prefix). `create_post` / `update_post` intentionally do NOT accept format=static \u2014 the bundle tools are the only supported entry point so the Post manifest stays in sync with the S3 prefix.",

package/dist/index.js

@@ -482,7 +482,7 @@ function amplessSchemaModels(a, opts = {}) {
     // Lambda. The Lambda receives the plaintext, reads the encryption
     // key from `process.env.PLUGIN_SECRET_ENCRYPTION_KEY` (injected by
     // CDK at deploy time from `amplify/secrets/encryption-key.ts` — see
-    // Phase 6a v2.2 in docs/architecture/08-plugin-architecture.md),
+    // Phase 6a v2.2 in https://github.com/heavymoons/ampless/wiki/architecture-08-plugin-architecture),
     // and performs the DDB PutItem using its own IAM role. Ciphertext
     // never flows back to the browser.
     //
@@ -530,7 +530,7 @@ function amplessSchemaModels(a, opts = {}) {
       // constant). Even if an AWS account operator reads this column
       // via the DDB Console they only see ciphertext — the key lives
       // outside DynamoDB. The honest threat model is documented in
-      // docs/architecture/08-plugin-architecture.md: defeated for
+      // https://github.com/heavymoons/ampless/wiki/architecture-08-plugin-architecture: defeated for
       // DDB-only browsing, NOT defeated for anyone with source repo
       // / deploy artifact access, NOT defeated for a malicious
       // trusted plugin co-located in the same Lambda.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ampless/backend",
-  "version": "1.0.0-beta.91",
+  "version": "1.0.0-beta.93",
   "description": "Amplify Gen 2 backend factories for ampless: auth, data, storage, event processors, API key renewer",
   "license": "MIT",
   "type": "module",
@@ -69,8 +69,8 @@
     "@smithy/protocol-http": "^5.4.4",
     "@smithy/signature-v4": "^5.4.4",
     "fflate": "^0.8.3",
-    "@ampless/mcp-server": "1.0.0-beta.68",
-    "ampless": "1.0.0-beta.61"
+    "@ampless/mcp-server": "1.0.0-beta.70",
+    "ampless": "1.0.0-beta.63"
   },
   "peerDependencies": {
     "@aws-amplify/backend": "^1.19.0",