minutework 0.1.31 → 0.1.33

package/EXTERNAL_ALPHA.md

@@ -1,35 +1,35 @@
-# PandaWork CLI External Alpha
+# MinuteWork CLI External Alpha
 
-This document is the operator-facing onboarding contract for the first external PandaWork CLI alpha.
+This document is the operator-facing onboarding contract for the first external MinuteWork CLI alpha.
 
 ## Supported paths
 
 Every supported external path starts with the same workspace/bootstrap flow:
 
 ```bash
-npx pandawork init my-site --starter tenant-app
+npx minutework init my-site --starter tenant-app
 cd my-site
-npx pandawork login
-npx pandawork link
+npx minutework login
+npx minutework link
 ```
 
 From there, the current external alpha supports two post-link lanes.
 
 The shipped `tenant-app` starter is the combined web surface: public routes at
-the root, a private `/app` workspace, and a PandaWork-managed public-content
+the root, a private `/app` workspace, and a MinuteWork-managed public-content
 path over the runtime-baseline `mw.core.site` contract.
 
 ### Developer-local broker lane
 
-Use `pandawork session` when you want PandaWork to assemble the workspace
+Use `minutework session` when you want MinuteWork to assemble the workspace
 snapshot, choose a local workflow mode, and optionally launch the first shipped
 local coding engine.
 
 ```bash
-pandawork session start --mode human
-pandawork session start --mode ai --engine claude
-pandawork session status
-pandawork session resume
+minutework session start --mode human
+minutework session start --mode ai --engine claude
+minutework session status
+minutework session resume
 ```
 
 - `start` stores or updates the workspace preference, writes a bounded context
@@ -41,10 +41,10 @@ pandawork session resume
 - `human` and `ai` are alternative start modes, not a required sequence.
 - Claude is the only supported local coding engine today.
 - AI mode now auto-installs and auto-updates managed Claude Code under the
-  machine-local PandaWork CLI state root and prefers that managed binary over
+  machine-local MinuteWork CLI state root and prefers that managed binary over
   any `claude` already on `PATH`.
-- Claude authentication still happens outside PandaWork. If Claude needs local
-  login or approval, complete that in Claude itself and rerun the PandaWork
+- Claude authentication still happens outside MinuteWork. If Claude needs local
+  login or approval, complete that in Claude itself and rerun the MinuteWork
   broker command.
 
 The broker state model is intentionally split:
@@ -52,7 +52,7 @@ The broker state model is intentionally split:
 - repo-local pointer and lock state under `.minutework/` tracks the current
   workspace session
 - machine-local preferences, per-session context packs, transcripts, and
-  session history stay under the PandaWork CLI state root
+  session history stay under the MinuteWork CLI state root
 
 The broker fails closed when a live session is already active, the selected
 engine is missing, a prior running record has gone stale, or the launch is
@@ -74,7 +74,7 @@ trusted projects); `mcp/claude-desktop.sample.json` is included for Claude
 Desktop.
 
 Generated guidance and MCP wiring can be reconciled later with
-`pandawork workspace sync-assets`.
+`minutework workspace sync-assets`.
 
 Runtime-only Claude hooks remain excluded from the generated workspace export.
 
@@ -84,28 +84,28 @@ Use the existing local preview/test loop and hosted preview deploy lane when
 you want to run the generated app locally or submit a hosted preview:
 
 ```bash
-pandawork dev
-pandawork test
-pandawork deploy --preview
+minutework dev
+minutework test
+minutework deploy --preview
 ```
 
-Combined **tenant-app + sidecar** workspaces keep sidecar setup explicit. Root `pnpm install` stays Node-only and does not run `poetry install` for you. If you need the sidecar, run `pnpm run install:sidecar` from the workspace root or `cd sidecar && poetry install` yourself before `pandawork dev` or `pandawork test`.
+Combined **tenant-app + sidecar** workspaces keep sidecar setup explicit. Root `pnpm install` stays Node-only and does not run `poetry install` for you. If you need the sidecar, run `pnpm run install:sidecar` from the workspace root or `cd sidecar && poetry install` yourself before `minutework dev` or `minutework test`.
 
 For direct third-party web hosts such as Vercel, deploy `tenant-app` only. In Vercel, point the project Root Directory at `tenant-app`; the optional sidecar remains a separate Poetry-managed surface.
 
 For native mobile clients, use the `mobile` starter. It is a standalone Expo /
 React Native client that authenticates directly against the platform with the
 native session-token flow; it is distributed through EAS/App Store/Play Store
-instead of `pandawork deploy`.
+instead of `minutework deploy`.
 
 Anything outside these lanes remains deferred, including `--live`,
 runtime-backed deploy targets, and additional local coding engines.
 
-If you run `pandawork init` **without** `--starter` in an interactive terminal, the CLI prompts for tenant-app, sidecar, mobile, common combinations, or base-only. In CI or scripts, use `--starter` or set `MW_CLI_NONINTERACTIVE=1` to skip the prompt (base-only scaffold).
+If you run `minutework init` **without** `--starter` in an interactive terminal, the CLI prompts for tenant-app, sidecar, mobile, common combinations, or base-only. In CI or scripts, use `--starter` or set `MW_CLI_NONINTERACTIVE=1` to skip the prompt (base-only scaffold).
 
 ## What `link` does
 
-`pandawork link` is no longer tenant-only. It now:
+`minutework link` is no longer tenant-only. It now:
 
 1. Resolves the active auth profile and workspace platform.
 2. Resolves or creates the tenant-scoped `PublishedWebProperty`.
@@ -133,7 +133,7 @@ If the workspace cannot compile hosted preview release metadata for the linked p
 
 ## What `deploy --preview` does
 
-`pandawork deploy --preview` is preview-only and guarded:
+`minutework deploy --preview` is preview-only and guarded:
 
 1. Loads the active auth profile and linked workspace property.
 2. Re-runs validate and compile.
@@ -153,12 +153,12 @@ The CLI does not fabricate success. If the backend cannot materialize a hosted p
 
 ## Failure semantics
 
-- Missing auth: run `pandawork login`
-- Missing binding: run `pandawork link`
-- Missing stored broker preference before resume: run `pandawork session start --mode <human|ai>`
-- Missing Claude binary or local Claude auth for AI mode: let PandaWork retry the managed install when network access is available, or complete Claude authentication locally, then rerun `pandawork session start --mode ai --engine claude`
-- Live or stale local broker session state: inspect `pandawork session status`, let the live process exit, or rerun `pandawork session resume`
-- Missing property-scoped release metadata: fix `tenant-app/.env.example` and re-run `pandawork compile`
+- Missing auth: run `minutework login`
+- Missing binding: run `minutework link`
+- Missing stored broker preference before resume: run `minutework session start --mode <human|ai>`
+- Missing Claude binary or local Claude auth for AI mode: let MinuteWork retry the managed install when network access is available, or complete Claude authentication locally, then rerun `minutework session start --mode ai --engine claude`
+- Live or stale local broker session state: inspect `minutework session status`, let the live process exit, or rerun `minutework session resume`
+- Missing property-scoped release metadata: fix `tenant-app/.env.example` and re-run `minutework compile`
 - Unsupported release class: external alpha only supports hosted `ssr_container`
 - Missing provider/receipt substrate: deploy returns a typed failure receipt
 - Failed preview deploy with an existing preview target: the platform reports `rolled_back` with `previous_preview_preserved`
@@ -166,9 +166,9 @@ The CLI does not fabricate success. If the backend cannot materialize a hosted p
 ## CLI bug reports
 
 - The CLI automatically submits a sanitized bug report for failed commands unless `MW_CLI_BUG_REPORTS=never` is set (machine-readable `--json` verbs suppress this automatically).
-- Automatic reports keep a local JSON bundle under the PandaWork CLI state root for retry and support follow-up.
-- `pandawork report-bug --note "..."` sends a manual report for UX issues or suspicious behavior that did not crash.
-- `pandawork report-bug --last --note "..."` resends the last saved bundle with extra context.
+- Automatic reports keep a local JSON bundle under the MinuteWork CLI state root for retry and support follow-up.
+- `minutework report-bug --note "..."` sends a manual report for UX issues or suspicious behavior that did not crash.
+- `minutework report-bug --last --note "..."` resends the last saved bundle with extra context.
 - Support should always ask for the printed `report_id` before requesting extra screenshots or logs.
 
 ## Release notes for operators

package/README.md

@@ -1,31 +1,31 @@
-# PandaWork CLI
+# MinuteWork CLI
 
-PandaWork CLI for initializing a workspace, authenticating against a PandaWork platform, linking a repo to a tenant-scoped public-site property, launching developer-local session broker flows, running local preview/test loops, submitting hosted preview deploys, and publishing app packs to the marketplace through the publication-review gate.
+MinuteWork CLI for initializing a workspace, authenticating against a MinuteWork platform, linking a repo to a tenant-scoped public-site property, launching developer-local session broker flows, running local preview/test loops, submitting hosted preview deploys, and publishing app packs to the marketplace through the publication-review gate.
 
-The npm package is still published as `minutework` for compatibility. Use `pandawork` for new commands; the existing `minutework` command remains supported.
+The npm package and primary command are `minutework`. The `pandawork` command remains available only as a compatibility alias for older installs and scripts.
 
 ## External alpha scope
 
 The current external alpha is intentionally narrow:
 
 - Starters: `tenant-app` (the deployable web surface), `sidecar` (local/internal runtime surface), and `mobile` (init-only native client)
-- Developer-local broker surface: `pandawork session start|resume|status`
+- Developer-local broker surface: `minutework session start|resume|status`
 - Hosted release class: `ssr_container`
-- Deploy surface: `pandawork deploy --preview`
+- Deploy surface: `minutework deploy --preview`
 - Deferred: `--live`, additional local coding engines, sidecar/runtime-backed deploys, and the commercial marketplace listing/pricing layer
-- Marketplace publish: `pandawork publish` submits the compiled, digest-bound app pack through the platform publication-review + attestation gate and publishes it to the public marketplace catalog **only** on an approved (or approved-with-warnings) attestation; a rejected attestation prints the review findings and exits 1 without publishing
+- Marketplace publish: `minutework publish` submits the compiled, digest-bound app pack through the platform publication-review + attestation gate and publishes it to the public marketplace catalog **only** on an approved (or approved-with-warnings) attestation; a rejected attestation prints the review findings and exits 1 without publishing
 
 The shipped `tenant-app` starter is the combined web surface: public routes at
 the root plus a private `/app` workspace. Public-site content follows the
-PandaWork-managed `mw.core.site` baseline and published-snapshot flow.
+MinuteWork-managed `mw.core.site` baseline and published-snapshot flow.
 
 The CLI fails closed when the backend cannot provide typed release metadata, deploy status, receipts, activation state, or rollback state. It does not claim a successful deploy when the provider substrate is unavailable.
 
 ## Install
 
 ```bash
-npx pandawork --help
-npx pandawork --version
+npx minutework --help
+npx minutework --version
 ```
 
 For repeat use in a local environment:
@@ -41,10 +41,10 @@ The package currently ships on a `0.x` alpha channel. Publish from this repo wit
 Start with the shared setup:
 
 ```bash
-npx pandawork init my-site --starter tenant-app
+npx minutework init my-site --starter tenant-app
 cd my-site
-npx pandawork login
-npx pandawork link
+npx minutework login
+npx minutework link
 ```
 
 After `link`, the current alpha has two supported lanes (both `tenant-app`).
@@ -52,7 +52,7 @@ After `link`, the current alpha has two supported lanes (both `tenant-app`).
 For a native mobile client, scaffold the **`mobile`** starter instead:
 
 ```bash
-npx pandawork init my-app --starter mobile
+npx minutework init my-app --starter mobile
 ```
 
 It is **init-only** and bring-your-own-UI: a minimal Expo (React Native) client
@@ -60,34 +60,34 @@ that authenticates **directly** against the platform with a native device-flow
 session token (PKCE authorize -> exchange -> bearer + refresh in the device
 keychain), not the `tenant-app` BFF cookie path. There is no `link`/`deploy`
 lane for it — distribution is your own EAS pipeline (`eas build`/`eas submit`,
-EAS Update), not `pandawork deploy`.
+EAS Update), not `minutework deploy`.
 
 ### Developer-local broker lane
 
-Use this lane when you want PandaWork to assemble a bounded workspace context,
+Use this lane when you want MinuteWork to assemble a bounded workspace context,
 persist broker state locally, and either prepare a human-mode session or launch
 the first supported local coding engine.
 
 ```bash
-pandawork session start --mode human
-pandawork session start --mode ai --engine claude
-pandawork session status
-pandawork session resume
+minutework session start --mode human
+minutework session start --mode ai --engine claude
+minutework session status
+minutework session resume
 ```
 
 - `human` and `ai` are alternative start modes, not a required sequence.
 - Claude is the only supported local coding engine today.
 - AI mode launches Claude with explicit workspace MCP bootstrap plus a bounded
-  PandaWork context pack instead of relying on implicit shell state.
-- PandaWork now installs and updates managed Claude Code automatically under
+  MinuteWork context pack instead of relying on implicit shell state.
+- MinuteWork now installs and updates managed Claude Code automatically under
   the machine-local CLI state root when AI mode needs it, and prefers that
   managed Claude binary over any `claude` already on `PATH`.
-- Claude authentication still happens outside PandaWork. If Claude needs local
+- Claude authentication still happens outside MinuteWork. If Claude needs local
   login or account approval, complete that in Claude itself and rerun the
-  PandaWork session command.
+  MinuteWork session command.
 - Current-session coordination stays repo-local under `.minutework/`, while
   preferences, per-session context packs, transcripts, and session history stay
-  machine-local under the PandaWork CLI state root.
+  machine-local under the MinuteWork CLI state root.
 - The broker fails closed on live overlap, missing engine binaries, stale
   session records, interrupts, and launch failures instead of allowing
   overlapping phantom sessions.
@@ -104,7 +104,7 @@ pandawork session resume
   trusted projects); `mcp/claude-desktop.sample.json` is included for Claude
   Desktop.
 - Managed guidance and MCP wiring can be refreshed later with
-  `pandawork workspace sync-assets`.
+  `minutework workspace sync-assets`.
 - Runtime-only Claude hooks are not exported into the generated workspace.
 
 ### Local preview and deploy lane
@@ -113,12 +113,12 @@ Use this lane when you want the workspace-local preview/test loop or a hosted
 preview deploy:
 
 ```bash
-pandawork dev
-pandawork test
-pandawork deploy --preview
+minutework dev
+minutework test
+minutework deploy --preview
 ```
 
-Combined **tenant-app + sidecar** workspaces keep sidecar setup explicit. Root `pnpm install` stays Node-only and does not run `poetry install` for you. If you need the sidecar, run `pnpm run install:sidecar` from the workspace root or `cd sidecar && poetry install` yourself before `pandawork dev` or `pandawork test`. Sidecar-only scaffolds have no root `package.json`; install Python deps once inside `sidecar/` before running local sidecar workflows.
+Combined **tenant-app + sidecar** workspaces keep sidecar setup explicit. Root `pnpm install` stays Node-only and does not run `poetry install` for you. If you need the sidecar, run `pnpm run install:sidecar` from the workspace root or `cd sidecar && poetry install` yourself before `minutework dev` or `minutework test`. Sidecar-only scaffolds have no root `package.json`; install Python deps once inside `sidecar/` before running local sidecar workflows.
 
 For direct third-party web hosts such as Vercel, deploy `tenant-app` only. In Vercel, point the project Root Directory at `tenant-app`; the optional sidecar remains a separate Poetry-managed surface.
 
@@ -148,20 +148,20 @@ For direct third-party web hosts such as Vercel, deploy `tenant-app` only. In Ve
 
 ## Bug reporting
 
-CLI failures automatically send a sanitized diagnostic report to the PandaWork platform unless `MW_CLI_BUG_REPORTS=never` is set.
+CLI failures automatically send a sanitized diagnostic report to the MinuteWork platform unless `MW_CLI_BUG_REPORTS=never` is set.
 
 - Machine-readable verbs run with `--json` suppress automatic reporting; rely on the result envelope and exit code instead.
 
 - Automatic reports never include raw `.env` contents, tokens, source files, or full local paths.
-- The CLI keeps a local report bundle under the PandaWork state root so you can retry or inspect what was sent.
-- Use `pandawork report-bug --note "what happened"` for manual reports.
-- Use `pandawork report-bug --last --note "extra context"` to resend the last saved bundle with more detail.
+- The CLI keeps a local report bundle under the MinuteWork state root so you can retry or inspect what was sent.
+- Use `minutework report-bug --note "what happened"` for manual reports.
+- Use `minutework report-bug --last --note "extra context"` to resend the last saved bundle with more detail.
 
 ## Requirements
 
 - Node.js 18 or newer
 - [Poetry](https://python-poetry.org/) on `PATH` when your workspace includes the FastAPI sidecar and you plan to run it locally (then run `pnpm run install:sidecar` or `cd sidecar && poetry install`)
-- A PandaWork platform that exposes the developer CLI auth and public-site preview deploy endpoints
+- A MinuteWork platform that exposes the developer CLI auth and public-site preview deploy endpoints
 - An auth profile with interactive developer access, or a deploy token that includes `deploy.preview.request`
 
 If the hosted preview provider is not configured, preview deploy returns a typed failure or rollback-preserved receipt instead of a fake success.

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

@@ -1,6 +1,6 @@
-# PandaWork Builder
+# MinuteWork Builder
 
-Use this workspace to build or extend PandaWork app packs. `tenant-app`,
+Use this workspace to build or extend MinuteWork app packs. `tenant-app`,
 `sidecar`, and optional `mobile` are implementation surfaces; choose the
 smallest surface that fits the request.
 
@@ -10,27 +10,27 @@ private authenticated workspace under `/app`.
 `mobile` is the standalone Expo/React Native client starter. It talks directly
 to the platform with native device-flow auth and bearer tokens; it is not a
 `tenant-app` BFF cookie client and not a `sidecar`. It ships through the
-developer's own EAS/App Store/Play Store pipeline, not `pandawork deploy`.
+developer's own EAS/App Store/Play Store pipeline, not `minutework deploy`.
 
 ## Refresh Managed Guidance
 
 If this workspace's exported guidance looks stale or a newly added skill is
-missing, run `pandawork workspace sync-assets` from the workspace root. See
+missing, run `minutework workspace sync-assets` from the workspace root. See
 `skills/workspace-guidance-refresh/SKILL.md` for the managed refresh flow.
 
 ## Workspace MCP
 
-The PandaWork workspace MCP server exposes read-only context tools (workspace
+The MinuteWork workspace MCP server exposes read-only context tools (workspace
 snapshot, schema status, capability inventory, deploy status, and a workspace
 doctor; tool names are prefixed `minutework_`). Prefer these over guessing at
 workspace state. It is wired for Cursor (`.cursor/mcp.json`) and Codex
 (`.codex/config.toml`, loaded for trusted projects); for Claude Desktop, copy
 `mcp/claude-desktop.sample.json`. Refresh all of this with
-`pandawork workspace sync-assets`.
+`minutework workspace sync-assets`.
 
 ## Skills
 
-This workspace includes PandaWork architecture skills under `skills/`. Your IDE
+This workspace includes MinuteWork architecture skills under `skills/`. Your IDE
 coding agent can use them as reference: browse `skills/` and read the relevant
 `SKILL.md` when a topic matches your task. In Claude Code these skills load
 automatically and `/skill-name` invokes one directly; other agents (Codex,
@@ -39,7 +39,7 @@ Cursor) can open the files directly or ask "What skills are available?".
 ## Project Orientation Fast Path
 
 When the user asks broad context questions like "what is this project about?",
-"what can we build with PandaWork?", "can we build our own product or make an
+"what can we build with MinuteWork?", "can we build our own product or make an
 existing product agentic?", "how do OSS products fit?", or "what is the
 ontology/network effect?", do not wait for them to name skills one by one. Read
 `skills/project-overview-and-strategy/SKILL.md` first, then pull the routed
@@ -108,7 +108,7 @@ a concrete backend responsibility such as:
 - 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 PandaWork substrate
+  - existing MinuteWork substrate
   - reviewed capability skill or `catalog_native`
   - app-pack/schema/flow extension
   - adopt OSS when it clearly fits
@@ -118,11 +118,11 @@ a concrete backend responsibility such as:
 - 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 PandaWork artifacts or keep it external through `attached_app`.
+  into governed MinuteWork artifacts or keep it external through `attached_app`.
 
 ## Compose Before Rebuild
 
-- Compose shared PandaWork substrate first: baseline capabilities, runtime
+- Compose shared MinuteWork substrate first: baseline capabilities, runtime
   primitives, reviewed capability skills, app packs, overlays, and hosted
   publication flows.
 - For external collaboration, start from the native substrate: shadow tenant,
@@ -234,7 +234,7 @@ a concrete backend responsibility such as:
   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 PandaWork governs drafts, approvals, and
+  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.

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

@@ -1,6 +1,6 @@
 # Builder Skills
 
-Place focused PandaWork architecture skills here.
+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.
@@ -15,6 +15,8 @@ receive:
 
 - Builder should compose shared substrate before generating bespoke tenant code
 - `tenant-app` is the combined public plus private web starter
+- `tenant-app` auth/data uses `@minutework/web-auth` and thin `src/mw/`
+  substrate, not per-app auth/gateway BFF routes
 - `mw.core.site` is a runtime baseline capability
 - tenant public authoring is runtime/CMS-backed through `mw.core.site`
 - Vuilder-owned public sites use `vuilder-public-site` and public-dj CMS

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

@@ -7,15 +7,28 @@ description: "Deciding the shipped product shape, choosing between tenant-app an
 
 An `app pack` is the shipped product unit.
 
-- Compose shared PandaWork substrate first: baseline capabilities, runtime
+- 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 PandaWork
+  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.
+- `tenant-app` auth/data must stay on the frozen `@minutework/web-auth`
+  contract. Wire it through the thin `src/mw/` substrate only; do not add
+  per-app `src/app/api/auth/*`, `src/app/api/gateway/*`, platform-session BFF
+  layers, platform credential login screens, operator-console links, or
+  runtime-command demos.
+- Browser calls from `tenant-app` should use `mw.query(...)` and
+  `mw.action(..., { idempotencyKey })`; actions require a non-empty
+  idempotency key. The runtime surface must be declared on the manifest with
+  `webCustomerExposed` / `web_customer_exposed`, and V1 customer roles are
+  `customer` only.
+- The authenticated `tenant-app` principal is `tenant_customer`. Do not model
+  the generated customer app as an operator/platform-session app, and do not
+  persist bearer/session/runtime tokens in browser JavaScript.
 - Use `sidecar` for internal APIs, workers, integrations, or Python-heavy compute.
 - For member-facing collaboration and operator workflows, check shell fit first
   before proposing standalone `tenant-app` routes or dashboards.
@@ -42,7 +55,7 @@ An `app pack` is the shipped product unit.
 - 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 PandaWork substrate or a reviewed capability skill
+  - 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
@@ -77,7 +90,7 @@ An `app pack` is the shipped product unit.
   `SCHEMA_KEY_UPSERT_REGISTRY` may ship in the active manifest.
 - For `mw.core.site.form`, do not author `form_key` or `app_pack_ref` inside
   `data`; the install pipe injects both. Keep `surface_key == form_key` for
-  public intake BFFs.
+  public intake gateway handling.
 - For `mw.runtime.agent`, use `logical_key` as the runtime `Agent.slug`.
   Author stable agent fields in `data` such as `name`, `system_instruction`,
   `enabled_tools`, `trigger_intents`, `channels_enabled`, and

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

@@ -1,12 +1,12 @@
 ---
 name: capability-gap-reporting
-description: "A request does not cleanly fit current PandaWork substrate and a capability gap needs to be recorded."
+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
-implementation does not cleanly fit current PandaWork substrate.
+implementation does not cleanly fit current MinuteWork substrate.
 
 - Record architecture gaps in `.minutework/runtime/capability-gap-report.json`.
 - Keep the report sanitized and tenant-safe. Do not include secrets, raw
@@ -52,5 +52,5 @@ implementation does not cleanly fit current PandaWork substrate.
   - `attached_app` when the right home is an attached-app integration surface
     rather than shared core substrate.
 - Prefer one concrete gap per missing shared capability.
-- Use gap reports to tell humans where PandaWork needs new substrate. Do not
+- Use gap reports to tell humans where MinuteWork needs new substrate. Do not
   treat them as automatic implementation instructions.

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

@@ -35,6 +35,14 @@ guest-continuity threads, public submission routing, or claim-after-auth flows.
 - Post-auth continuation stays on the existing `handoff_key` and flows through
   `apply_post_auth_access_policy()`. Do not invent automatic membership upgrades
   or a parallel claim token model.
+- Tenant web auth `claimRef` is an opaque platform-signed handoff claim token,
+  not a raw `PublicHandoff.id` or `core:public_handoff:*` ref. A `tenant-app`
+  may pass that token through `@minutework/web-auth` signup, but platform must
+  store it pending verification and link only after the authenticating email is
+  verified, the signed handoff is bound to that verified identity, and
+  `apply_post_auth_access_policy()` succeeds.
+- Do not create customer identity claims during unverified signup. Anonymous or
+  unbound handoffs must not be auto-linked.
 
 ## Privacy And Prompt Semantics
 
@@ -65,9 +73,9 @@ guest-continuity threads, public submission routing, or claim-after-auth flows.
   source that can drive later `action:` or `flow:` execution.
 - Do not gate public intake render on a hardcoded client-side token
   allowlist. The handoff token is a platform-issued, server-validated
-  payload; the workspace UI should pass it through to the BFF and let the
-  platform decide validity. A client-side allowlist drifts from the real
-  token registry and silently breaks once real tokens are minted.
+  payload; the workspace UI should pass it through to the hosted gateway/auth
+  path and let the platform decide validity. A client-side allowlist drifts
+  from the real token registry and silently breaks once real tokens are minted.
 
 ## Vuilder Vertical Onboarding
 

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

@@ -8,10 +8,10 @@ description: "Reasoning from a CLI-generated Builder workspace rather than the m
 Use this skill when reasoning from a CLI-generated Builder workspace rather than
 the monorepo or a live tenant runtime.
 
-- A generated workspace is a developer-local authoring client of PandaWork, not
+- A generated workspace is a developer-local authoring client of MinuteWork, not
   the runtime itself.
 - Treat these as separate surfaces with different trust boundaries:
-  - developer-local broker/orchestrator (`pandawork session ...`)
+  - developer-local broker/orchestrator (`minutework session ...`)
   - runtime-local Builder host inside the tenant runtime
   - runtime-local non-coding assistant inside the tenant product
 - The clearest layering model is:
@@ -22,13 +22,20 @@ the monorepo or a live tenant runtime.
 - `tenant-app`, optional `sidecar`, and the optional `mobile` starter are
   implementation surfaces inside the tenant product, not the whole architecture.
 - `tenant-app` is the combined public plus private web starter.
+- In `tenant-app`, keep MinuteWork web auth/data access inside the thin
+  `src/mw/` substrate and `@minutework/web-auth`. Product UI may call that
+  substrate, but it must not recreate platform-session BFF routes, platform
+  credential login, or browser-exposed platform/runtime tokens.
+- `tenant-app` runtime data access goes through `mw.query(...)` and
+  `mw.action(..., { idempotencyKey })` against manifest-declared
+  `webCustomerExposed` / `web_customer_exposed` customer surfaces.
 - A mobile / native client (Expo, React Native, native iOS/Android) is a
   standalone-client exception authored in the `mobile` starter, not in
   `tenant-app` or `sidecar`. It is a direct platform API client that consumes
   the platform native-token API (`/api/v1/native/...`) directly with a
-  platform-issued native session token, rather than the `tenant-app` BFF cookie
-  session. The mobile starter remains npm-owned standalone app code and should
-  not be added to the generated root `pnpm-workspace.yaml`.
+  platform-issued native session token, rather than the `tenant-app` web SDK /
+  hosted-cookie session. The mobile starter remains npm-owned standalone app
+  code and should not be added to the generated root `pnpm-workspace.yaml`.
 - If the `mobile` starter is enabled (`starters.mobile.enabled`), read
   `standalone-mobile-client/SKILL.md` before proposing the mobile surface.
 - `vuilder-public-site` is a Vuilder-owned public-site authoring workspace for

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

@@ -17,7 +17,7 @@ Use this skill when choosing between configuration, app-pack changes, overlays,
 - 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
-  subsystem and PandaWork should compile a governed control surface around it.
+  subsystem and MinuteWork should compile a governed control surface around it.
 - Use `external_repo_intake` only when no reviewed capability skill or cleaner
   `attached_app` path fits. Any repo intake must stay inside the bounded Builder
   sandbox.
@@ -26,7 +26,7 @@ Use this skill when choosing between configuration, app-pack changes, overlays,
 - 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 PandaWork artifacts.
+  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

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

@@ -1,13 +1,13 @@
 ---
 name: openclaw-skill-importer
-description: "Importing OpenClaw or other third-party skill or plugin material into governed PandaWork artifacts."
+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 PandaWork artifacts before using it.
+- Translate imported OpenClaw material into governed MinuteWork artifacts before using it.
 - 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:

package/assets/claude-local/skills/project-overview-and-strategy/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: project-overview-and-strategy
-description: "Broad project questions: what this workspace is, what PandaWork can build, agentic apps, OSS adoption, ontology, or network effects."
+description: "Broad project questions: what this workspace is, what MinuteWork can build, agentic apps, OSS adoption, ontology, or network effects."
 ---
 
 # Project Overview And Strategy
@@ -8,7 +8,7 @@ description: "Broad project questions: what this workspace is, what PandaWork ca
 Use this skill before answering broad orientation or strategy questions such as:
 
 - "What is this project about?"
-- "What can we build with PandaWork?"
+- "What can we build with MinuteWork?"
 - "Can we build our own product or make an existing product agentic?"
 - "How do OSS products fit?"
 - "What is the ontology or network effect?"
@@ -48,14 +48,14 @@ needed:
 
 ## Compact Project Answer
 
-PandaWork Builder is a governed local authoring workspace for building or
-extending PandaWork app packs. An app pack is the product unit. The workspace
+MinuteWork Builder is a governed local authoring workspace for building or
+extending MinuteWork app packs. An app pack is the product unit. The workspace
 usually composes schemas, manifests, `mw.core.site`, runtime capabilities,
 agents, overlays, and published-web flows before writing bespoke code.
 
-PandaWork supports two legitimate paths:
+MinuteWork supports two legitimate paths:
 
-- Build a product natively on PandaWork.
+- Build a product natively on MinuteWork.
 - Wrap an existing product or OSS system with a governed, agentic control
   surface.
 
@@ -75,7 +75,7 @@ separate client experiences.
 
 ## Strategic Positioning
 
-PandaWork is most differentiated when identity, shared meaning, external
+MinuteWork is most differentiated when identity, shared meaning, external
 collaboration, AI agents, and foreign systems participate in the same governed
 substrate:
 
@@ -92,7 +92,7 @@ substrate:
   deployed, and use sidecar bridge code plus runtime agents/tool packs to make
   it governed and agentic.
 - Build-native is appropriate when the capability is central, reusable, and
-  should become PandaWork substrate. Greenfield is last after existing
+  should become MinuteWork substrate. Greenfield is last after existing
   substrate, reviewed skills, app-pack extension, OSS adoption, and
   `attached_app` have been considered.