@slaw-ai/server 2026.611.0

package/skills/slaw-create-agent/references/api-reference.md

@@ -0,0 +1,110 @@
+# Slaw Create Agent API Reference
+
+## Core Endpoints
+
+- `GET /llms/agent-configuration.txt`
+- `GET /llms/agent-configuration/:adapterType.txt`
+- `GET /llms/agent-icons.txt`
+- `GET /api/squads/:squadId/agent-configurations`
+- `GET /api/squads/:squadId/skills`
+- `POST /api/squads/:squadId/skills/import`
+- `GET /api/agents/:agentId/configuration`
+- `POST /api/agents/:agentId/skills/sync`
+- `POST /api/squads/:squadId/agent-hires`
+- `POST /api/squads/:squadId/agents`
+- `GET /api/agents/:agentId/config-revisions`
+- `POST /api/agents/:agentId/config-revisions/:revisionId/rollback`
+- `POST /api/issues/:issueId/approvals`
+- `GET /api/approvals/:approvalId/issues`
+
+Approval collaboration:
+
+- `GET /api/approvals/:approvalId`
+- `POST /api/approvals/:approvalId/request-revision` (operator)
+- `POST /api/approvals/:approvalId/resubmit`
+- `GET /api/approvals/:approvalId/comments`
+- `POST /api/approvals/:approvalId/comments`
+- `GET /api/approvals/:approvalId/issues`
+
+## `POST /api/squads/:squadId/agent-hires`
+
+Request body matches agent create shape:
+
+```json
+{
+  "name": "Engineering Lead",
+  "role": "engineering_lead",
+  "title": "Engineering Lead",
+  "icon": "crown",
+  "reportsTo": "uuid-or-null",
+  "capabilities": "Owns architecture and engineering execution",
+  "desiredSkills": ["vercel-labs/agent-browser/agent-browser"],
+  "adapterType": "claude_local",
+  "adapterConfig": {
+    "cwd": "/absolute/path",
+    "model": "claude-sonnet-4-5-20250929"
+  },
+  "instructionsBundle": {
+    "entryFile": "AGENTS.md",
+    "files": {
+      "AGENTS.md": "You are the Engineering Lead..."
+    }
+  },
+  "runtimeConfig": {
+    "heartbeat": {
+      "enabled": false,
+      "wakeOnDemand": true
+    }
+  },
+  "budgetMonthlyCents": 0,
+  "sourceIssueId": "uuid-or-null",
+  "sourceIssueIds": ["uuid-1", "uuid-2"]
+}
+```
+
+Response:
+
+```json
+{
+  "agent": {
+    "id": "uuid",
+    "status": "pending_approval"
+  },
+  "approval": {
+    "id": "uuid",
+    "type": "hire_agent",
+    "status": "pending",
+    "payload": {
+      "desiredSkills": ["vercel-labs/agent-browser/agent-browser"]
+    }
+  }
+}
+```
+
+If squad setting disables required approval, `approval` is `null` and the agent is created as `idle`.
+
+`desiredSkills` accepts squad skill ids, canonical keys, or a unique slug. The server resolves and stores canonical squad skill keys.
+Leave timer heartbeats disabled by default. Only set `runtimeConfig.heartbeat.enabled=true` and include an `intervalSec` when the role truly needs scheduled recurring work or the user explicitly requested it.
+
+## Approval Lifecycle
+
+Statuses:
+
+- `pending`
+- `revision_requested`
+- `approved`
+- `rejected`
+- `cancelled`
+
+For hire approvals:
+
+- approved: linked agent transitions `pending_approval -> idle`
+- rejected: linked agent is terminated
+
+## Safety Notes
+
+- Config read APIs redact obvious secrets.
+- `pending_approval` agents cannot run heartbeats, receive assignments, or create keys.
+- All actions are logged in activity for auditability.
+- Use markdown in issue/approval comments and include links to approval, agent, and source issue.
+- After approval resolution, requester may be woken with `SLAW_APPROVAL_ID` and should reconcile linked issues.

package/skills/slaw-create-agent/references/baseline-role-guide.md

@@ -0,0 +1,168 @@
+# Baseline Role Guide (No-Template Fallback)
+
+Use this guide when no template under `references/agents/` is a close fit for the role you are hiring. It gives you a concrete structure for drafting a new `AGENTS.md` from scratch without asking the board for prompt-writing help.
+
+The guide is not itself a template — copy the section outline below into your draft and fill each section with role-specific content. Aim for roughly 60–150 lines of `AGENTS.md`; longer is fine for lens-heavy expert roles, shorter is fine for narrow operational roles.
+
+---
+
+## Section outline
+
+Every new-role `AGENTS.md` should cover these sections in order. Remove a section only if you can justify why the role does not need it.
+
+1. Identity and reporting line
+2. Role charter
+3. Operating workflow
+4. Domain lenses
+5. Output / review bar
+6. Collaboration and handoffs
+7. Safety and permissions
+8. Done criteria
+
+### 1. Identity and reporting line
+
+One or two sentences. Name the agent, its role, and its squad. State the reporting line. Point at the Slaw heartbeat skill as the source of truth for the wake procedure.
+
+Reference phrasing:
+
+```md
+You are agent {{agentName}} ({{roleTitle}}) at {{squadName}}.
+
+When you wake up, follow the Slaw skill - it contains the full heartbeat procedure.
+
+You report to {{managerTitle}}.
+```
+
+### 2. Role charter
+
+A short paragraph plus a bullet list. Answer:
+
+- What does this agent own end-to-end?
+- What problem does it solve for the squad?
+- What is explicitly out of scope? What should it decline, hand off, or escalate?
+
+A good charter lets the agent say no to work that is not its job. Avoid generic "helps the team" framing — name the specific artifacts, decisions, or surfaces the agent is accountable for.
+
+### 3. Operating workflow
+
+How the agent runs a single heartbeat end-to-end. Cover:
+
+- how it decides what to work on (scope to assigned tasks; do not freelance)
+- what a progress comment must include (status, what changed, next action)
+- when to create child issues instead of polling or batching
+- how to mark work as `blocked` with owner + action
+- when to hand off to a reviewer or manager
+- the requirement to always leave a task update before exiting a heartbeat
+
+Include this line verbatim for any execution-heavy role:
+
+> Start actionable work in the same heartbeat; do not stop at a plan unless planning was requested. Leave durable progress with a clear next action. Use child issues for long or parallel delegated work instead of polling. Mark blocked work with owner and action. Respect budget, pause/cancel, approval gates, and squad boundaries.
+
+### 4. Domain lenses
+
+5 to 15 named lenses the agent applies when making judgment calls. Lenses are short labels with a one-line explanation. They let the agent cite its reasoning in comments ("applying the Fitts's Law lens, the primary CTA is too small").
+
+Lenses should be specific to the role. Examples of what good lenses look like:
+
+- **UX designer**: Nielsen's 10, Gestalt proximity, Fitts's Law, Jakob's Law, Tesler's Law, Recognition over Recall, Kano Model, WCAG POUR.
+- **Security engineer**: STRIDE, OWASP Top 10, least-privilege, blast radius, defence in depth, secrets in process memory vs disk, auditability, LLM prompt-injection surface, supply-chain trust.
+- **Data engineer**: backpressure, idempotency, exactly-once vs at-least-once, schema evolution, freshness vs completeness, lineage, cost-per-query.
+- **Ops/SRE**: error budgets, blast radius, rollback path, MTTR, canary vs full deploy, observability-before-launch, runbook hygiene.
+- **Customer support**: severity triage, reproducibility bar, known-issue dedup, empathy before explanation, close-loop signal to engineering.
+
+If you cannot list five role-specific lenses, the role is probably a variant of an existing template — use the adjacent-template path instead of the generic fallback.
+
+### 5. Output / review bar
+
+Describe what a good deliverable from this role looks like. Be concrete — give the bar a stranger could judge against:
+
+- what shape the output takes (PR, spec, report, ticket triage, screenshot bundle)
+- what it must include (repro steps, evidence, tradeoffs, acceptance criteria, sign-off from X)
+- what "not done" looks like (e.g., "a flow that works but looks unstyled is not done")
+- what never ships (e.g., "no secrets in plain text", "no deploys without a rollback path")
+
+### 6. Collaboration and handoffs
+
+Name the other agents or roles this agent must route to, and when:
+
+- UX-facing changes → involve `[UXDesigner](/PAP/agents/uxdesigner)`
+- security-sensitive changes, permissions, secrets, auth, adapter/tool access → involve `[SecurityEngineer](/PAP/agents/securityengineer)`
+- browser validation / user-facing workflow verification → involve `[QA](/PAP/agents/qa)`
+- skill architecture / instruction quality → involve the Skill Consultant
+- engineering/runtime changes → involve the Engineering Lead and a coder
+
+Only list routes that apply to this role. Do not force every agent to CC the board.
+
+### 7. Safety and permissions
+
+Default to least privilege. For each new role, explicitly state:
+
+- what the role is allowed to do that other agents cannot
+- what the role must never do (examples: post to external services, modify shared infra, delete data without approval)
+- how credentials/secrets are handled (never in plain text unless the adapter requires it; use `desiredSkills` or environment-injected credentials)
+- whether a timer heartbeat is needed (default: off; only enable with an explicit justification and `intervalSec`)
+- which `desiredSkills` the role needs on day one — install missing skills before submitting the hire
+
+### 8. Done criteria
+
+How the agent verifies its own work before marking an issue done or handing it to a reviewer. Be concrete:
+
+- the smallest check that proves the work (tests run, screenshots captured, query executed, spec reviewed)
+- what evidence goes in the final comment
+- who the task is reassigned to on completion (reviewer, manager, or `done`)
+
+---
+
+## Anti-patterns to avoid
+
+- **Over-generic prompts.** "Be helpful, be thorough, be correct" is worthless — the next agent drafts a better version by reading the template you adapted from. Write role-specific guidance only.
+- **Lens dumping.** Copying every lens from an expert template into an unrelated role adds noise and burns context. Five well-chosen lenses beat fifteen irrelevant ones.
+- **Permission sprawl.** Do not grant write access, admin endpoints, or broad skill sets "just in case." Grant exactly what the role needs.
+- **Secrets in agent config.** Do not embed long-lived tokens, API keys, or private URLs in `adapterConfig`, `instructionsBundle`, or legacy prompt fields when environment injection or a scoped skill can carry the capability instead.
+- **Silent timer heartbeats.** A timer heartbeat burns budget every interval. If the role has no scheduled work, leave it off.
+- **Bypassing governance.** Never skip `sourceIssueId`, reporting line, icon, or approval flow to ship faster. Hires without these are hard to audit and hard to hand off.
+- **Copying another squad's prompt verbatim.** Placeholders like `{{squadName}}`, `{{managerTitle}}`, and `{{issuePrefix}}` must be replaced with this squad's values before submitting the hire.
+
+---
+
+## Minimal scaffold
+
+Copy this scaffold into your draft and fill each section. Delete the comments (`<!-- -->`) once each section is specific.
+
+```md
+You are agent {{agentName}} ({{roleTitle}}) at {{squadName}}.
+
+When you wake up, follow the Slaw skill. It contains the full heartbeat procedure.
+
+You report to {{managerTitle}}. Work only on tasks assigned to you or explicitly handed to you in comments.
+
+## Role
+
+<!-- One paragraph + bullets: what this agent owns, what it declines/escalates. -->
+
+## Working rules
+
+<!-- Scope, progress comments, child issues, blockers, handoffs, heartbeat exit rule. -->
+
+## Domain lenses
+
+<!-- 5-15 named lenses that guide judgment for this role. Cite by name in comments. -->
+
+## Output bar
+
+<!-- What a good deliverable looks like. Include concrete negative examples. -->
+
+## Collaboration
+
+<!-- Which agents to route to and when. -->
+
+## Safety and permissions
+
+<!-- Least privilege. Heartbeat default off. Secrets handling. desiredSkills. -->
+
+## Done
+
+<!-- How you verify before marking done. What evidence goes in the final comment. -->
+
+You must always update your task with a comment before exiting a heartbeat.
+```

package/skills/slaw-create-agent/references/draft-review-checklist.md

@@ -0,0 +1,95 @@
+# Draft-Review Checklist
+
+Walk this checklist before submitting any `agent-hires` request. Fix each item that does not pass — do not submit a draft with open failures.
+
+Use it for every path: exact template, adjacent template, or generic fallback.
+
+---
+
+## A. Identity and framing
+
+- [ ] `name`, `role`, and `title` are set and consistent with each other
+- [ ] `AGENTS.md` names the agent, the role, and the squad in the first sentence
+- [ ] The first paragraph points at the Slaw skill as the source of truth for the heartbeat procedure
+- [ ] The reporting line (`reportsTo`) resolves to a real in-squad agent id
+- [ ] The `AGENTS.md` states the same reporting line in prose
+
+## B. Role clarity
+
+- [ ] `capabilities` is one concrete sentence about what the agent does — not a vague "assists with X"
+- [ ] The role charter in `AGENTS.md` names what the agent owns end-to-end
+- [ ] The charter names what the agent should decline, hand off, or escalate
+- [ ] A stranger reading `capabilities` plus the role charter can tell in 30 seconds what this agent is for
+
+## C. Operating workflow
+
+- [ ] `AGENTS.md` states the comment-on-every-touch rule
+- [ ] `AGENTS.md` states the "leave a clear next action" rule
+- [ ] `AGENTS.md` covers how to mark work `blocked` with owner + action
+- [ ] `AGENTS.md` covers handoff to reviewer or manager on completion
+- [ ] For execution-heavy roles (coders, operators, designers, security, QA), `AGENTS.md` includes the Slaw execution contract verbatim:
+  > Start actionable work in the same heartbeat; do not stop at a plan unless planning was requested. Leave durable progress with a clear next action. Use child issues for long or parallel delegated work instead of polling. Mark blocked work with owner and action. Respect budget, pause/cancel, approval gates, and squad boundaries.
+
+## D. Domain lenses and judgment
+
+- [ ] Expert roles list 5–15 named lenses with one-line explanations
+- [ ] Lenses are role-specific, not generic productivity advice
+- [ ] Simple operational roles do not carry copy-pasted lenses from expert templates
+
+## E. Output / review bar
+
+- [ ] `AGENTS.md` describes what a good deliverable looks like for this role
+- [ ] Negative examples are included where useful ("a flow that works but looks unstyled is not done")
+- [ ] Evidence expectations are concrete (tests, screenshots, repro steps, spec sections)
+
+## F. Collaboration routing
+
+- [ ] Cross-role handoffs are named only when the role actually touches that domain
+- [ ] UX-facing role or change → routes to `[UXDesigner](/PAP/agents/uxdesigner)`
+- [ ] Security-sensitive role, permissions, secrets, auth, adapters, tool access → routes to `[SecurityEngineer](/PAP/agents/securityengineer)`
+- [ ] Browser validation or user-facing verification → routes to `[QA](/PAP/agents/qa)`
+- [ ] Skill architecture / instruction quality changes → routes to the Skill Consultant when present
+- [ ] Engineering/runtime changes → routes to the Engineering Lead and a coder
+
+## G. Governance fields
+
+- [ ] `icon` is set to one of `/llms/agent-icons.txt` and fits the role
+- [ ] `sourceIssueId` (or `sourceIssueIds`) is set when the hire was triggered by an issue
+- [ ] `desiredSkills` lists only skills that already exist in the squad library, or will be installed first via the squad-skills workflow
+- [ ] Adapter config matches this Slaw instance (cwd, model, credentials) per `/llms/agent-configuration/<adapter>.txt`
+- [ ] Local managed-bundle adapters send custom instructions through top-level `instructionsBundle.files["AGENTS.md"]` and do not set `adapterConfig.promptTemplate` or `bootstrapPromptTemplate`
+- [ ] Placeholders like `{{squadName}}`, `{{managerTitle}}`, `{{issuePrefix}}`, and any URL stubs are replaced with real values
+
+## H. Safety and permissions (least privilege)
+
+- [ ] The hire grants only the access the role needs — no "just in case" permissions
+- [ ] No secrets are embedded in plain text in `adapterConfig`, `instructionsBundle`, or any legacy prompt field; prefer environment-injected credentials or scoped skills
+- [ ] Any `desiredSkills` or adapter settings that expand external-system access, browser/network reach, filesystem scope, or secret-handling capability are individually justified in the hire comment
+- [ ] `runtimeConfig.heartbeat.enabled` is `false` unless the role genuinely needs scheduled recurring work AND `intervalSec` is justified in the hire comment
+- [ ] `AGENTS.md` explicitly names anything the role must never do (external posts, shared infra changes, destructive ops without approval)
+- [ ] If the role may handle private disclosures or security advisories, the hire names a confidential workflow (dedicated skill or documented manual process) instead of relying on normal issue threads
+- [ ] No tool, skill, or capability is listed that this environment cannot actually provide
+
+## I. Done criteria
+
+- [ ] `AGENTS.md` states how the agent verifies its work before marking an issue done
+- [ ] `AGENTS.md` states who the task goes to on completion (reviewer, manager, or `done`)
+- [ ] `AGENTS.md` ends with the "always update your task with a comment" rule
+
+## J. Choice of instruction source was explicit
+
+- [ ] The hire comment states which path was used: exact template, adjacent template, or generic fallback
+- [ ] If an adjacent template was used, the comment names what was adapted (charter rewritten, lenses swapped, sections removed)
+- [ ] If the generic fallback was used, every section of the baseline role guide is present in the draft
+
+---
+
+## Failure modes to watch for
+
+- **Boilerplate pass-through.** If `AGENTS.md` reads like it could apply to any role, the charter and lenses are too generic — rewrite them.
+- **Quiet permission sprawl.** A big `desiredSkills` list or an open-ended adapter config usually means "just in case" access. Trim to what the charter needs.
+- **Capability expansion without review.** Browser, external-system, wide-filesystem, or secret-handling access hidden inside adapter config or `desiredSkills` must be called out explicitly in the hire comment.
+- **Timer-heartbeat-by-default.** If you enabled a timer heartbeat, the hire comment must state why schedule-based wake is required.
+- **No confidential path for sensitive work.** Roles that may receive private advisories or incident details need a private workflow, not normal issue comments.
+- **Missing governance fields.** A hire without `sourceIssueId`, `icon`, or a resolvable reporting line is hard to audit later.
+- **Unreplaced placeholders.** `{{squadName}}`, `{{managerTitle}}`, and URL stubs in a submitted draft are the most common rejected-hire defect — grep the draft for `{{` before submitting.

package/skills/slaw-create-plugin/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: slaw-create-plugin
+description: >
+  Create and develop external Slaw plugins with the CLI-first workflow.
+  Use when scaffolding a new plugin, working on a local plugin against a running
+  Slaw instance, or updating plugin authoring docs. Covers `slaw
+  plugin init`, the local install loop via `slaw plugin install <path>`,
+  worker/UI rebuild and reload semantics, and the required success checklist.
+---
+
+# Create and develop a Slaw plugin
+
+Use this skill when the task is to create, scaffold, or iterate on a Slaw plugin against a local Slaw instance.
+
+## 1. Default: build the plugin OUTSIDE Slaw core
+
+Plugins are their own packages. Unless the task **explicitly** asks for a bundled in-repo example, do not add plugin source under `packages/plugins/` in this repo.
+
+- Scaffold the plugin into a directory outside the Slaw checkout (e.g. `~/dev/slaw-plugins/<name>`).
+- Install it into the running Slaw instance by local absolute path.
+- Edit code in the external package; let Slaw pick up rebuilt output.
+
+Only edit Slaw core itself when the user asks to surface a plugin as a bundled example (`server/src/routes/plugins.ts`, in-repo example lists, docs).
+
+## 2. Ground rules
+
+Reference docs when you need detail:
+
+1. `doc/plugins/PLUGIN_AUTHORING_GUIDE.md`
+2. `packages/plugins/sdk/README.md`
+3. `doc/plugins/PLUGIN_SPEC.md` — future-looking context only
+
+Current runtime assumptions:
+
+- plugin workers are trusted code
+- plugin UI is trusted same-origin host code
+- worker APIs are capability-gated
+- plugin UI is not sandboxed by manifest capabilities
+- no host-provided shared plugin UI component kit yet
+- `ctx.assets` is not supported in the current runtime
+
+## 3. CLI-first scaffold workflow
+
+Use `slaw plugin init`. Do not invoke the scaffold package node entrypoint by hand unless the CLI command is unavailable in the environment.
+
+```bash
+slaw plugin init @acme/my-plugin --output ~/dev/slaw-plugins
+```
+
+Useful flags (all optional):
+
+- `--output <dir>` — parent directory; the command creates `<dir>/<unscoped-name>/`. Defaults to the current directory.
+- `--template <default|connector|workspace|environment>` — starter template.
+- `--category <connector|workspace|automation|ui|environment>` — manifest category.
+- `--display-name <name>`, `--description <text>`, `--author <name>` — manifest metadata.
+- `--sdk-path <path>` — snapshot the local SDK from a Slaw checkout into `.slaw-sdk/` (useful when developing against an unreleased SDK).
+
+On success the command prints the exact next commands (`cd`, `pnpm install`, `pnpm dev`, `slaw plugin install <abs-path>`). Run them in order.
+
+If `slaw` is not on PATH in your environment, fall back to:
+
+```bash
+pnpm --filter @slaw-ai/create-slaw-plugin build
+node packages/plugins/create-slaw-plugin/dist/index.js @acme/my-plugin \
+  --output /absolute/path \
+  --sdk-path /absolute/path/to/slaw/packages/plugins/sdk
+```
+
+## 4. Local install + rebuild loop
+
+In the scaffolded plugin folder:
+
+```bash
+pnpm install
+pnpm dev            # esbuild --watch: rebuilds dist/manifest.js, dist/worker.js, dist/ui/
+slaw plugin install /absolute/path/to/my-plugin
+```
+
+Notes:
+
+- `slaw plugin install` auto-detects local paths (absolute, `./`, `../`, `~`, or an existing relative folder) and forwards `isLocalPath: true` to the server. Pass `--local` to force local mode if the heuristic is ambiguous.
+- Paths are resolved to absolute paths before being sent to the server.
+- The server watches built outputs (`dist/`) for local-path plugins and restarts the plugin worker on rebuild — you do not need to reinstall after every edit.
+- UI hot reload via the SDK dev server (`pnpm dev:ui`, port `4177`) is optional and template-dependent; only mention it if the template wires `devUiUrl` and you verified it works end to end.
+- `--version` only applies to npm package installs. Combining it with a local path is an error.
+
+After install, inspect with:
+
+```bash
+slaw plugin list
+slaw plugin inspect <plugin-key>
+```
+
+## 5. After scaffolding, sanity-check the package
+
+Open and confirm:
+
+- `src/manifest.ts` — declared capabilities and slots
+- `src/worker.ts` — worker entry
+- `src/ui/index.tsx` — UI entry (if applicable)
+- `tests/plugin.spec.ts` — placeholder test
+- `package.json` — `slawPlugin` block points at `dist/manifest.js`, `dist/worker.js`, `dist/ui/`
+
+Make sure the plugin:
+
+- declares only supported capabilities
+- does not use `ctx.assets`
+- does not import host UI component stubs
+- keeps UI self-contained
+- uses `routePath` only on `page` slots
+
+## 6. Verification (run before declaring success)
+
+From the plugin folder:
+
+```bash
+pnpm typecheck
+pnpm test
+pnpm build
+```
+
+If the plugin is already running under `pnpm dev`, you can keep the watcher up and run `pnpm typecheck` and `pnpm test` in a separate shell.
+
+If you changed Slaw SDK/host/plugin runtime code in addition to the plugin, also run the relevant Slaw workspace checks.
+
+## 7. Success checklist (report this back)
+
+When you finish a local plugin task, report:
+
+- **Scaffold path** — absolute path of the created plugin folder.
+- **Commands run** — the exact `slaw plugin init`, `pnpm install`, `pnpm dev`, `slaw plugin install <path>` invocations (and any verification commands).
+- **Install status** — output of `slaw plugin list` / `plugin inspect` (plugin key, version, status). Note if `status` is anything other than `ready` and include `lastError`.
+- **Tests / build result** — `pnpm typecheck`, `pnpm test`, `pnpm build` pass/fail with the failing output if any.
+- **Reload limitations** — call out anything that did not hot-reload (e.g. manifest changes required a reinstall, UI dev server was not wired, etc.).
+
+If any item is missing, mark it as such — do not silently skip.
+
+## 8. When NOT to edit Slaw core
+
+Do not add the plugin under `packages/plugins/` or update bundled-example wiring unless the user explicitly asks for a bundled example. Local-path installs are the supported development model; npm packages are the production deployment path.
+
+If the user does ask for a bundled example, also update:
+
+- `server/src/routes/plugins.ts` example list
+- any docs that enumerate in-repo example plugins
+
+## 9. Documentation expectations
+
+When authoring or updating plugin docs:
+
+- distinguish current implementation from future spec ideas
+- be explicit about the trusted-code model
+- do not promise host UI components or asset APIs
+- prefer local-path development + npm-package deployment guidance over repo-local workflows