@aotter/mantle 0.0.11-alpha.57 → 0.0.11-alpha.59

package/docs/adapter-guide.md

@@ -93,6 +93,26 @@ passed through `CmsConfig.templates`, and a `publicPathResolver` passed through
 consumer; mounting every Schema automatically is not, because some collections
 are private even when they contain a slug.
 
+### HTTP cache contract
+
+The Cloudflare adapter is private by default. Consumers must export
+`createOAuthProvider(...)` as the Worker's top-level handler so its final
+response policy covers admin, auth, API, OAuth, MCP, redirects, and errors.
+Those responses receive `Cache-Control: private, no-store`; Cloudflare-specific
+CDN cache overrides are removed.
+
+`mountPublicRoutes(...)` opts only successful pre-rendered HTML, markdown,
+`llms.txt`, and sitemap responses into the shared cache with
+`Cache-Control: public, max-age=0, s-maxage=300`. The top-level policy preserves
+that opt-in only for anonymous `GET`/`HEAD` responses with status 200, explicit
+shared freshness, no request `Cookie` or `Authorization`, and no response
+`Set-Cookie`. It also varies public responses by `Cookie` and `Authorization`.
+
+A starter-level Workers Cache may therefore store only responses that still
+meet that exact public contract. It must bypass credentialed/cookie requests
+and must never infer cacheability from a URL prefix. Cache entries remain
+version-local; cross-version caching is outside this contract.
+
 Minimum auth/MCP behavior:
 
 - Provide Better Auth-compatible sign-in/session routes for the platform.
@@ -124,6 +144,7 @@ Minimum auth/MCP behavior:
 - [ ] Normalize session/OAuth and any consumer credential seam into
       `HandlerContext.auth`; never put raw credentials in runtime context.
 - [ ] Mount `/mcp/staff` and `/mcp` via the platform's OAuth provider lib (Cloudflare adapter uses `@cloudflare/workers-oauth-provider` at top level). Enforce staff D1 role inside the apiHandler.
+- [ ] Preserve the HTTP cache contract: private by default; explicit anonymous 200 `GET`/`HEAD` public opt-in only.
 - [ ] Prove one guarded target has identical REST/MCP outcomes, including
       mutable revocation on the next call.
 - [ ] Add optional `MediaStorage` or `DeferredHookDispatcher` only when the adapter supports those features.

package/docs/design-atoms.md

@@ -171,7 +171,8 @@ entry's state machine.
   with `CONFLICT`). The admin console renders these collections flat —
   no draft/published filter buckets, no publish controls. Declare it
   on any Schema whose rows a human should *inspect and correct*, never
-  *stage and publish*.
+  *stage and publish*. Staff MCP emits `create_record_<schema>` and
+  `update_record_<schema>` for these Schemas instead of draft tools.
 
 The modes are **per-Schema and mix freely** within a site. There is no
 site-wide lifecycle setting; one Schema can be `simple` while another

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aotter/mantle",
-  "version": "0.0.11-alpha.57",
+  "version": "0.0.11-alpha.59",
   "description": "Umbrella entry for @aotter/mantle. Adopters install this one package and import from subpaths: /spec, /runtime, /cloudflare, /admin-ui. Sub-packages remain individually installable on npm for tooling / alt-adapter authors. The Netlify adapter ships as a private workspace stub in v0.1 — its subpath will be added when the impl lands in v0.2.",
   "license": "Apache-2.0",
   "homepage": "https://mantle.tools/",
@@ -47,10 +47,10 @@
     "README.md"
   ],
   "dependencies": {
-    "@aotter/mantle-admin-ui": "0.0.11-alpha.57",
-    "@aotter/mantle-cloudflare": "0.0.11-alpha.57",
-    "@aotter/mantle-spec": "0.0.11-alpha.57",
-    "@aotter/mantle-runtime": "0.0.11-alpha.57"
+    "@aotter/mantle-admin-ui": "0.0.11-alpha.59",
+    "@aotter/mantle-runtime": "0.0.11-alpha.59",
+    "@aotter/mantle-cloudflare": "0.0.11-alpha.59",
+    "@aotter/mantle-spec": "0.0.11-alpha.59"
   },
   "peerDependencies": {
     "@cloudflare/workers-oauth-provider": "^0.8.0",

package/skills/develop/SKILL.md

@@ -82,6 +82,12 @@ the atoms cannot express the behavior.
   `Procedure.spec.input` before the seed/form. Keep public mutation inputs
   `additionalProperties: false`; otherwise JSON Schema's default may strip an
   undeclared field while returning success.
+- Use `lifecycle: none` for submissions, inquiries, orders, and other
+  Procedure-created operational records that staff inspect or correct. Reserve
+  `simple` for content a person stages and publishes.
+- When a form's fixed option values change, update the stored Schema and public
+  Procedure input `enum` together. Keep translated labels in the page seed;
+  Admin and Staff MCP derive their typed controls from the manifest values.
 - For a new section display property, update the content type and the `page`
   Schema's `sections[].properties`; an undeclared property has no
   runtime-backed Admin or Staff MCP path.

package/skills/extend/SKILL.md

@@ -146,7 +146,10 @@ pnpm view-smoke        # 10 cases against /api/views/*
 pnpm mcp-smoke         # 12 cases against /mcp
 ```
 
-If you added a new MCP-relevant Schema, the per-collection authoring tools (`create_draft_<segment>`, `update_draft_<segment>`) auto-emit; verify with `tools/list`.
+If you added a new MCP-relevant Schema, per-collection authoring tools auto-emit:
+`create_draft_<segment>` / `update_draft_<segment>` for content lifecycles,
+or `create_record_<segment>` / `update_record_<segment>` for
+`lifecycle: none`. Verify the actual surface with `tools/list`.
 
 ## API and MCP authorization
 

package/skills/theme/SKILL.md

@@ -33,8 +33,9 @@ tokens, or recipes, but the skill contract is Core-owned.
 ## Work
 
 - Use existing tokens, CSS, components, and installed dependencies first.
-- When the generated section type exposes `showImage`, set it to `false` for
-  a text-only hero/content block. Put custom media in a project-owned section.
+- For a standard hero image, set the section's `image: { src, alt }`; use
+  `showImage: false` for text-only hero/content blocks. Put non-image media in
+  a project-owned section.
 - Keep accessibility basics: semantic HTML, focus states, contrast, and
   keyboard reachability. Against a non-default background, check
   `--foreground-muted` and `--primary`, not only `--foreground`; keep normal