minutework 0.1.16 → 0.1.18

package/assets/claude-local/CLAUDE.md.template

@@ -11,41 +11,13 @@ private authenticated workspace under `/app`.
 
 If this workspace's exported guidance looks stale or a newly added skill is
 missing, run `minutework workspace sync-assets` from the workspace root. See
-`skills/workspace-guidance-refresh.md` for the managed refresh flow.
-
-## Read These First
-
-Read these exported skills before making MinuteWork-specific architecture
-decisions from a generated workspace:
-
-- `skills/generated-workspace-architecture.md`
-- `skills/workspace-guidance-refresh.md` when exported guidance, `CLAUDE.md`, or
-  `skills/` may be stale
-- `skills/app-pack-authoring.md` when deciding the shipped product shape or
-  choosing between `tenant-app` and `sidecar` inside an app pack
-- `skills/shell-architecture.md` when the request touches member-facing UI,
-  operator workflows, threads, channels, cards, dashboards, approvals, or "do
-  we need a separate frontend?" questions
-- `skills/runtime-capability-inventory.md`
-- `skills/layering-and-import-modes.md`
-- `skills/schema-engine.md` when the request adds schema, forms, submissions, or
-  other runtime data structures
-- `skills/published-web-and-mw-core-site.md` when the request touches public
-  sites, intake forms, published-web, or anonymous/live delivery
-- `skills/contract-first-public-intake.md` when the request touches public
-  forms, guest continuity, anonymous intake, or claim-after-auth flows
-- `skills/sidecar-generation.md` when the request clearly needs backend
-  execution such as webhooks, workers, schedulers, integrations, or
-  Python-heavy compute
-- `skills/openclaw-skill-importer.md` when importing OpenClaw or other
-  third-party skill/plugin material
-- `skills/capability-gap-reporting.md`
-- `skills/ai-capability-defaults.md` when the request includes drafting,
-  generation, or other model-backed UX
-- `skills/shadow-participation-and-guest-threads.md` when the request touches
-  external participants, guests, shared collaboration, or claimable users
-- `skills/email-ingress-and-thread-routing.md` when the request touches inboxes,
-  aliases, email/SMS/chat routing, or thread-based communication
+`skills/workspace-guidance-refresh/SKILL.md` for the managed refresh flow.
+
+## Skills
+
+This workspace includes MinuteWork architecture skills under `skills/`. Claude
+loads them automatically when relevant to your request. Run `/skill-name` to
+invoke one directly, or ask "What skills are available?" to see the full list.
 
 ## Shell-First UI Default
 
@@ -99,6 +71,24 @@ a concrete backend responsibility such as:
 - internal API endpoint
 - external system sync
 
+## OSS And Adoption
+
+- Templates are governed starters, not the full limit of what Builder may use.
+- Builder may adopt open-source libraries, frameworks, and products inside the
+  sandbox when that produces a better result than bespoke code.
+- Prefer this solution order before writing greenfield code:
+  - existing MinuteWork substrate
+  - reviewed capability skill or `catalog_native`
+  - app-pack/schema/flow extension
+  - adopt OSS when it clearly fits
+  - `attached_app` when the foreign system should stay its own subsystem
+  - `external_repo_intake` when Builder needs to inspect or wrap external code
+  - greenfield code last
+- If a strong OSS product already solves the problem well, prefer integrating,
+  wrapping, or governing it instead of rebuilding it from scratch.
+- Never treat imported OSS as a direct runtime install contract; normalize it
+  into governed MinuteWork artifacts or keep it external through `attached_app`.
+
 ## Compose Before Rebuild
 
 - Compose shared MinuteWork substrate first: baseline capabilities, runtime
@@ -115,6 +105,8 @@ a concrete backend responsibility such as:
   product, not fresh app rebuilds.
 - Use schemas, manifests, `mw.core.site`, and flows before adding custom code
   surfaces.
+- For public web, prefer `tenant-app` plus existing OSS libraries or `attached_app`
+  over rebuilding a full custom stack when a good external solution already exists.
 - If shared substrate is missing today, implement the smallest tenant-local
   extension that can later collapse into a reusable primitive, baseline
   capability, reviewed skill, or app pack.
@@ -150,8 +142,27 @@ a concrete backend responsibility such as:
 - `MW_PUBLIC_SITE_ENV=live` is for publication-safe delivery.
 - Anonymous live delivery should prefer published snapshots instead of direct
   runtime reads on every request.
+- `runtime_local_sidecar` is an opt-in public-site serving exception, not the
+  default live path.
+- If `runtime_local_sidecar` is chosen, Builder should target immutable runtime
+  publication refs and declared public route prefixes rather than mutable draft
+  records.
+- Hosted live reads remain `published_live`; gateway-forwarded runtime-served
+  live reads are `runtime_live`.
 - The runtime headless companion API is runtime-authenticated and should not be
   treated as the default anonymous live surface.
+- Runtime sidecar `auth_mode = public` means gateway-forwarded public traffic
+  only, and only for constrained safe public-site surfaces. Browsers must not
+  talk directly to the runtime sidecar.
+- The constrained public headless site content route is one of those safe
+  public-site surfaces, but only for published `mw.core.site.page` and
+  `mw.core.site.form` content. Missing content should be modeled as `404`, and
+  existing but unpublished content as `403`.
+- The runtime headless site content endpoint is for published page/form content,
+  not draft content retrieval.
+- Attached external sites stay in the `attached_app` integration lane with
+  subordinate `attached_site` metadata and optional `custom-adapter.ts`, not a
+  new release class.
 - `content_structure` is open and ordered. Extend it through adjacent schemas or
   extension packs when needed instead of bloating the baseline.
 
@@ -163,6 +174,12 @@ a concrete backend responsibility such as:
 - Public anonymous pages usually belong in `tenant-app` and ship through the hosted public-release path, not a runtime-local sidecar.
 - Do not use `sidecar` as the default public-site renderer for pricing, docs,
   blog, or landing pages.
+- Do not read live public page content straight from mutable runtime drafts when
+  the property uses `runtime_local_sidecar`; publish immutable runtime content
+  first.
+- Do not treat `attached_app` as a third serving mode; keep the foreign renderer
+  and deploy pipeline external while MinuteWork governs drafts, approvals, and
+  publish actions.
 - Do not invent a separate guest-account or inbox-routing model when the
   existing shadow identity, alias, route, and thread substrate fits.
 - Do not add direct model/provider integrations in `tenant-app` for MVP when

package/assets/claude-local/skills/README.md

@@ -5,6 +5,11 @@ Place focused MinuteWork architecture skills here.
 These files are part of the canonical Builder common bundle and are allowlisted
 for developer-local export. Skills are shared across all engine renderers.
 
+Each skill lives in `skill-name/SKILL.md` so Claude Code can load its
+frontmatter description eagerly and defer the full body until the skill is
+invoked. Keep each `description` front-loaded and under 250 characters so it
+survives Claude Code's skill-description truncation budget.
+
 They should describe the shipped authoring model external workspaces actually
 receive:
 
@@ -21,11 +26,11 @@ receive:
 
 Generated-workspace-first guidance should live here, especially:
 
-- `generated-workspace-architecture.md`
-- `workspace-guidance-refresh.md`
-- `shell-architecture.md`
-- `runtime-capability-inventory.md`
-- `layering-and-import-modes.md`
-- `capability-gap-reporting.md`
-- `shadow-participation-and-guest-threads.md`
-- `email-ingress-and-thread-routing.md`
+- `generated-workspace-architecture/SKILL.md`
+- `workspace-guidance-refresh/SKILL.md`
+- `shell-architecture/SKILL.md`
+- `runtime-capability-inventory/SKILL.md`
+- `layering-and-import-modes/SKILL.md`
+- `capability-gap-reporting/SKILL.md`
+- `shadow-participation-and-guest-threads/SKILL.md`
+- `email-ingress-and-thread-routing/SKILL.md`

package/assets/claude-local/skills/{ai-capability-defaults.md → ai-capability-defaults/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: ai-capability-defaults
+description: "AI-assisted drafting, generation, structured-output UX, or deciding whether to reuse existing runtime AI capability."
+---
+
 # AI Capability Defaults
 
 Use this skill when the request includes AI-assisted drafting, proposal
@@ -19,9 +24,9 @@ generation, itinerary generation, content generation, or structured-output UX.
   context or ask a clarifying question before inventing new AI infrastructure.
 - When AI drafting or generation touches external participants, guests,
   anonymous/public intake, or pre-claim collaboration, also read
-  `contract-first-public-intake.md`,
-  `shadow-participation-and-guest-threads.md` and
-  `email-ingress-and-thread-routing.md` before choosing `tenant-app`, gateway,
+  `contract-first-public-intake/SKILL.md`,
+  `shadow-participation-and-guest-threads/SKILL.md` and
+  `email-ingress-and-thread-routing/SKILL.md` before choosing `tenant-app`, gateway,
   runtime, or `sidecar` surfaces.
 - For guest-facing AI flows, inspect runtime, gateway, and platform ingress
   source before inventing a new collaboration or communications backend.

package/assets/claude-local/skills/{app-pack-authoring.md → app-pack-authoring/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: app-pack-authoring
+description: "Deciding the shipped product shape, choosing between tenant-app and sidecar, or composing shared substrate before greenfield code."
+---
+
 # App Pack Authoring
 
 An `app pack` is the shipped product unit.
@@ -5,6 +10,10 @@ An `app pack` is the shipped product unit.
 - Compose shared MinuteWork substrate first: baseline capabilities, runtime
   primitives, reviewed capability skills, app packs, overlays, and hosted
   publication flows.
+- Templates are governed starters, not the full limit of what Builder may use.
+- Builder may adopt open-source libraries, frameworks, and products inside the
+  sandbox when that reduces bespoke code and still preserves the MinuteWork
+  contract boundaries.
 - Start with declarative schema/manifests and add code surfaces only when needed.
 - Use `tenant-app` for the combined public-site plus private-app web surface.
 - Use `sidecar` for internal APIs, workers, integrations, or Python-heavy compute.
@@ -26,6 +35,14 @@ An `app pack` is the shipped product unit.
   available; ask or inspect context if that availability is unclear.
 - Public-site authoring should stay CMS/runtime-backed, while anonymous live
   delivery should prefer published snapshots.
+- Prefer this decision order before writing greenfield code:
+  - reuse existing MinuteWork substrate or a reviewed capability skill
+  - extend app-pack/schema/flow surfaces
+  - adopt a strong OSS library or product when it clearly fits
+  - use `attached_app` when the foreign system should stay its own subsystem
+  - use repo intake or greenfield code only when the cleaner options do not fit
+- If a mature OSS product already solves the problem well, prefer integrating,
+  wrapping, or governing it instead of rebuilding it from scratch.
 - Builder usually builds the reusable tenant product once. Per-customer
   deliverables such as itineraries, proposals, pages, and generated assets
   should usually come from runtime data/content/workflows, not fresh rebuilds.

package/assets/claude-local/skills/{capability-gap-reporting.md → capability-gap-reporting/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: capability-gap-reporting
+description: "A request does not cleanly fit current MinuteWork substrate and a capability gap needs to be recorded."
+---
+
 # Capability Gap Reporting
 
 Use this skill when a generated workspace discovers that the requested

package/assets/claude-local/skills/{content-structure-and-sections.md → content-structure-and-sections/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: content-structure-and-sections
+description: "CMS page models, section rendering, content_structure, or public content composition."
+---
+
 # Content Structure And Sections
 
 Use this skill when the request touches CMS page models, section rendering, or

package/assets/claude-local/skills/{contract-first-public-intake.md → contract-first-public-intake/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: contract-first-public-intake
+description: "Public forms, anonymous intake, guest-continuity threads, public submission routing, or claim-after-auth flows."
+---
+
 # Contract-First Public Intake
 
 Use this skill when the request touches public forms, anonymous intake,

package/assets/claude-local/skills/{email-ingress-and-thread-routing.md → email-ingress-and-thread-routing/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: email-ingress-and-thread-routing
+description: "Inboxes, aliases, email-SMS-chat routing, or thread-based communication with external parties."
+---
+
 # Email Ingress And Thread Routing
 
 Use this skill when the product touches inboxes, aliases, email-driven
@@ -47,7 +52,7 @@ workflows, guest chat, or thread-based communication with external parties.
     routing family dispatching canonical public submission ingress, while
     `dispatch_public_handoff(...)` remains the wrapper alias into the same path.
 - When the request is specifically about web intake or claim-after-auth,
-  also read `contract-first-public-intake.md`.
+  also read `contract-first-public-intake/SKILL.md`.
 
 Useful inspection points when source is available:
 

package/assets/claude-local/skills/{event-bus.md → event-bus/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: event-bus
+description: "Runtime-local events, decoupled app behavior, typed local event subscriptions, or cross-surface event coordination."
+---
+
 # Event Bus
 
 Use runtime-local events for decoupled app behavior.

package/assets/claude-local/skills/{generated-workspace-architecture.md → generated-workspace-architecture/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: generated-workspace-architecture
+description: "Reasoning from a CLI-generated Builder workspace rather than the monorepo or a live tenant runtime. Trust boundaries, layering, and workspace-local authoring."
+---
+
 # Generated Workspace Architecture
 
 Use this skill when reasoning from a CLI-generated Builder workspace rather than

package/assets/claude-local/skills/{layering-and-import-modes.md → layering-and-import-modes/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: layering-and-import-modes
+description: "Choosing between configuration, app-pack changes, overlays, attached_app, or OSS intake for a given request."
+---
+
 # Layering And Import Modes
 
 Use this skill when choosing between configuration, app-pack changes, overlays,
@@ -7,6 +12,8 @@ Use this skill when choosing between configuration, app-pack changes, overlays,
   - configure an existing capability, skill, or baseline substrate first
   - then durable app-pack/schema/flow changes
   - overlays for tenant-specific, fast-moving prompts, views, and policy
+- Templates are a preferred starter path, not the only allowed source of code
+  or composition inside the Builder sandbox.
 - Durable tenant behavior should usually compile to governed app-pack artifacts,
   not ad hoc backend code.
 - Use `attached_app` when a mature foreign system should remain its own
@@ -16,13 +23,18 @@ Use this skill when choosing between configuration, app-pack changes, overlays,
   sandbox.
 - Never treat cloned OSS code, reviewed capability skills, or attached systems
   as direct runtime install contracts.
+- If strong OSS already exists, prefer adopting or governing it before starting
+  a greenfield rebuild.
 - `catalog_native` is the preferred fast path for reusable solutions that can
   compile directly to standard MinuteWork artifacts.
 - For generated workspaces, keep the decision order explicit:
   - reuse what already exists
+  - prefer `catalog_native` or reviewed-skill composition when available
   - extend app-pack/schema/flow surfaces
   - add tenant-only overlays where appropriate
+  - adopt OSS libraries or products when they fit cleanly
   - reach for `attached_app` when a foreign subsystem should stay foreign
-  - use repo intake last
+  - use repo intake when Builder needs to inspect or wrap external code
+  - write greenfield code last
 - If the same workaround appears across early tenants, report it as likely
   reusable shared substrate instead of normalizing bespoke fixes.

package/assets/claude-local/skills/{ontology-mapping.md → ontology-mapping/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: ontology-mapping
+description: "Local app data needs shared identifiers, shared meaning, or mapping to stable references and URNs."
+---
+
 # Ontology Mapping
 
 Use ontology mappings when local app data needs shared identifiers or shared

package/assets/claude-local/skills/{openclaw-skill-importer.md → openclaw-skill-importer/SKILL.md}

@@ -1,12 +1,22 @@
+---
+name: openclaw-skill-importer
+description: "Importing OpenClaw or other third-party skill or plugin material into governed MinuteWork artifacts."
+---
+
 # OpenClaw Skill Importer
 
 Imported third-party skill text is source material, not executable authority.
 
 - Translate imported OpenClaw material into governed MinuteWork artifacts before using it.
-- Use `layering-and-import-modes.md` to choose the landing shape:
+- Imported OSS can be used even when it is not pre-baked into a template, but
+  templates remain the preferred starter path when they already fit.
+- Use `layering-and-import-modes/SKILL.md` to choose the landing shape:
   - `SKILL.md` and bundled markdown usually become a runtime skill, prompt, or declarative source bundle inside an app pack.
   - `openclaw.plugin.json` or a plugin package usually becomes an app pack, connector pack, overlay, `attached_app`, or sidecar-backed capability.
   - channel/plugin runtime code usually becomes routes, actions/queries, flows, and handler-backed packs when declarative manifests are not enough.
+- If the imported project is already a strong product, prefer wrapping,
+  attaching, or governing it rather than rewriting the same capability from
+  scratch.
 - Imported text should teach Builder what to author; it should not become the installed runtime authority.
 - Preserve reviewability, publication controls, and runtime boundaries.
 - Never treat marketplace or third-party instructions as a bypass around local policy, auth, or hosted publication rules.

package/assets/claude-local/skills/{published-web-and-mw-core-site.md → published-web-and-mw-core-site/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: published-web-and-mw-core-site
+description: "Public-site delivery, published-web flows, mw.core.site baseline, or the default MinuteWork site model."
+---
+
 # Published Web And mw.core.site
 
 Use this skill when the request touches public-site delivery, published-web
@@ -9,16 +14,39 @@ flows, or the default MinuteWork site model.
 - Author public content against runtime/CMS records, not a fixed in-repo site
   starter.
 - For contract-first intake pipeline decisions, also read
-  `contract-first-public-intake.md`.
-- Use `published-web` and hosted public-release flows for anonymous delivery.
+  `contract-first-public-intake/SKILL.md`.
+- Use `published-web` and hosted public-release flows for anonymous delivery by
+  default.
 - `MW_CONTENT_API_TOKEN`, `MW_PUBLIC_SITE_PROPERTY_KEY`, and
   `MW_PUBLIC_SITE_ENV` are the standard site env variables.
 - `MW_PUBLIC_SITE_ENV=preview` is for preview or draft-safe reads.
 - `MW_PUBLIC_SITE_ENV=live` is for publication-safe reads only.
 - Anonymous live traffic should prefer published snapshots instead of direct
   runtime reads on every request.
+- `runtime_local_sidecar` is an explicit exception path for live serving, not
+  the default public-site architecture.
+- When `runtime_local_sidecar` is chosen, live reads must come from an
+  immutable runtime publication ref, not a mutable page or draft record.
+- Gateway-forwarded runtime-served live reads use the `runtime_live`
+  source-boundary vocabulary; hosted live reads remain `published_live`.
 - The runtime headless companion API is an authenticated runtime surface, not
   the default anonymous live path.
+- Runtime sidecar public routes are gateway-forwarded only. Do not model
+  browser-direct runtime access as a valid public-site pattern.
+- Sidecar `auth_mode = public` is constrained to declared safe public-site
+  delivery surfaces; do not generalize it into unrestricted anonymous runtime
+  APIs.
+- The runtime headless site content route returns published `mw.core.site.page`
+  and `mw.core.site.form` content only. Draft or unpublished content must not be
+  treated as available from that surface.
+- The public headless site content endpoint is a constrained `auth_mode = public`
+  surface for gateway-forwarded reads of published `mw.core.site.page` and
+  `mw.core.site.form` records by schema/name. Missing content should be treated
+  as `404`; existing but unpublished content should be treated as `403`. It must
+  not be used for draft, unpublished, or arbitrary runtime data access.
+- Attached external sites stay in the `attached_app` lane with subordinate
+  `attached_site` metadata and optional `custom-adapter.ts`; they do not become
+  a new published-web release class.
 - `mw.core.site.form` plus `mw.core.site.submission` already provide the
   baseline intake substrate; extend them before inventing a parallel public
   form/submission model.

package/assets/claude-local/skills/{runtime-capability-inventory.md → runtime-capability-inventory/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: runtime-capability-inventory
+description: "Answering what the runtime already provides from a generated Builder workspace. Capability inventory and known primitives."
+---
+
 # Runtime Capability Inventory
 
 Use this skill when you need to answer "what does runtime already have?" from a

package/assets/claude-local/skills/{schema-engine.md → schema-engine/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: schema-engine
+description: "Adding schemas, forms, submissions, or other tenant-defined runtime data structures."
+---
+
 # Schema Engine
 
 Use this skill when the request needs tenant-defined data structures.
@@ -10,7 +15,7 @@ Use this skill when the request needs tenant-defined data structures.
 - Treat `mw.core.site.form` plus `mw.core.site.submission` as the existing
   public-intake substrate before inventing parallel site submission storage.
 - For intake behavior, continuity policy, and claim-after-auth rules, also read
-  `contract-first-public-intake.md`.
+  `contract-first-public-intake/SKILL.md`.
 - For `mw.core.site.submission`, keep replay/idempotency centered on
   `platform_submission_ref` and preserve the original record on retry.
 - The default lookup fields that usually deserve indexes for public intake are

package/assets/claude-local/skills/{secrets-runtime-bridge.md → secrets-runtime-bridge/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: secrets-runtime-bridge
+description: "Secrets, bridge reads, runtime-private data access, or token handling across trust boundaries."
+---
+
 # Secrets And Runtime Bridge
 
 Use this skill when a request touches secrets, bridge reads, or runtime-private

package/assets/claude-local/skills/{shadow-participation-and-guest-threads.md → shadow-participation-and-guest-threads/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: shadow-participation-and-guest-threads
+description: "External participants, guests, shared collaboration, claimable users, or features involving people who do not have their own runtime."
+---
+
 # Shadow Participation And Guest Threads
 
 Use this skill when a product feature involves external people who may not have
@@ -28,7 +33,7 @@ their own runtime yet.
   member claim should converge on the existing shadow tenant/shadow person
   instead of creating fresh guest identities.
 - When the request is specifically about public forms or claim-after-auth on
-  anonymous intake, also read `contract-first-public-intake.md`.
+  anonymous intake, also read `contract-first-public-intake/SKILL.md`.
 - Implementation cues in current source:
   - Platform/public ingress often starts from external-identity fields such as
     `external_identity_key`, `visitor_email`, `visitor_name`, and continuity

package/assets/claude-local/skills/{shell-architecture.md → shell-architecture/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: shell-architecture
+description: "Member-facing UI, operator workflows, threads, channels, cards, dashboards, approvals, or deciding whether the request should be a shell extension."
+---
+
 # Shell Architecture
 
 Use this skill when the request touches member-facing UI, operator workflows,

package/assets/claude-local/skills/{sidecar-generation.md → sidecar-generation/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: sidecar-generation
+description: "Backend execution such as webhooks, workers, schedulers, integrations, or Python-heavy compute that does not belong in tenant-app."
+---
+
 # Sidecar Generation
 
 Use a `sidecar` only when the app needs backend/runtime execution that does not

package/assets/claude-local/skills/{workspace-guidance-refresh.md → workspace-guidance-refresh/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: workspace-guidance-refresh
+description: "Exported guidance looks stale, a newly added skill is missing, or CLAUDE.md does not match the current CLI export."
+---
+
 # Workspace Guidance Refresh
 
 Use this skill when the generated workspace guidance looks stale, a newly added

package/assets/templates/next-tenant-app/README.md

@@ -58,10 +58,12 @@ composes against that baseline rather than trying to install it locally.
 The gateway response carries an explicit boundary:
 
 - `environment=preview` must declare `source_boundary=runtime_preview`
-- `environment=live` must declare `source_boundary=published_live`
+- `environment=live` may declare `source_boundary=published_live` for hosted releases or `source_boundary=runtime_live` for runtime-served sidecar releases
 
 That keeps preview free to use runtime-backed draft reads while keeping live
-publication-safe for static generation and anonymous delivery.
+publication-safe for hosted delivery while still allowing an explicit
+runtime-served public lane when the release is activated through
+`runtime_local_sidecar`.
 
 To replace the built-ins for a tenant-specific CMS or content API, implement the hook in `src/lib/content/custom-adapter.ts`.
 

package/assets/templates/next-tenant-app/src/lib/content/adapter.server.test.ts

@@ -203,6 +203,30 @@ describe("public content adapter", () => {
     ).rejects.toThrow("published_live");
   });
 
+  it("accepts runtime_live for live runtime-served publications", async () => {
+    const fetchMock = vi.fn().mockResolvedValue(
+      jsonResponse(
+        createEnvelope({
+          environment: "live",
+          source_boundary: "runtime_live",
+        }),
+      ),
+    );
+    vi.stubGlobal("fetch", fetchMock);
+
+    await expect(
+      fetchPublicSiteSnapshotEnvelope({
+        contentApiToken: "content-token",
+        environment: "live",
+        platformBaseUrl: "https://platform.example.com",
+        propertyKey: "main-site",
+      }),
+    ).resolves.toMatchObject({
+      environment: "live",
+      source_boundary: "runtime_live",
+    });
+  });
+
   it("maps MinuteWork public-site snapshots through the adapter interface", async () => {
     const adapter = new MinuteWorkPublicSiteContentAdapter(async () =>
       createEnvelope({

package/assets/templates/next-tenant-app/src/lib/content/contracts.ts

@@ -303,6 +303,7 @@ export const publicContentSnapshotSchema = z.object({
 export const publicSiteSnapshotEnvironmentSchema = z.enum(["preview", "live"]);
 export const publicSiteSnapshotSourceBoundarySchema = z.enum([
   "runtime_preview",
+  "runtime_live",
   "published_live",
 ]);
 
@@ -327,13 +328,13 @@ export const publicSiteSnapshotEnvelopeSchema = z
 
     if (
       value.environment === "live" &&
-      value.source_boundary !== "published_live"
+      !["published_live", "runtime_live"].includes(value.source_boundary)
     ) {
       context.addIssue({
         code: z.ZodIssueCode.custom,
         path: ["source_boundary"],
         message:
-          'Live public-site snapshots must declare the "published_live" source boundary.',
+          'Live public-site snapshots must declare the "published_live" or "runtime_live" source boundary.',
       });
     }
   });

package/assets/templates/next-tenant-app/src/lib/content/release-manifest.test.ts

@@ -58,6 +58,29 @@ describe("release-manifest", () => {
     expect(manifest.composition.config_updated).toBe(false);
   });
 
+  it("supports attached external site metadata without adding a new release class", () => {
+    const manifest = buildReleaseManifest({
+      appPackId: "mw.core.site",
+      snapshotSchemaVersion: 1,
+      releaseClass: "runtime_local_sidecar",
+      config: null,
+      pages: [],
+      navigation: [],
+      forms: [],
+      attachedSite: {
+        mode: "attached_app",
+        adapter_module: "src/lib/content/custom-adapter.ts",
+        renderer: "external_next",
+        publish_target: "repo-sync",
+      },
+      contentDigest: "sha256-attached",
+    });
+
+    const parsed = releaseManifestSchema.safeParse(manifest);
+    expect(parsed.success).toBe(true);
+    expect(manifest.attached_site?.mode).toBe("attached_app");
+  });
+
   it("validates against the schema", () => {
     const invalid = {
       manifest_version: 2, // wrong version

package/assets/templates/next-tenant-app/src/lib/content/release-manifest.ts

@@ -52,6 +52,16 @@ export const releaseManifestSchema = z.object({
     ),
   }),
 
+  /** Optional metadata for attached external renderers that sync against the standard artifact graph. */
+  attached_site: z
+    .object({
+      mode: z.literal("attached_app"),
+      adapter_module: z.string().min(1),
+      renderer: z.string().min(1),
+      publish_target: z.string().min(1),
+    })
+    .optional(),
+
   /** Digest of the composed content for integrity verification. */
   content_digest: z.string().min(1),
 
@@ -75,6 +85,12 @@ export function buildReleaseManifest(input: {
   pages: { page_key: string; path: string; title: string; sections: unknown[] }[];
   navigation: { nav_key: string; slot: string; items: unknown[] }[];
   forms: { form_key: string; schema?: { fields?: unknown[] } }[];
+  attachedSite?: {
+    mode: "attached_app";
+    adapter_module: string;
+    renderer: string;
+    publish_target: string;
+  } | null;
   contentDigest: string;
 }): ReleaseManifest {
   return {
@@ -100,6 +116,7 @@ export function buildReleaseManifest(input: {
         field_count: f.schema?.fields?.length ?? 0,
       })),
     },
+    attached_site: input.attachedSite ?? undefined,
     content_digest: input.contentDigest,
     generated_at: new Date().toISOString(),
   };

package/assets/templates/next-tenant-app/tools/template/with-public-site-fixture.mjs

@@ -59,7 +59,7 @@ const server = createServer((request, response) => {
   }
 
   const environment = requestUrl.searchParams.get("environment") ?? "preview";
-  const sourceBoundary = environment === "live" ? "published_live" : "runtime_preview";
+  const sourceBoundary = environment === "live" ? "runtime_live" : "runtime_preview";
 
   response.writeHead(200, { "content-type": "application/json" });
   response.end(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "minutework",
-  "version": "0.1.16",
+  "version": "0.1.18",
   "description": "MinuteWork CLI for workspace scaffolding, local preview workflows, and hosted preview deploys.",
   "type": "module",
   "bin": {
@@ -23,8 +23,8 @@
     "@modelcontextprotocol/sdk": "^1.28.0",
     "jiti": "^2.6.1",
     "zod": "^4.3.6",
-    "@minutework/schema-compiler": "0.1.0",
-    "@minutework/platform-config": "0.1.0"
+    "@minutework/platform-config": "0.1.0",
+    "@minutework/schema-compiler": "0.1.0"
   },
   "devDependencies": {
     "@types/node": "^24.9.1",