@telepath-computer/television 0.1.206 → 0.1.209

package/dist/skills/television/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: television
-description: Mental model, when to create artifacts, how Television's bundled skills fit together, and where the admin guide lives. Read for screen, artifact, and CLI work, and before installing, upgrading, or reconfiguring Television.
+description: Mental model, when to create artifacts, how Television's bundled skills fit together, and where the admin guide lives. Read for channel, artifact, and CLI work, and before installing, upgrading, or reconfiguring Television.
 ---
 
 
 # Television
 
-Television is a persistent artifact screen for agents.
+Television is a persistent artifact channel for agents.
 
-Load this skill when you need to create, update, inspect, focus, delete, or otherwise manage Television screens and artifacts.
+Load this skill when you need to create, update, inspect, focus, delete, or otherwise manage Television channels and artifacts.
 
 Re-read this skill only if it is not already in your context or you know it changed.
 
@@ -34,20 +34,20 @@ When the artifact is the real answer, keep the final reply short. Tell the user
 
 ### Core entities
 
-- A **screen** is a named viewer surface with a layout.
-- An **artifact** is a registry record shown on exactly one screen.
-- Screen layout is the source of truth for where an artifact appears.
+- A **channel** is a named viewer surface with a layout.
+- An **artifact** is a registry record shown on exactly one channel.
+- Channel layout is the source of truth for where an artifact appears.
 
 That relationship matters:
 
-- creating an artifact places it on a screen immediately
-- repositioning is a browser UI drag/drop gesture; the CLI does not expose layout mutation today
-- deleting an artifact removes its registry record and its card from the screen
-- moving the same underlying path or URL to another screen means deleting the old artifact and creating a new artifact with the same path or URL on the target screen
+- creating an artifact places it on a channel immediately
+- reordering an artifact's tab page is a browser UI tab-drag gesture; the CLI does not expose layout mutation today
+- deleting an artifact removes its registry record and its tab page from the channel
+- moving the same underlying path or URL to another channel means deleting the old artifact and creating a new artifact with the same path or URL on the target channel
 
-### Onboarding screens
+### Onboarding channels
 
-Fresh installations receive a small set of bundled onboarding screens, each installed exactly once per storage directory. After installation they are ordinary screens: rename, edit, or delete them like any other, and Television never re-creates or overwrites what changed. You can tell one apart from a user-created screen by the `onboarding` marker (slug and install order) persisted in its screen metadata — visible in `tv list-screens` / `tv get-screen` output; user-created screens have no such field. The marker changes nothing about how you manage the screen.
+Fresh installations receive a small set of bundled onboarding channels, each installed exactly once per storage directory. After installation they are ordinary channels: rename, edit, or delete them like any other, and Television never re-creates or overwrites what changed. You can tell one apart from a user-created channel by the `onboarding` marker containing its stable channel slug — visible in `tv list-channels` / `tv get-channel` output; user-created channels have no such field. Marked channels appear as ordinary unpinned channels and receive no special browser promotion. The marker changes nothing about how you manage the channel.
 
 ### Artifact shapes
 
@@ -67,7 +67,7 @@ Questions to keep straight:
 
 - should this result be markdown, HTML, or a URL pointer?
 - where should the underlying file live?
-- should it appear on the current screen, another existing screen, or a new screen?
+- should it appear on the current channel, another existing channel, or a new channel?
 - should the user see it immediately, or should it be prepared without moving their attention yet?
 
 Those questions interact, but they are not the same question.
@@ -86,7 +86,7 @@ Read the entire document before acting. If your web fetch tool returned a summar
 
 ## Telemetry awareness and control
 
-Television collects anonymous, content-free telemetry by default to understand early usage and improve the product. Telemetry records predefined usage events and content-free classifications; it does not record artifact paths or URLs, artifact titles, screen names, theme names, file contents, or user-authored text.
+Television collects anonymous, content-free telemetry by default to understand early usage and improve the product. Telemetry records predefined usage events and content-free classifications; it does not record artifact paths or URLs, artifact titles, channel names, theme names, file contents, or user-authored text.
 
 If the user wants to opt out, you turn telemetry off for them by running `tv telemetry disable` against the running server (`tv telemetry enable` turns it back on); `tv status` reports the current telemetry state. The command needs a live server. Television also honors the standard `DO_NOT_TRACK` environment variable when it is set, but `tv telemetry disable` is the intended way to opt out. Install- and upgrade-time telemetry duties — the disclosure to give the user and the `--installed-by-agent` flag — are covered in the admin guide (see the Administration section above).
 
@@ -94,7 +94,7 @@ If the user wants to opt out, you turn telemetry off for them by running `tv tel
 
 Television guidance is split across bundled skills.
 
-- Use this skill for screens, focus, artifact decisions, and the `tv` CLI. Required means the knowledge is required, not that you must re-read it before every Television action.
+- Use this skill for channels, focus, artifact decisions, and the `tv` CLI. Required means the knowledge is required, not that you must re-read it before every Television action.
 - Install the bundled Television skills into the agent harness skills folder with `tv skills install <path>` (for example `~/.openclaw/skills`, `~/.hermes/skills`, or `~/.agents/skills`) or use `tv skills install -i` before artifact authoring work.
 - For specialized HTML work, load the matching skill such as `tv-calendar` or `tv-table`.
 
@@ -103,11 +103,11 @@ Television guidance is split across bundled skills.
 
 # TV CLI capabilities
 
-Use this document when you need to reason about what the `tv` CLI can do, which command family fits the user's request, and how focus and screen placement should be decided.
+Use this document when you need to reason about what the `tv` CLI can do, which command family fits the user's request, and how focus and channel placement should be decided.
 
 ## Agent recovery surfaces
 
-The `television` skill is the primary guidance surface for Television screens, focus, and artifact work. Keep that guidance available; re-read it only if it is not already in context or you know it changed.
+The `television` skill is the primary guidance surface for Television channels, focus, and artifact work. Keep that guidance available; re-read it only if it is not already in context or you know it changed.
 
 Install bundled Television skills with either:
 
@@ -129,14 +129,14 @@ tv help
 tv help <command>
 ```
 
-`tv help <command>` is the source of truth for per-command semantics that are not obvious from the name — focus decisions, cascading effects, JSON vs plain-text output, and distinctions between superficially similar commands (delete-artifact vs remove-screen, focus-screen vs focus-artifact). Read it before choosing a command when you are unsure.
+`tv help <command>` is the source of truth for per-command semantics that are not obvious from the name — focus decisions, cascading effects, JSON vs plain-text output, and distinctions between superficially similar commands (delete-artifact vs remove-channel, focus-channel vs focus-artifact). Read it before choosing a command when you are unsure.
 
 Commands group into four intents:
 
-- **Screen and display commands** — create, inspect, remove, or switch screens, or change the active display theme (`create-screen`, `list-screens`, `get-screen`, `remove-screen`, `focus-screen`, `focus-status`, `set-theme`).
+- **Channel and display commands** — create, inspect, remove, or switch channels, or change the active display theme (`create-channel`, `list-channels`, `get-channel`, `remove-channel`, `focus-channel`, `focus-status`, `set-theme`).
 - **Artifact creation commands** — register path or URL artifacts (`create-path-artifact`, `create-url-artifact`).
 - **Artifact management commands** — inspect, retitle, repoint, focus, list, or delete existing artifacts (`delete-artifact`, `get-artifact`, `list-artifacts`, `update-artifact`, `focus-artifact`).
-- **Server and environment commands** — operate on the Television server itself (`serve`, `status`, `stop`, `storage-path`, `skills install`).
+- **Server and environment commands** — operate on the Television server itself (`serve`, `status`, `stop`, `storage-path`, `telemetry`, `skills install`).
 
 When the CLI rejects a command, follow the directive it prints rather than guessing flags.
 
@@ -156,10 +156,10 @@ Use read commands when you need authoritative state for planning or verification
 
 Television separates state changes from focus. Choosing where an artifact lives is one decision; choosing whether the user's attention moves there is a separate one.
 
-- **screen focus** is persistent: which screen the user is currently looking at
-- **artifact focus** is transient: clients may switch screens first, then scroll and highlight the artifact
+- **channel focus** is persistent: which channel the user is currently looking at
+- **artifact focus** is transient: clients select the artifact's tab page, switching channels first when needed
 
-There is a persisted focused screen.
+There is a persisted focused channel.
 There is not a persisted focused artifact.
 
 Important consequence: creating something does not by itself answer whether the user should be taken to it now.
@@ -168,10 +168,10 @@ Important consequence: creating something does not by itself answer whether the
 
 Create commands require an explicit focus decision.
 
-- `tv create-screen` requires exactly one of `--focus-screen` or `--no-focus`
+- `tv create-channel` requires exactly one of `--focus-channel` or `--no-focus`
 - `tv create-path-artifact` and `tv create-url-artifact` require exactly one of `--focus-artifact` or `--no-focus`
 
-If you omit that decision, the CLI rejects the command. Dedicated `focus-screen` and `focus-artifact` commands can also move attention later as separate steps.
+If you omit that decision, the CLI rejects the command. Dedicated `focus-channel` and `focus-artifact` commands can also move attention later as separate steps.
 
 ## Choosing the focus directive
 
@@ -181,9 +181,9 @@ Rules of thumb:
 
 - **focus now** when seeing the result immediately is part of successfully answering the request
 - **`--no-focus`** when the user is likely to want the result available without breaking their current flow, or when the work should run in the background
-- **direct `focus-screen` / `focus-artifact` commands** when placement and attention movement should happen as separate steps
+- **direct `focus-channel` / `focus-artifact` commands** when placement and attention movement should happen as separate steps
 
-When your action would not be visually obvious to the user — you used `--no-focus`, you placed something on a non-current screen, or you moved focus — tell them what you did, name the screen, and say what they should see. Otherwise the Television display may not change in a way they can interpret.
+When your action would not be visually obvious to the user — you used `--no-focus`, you placed something on a non-current channel, or you moved focus — tell them what you did, name the channel, and say what they should see. Otherwise the Television display may not change in a way they can interpret.
 
 ## Listening for focus intent in the user's language
 
@@ -194,7 +194,7 @@ Phrases that usually indicate the user wants attention moved:
 - "show me", "show me that", "let me see it", "let me review it"
 - "switch to", "change to", "go to", "take me there", "open it"
 - "put it on screen", "put it on my screen", "bring it up"
-- references to the **active**, **current**, **showing**, or **visible** screen or artifact
+- references to the **active**, **current**, **showing**, or **visible** channel or artifact
 
 Phrases that usually indicate the user wants the work to happen without disturbing their current view:
 
@@ -204,42 +204,42 @@ Phrases that usually indicate the user wants the work to happen without disturbi
 
 These are illustrative, not exhaustive. When the language is ambiguous or unusual, reason about the user's attention stream instead of pattern-matching keywords.
 
-## Screen placement
+## Channel placement
 
-Artifact creation commands require `--screen` because new artifacts need immediate screen membership. Repositioning an artifact on its current screen is a browser UI drag/drop gesture; the CLI does not expose layout mutation today. To move the same underlying path or URL to a different screen, delete the old artifact and create a new artifact on the target screen with the same path or URL.
+Artifact creation commands require `--channel` because new artifacts need immediate channel membership. Reordering an artifact's tab page on its current channel is a browser UI tab-drag gesture; the CLI does not expose layout mutation today. To move the same underlying path or URL to a different channel, delete the old artifact and create a new artifact on the target channel with the same path or URL.
 
 Think carefully about whether the user means:
 
-- create something new on a screen
-- reposition an artifact on its current screen in the browser UI
-- delete an artifact from its screen
-- recreate the same path or URL on a different screen
+- create something new on a channel
+- reorder an artifact's tab page on its current channel in the browser UI
+- delete an artifact from its channel
+- recreate the same path or URL on a different channel
 
 Those are different operations with different consequences. The per-command help text spells out which is which.
 
-### Choosing the right screen
+### Choosing the right channel
 
 When deciding where an artifact should go:
 
-- If the current screen is the right place and the user should see the result immediately, create the artifact there with `--focus-artifact`.
-- If the current screen is the right place but the work should appear without interrupting their reading flow, create it with `--no-focus`.
-- If the work belongs on a different existing screen, place it there. Then decide whether to focus or merely tell the user where it is.
-- Sometimes a new screen is the right call.
+- If the current channel is the right place and the user should see the result immediately, create the artifact there with `--focus-artifact`.
+- If the current channel is the right place but the work should appear without interrupting their reading flow, create it with `--no-focus`.
+- If the work belongs on a different existing channel, place it there. Then decide whether to focus or merely tell the user where it is.
+- Sometimes a new channel is the right call.
 
-### When to create a new screen
+### When to create a new channel
 
-Reach for `tv create-screen` when:
+Reach for `tv create-channel` when:
 
-- the request is meaningfully separate from the current screen's purpose
+- the request is meaningfully separate from the current channel's purpose
 - the result should become its own durable workspace the user can return to
-- mixing it into the current screen would make the user's mental model worse
+- mixing it into the current channel would make the user's mental model worse
 
-Default to placing things on an existing screen unless one of those conditions is true. Spawning a new screen for every request fragments the user's workspace; spawning none ever forces unrelated content together.
+Default to placing things on an existing channel unless one of those conditions is true. Spawning a new channel for every request fragments the user's workspace; spawning none ever forces unrelated content together.
 
 
 # Artifact workflow
 
-Read this document for Television artifact work: creating files, registering path or URL artifacts, browser-only repositioning, deleting, and updating titles.
+Read this document for Television artifact work: creating files, registering path or URL artifacts, browser-only tab-page reordering, deleting, and updating titles.
 
 If you need bundled Television authoring skills installed first, copy them into the agent harness skills folder with `tv skills install <path>` (for example `~/.openclaw/skills`, `~/.hermes/skills`, or `~/.agents/skills`) or use `tv skills install -i`.
 
@@ -332,7 +332,7 @@ Good examples:
 - "Starting the artifact now."
 - "Reviewing the draft and source material."
 - "Writing the HTML and checking it in the browser."
-- "Registering the artifact on your screen."
+- "Registering the artifact on your channel."
 - "Done."
 
 Avoid:
@@ -347,7 +347,7 @@ Avoid:
 2. Register it:
 
    ```bash
-   tv create-path-artifact --screen "<screen-id>" --title "Artifact title" --path /absolute/path/to/file.md --focus-artifact
+   tv create-path-artifact --channel "<channel-id>" --title "Artifact title" --path /absolute/path/to/file.md --focus-artifact
    ```
 
 Rules:
@@ -363,13 +363,13 @@ HTML can be a single file or a directory bundle.
 Single-file example:
 
 ```bash
-tv create-path-artifact --screen "<screen-id>" --title "Artifact title" --path /absolute/path/to/report.html --focus-artifact
+tv create-path-artifact --channel "<channel-id>" --title "Artifact title" --path /absolute/path/to/report.html --focus-artifact
 ```
 
 Directory example (trailing slash optional):
 
 ```bash
-tv create-path-artifact --screen "<screen-id>" --title "Artifact title" --path /absolute/path/to/dashboard --focus-artifact
+tv create-path-artifact --channel "<channel-id>" --title "Artifact title" --path /absolute/path/to/dashboard --focus-artifact
 ```
 
 A directory artifact needs root `index.html` or `index.htm`. Keep sibling assets relative so they resolve through the artifact proxy:
@@ -426,13 +426,13 @@ tv update-artifact --id "<artifact-id>" --path /absolute/path/to/new-target
 tv update-artifact --id "<artifact-id>" --url "https://example.com/next"
 ```
 
-The new path follows the same rules as creation (file or indexed directory, trailing separator optional). Rendering follows the new pointer immediately, and for path artifacts the content watcher retargets with it. Prefer repointing over delete-and-recreate when the artifact should keep its identity and screen placement.
+The new path follows the same rules as creation (file or indexed directory, trailing separator optional). Rendering follows the new pointer immediately, and for path artifacts the content watcher retargets with it. Prefer repointing over delete-and-recreate when the artifact should keep its identity and channel placement.
 
-Artifact repositioning on its current screen is a browser UI drag/drop gesture; the CLI does not expose layout mutation today.
+Reordering an artifact's tab page on its current channel is a browser UI tab-drag gesture; the CLI does not expose layout mutation today.
 
-To move the same underlying path or URL to another screen, delete the existing artifact and create a new one on the target screen with the same `--path` or `--url`.
+To move the same underlying path or URL to another channel, delete the existing artifact and create a new one on the target channel with the same `--path` or `--url`.
 
-To delete the registry record and remove its card from its screen:
+To delete the registry record and remove its tab page from the channel:
 
 ```bash
 tv delete-artifact --id "<artifact-id>"
@@ -443,7 +443,7 @@ tv delete-artifact --id "<artifact-id>"
 URL artifacts point at external `http(s)://` pages.
 
 ```bash
-tv create-url-artifact --screen "<screen-id>" --title "Artifact title" --url https://example.com --no-focus
+tv create-url-artifact --channel "<channel-id>" --title "Artifact title" --url https://example.com --no-focus
 ```
 
 Rules:
@@ -482,32 +482,31 @@ If the browser placeholder for an ordinary non-Television URL is not sufficient,
 
 # HTML artifact style
 
-Write a complete HTML document for the Television viewer. Always include the
-canonical stylesheet:
+Write a complete HTML document for the Television viewer. Load both canonical
+v1 resources in the document head:
 
 ```html
 <link rel="stylesheet" href="/canonical/v1/styles.css">
+<script type="module" src="/canonical/v1/components.js"></script>
 ```
 
-The canonical stylesheet provides the shared artifact foundation: reset, Hind
-font, design tokens, default semantic theme colors, and conservative document
-typography for plain semantic HTML.
+The stylesheet provides Television's reset, Hind font, public design tokens,
+semantic document defaults, and published element styles. The script registers
+the published custom elements. Add local CSS for the artifact's own layout,
+density, hierarchy, and specialized presentation.
 
 Lean on semantic HTML first. Headings, paragraphs, lists, links, code blocks,
-blockquotes, rules, images, and tables have readable defaults. Add local CSS for
-artifact-specific layout, density, hierarchy, or specialized presentations; do
-not recreate baseline prose styling in every artifact.
+blockquotes, rules, images, and tables receive readable document styling from
+the canonical sheet. Rely on those defaults instead of recreating baseline
+typography in each artifact.
 
 ## Page header
 
-A page header is optional — the Television card already names the artifact in
-its title bar, so don't add one just to repeat that. Add one when the document
-benefits from its own masthead: a title that differs from or says more than
-the card name, or a subtitle line carrying context like a date, a person, or
-a status.
+The artifact frame's title bar already names the artifact. Add a page header
+when the document benefits from its own masthead, such as a more specific title
+or a subtitle carrying a date, person, or status.
 
-When you do, use the house header idiom — a `<header>` holding an `<h1>` and
-optionally one `<p>` subtitle:
+Use a `<header>` containing an `<h1>` and, when useful, one `<p>` subtitle:
 
 ```html
 <header>
@@ -516,12 +515,12 @@ optionally one `<p>` subtitle:
 </header>
 ```
 
-A `<p>` inside any `<header>` renders as a subtitle — slightly smaller than
-body prose, at body weight, hugging its heading; proximity and the heading
-above do the differentiating. The idiom is house language: use it as-is,
-don't restyle it per artifact.
+A lead paragraph in a header is automatically muted and drawn close to its
+heading.
 
-For prose-like documents, consider giving the content enough room above the bottom title bar. A reasonable starting point is 32px padding on the top and sides, with 64px at the bottom; adjust based on the content and layout:
+For prose-like documents, 32px padding on the top and sides with 64px at the
+bottom is a useful starting point. Adapt it to the document's content and
+available space:
 
 ```css
 body {
@@ -529,34 +528,86 @@ body {
 }
 ```
 
-## Spacing tokens
-
-The canonical stylesheet exposes a small, closed spacing scale for custom layouts:
-`--space-2`, `--space-4`, `--space-6`, `--space-8`, `--space-10`,
-`--space-12`, `--space-16`, `--space-20`, `--space-24`, `--space-32`,
-`--space-48`, and `--space-64`.
+## Canonical tokens
 
-Do not invent token names such as `--space-14` or `--space-xl`. If no token fits,
-use a literal pixel value instead. When you do use a spacing token in
-artifact-authored CSS, always include the matching fallback so the artifact still
-renders if the canonical stylesheet is unavailable:
+Use these public custom properties in artifact-authored CSS. Include a literal
+fallback when the artifact should remain readable without the canonical sheet:
 
 ```css
-.card {
+.panel {
   padding: var(--space-16, 16px);
   gap: var(--space-12, 12px);
+  color: var(--color-text, #222);
 }
 ```
 
+Fallbacks are paired: a guarded ground goes with a guarded text color, using
+values that read together.
+
+This published inventory is closed. Do not invent token names; when no public
+token expresses a value, use an intentional literal, and when one does, use the
+documented token with a literal fallback where appropriate.
+
+### Color values and ramps
+
+- Base: `--black`, `--white`.
+- Neutral: `--neutral-50`, `--neutral-100`, `--neutral-200`,
+  `--neutral-300`, `--neutral-400`, `--neutral-500`, `--neutral-600`,
+  `--neutral-700`, `--neutral-800`, `--neutral-900`, `--neutral-950`.
+- Alpha: `--alpha-50`, `--alpha-100`, `--alpha-200`, `--alpha-300`,
+  `--alpha-400`, `--alpha-500`, `--alpha-600`, `--alpha-700`,
+  `--alpha-800`, `--alpha-900`, `--alpha-950`.
+- Blue: `--blue-50`, `--blue-100`, `--blue-200`, `--blue-300`,
+  `--blue-400`, `--blue-500`, `--blue-600`, `--blue-700`, `--blue-800`,
+  `--blue-900`.
+- Red: `--red-50`, `--red-100`, `--red-200`, `--red-300`, `--red-400`,
+  `--red-500`, `--red-600`, `--red-700`, `--red-800`, `--red-900`.
+- Yellow: `--yellow-50`, `--yellow-100`, `--yellow-200`, `--yellow-300`,
+  `--yellow-400`, `--yellow-500`, `--yellow-600`, `--yellow-700`,
+  `--yellow-800`, `--yellow-900`, `--yellow-950`.
+- Green: `--green-50`, `--green-100`, `--green-200`, `--green-300`,
+  `--green-400`, `--green-500`, `--green-600`, `--green-700`,
+  `--green-800`, `--green-900`.
+- Orange: `--orange-50`, `--orange-100`, `--orange-200`, `--orange-300`,
+  `--orange-400`, `--orange-500`, `--orange-600`, `--orange-700`,
+  `--orange-800`, `--orange-900`.
+- Purple: `--purple-50`, `--purple-100`, `--purple-200`, `--purple-300`,
+  `--purple-400`, `--purple-500`, `--purple-600`, `--purple-700`,
+  `--purple-800`, `--purple-900`.
+- Current-color tints: `--tint-50`, `--tint-100`, `--tint-200`,
+  `--tint-300`, `--tint-400`, `--tint-500`, `--tint-600`, `--tint-700`,
+  `--tint-800`, `--tint-900`, `--tint-950`.
+
+Prefer the semantic roles when they express the intended meaning:
+`--color-text`, `--color-text-muted`, `--color-primary`,
+`--color-on-primary`, `--color-selected`, `--color-link`, `--color-danger`,
+`--color-success`, `--color-warning`, `--color-background`, `--color-surface`,
+`--color-surface-muted`, `--color-border`, and `--color-border-muted`.
+
+### Type
+
+- Scale and line height: `--text-base`, `--text-sm`, `--text-md`,
+  `--text-lg`, `--text-xl`, `--text-2xl`, `--text-3xl`, `--text-4xl`,
+  `--text-scale`, `--leading-base`.
+- Families: `--font-sans`, `--font-mono`.
+- Weights: `--font-weight-normal`, `--font-weight-medium`,
+  `--font-weight-body`, `--font-weight-semibold`.
+
+### Spacing, radii, and elevation
+
+- Spacing: `--space-2`, `--space-4`, `--space-6`, `--space-8`,
+  `--space-10`, `--space-12`, `--space-16`, `--space-20`, `--space-24`,
+  `--space-32`, `--space-48`, `--space-64`.
+- Radii: `--radius-4`, `--radius-6`, `--radius-8`, `--radius-12`,
+  `--radius-16`, `--radius-24`, `--radius-full`.
+- Floating-panel elevation: `--shadow-panel`.
+
 ## Canonical components
 
-For house-style components, import the canonical component bundle:
+### Static checkbox lists
 
-```html
-<script type="module" src="/canonical/v1/components.js"></script>
-```
-
-Use checkbox-list components for checklists rather than markdown task syntax:
+Use `checkbox-list` and `checkbox-item` for a checklist whose state is authored
+into the document:
 
 ```html
 <checkbox-list>
@@ -565,60 +616,53 @@ Use checkbox-list components for checklists rather than markdown task syntax:
 </checkbox-list>
 ```
 
-Checked items render muted and struck through. The checkbox marker is static and
-shows a not-allowed cursor when hovered.
-
-Checkbox-list styling API:
-
-- `checkbox-list::part(list)` — the internal item stack.
-- `checkbox-item::part(label)` — row containing marker and content.
-- `checkbox-item::part(box)` — visual checkbox marker.
-- `checkbox-item::part(check)` — checkmark.
-- `checkbox-item::part(content)` — item text/content.
-- Useful variables: `--checkbox-list-gap`, `--checkbox-size`,
-  `--checkbox-gap`, `--checkbox-color`, `--checkbox-border-color`,
-  `--checkbox-radius`, `--checkbox-checked-content-color`,
-  `--checkbox-checked-decoration`.
-
-Example local variation:
+`checked` marks a completed `checkbox-item`. Checked rows render muted and
+struck through, and the marker shows a not-allowed cursor to communicate its
+static nature. The list is presentational and does not toggle when pressed.
+`--checkbox-color` is the checkbox item's documented styling property:
 
 ```css
-checkbox-list {
-  --checkbox-list-gap: 8px;
-}
-
 checkbox-item {
   --checkbox-color: var(--green-600);
 }
-
-checkbox-item::part(box) {
-  border-radius: 999px;
-}
 ```
 
 ### Icons
 
-`<tv-icon name="…" size="16|24|32">` renders a glyph from the canonical
-catalog. The catalog is small and closed — these are the only valid names:
+`<tv-icon name="…" size="sm|md|lg|xl" spinning>` is the complete authoring
+shape. Supply `name`. Omit `size` beside text so the icon follows the current
+font size, or choose `sm`, `md`, `lg`, or `xl` for a standalone icon. Add the
+boolean `spinning` attribute for continuous activity.
 
-- `calendar-blank`
-- `hash`
-- `plus`
-- `squares-four`
-- `subtract-square`
-- `television`
+`tv-icon` may be composed inside an author-created shadow root; it renders and
+sizes there the same way it does in document light DOM.
 
-Do not invent other names (an unknown name silently renders the
-`subtract-square` fallback, which looks like a broken glyph). If no glyph
-fits, use text without an icon; if a glyph is genuinely needed and none
-fits, use an emoji instead of `<tv-icon>`.
-
-## Viewport
-
-Artifacts render inside a resizable Television card, not a full browser page.
-The default card is roughly 528px wide by 800px tall. Users may make cards
-narrower, wider, shorter, or taller. Treat 528px × 800px as the first layout
-target, then make sure the artifact still works when narrower.
+```html
+<tv-icon name="check" size="md"></tv-icon>
+<tv-icon name="spinner" size="md" spinning></tv-icon>
+```
 
-If content overflows, artifacts can scroll vertically. Avoid horizontal scrolling
-unless the content genuinely requires it, such as a wide data table or timeline.
+The public icon names are:
+
+- `check`, `close`, `copy`, `pin`, `search`, `add`, `more`, `settings`
+- `expand`, `collapse`, `collapse-up`, `skills`, `notification`, `artifact`
+- `spinner`, `locked`, `unpin`, `back`, `forward`, `television`, `calendar`
+- `grid`, `hash`, `delete`, `edit`, `link`, `external`, `download`, `reload`
+- `warning`, `info`, `file`, `folder`, `clock`, `user`, `upload`, `star`
+- `home`, `send`, `filter`, `sort`, `help`, `chart`, `image`, `chat`
+- `location`, `play`, `pause`, `stop`, `video`, `music`, `error`, `email`
+- `phone`, `web`, `tag`, `bookmark`, `table`, `code`, `group`, `up`, `down`
+- `money`, `bank`, `card`, `wallet`, `gauge`, `activity`, `trend-up`
+- `trend-down`, `database`, `server`, `deploy`, `list`, `terminal`, `branch`
+- `shield`
+
+Choose a name from this catalog. When the catalog has no suitable glyph, use a
+text label or an emoji.
+
+## Available document space
+
+Television presents each artifact as its own document inside a resizable
+artifact frame. Build responsive layouts from the document's available width
+and height. Vertical document scrolling is appropriate for overflow; reserve
+horizontal scrolling for content that needs width, such as a data table or
+timeline.