@songsid/agend 2.3.0-beta.2 → 2.3.0-beta.20

package/dist/general-knowledge/skills/web-appearance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: web-appearance
-description: How you look on the AgEnD web dashboard — check it, change your own theme, identity card, identity colour and widgets, play Canvas Worker effects in your chat (and offer a Try), preview the result, share it as a mod
-roles: [worker]
+description: How you look on the AgEnD web dashboard — check it, change your own theme, identity card, identity colour and widgets, set an ambient effect (falling petals, click stars), play Canvas Worker effects in your chat (and offer a Try), preview the result, share it as a mod; and, for General, changing Settings → Web appearance for the user
+roles: [general, worker, classic]
 ---
 
 ## What it is
@@ -14,15 +14,52 @@ can shape how you look there — **only your own look, and only on the surfaces
 | Your name and role line | display name, description | `set_display_name`, `set_description` |
 | Your status stamp | persona emoji | `set_persona_emoji` (see the `persona-emoji` skill) |
 | Your chat | theme: colours, accent, bubbles, font, background picture, working label | `set_web_theme`, `set_web_theme_asset` |
+| The whole page, while your chat is open | your theme's colours on the sidebar, the header, the usage rail (a phone: the drawer, the header, the tabs) — colours only | `set_web_theme` (`page`) |
 | Your face and ring | theme picture and accent | `set_web_theme`, `set_web_theme_asset` |
 | Your identity card | portrait, banner, tagline, bio | `set_web_theme` (`card.*`), `set_web_theme_asset` |
 | Your identity colour | the colour people find you by in the sidebar, and where it shows (name, bar, ring) | `set_web_theme` (`identity`) |
 | Your chat header strip and Details page | widgets: small panels of facts the dashboard draws | `set_web_widget`, `remove_web_widget` |
+| An ambient effect in your chat | falling petals, snow, rising lanterns, twinkles, stars where a person clicks — data only, drawn by the dashboard | `set_web_ambient`, `clear_web_ambient` |
 | A file of your look | a mod: export yours, or propose one for a person | `export_web_mod`, `propose_web_mod` |
-| Effects in your chat | Canvas Worker animations, and Try cards a local admin may start | `upload_web_effect`, `apply_web_effect`, `preview_web_effect`, … (see Effects) |
+| Effects in your chat | Canvas Worker animations, and Try cards an admin outside the public link may start | `upload_web_effect`, `apply_web_effect`, `preview_web_effect`, … (see Effects) |
 
 None of these tools takes a target: they always act on you. You can't change another instance, the dashboard's own
-chrome, a person's sidebar widget, or a person's custom CSS.
+chrome (beyond your colours on it while your chat is open), a person's sidebar widget, or a person's custom CSS.
+
+## For the user: Settings → Web appearance (General, coordinators, full)
+
+If you are General (or a coordinator or full profile), you can change the user's **Settings → Web appearance** for
+them, exactly as the page changes it: the same checks, the same refusals. Custom CSS keeps its safe rules: no remote
+URLs, assets only as `url("asset:<id>")`, at most 64 KiB. Other instances can't; they shape only their own look (the rest
+of this skill).
+
+1. **Read first:** `get_web_settings` returns a `summary` in plain words (tell the user from it), the values, and
+   `people`: the host operator and everyone who has signed in. Host settings are everyone's on this host. Custom CSS and
+   effect slots are one person's own: pass `person` as the entry whose id is the user's (`person:<adapter>:<their id>`),
+   else the host operator's are changed.
+2. **One change per call:** `set_web_settings({ person?, change })`, where `change.what` is one of:
+
+| `what` | Changes | Example |
+|---|---|---|
+| `host` | `themes_shown`, `card_size` (s/m/l), `card_sizes` ({instance: s/m/l}), `page_colours` ({instance: page/chat}), `colour_places` (name/bar/ring), `colours_off`, `sidebar_widget` ({spec, data}) — null puts one back to its default | `{ what: "host", set: { colour_places: ["name","ring"] } }` |
+| `agent_colour` | one agent's colour (`preset:<name>` or `#rrggbb`) and places; null resets each | `{ what: "agent_colour", instance: "atlas", colour: "preset:teal" }` |
+| `page_colours` | where one agent's theme colours go: `page` (the whole page), `chat` (only its chat) or `agent` (its own `page.on`) — as ⋯ → Page colours sets it | `{ what: "page_colours", instance: "atlas", choice: "chat" }` |
+| `banner_focus` | which part of one agent's cropped card banner stays in view: `focus` 0 (top) … 100 (bottom), 50 the centre; it wins over the agent's own `card.bannerFocus`; null follows the agent's again | `{ what: "banner_focus", instance: "atlas", focus: 20 }` |
+| `custom_css` | `save` (with `text`): goes **on trial**. It waits until they open the dashboard (up to 10 minutes; never opened, it goes back unseen), then goes back by itself 20 s after it is on their screen unless kept (#2198). `keep` (with `trial`: the id `save` returned — a different trial on now, say one they saved on their page since, is refused with `trial_mismatch`, never kept instead; or, kept after that 20 s ran out, it is put back in force as `use` of it), `revert` (the trial), `use` (with `version`: an earlier saved one, at once), `off` | `{ what: "custom_css", action: "save", text: "…" }`; tell them to open the dashboard and look, then `keep` (with that `trial`) only when they say so — a `keep` that comes too late (`not_on_trial`) means use `use` with the version from `get_web_settings` |
+| `mod` | an agent's proposal: `review` (instance → `stage`, `plan`, `plan_hash`), then `install` (stage, plan_hash, `include`: the parts, `target`: the agent); `cancel`, `dismiss`, `uninstall` (id) | review, show the user the plan, install only what they asked for — never custom CSS unasked. A person has one review open at a time: while theirs is open (`mod_review_open`) ask them to finish it; a mod they imported from a file is theirs to install (`mod_not_from_an_agent`) |
+| `effect` | `apply` (instance, id, params?) or `remove` (instance, id?) an effect on a chat | |
+| `ambient` | one agent's ambient effect, set for the user: `ambient` is the same spec as `set_web_ambient`'s (it replaces the one of its kind, and the agent can't change it after); `ambient: null` clears (`which`: `loop` or `click`, default both) | `{ what: "ambient", instance: "atlas", ambient: { preset: "fall", glyphs: ["🌸","❀","✿"] } }` |
+| `effect_slot` | a person's `sidebar` / `header` / `page` / `box` / `cursor` effect (an id, or null) | |
+| `restore_defaults` | the host settings back to their defaults, and the person's custom CSS off | |
+
+3. **Say what changed** in the user's words (read again if unsure). A refusal says why: the same words the page would
+   show.
+
+**Only the person can do these, on the page:**
+- choose a file from their computer: import a mod file, upload an effect folder, add a CSS asset or a card picture;
+- this browser's own switches: custom CSS off on this device, pausing effect playback;
+- download an export;
+- the card upload limits (fleet configuration; a raise waits for an admin's confirmation).
 
 ## Look first
 
@@ -39,7 +76,7 @@ chrome, a person's sidebar widget, or a person's custom CSS.
   (`avatar.png`, `portrait.png`, …), and returns both lists of paths. Read the SVGs for exact colours, geometry and
   text, and the pictures as images. Only your own pictures are there.
 - `get_web_theme` — your stored theme, the token defaults it is drawn over, your uploaded pictures (`id`, `slot`), and
-  `limits` (changes and uploads left, each picture slot's size limits, your picture quota).
+  `limits` (changes left, each picture slot's size limits, your picture quota).
 
 ## What wins over what
 
@@ -69,15 +106,26 @@ Typed values only; anything else is refused with `{ errors: [{ path, problem }]
 - `identity`: `{ color?, show? }`: your identity colour and where it shows.
   - `color` is a preset (`red`, `orange`, `amber`, `lime`, `green`, `teal`, `cyan`, `blue`, `indigo`, `violet`, `pink`,
     `slate`, each readable in light and dark) or `#rrggbb`.
-  - `show` is a list of `name`, `bar` and `ring` (`[]` for nowhere). Left out, the host's default applies (ring and bar).
+  - `show` is a list of `name`, `bar` and `ring` (`[]` for nowhere). Left out, the host's default applies (name, bar and ring).
   - A person's choice for you in the dashboard always wins, field by field, and their Reset brings yours back.
     `get_web_appearance` says which is in force.
+- `page` (#2196): `{ on?: true | false, sidebar?: { light?, dark? } }` — `on: true` puts your colours (bg, surface, text,
+  text2, accent; the sidebar's own colour per mode in `sidebar`, else your `bg`) on **the whole page while your chat,
+  View, Log or Details is open**: the sidebar, the header, the usage rail; on a phone the drawer, the header and the
+  tabs. Colours only: never fonts, pictures or layout, and **AgEnD's status colours** (the Needs you count, the state
+  dots, errors, the focus ring — `get_web_theme`'s `status_colors`) are never yours to change. With `on: true` the
+  contrast check adds: `text` and `text2` 4.5:1 and `accent` 3:1 on the sidebar, and every status colour 3:1 on the
+  sidebar and on `bg`. A person's choice for you (⋯ → **Page colours**: your choice, the whole page, only your chat)
+  wins; viewers with agents' themes off or `?safe=1` see the page's own look.
+- For a person's **custom CSS** (#2199): while an agent's Chat, View, Log or Details is open, `<body>` has
+  `data-agent="<instance name>"` (none elsewhere), set in the same render as the page — so a person's stylesheet can
+  follow the open agent: `body[data-agent="atlas"] { --bg-sidebar: … }`. It is the person's, not yours to set.
 - `bubble`: `{ radius: 0..24, border: "none" | "thin" | "accent" }`.
 - `font`: `"inter"`, `"system"` or `"mono"`.
 - `background`: `{ image: <asset id>, fit: "cover" | "contain", opacity: 0.05..1 }`.
 - `avatar`: an asset id — your face (below a person's upload).
 - `workingLabel`: 1..24 characters on one line, shown while you work instead of "is working…".
-- `card`: `{ portrait?, banner?, tagline?, bio? }` — see below.
+- `card`: `{ portrait?, banner?, tagline?, bio?, bannerFocus? }` — see below.
 
 Example:
 
@@ -100,6 +148,7 @@ the id is the hash of what is kept, so the same picture is the same id.
 | `avatar` | png, jpeg, webp, gif | 256 KiB, 4096 px a side |
 | `portrait` | png, jpeg, webp | set by the fleet (default 1024×1536, 1.5 MiB) |
 | `banner` | png, jpeg, webp | set by the fleet (default 1600×600, 768 KiB) |
+| `glyph` | png, webp, gif | 64 KiB, 128 px a side; at most 4 (for `set_web_ambient`'s `glyphs`) |
 
 A picture holds one slot: upload it again for another slot only if it is a different picture. `get_web_theme`'s
 `limits.asset_slots` has the limits in force and `limits.asset_quota` how many pictures you may keep. A picture your
@@ -114,6 +163,18 @@ their own version of any field; theirs is shown instead of yours.
 The card goes **inside `set`**: `set_web_theme({ set: { card: { tagline, bio, portrait, banner } } })` (a top-level
 `card` argument is refused).
 
+**Your banner is cropped: never drawn wider than 5 : 1** (on a wider screen it is centred over a blurred copy) **nor
+narrower than 9 : 4** (which crops the sides). Make it **1600×600** (the default limit) and keep faces and text
+inside the **safe area: the middle 84% of the width × 53% of the height — 1350×320** — which every card shows on every
+screen and layout. `card.bannerFocus` (0 top … 100 bottom; default 50, the centre) moves that area up or down: put a face
+near the top at `bannerFocus: 0`. A person's focus (Edit profile, or General's `set_web_settings { what: "banner_focus" }`)
+wins over yours. `preview_web_appearance` draws the banner cropped at its focus, as the page does (an M card).
+
+**In your chat** the card is hidden until the person shows it (the card menu in the chat header: Show card, Show picture
+and bio). Shown, the banner sits right under the header and they can fold your portrait, tagline and bio away, keeping
+only the banner. Their choice,
+kept on their device; you cannot change it. So a banner that says who you are on its own reads well in your chat too.
+
 ## Your identity colour
 
 The colour people find you by in the sidebar, drawn on your name, a bar at your row's left edge and/or the ring around
@@ -124,7 +185,7 @@ your picture. Set yours with `set_web_theme({ set: { identity: { color, show } }
   themes) > your own bot's Discord **role** colour > an **automatic** soft colour chosen from your name (two instances
   may share one).
 - **Where it shows**: a person's choice for you > yours (`identity.show`; again only while themes are shown) > the
-  host's default (Settings → Web appearance; ring and bar unless changed).
+  host's default (Settings → Web appearance; name, bar and ring unless changed).
 - The host can **turn colours off** for everyone: nothing is drawn, and every pick, yours included, is kept for when
   they come back.
 - `get_web_appearance`'s `identity_color` shows what is in force: `color`, `source` (`person`, `agent`, `role`, `auto`),
@@ -174,6 +235,42 @@ in it can be clicked or focused.
 
 Then, as you go: `set_web_widget { "slot": "chat_header", "data": { "tests": 75 } }`.
 
+## Ambient effects
+
+An ambient effect is **data only**: you choose a preset and its glyphs, the dashboard draws them. No code runs, so it
+needs no Try, no preview consent and no measurement — use it for petals, snow, lanterns, sparkles and stars on a click.
+Use a Canvas Worker effect (below) only for what a preset can't express.
+
+`set_web_ambient { preset, glyphs, colors?, count?, duration?, size?, sway?, spread?, rotate?, opacity? }`:
+
+| `preset` | What it draws | `count` | `duration` (seconds, [min, max]) |
+|---|---|---|---|
+| `fall` | glyphs drifting down behind your chat, endlessly | 1..24 particles (default 12) | 4..30 (default [9, 19]) |
+| `rise` | the same, drifting up | 1..24 (12) | 4..30 ([9, 19]) |
+| `twinkle` | glyphs pulsing in place | 1..24 (12) | 1..10 ([2, 5]) |
+| `burst-on-click` | glyphs scattering from where a person clicks or taps in your chat | 4..16 per click (10) | 0.3..2 ([0.5, 0.9]) |
+
+- `glyphs`: 1..4, picked at random per particle — a string of 1..2 characters (an emoji, `✦`, `❀`), or `{ "asset": id }`,
+  a picture you uploaded with `set_web_theme_asset` to the `glyph` slot.
+- `colors`: 0..5 `#rrggbb` for text glyphs (default: your accent). `size`: [min, max] px, 10..40 (default [14, 22]).
+  `sway`: sideways drift for fall and rise, 0..80 px (40). `spread`: how far a burst scatters, [min, max] 20..120 px
+  ([34, 90]). `rotate`: 0..720 degrees over a run (300). `opacity`: [start, peak, end], each 0..1 ([0, 0.85, 0.15]).
+- Your chat holds **one looping ambient** (`fall`, `rise` or `twinkle`) **and one `burst-on-click`**: setting one
+  replaces only its own kind. `clear_web_ambient { which? }` clears `loop`, `click`, or both.
+- It is drawn **behind your messages** and never takes a click (a burst shows over them for a moment, then is gone).
+- Who sees it: everyone who shows agents' looks, the public link included. Not with "Show agents' themes, effects and
+  widgets" off, `?safe=1`, or on a device that chose to follow the system's reduced-motion setting while
+  the system asks for it. A hidden tab pauses it.
+- Like a theme: a change for the rate limit, refused while a person locked your look; one a person set is theirs
+  (`person_placed`). A person's Reset of your theme clears it. `get_web_appearance` shows it, and
+  `preview_web_appearance` draws the looping one, still, behind the bubbles.
+
+```json
+{ "preset": "fall", "glyphs": ["🌸", "❀", "✿"], "colors": ["#f4a7b9", "#ffd1dc"], "count": 12, "duration": [9, 19] }
+```
+
+Then stars on a click, alongside: `set_web_ambient { "preset": "burst-on-click", "glyphs": ["✦", "✧"] }`.
+
 ## Mods
 
 A mod is one file, `<name>-<version>.agendmod.json`, that carries a look: a theme with its pictures, card text,
@@ -183,29 +280,33 @@ everything in a mod and ticks what to apply.
 - `export_web_mod { name, version, title? }` writes **your own** look to `.agend/mods/<name>-<version>.agendmod.json`
   in your working directory and returns `{ path, bytes }`. It carries your theme with its pictures, the effects your
   theme places (with their params) when they are yours or shared with you, your own card text (not a person's card
-  fields), and the widgets you placed. A person's private effect placed on you stays out (`effects_omitted` counts it).
+  fields), the widgets and ambient effects you set yourself. A person's private effect placed on you stays out (`effects_omitted` counts it).
   It never carries custom CSS or the sidebar widget, which are a person's. `name` is a-z, 0-9 and -, `version` is
   MAJOR.MINOR.PATCH.
 - `propose_web_mod { file }` sends a mod file from your working directory (at most 8 MiB) for a person to review. It
   is checked whole and answers with its problems if it isn't valid. **A mod carrying custom CSS is refused**
   (`owner_css_not_from_agent`). A muted line in your chat says it was proposed. Nothing changes until a person
-  installs it. One proposal at a time: a new one replaces yours. It counts as an upload.
+  installs it. One proposal at a time: a new one replaces yours.
 - A widget a person placed from a mod is theirs: you may give it values (`set_web_widget` with `data`), but not replace
   or remove it (`person_placed`).
 
 The file format: `{ "format": "agend-mod", "v": 1, "manifest": { name, version, title, description?, author?,
-requires?: { agend: ">=X.Y.Z" }, contents: { theme?, identity?, widgets?: { chat_header?, details? }, effects? } },
+requires?: { agend: ">=X.Y.Z" }, contents: { theme?, identity?, widgets?: { chat_header?, details? }, ambient?, effects? } },
 "files": { "<path>": { "sha256", "b64" } } }`. Every file is listed with its sha256 and used by exactly one part, paths
-are lowercase with no `..`, and a theme names its pictures by path. The easiest way to get one right is to set your look
+are lowercase with no `..`, and a theme names its pictures by path (an ambient's glyph pictures too: `{ "asset": "<path>" }`). The easiest way to get one right is to set your look
 with the tools above, then `export_web_mod`.
 
 ## Limits
 
-- At least **30 s** between changes, at most **10 changes an hour**, at most **3 picture uploads an hour** — refused
-  with `rate_limited` and `retry_after_s`. Only an accepted change counts; a refused or invalid one costs nothing.
+- At least **30 s** between changes, at most **10 changes an hour** — refused with `rate_limited` and
+  `retry_after_s`. Only an accepted change counts; a refused or invalid one costs nothing.
+- Uploads (pictures, effects, proposed mods) are not counted. Each picture slot's size limits, your picture quota and
+  each file's own caps still apply; using a picture in your theme is a change.
 - Widget values (`set_web_widget` with `data` only): at least **10 s** apart, at most **180 an hour**, apart from the
   above.
-- Effects: `apply_web_effect` and `remove_web_effect` are changes; `upload_web_effect` and `propose_web_mod` are uploads.
+- `set_web_ambient` and `clear_web_ambient` are changes.
+- Effects: `apply_web_effect` and `remove_web_effect` are changes; `upload_web_effect` and `propose_web_mod` are not
+  counted.
   At most 10 effects and 8 MiB of your own, at most two placed in your chat.
 - Plan the whole look, check it in one `set_web_theme`, then preview — don't iterate change by change.
 
@@ -218,25 +319,47 @@ with the tools above, then `export_web_mod`.
 
 From a shell: `agend-agent theme get|set key=value…|set --json '<patch>'|clear <path>…|asset <slot> <file>|reset`,
 `agend-agent appearance`, `agend-agent appearance preview [light|dark]`, and
-`agend-agent widget set <slot> '<spec json>' ['<data json>']|data <slot> '<data json>'|remove [slot]`, and
+`agend-agent widget set <slot> '<spec json>' ['<data json>']|data <slot> '<data json>'|remove [slot]`,
+`agend-agent ambient set '<spec json>'|clear [loop|click]`, and
 `agend-agent mod export <name> <version> [title]|propose <file>`.
 
 ## Files in your working directory
 
-Asset uploads, effect directories and mod proposals must be inside your working directory. This includes your own
-AgEnD-managed workspace (`~/.agend/workspaces/<your-instance-name>`), used by ClassicBot and instances without a
-project directory. `web-assets/` and `web-effects/` are convenient staging folders, not required names. Paths are
-checked after resolving symlinks: for the supplied caller identity, another instance's workspace and all other AgEnD
-state remain forbidden, including
-`.env`, databases, `instances/`, `credential-profiles/` and `inbox/`. Symlinks cannot grant access outside your working
-directory or into protected state; uploaded files themselves must not be symlinks. Generated appearance previews and
-mod exports follow the same workspace boundary. The CLI takes its caller name from `AGEND_INSTANCE_NAME` and its
-working directory from the shell; these local checks do not isolate shells running as the same OS user.
+Asset uploads, effect directories and mod proposals must be inside your working directory. For an external project,
+use files there as before. For your own AgEnD-managed workspace under `~/.agend/workspaces/`, ordinary files there
+also work; no staging folder is required. This includes the standard `<your-instance-name>` folder (ClassicBot and
+instances without a project directory) and an exclusively configured folder with another name, such as instance
+`alpha` with `working_directory: ~/.agend/workspaces/alpha-home` in `fleet.yaml`. Its canonical configured path must
+not overlap another instance's configured or standard workspace, including persisted ClassicBot peers that are
+stopped or paused. The `workspaces/` root itself is not a workspace.
+
+General, adapter-specific General (such as `general-telegram`), and other configured working directories elsewhere
+inside the AgEnD state directory must stage inputs under **`web-assets/` or `web-effects/`**. For example, put a banner at
+`web-assets/banner.png` or an effect package at `web-effects/sparks/`, relative to that working directory. Its root
+and backend configuration folders are not upload areas. Generated previews and exported mods still use the fixed
+`.agend/appearance/` and `.agend/mods/` directories and can be read back or proposed there.
+
+The daemon uses its launch identity and configuration; the CLI resolves `AGEND_INSTANCE_NAME` against `fleet.yaml`.
+These checks require a canonical, exclusively owned directory: the state root, shared or overlapping configured
+working directories, another instance's directory, and the host's state stores never qualify. No tool argument can
+select an identity or working directory. Missing or unreadable ownership evidence refuses in-state access.
+
+Inside all admitted in-state areas, `.env`, databases and their WAL/SHM/journal files, `instances/`,
+`credential-profiles/`, `inbox/`, `web-files/`, `web-chat.json`, `chat-logs/`, backend credential/session/config files,
+and hidden files or folders are refused. The only hidden-directory exception is the two generated `.agend/`
+output directories above; their contents still undergo the sensitive-name checks. Hard-linked state files are also
+refused. Copy an intended asset into staging as a new regular file; do not link a private state file there.
+
+Paths are checked after resolving symlinks. A symlink named after General or a workspace, or in its managed parent
+path, cannot widen access; uploaded files themselves must not be symlinks. Containment still applies to relative and
+absolute paths and to each file in an effect package. The CLI name and current directory are controlled by its shell:
+these local checks prevent accidental uploads, but do not isolate shells running as the same OS user.
 
 ## Effects
 
 A Canvas Worker effect is a small animation drawn by code that runs in an isolated Worker: no page, no DOM, no
-network. You place effects **only in your own chat**; a person can place them in the regions an effect's manifest
+network. For petals, snow or stars on a click, an ambient effect (above) is simpler and plays without a Try. You place
+effects **only in your own chat**; a person can place them in the regions an effect's manifest
 allows. None of these tools takes a target.
 
 **The package** (CW1): a directory in your working directory with `effect.json` and `worker.js`, optionally
@@ -266,12 +389,18 @@ smallest valid `effect.json`:
   at most 4096 px a side, and **8,388,608 pixels in total** across the assets, poster and cursor together. A cursor is
   a square PNG of at most 64 px and 32 KiB (after metadata is stripped).
 
+**Reusable pointer example:** [`docs/examples/click-sparks`](https://github.com/songsid/AgEnD/blob/main/docs/examples/click-sparks.md) has a small two-file CW1 package: click for a burst, hold the primary button and move for a trail. Copy it into your working directory before uploading. Protected controls receive no pointer input; samples are coalesced (up to 60 Hz, 30 at reduced quality), so do not use it as a required click or drag control.
+
 **The tools:**
 
-- `upload_web_effect { dir }` → `{ id, warnings }`. It counts as an upload (3 an hour, shared with pictures and mods).
+- `upload_web_effect { dir }` → `{ id, warnings }`. Uploads are not counted; the effect's own size caps apply.
   **Your own** copies are at most **10 effects and 8 MiB**; effects a person shared with you don't count.
 - `list_web_effects` — your own effects and those a person shared with you: `id`, `name`, `title`, `regions`, `layer`,
-  `bytes`, `latest_profile`.
+  `bytes`, `latest_profile`. A currently placed effect also has `playback`: `status: "reported_blocked"` with closed
+  `reasons`, or `status: "unknown"`. `get_web_appearance.effects` lists your current placements with the same projection.
+  This means **some recent viewers reported blocked**, not all viewers and not a live permission or health check.
+  Observations expire after five minutes and stay in memory. Agents receive no viewer identifiers, counts, device/OS,
+  text, URLs or observation timestamps. Unknown means unknown; do not keep reapplying to bypass a viewer's choice.
 - `apply_web_effect { id, params? }` places one in your chat, **at most two at a time**, with the declared `params`
   (unknown or out of range → `effect_params`; regions without `chat` → `effect_region`). `remove_web_effect { id? }`
   takes one out, or all of them. Both are changes (30 s apart, 10 an hour), and are refused while a person has locked
@@ -293,14 +422,26 @@ smallest valid `effect.json`:
 
 - At most **3** effects play at once, at most **2** of them `front` (1 and 1 on a constrained device); the rest wait
   (`frame_limit`, `front_limit`).
-- Nothing plays in safe mode, over a temporary public link, with reduced motion or save-data, on a hidden page, while
-  the viewer has effects off, or before they consent to previews. A `poster.png` may then show behind the chat (see
-  Static Chat fallback). A visible menu or dialog stops `front` effects; these stops lift by themselves.
-- **Safety pause** — it measures the page's responsiveness, not your Worker's CPU. The page's frame-rate floor is
-  90% of what it measured before the effect started, capped at 55 fps (50 on a constrained device), so a 30 Hz screen
-  has a 27 fps floor. Where the browser reports them, long tasks may take at most 50 ms a second (25 ms constrained);
-  unknown timing doesn't count as free. Overlapping 2-second windows are judged at most once a second after a warm-up,
-  and three bad judgements in a row pause the effect (`host_budget`).
+- CW uses an opaque isolated document on the dashboard listener: no HTML-preview consent, separate preview port or
+  localhost requirement. Signed-in public/guest viewers may read and play only current effects in chats they can see;
+  this grants no library management, personal-slot, private-image, Trial or profile access. Their Chat header has a
+  browser-local show/off switch, including on phones, and an inline recovery action. It never writes host preferences.
+- Playback starts without an empty-page FPS calibration. Safe mode, hidden tabs and the viewer's show switch still
+  stop it. **Effects: follow the system's reduced-motion setting** is device-local and **off by default**, shared with
+  ambient effects. The OS request alone does not block playback; data saver is informational. A one-time chat note
+  offers to follow reduced motion, and a motion refusal offers **Play effects anyway** right there, including public/guest
+  viewers. Safe mode offers **Leave safe mode**. A poster may replace unsupported playback or a chosen motion block
+  (see Static Chat fallback). Menus/dialogs stop `front` effects temporarily.
+- A layout refusal keeps its local code in the Chat notice and Effects dialog (for example `stock_order_unknown`);
+  the browser console also names it. Report that code rather than repeatedly applying the effect. A failed Try leaves
+  its stop code on the offer card. Pointer-leave does not stop Try; window blur, closing, navigation or lost stage proof do.
+  Agent playback summaries still contain only the closed reporting reasons, never raw local diagnostics.
+- **Safety pause** — it measures the page's responsiveness, not your Worker's CPU. Host rAF observations learn a live
+  cadence during warm-up, then fix the mount's floor at 90% of a faster observed cadence, capped at 55 fps (50 on a
+  constrained device). A steady 30 Hz display has a 27 fps floor. This is not an empty-page health certificate; uniformly
+  slow startup can look like a low-refresh display. Where reported, long tasks may take at most 50 ms a second (25 ms
+  constrained); unknown observations never count as free. Overlapping 2-second windows are judged at most once a second
+  after warm-up, and three bad judgements in a row pause the effect (`host_budget`).
 - Only a viewer's explicit **Resume** restarts a safety-paused effect, and it doesn't clear the history: three such
   pauses within 24 hours turn the effect **off** for that viewer's browser and device class, across tabs and reloads,
   and Resume then refuses. It doesn't come back by itself after 24 hours.
@@ -321,25 +462,27 @@ from being collected until cleared. This is deliberately stricter than chat plac
 a personal choice keeps following its person's current own/shared access, while a chat preserves the exact effect
 placed there. A reference is not a sharing or export grant. Do not keep retrying a denied personal selection.
 
-Owner selectors are available in Settings → Web appearance. With effects and preview consent enabled, personal
-page/header/sidebar/box choices play across supported stock pages in the same pool as local signed-in Chat.
-Web appearance offers slot Pause/Resume and unavailable/Clear controls. The personal cursor uses a static PNG on the host shell after the same consent: no Worker/code read or frame slot. It preserves explicit pointer/text/resize cursors, falls back while dragging or on failure, and has status/Clear rather than Worker Pause/Resume. Before revealing paint, the host must prove stock content
+Owner selectors are available in Settings → Web appearance. With effects enabled, personal page/header/sidebar/box choices play across supported stock pages in the same pool
+as signed-in Chat. HTML-preview consent and its service are not involved.
+Web appearance offers slot Pause/Resume and unavailable/Clear controls. The personal cursor uses a static PNG on the host shell without HTML-preview consent: no Worker/code read or frame slot. It preserves explicit pointer/text/resize cursors, falls back while dragging or on failure, and has status/Clear rather than Worker Pause/Resume. Before revealing paint, the host must prove stock content
 ordering and trust paint coverage. Agent front effects must remain paused when custom CSS is active, loading or
 unknown; a person sees the reason and can open the causing setting. Human placements retain their exemption from
 that agent restriction, and behind effects still require proven ordering. Saving a placement alone is not proof of
 playback.
 
-Visible menus, dialogs, Keep/tour notices and focused inputs suppress all foreground effects; a human placement
-does not bypass those host safety gates. Unknown stock layout refuses admission. A trusted foreground plane is
+Visible menus, dialogs and Keep/tour notices suppress foreground effects; a human placement does not bypass them.
+Editable focus suppresses pointer signals, not unrelated drawing. Protected controls stay clipped out of front paint;
+keyboard events never enter the Worker. Unknown stock layout refuses admission. A trusted foreground plane is
 deferred to #1940; do not keep reapplying an agent front while custom CSS is on, loading or unknown.
 
-### Try: offer first, local admin click to start
+### Try: offer first, signed-in admin click to start
 
 `preview_web_effect({id})` posts a volatile Try card in your own web chat, using your current own/shared read rights. It starts nothing and changes no appearance. The sample is physically clipped inside its own host panel or sheet. Only an explicit
-click by a signed-in **local admin** may start it; never an agent, public link, header token or automatic action.
+click by a signed-in **admin outside the public link** may start it (localhost is not required); never an agent, public link, header token or automatic action.
 The host owns a visible Trial label and Stop control. Closing the panel/sheet, navigating, window blur, or another
-menu/dialog stops it. Custom CSS must be off (on/loading/unknown denies), and the same caps, profiler and safety
-stops apply. Ordinary foreground effects stay suppressed. A volatile offer lasts at most ten minutes (offering the same effect again keeps that offer and its expiry; a different effect replaces it); every read
+menu/dialog stops it. The explicit Try click consents to this sample only; no global HTML-preview opt-in is needed or changed.
+The host isolates the Trial controls and clipped stage in a closed Shadow DOM with fixed styles and reset typography.
+Custom CSS stays active elsewhere. The same caps, profiler and safety stops apply. Ordinary foreground effects stay suppressed. A volatile offer lasts at most ten minutes (offering the same effect again keeps that offer and its expiry; a different effect replaces it); every read
 rechecks the originating agent's current own/shared access, with the trial bound to the admin's session and epoch.
 There is no saved placement, claim, share, export or new saved profile record. Cards are memory-only and become inert when expired; a restart never restores them. Try uses manifest defaults and the existing app pool, not a second runtime. Do not treat an offer id or ordinary reply button
 as permission to run or fetch an effect, and do not keep retrying an unavailable Try.
@@ -347,12 +490,12 @@ as permission to run or fetch an effect, and do not keep retrying an unavailable
 
 ## Static Chat fallback
 
-When preview is unavailable, consent is missing, motion/data settings prevent playback, or the page is a public link,
+When Worker/transport support is unavailable, the chosen motion preference prevents playback, or the page has no playback session,
 a current chat placement with a poster can show its static PNG **behind** the content; a front declaration does not
 make its poster foreground. No poster means nothing is drawn. Safe mode and the viewer's show switch hide posters
 too; unknown stock ordering refuses paint. Explicit Pause, queued effects and a failed live read are not replaced by
 this surface fallback. A failed static read/decode stops its poster pool until a changed revision or page reload;
-there is no automatic network retry. The public link offers no Effects playback controls or Worker code.
+there is no automatic network retry. Public viewers can read current Chat Worker code, with fresh session/exposure/placement checks; they acquire no library or personal-slot grant. They have no placement-management or Try controls.
 
 The public-link show switch is this browser's choice, kept separately from boot-cached host defaults; it never writes
 a host preference. The ordinary signed-in switch keeps its existing host preference. Do not depend on decoration to