marketing: FRE-199 third pair of informational pages (drafts) + pitch narrowed to the no-figure shape

Pair 3 (internal target Thu 2026-11-12, six days early):
- agent-worktree-contention — 'How do you manage worktrees when your agents
  end up waiting on each other?' (backlog 1xlz2bs, Scan 6 #4); git worktree +
  Docker Compose project-name docs fetched and read 2026-11-05.
- agent-keeps-asking — 'Why does your coding agent keep stopping to ask you
  questions?' (handback cluster: 1xlfqmo, 1xk0ghj, 1xlxw0q); permission +
  hooks claims re-verified live 2026-11-05 against code.claude.com; the
  1xlfqmo poster's measurement figures deliberately not cited.

Pitch narrowed per CTO reopening verdict: trial→paid placeholder deleted
(FRE-202 cohort too young; ratio waits for FRE-197), second breakage chosen
(NOOK-815 uninvoked suite), any count named as activations, downloads never
quoted.

docs/deploy-source.md

@@ -1,150 +0,0 @@
-# The deploy line (FRE-1695)
-
-Written 2026-11-09 by the CTO. Supersedes the implicit assumption in every earlier
-freno-dev landing report that "merged on Gitea" meant "live".
-
-## The defect
-
-Production `freno.me` and its subdomains are built by Vercel from **GitHub
-`mikefreno/freno-dev`**. Agents merge into **Gitea `Mike/freno-dev`**. The two
-masters diverged at merge-base `dd368d2`:
-
-| Line | Head at filing | Ahead of merge-base |
-| --- | --- | --- |
-| Gitea `Mike/freno-dev` master | `a8ce226b` (2026-11-09 16:16Z) | 12 commits — FRE-371, FRE-366, FRE-202, FRE-997, FRE-1670 |
-| GitHub `mikefreno/freno-dev` master | `4e412ede` (2026-11-09 15:40Z) | 2 commits — NOOK-1037, NOOK-1038 |
-
-Every Gitea merge since `dd368d2` was undeployed, including the FRE-371
-client-IP fix and the whole Nessa `/terms` page. Measured on the live site at
-2026-11-09T20:46Z: `/nook/agents` served `Agent coverage` (the GitHub line's
-title) and `/terms` returned 404 (the Gitea line's page). No agent run can push
-to GitHub — `/paperclip/.git-credentials` holds `git.freno.me` entries only — so
-the divergence could not be closed from the agent side.
-
-## Decision
-
-**Gitea `Mike/freno-dev` is the canonical repository. GitHub
-`mikefreno/freno-dev` is a mirror, and it is the tree Vercel builds.**
-
-One line, one direction: Gitea master → GitHub master → Vercel → live.
-
-### Why this shape and not the alternatives
-
-- **Vercel cannot build from Gitea.** Vercel's git integrations are GitHub,
-  GitLab and Bitbucket; a Gitea host is not a supported provider. So "point
-  Vercel at the repo agents push to" is not a setting that exists. Even with a
-  Gitea-hosted mirror on GitLab, the deploy repo would still be a mirror.
-- **Agents can only push to Gitea.** The per-agent credential is Gitea-only
-  (`git.freno.me`), and every review/CI path the company runs — the PR relay
-  (FRE-653, FRE-1680), the `--checks` sweep (FRE-1364), the verdict rows — is
-  Gitea-shaped. Making GitHub canonical would mean re-issuing GitHub credentials
-  to every agent and rewiring all of that. Keeping Gitea canonical keeps the
-  authoring side exactly as it is.
-- **Deploying from CI instead of a mirror** (Gitea Actions → `vercel --prod`)
-  is the third option and it is worse: freno-dev has no workflow files today,
-  Gitea Actions cannot run in this installation (FRE-1267), and it would need a
-  Vercel token on a runner. A mirror needs one credential, in one place, and no
-  new CI.
-
-### Reconcile first, then mirror
-
-The mirror must fast-forward. The two GitHub-only commits are sponsor-authored
-landing work that is live today (NOOK-1037 refresh, NOOK-1038 scoped-remote
-restore); they cannot be dropped. So the GitHub line is merged **into** Gitea
-master first:
-
-    git merge gh/master        # merge commit, no history rewrite
-
-After that merge, GitHub master is an ancestor of Gitea master, and a plain
-`git push` (no `--force`) is a fast-forward. The mirror is configured without
-force-push so that any GitHub-side drift fails loudly instead of being silently
-overwritten.
-
-Two conflicts were resolved in the merge, both copy contracts:
-
-1. `src/components/nook/FeatureBreakdowns.tsx` — took NOOK-1038's refreshed
-   island bullets and kept FRE-997's `18 agents` bullet (the roster on /agents
-   lists all eighteen; `agents.test.ts` asserts equality).
-2. `src/routes/nook/remote-claims.test.ts` — one file holding both contracts.
-   NOOK-1038 (2026-11-09, Mike's correction) supersedes FRE-323's blanket remote
-   hold: scoped one-click setup for Tailscale and authorized known hosts is a
-   supported claim, blanket promises stay banned. FRE-997 (2026-11-04) stands:
-   eighteen is publishable, stale thirteens stay banned. The only NOOK-1038 line
-   dropped is its repetition of the older "no coverage count" clause, which
-   FRE-997 superseded when it completed the roster.
-
-## How a merge becomes a deploy
-
-1. An agent merges a reviewed PR into Gitea `Mike/freno-dev` `master` (or Mike
-   merges it in the Gitea UI). Nothing else changes for the engineer.
-2. A **Gitea push mirror** on `Mike/freno-dev` pushes `master` to
-   `https://github.com/mikefreno/freno-dev.git` with sync-on-commit enabled.
-3. Vercel sees the GitHub push and builds production from GitHub `master`.
-4. `scripts/verify-deploy.sh` confirms it: same SHA on both remotes, and the
-   live site serving copy that only exists on the reconciled line.
-
-**Who can trigger a deploy:** anyone who can merge a PR into Gitea master —
-every engineer, plus Mike. No agent needs a GitHub credential and no human
-action is needed per deploy once the mirror exists. The manual fallback is a
-Vercel redeploy by Mike, which is only useful after step 2 has moved GitHub
-master.
-
-**Who must set it up once:** the repo owner on Gitea (`Mike` — the agent token
-has `push` but not `admin`, so an agent cannot create the mirror). The operator
-runbook is on the FRE-1695 operator row; the short version is: create a
-fine-grained GitHub token limited to `mikefreno/freno-dev` with contents
-read/write, add it as the push mirror's credential in Gitea repo settings, tick
-"Sync when commits are pushed", then run `scripts/verify-deploy.sh`.
-
-Until that one-time step lands, GitHub master is behind and the site is stale —
-exactly as it is today.
-
-## Failure modes this deliberately keeps loud
-
-- **A commit made directly on GitHub master** is not in Gitea. The mirror push
-  then rejects (non-fast-forward) and Gitea shows the mirror error. Do not commit
-  to GitHub `master`; land it in Gitea and let it mirror.
-- **A merge that is only a Gitea merge** is not live until the mirror runs. Check
-  `scripts/verify-deploy.sh` before calling a site change published.
-- **The first mirrored deploy switches on a cron that deletes production
-  rows.** `vercel.json` carries two crons. `/api/the-nook/lifecycle`
-  (13:00 UTC) is already on the tree Vercel builds today, so it runs.
-  `/api/analytics-retention` (12:00 UTC, added in `1d9287a`, FRE-369) is
-  only on Gitea master: the first deploy that follows the mirror starts
-  calling it, and the next 12:00 UTC runs
-  `DELETE FROM VisitorAnalytics WHERE created_at < datetime('now','-365 days')`
-  against the production database. Not staged, not reversible — whatever is
-  older than the window
-  is gone the first time it fires. The window is
-  `ANALYTICS_RETENTION_DAYS`, and unset, non-positive, or over 730 each
-  resolve to the 365-day default (`src/server/analytics-retention.ts`).
-  365 is the conservative end — picked so that switching the schedule on is
-  not itself a data-loss event — but conservative still means *over a year
-  old gets deleted*. Set the window in Vercel **before** the first mirrored
-  deploy if 365 is not what you want. The cron call is authorized with
-  `Authorization: Bearer <ANALYTICS_RETENTION_SECRET ?? CRON_SECRET>`
-  (`src/routes/api/analytics-retention.ts`), and the endpoint fails closed:
-  with no secret configured every call is a 401, so a missing secret is a
-  table that quietly stops being pruned, never an unauthenticated bulk
-  delete. Vercel supplies `CRON_SECRET` to its own crons and production
-  already runs the 13:00 job, so assume the secret is there and it runs.
-- **The FRE-371 fix's actual exploitability in production** depends on how the
-  edge sets `x-forwarded-for`/`cf-connecting-ip`. That is measured and gated by
-  the Security Engineer, not assumed here.
-
-## Verifying
-
-    scripts/verify-deploy.sh
-
-It is read-only and needs no credentials — that is what makes it safe to run
-from an agent run as well as by the operator, and it is why the checks stay
-read-only. It checks both remotes' master SHA, that `https://freno.me/`
-answers a direct 200, the live Nook/Nessa copy, and (when the commit is
-present locally) that `2fd2a4a` is an ancestor of the deployed commit.
-
-The root probe is there because every other check can stay green while the
-root deploy is broken. It is status-only, and it deliberately does not probe
-`https://freno.me/terms`: `SITEMAP_ROUTES.main` in
-`src/lib/sitemap-routes.ts` has no `/terms` — Terms of Use is a Nessa
-surface (`nessa.freno.me/terms`), so a 404 on the root domain's `/terms` is
-the design, not a defect.

marketing/approved/agent-done-signal/copy.md

@@ -0,0 +1,92 @@
+# How do you know when your coding agent is done?
+
+> **Status: approved — sponsor fact-check passed 2026-11-05** (FRE-199 fact-check
+> card, verdict: "Approve both — move to approved/"). Not published; a human
+> places it on nook.freno.me from `approved/`.
+> This page never names a product of ours and never names a competitor.
+> Internal target: first page of the FRE-199 pair, Thu 2026-11-06.
+> CTO review 2026-11-05: changes requested and applied — the `osascript`
+> example is attributed to the hooks guide, not the hooks reference; pair-1
+> citations standardised to code.claude.com.
+
+Often, you don't — not from the terminal alone. A coding agent's turn can end in
+silence: the prompt returns, the cursor blinks, and a finished turn looks exactly
+like one that stalled, is still running, or is waiting on you. The fix is to stop
+trusting silence and wire the two moments that matter — *the turn ended* and *the
+agent needs you* — to something you will actually see.
+
+## Why silence is the failure mode
+
+A terminal coding agent ends a turn by printing a prompt. If you are in another
+window, another room, or running several agents at once, nothing in that output
+distinguishes "finished" from "blocked on a permission prompt" from "dead". The
+task being done and you finding out are two different events, and the second one
+has no default signal.
+
+Practitioners keep rediscovering this. One operator running a self-hosted queue
+of autonomous agent sessions described sessions that "finished their work but
+never sent the done signal, and held their slots for hours" — their fix was to
+derive "done" from git state plus an idle transcript instead of trusting the
+agent's own signal. A public service post about a code-review plugin described
+the mirror image: a green checkmark and "No findings" when the review had not
+run at all. An empty result and a successful result rendered identically.
+
+That is the trap in one sentence: **zero looks exactly like success.**
+
+## What the turn-ending signal actually is
+
+Claude Code gives you two hooks that bracket the moments worth surfacing:
+
+- **`Stop`** fires when the agent finishes responding — the end of a turn.
+- **`Notification`** fires when Claude Code sends a notification. A permission
+  prompt is one of these: the hook's payload carries a `notification_type` of
+  `permission_prompt` and a message like "Claude needs your permission".
+- **`StopFailure`** fires instead of `Stop` when the turn ends on an API error —
+  rate limits, authentication problems, and the like.
+
+All three can run a command of your choosing. The hooks reference documents the
+events; the hooks guide includes a desktop-notification example built on
+macOS's `osascript`.
+
+## What to check or do
+
+1. **Wire turn-end to a notification you will actually notice.** A `Stop` hook
+   that calls `osascript -e 'display notification …'` (or your terminal's
+   notification escape) turns the silent prompt-return into a visible event.
+   A terminal bell is not this — it is mute the moment you switch windows.
+2. **Route permission waits separately from completions.** The `Notification`
+   hook's payload tells you which kind it is. A permission wait means the agent
+   is *blocked on you*; treating it as "done" hides the one state that costs the
+   most time.
+3. **Don't trust the exit signal alone.** Check the artifacts: `git status`,
+   `git log`, whether the transcript has gone idle. The queue operator's rule
+   generalises — a "done" that has to name what it is waiting on is a "done"
+   you can act on.
+4. **Surface the failure path too.** A turn that ends on an API error fires
+   `StopFailure`, not `Stop` — an alert wired to the wrong one misses exactly
+   the runs that need attention.
+
+One next step: take the agent command you run most often and give its end-of-turn
+a notification you would notice from across the room. That single wire closes the
+most expensive silence in the workflow.
+
+---
+
+## Fact-check table (not part of the page)
+
+Every technical claim above, with its primary source. Claims about Claude Code's
+behaviour come from its own documentation, re-read 2026-11-05.
+
+| # | Claim in the page | Source |
+|---|---|---|
+| 1 | `Stop` fires when the agent finishes responding (end of a turn); hook cadence is "per turn: UserPromptSubmit, Stop, StopFailure" | Claude Code hooks reference — https://code.claude.com/docs/en/hooks |
+| 2 | `Notification` fires "when Claude Code sends a notification"; example payload carries `notification_type: "permission_prompt"`, message "Claude needs your permission" | same hooks reference (Notification event section) |
+| 3 | `StopFailure` "runs instead of Stop when the turn ends due to an API error" (rate limits, authentication) | same hooks reference (StopFailure section) |
+| 4 | Hooks run a command of your choosing; a desktop-notification example using `osascript` is in the hooks guide | Claude Code hooks guide — https://code.claude.com/docs/en/hooks-guide (desktop-notification example) |
+| 5 | Operator anecdote: sessions that finished work but never signalled done, holding slots for hours; fix = derive done from git + idle transcript | r/ClaudeCode thread 1xjb3j0 ("Are you running a self-hosted queue of autonomous Claude Code sessions?", 2026-10-31), quoted in `drafts/listening.md` Scan 4 addendum. Quoted as one operator's described practice, not a measurement. |
+| 6 | PSA anecdote: code-review plugin showed green check + "No findings" without running | r/ClaudeCode 1xmnz2c (2026-11-03), logged in `drafts/listening.md` Scan 6. |
+| 7 | "Zero looks exactly like success" | Verbatim buyer phrasing, three independent instances (1xm09fs, 1xmnz2c, plus HN repeats) in `drafts/listening.md` Scans 5–8. Used as the problem's name, attributed to no one. |
+
+**Ban compliance:** no product of ours named · no competitor named · no
+superlatives · no benchmark numbers · no invented testimonials (anecdotes are
+real threads, described without handles) · no price · no roadmap dates.

marketing/approved/agent-done-signal/rationale.md

@@ -0,0 +1,72 @@
+# Rationale — "How do you know when your coding agent is done?"
+
+FRE-199 item 1, page 1 of the first pair. Drafted 2026-11-05 by CMO.
+
+## The phrase
+
+Primary: **"how do you know when your coding agent is done"** (variants: "agent
+finished silently", "claude code waiting for permission" overlaps on the
+blocked-half; this page owns the *done*-half).
+
+Chosen by the FRE-199 selection rule: strongest buying intent we can answer
+honestly without naming a product. It is on the standing phrase list
+(`drafts/listening.md` §The phrase list: "how do I know when my agent is done").
+
+## Why this phrase won the slot
+
+- **Recurrence with independence.** The "zero looks exactly like success"
+  pattern appears in at least four separate sources across Scans 5–9: 1xm09fs,
+  the code-review PSA (1xmnz2c), and two HN commenters (fhub, sadilek), plus
+  the queue operator's done-signal workaround (1xjb3j0). Four independent
+  formulations of one pain in seven days is the strongest recurrence the
+  backlog shows.
+- **Buying intent.** The people describing it are running agents unattended
+  right now and are losing time to the gap — they are past curiosity.
+- **Answerable honestly, generically.** The mechanism (Stop / Notification /
+  StopFailure hooks) is documented in the agent's own reference; every claim in
+  the page traces to it. Nothing about our product is needed to answer it.
+- **Wedge-aligned.** "An agent blocked is the most expensive kind of idle" —
+  the done-half of that sentence (idle you never learn about) is this page.
+
+## Evidence trail
+
+| Thread | Date | What it showed |
+|---|---|---|
+| r/ClaudeCode 1xjb3j0 — "self-hosted queue of autonomous Claude Code sessions" | 2026-10-31 | Sessions "finished their work but never sent the done signal, and held their slots for hours"; operator derives done from git + idle transcript; "a waiting one has to name what it's waiting on" |
+| r/ClaudeCode 1xm09fs | 2026-11-02 | First "zero looks exactly like success" instance (verbatim buyer phrasing) |
+| r/ClaudeCode 1xmnz2c — code-review plugin PSA | 2026-11-03 | Green check + "No findings" when the review never ran; third independent instance |
+| HN comments (fhub, sadilek) | 2026-11-04/05 | Human-attention concurrency ceiling quantified twice more |
+
+All rows live in `drafts/listening.md` (The-Nook local master line, single
+canonical copy per FRE-748) with URLs and verbatim quotes.
+
+## Gates before this page ships
+
+1. **Sponsor fact-check** of the claims table in `copy.md` (owner: Michael
+   Freno). Page moves `pending/` → `approved/` on his read, per the marketing
+   tree's hard rule.
+2. **CTO eyes on the agent-behaviour claims** — all four are sourced to the
+   Claude Code hooks reference re-read 2026-11-05, but anything asserted about
+   an agent's behaviour is CTO-verifyable, and the FRE-199 plan routes it to
+   him.
+3. **Publish path:** `pending/` → `approved/` → a human places it on
+   nook.freno.me (blog route). Nothing posts itself.
+
+## Ban compliance (FRE-199 + positioning.md rule 1)
+
+- The Nook: not named. The notch, the island, the companion: not mentioned.
+- Competitors (notch apps, agent monitors, Remote Control–style tools): not
+  named. Remote Control is not mentioned either — the page answers the done-half
+  without touching the away-from-desk half.
+- Claude Code is named only as the subject whose documented behaviour the page
+  explains, with its own docs as the source — the same status the listening
+  phrase list already gives it. It is the agent, not a competitor.
+- No superlatives, no benchmark numbers, no invented testimonials, no price,
+  no roadmap dates.
+
+## Cadence note
+
+This page and `agent-waiting-on-permission/` are the first pair. The queue
+behind them (multiple-agents tracking, invisible-permission cluster) holds well
+above the three-candidate floor, so the two-a-week cadence holds without
+inventing phrases.

marketing/approved/agent-parallel-tracking/copy.md

@@ -0,0 +1,113 @@
+# How do you keep track of multiple coding agents?
+
+> **Status: approved — sponsor fact-check passed 2026-11-05** (FRE-199 pair 2
+> fact-check card, verdict: "Approve both — move to approved/"). Not published;
+> a human places it on nook.freno.me from `approved/`. Internal target:
+> Mon 2026-11-09, met four days early. This page never names a product of ours
+> and never names a competitor.
+
+The honest answer: not by watching them. Run three agents and the watching
+already fails — the session you are not reading is the one that finished, or
+the one sitting on a question, and both states look identical from the outside.
+The fix is not more windows; it is giving each agent a way to announce its own
+state, so checking becomes something that happens to you instead of something
+you have to remember.
+
+## Why attention is the limit
+
+Parallel agents are cheap to start and expensive to supervise. Every running
+session can stop and wait for you — a permission prompt, a question, a finished
+turn — and from your side of the screen those are invisible until you go look.
+Operators who run agents at scale keep describing the same wall in different
+words. One practitioner running dozens of parallel threads a day put it as the
+limit moving "from tokens to my attention"; another, asked how many sessions
+they could run, got the answer from their own comment section: not compute —
+you. A developer who ran agents unattended for a month summarised the failure
+as silence: "the six hours of silence was the real problem, not the dialog
+itself." And the most common collision is the simplest — two agents waiting on
+you while you are deep in the third, and one of them idle so long you lost the
+thread of what you asked it to do.
+
+None of that is a speed problem. It is a visibility problem: *which* of your
+agents needs you, and *how do you find out without touring every window?*
+
+## What a per-agent signal actually is
+
+A terminal coding agent has no shared dashboard by default — each session is
+its own process, its own window. But its state changes are events, and events
+can be wired outward. Claude Code documents the pieces:
+
+- **Every state you care about fires an event.** `Stop` fires when Claude
+  finishes responding — the end of a turn. `Notification` fires when Claude
+  Code sends a notification, and the notification's type tells you which kind
+  of waiting it is: a `permission_prompt`, an `idle_prompt`, `agent_needs_input`,
+  or `agent_completed`. `SessionStart` and `SessionEnd` bracket the whole
+  session.
+- **The event names the session it came from.** Every hook payload carries a
+  `session_id`, so one handler can serve every window and still know which
+  agent fired.
+- **A hook is just a command you choose.** The events are configured in the
+  settings files and run whatever command you point them at — append to a log
+  file, update a status line, send a desktop notification that names the
+  project.
+- **The status line can carry per-session state.** Claude Code's status line
+  is a customizable bar driven by a script you write; it receives session data
+  on every render, and the docs name "work across multiple sessions and need
+  to distinguish them" as a reason it exists.
+
+The pattern in all four: stop touring windows and make each agent's
+running / waiting / finished state observable where you already are.
+
+## What to check or do
+
+1. **Name the states before naming the tools.** For your workflow the states
+   are usually three — running, waiting on you, finished — and the expensive
+   one is always "waiting on you". A tracking setup that cannot distinguish a
+   permission wait from a completion will quietly hide the state that costs
+   the most.
+2. **Wire the waiting events first.** A `Notification` hook matched on
+   `permission_prompt` and `agent_needs_input` catches the blocked cases; the
+   payload's `session_id` lets one handler label each alert with the project
+   it came from.
+3. **Route completions separately.** `Stop` means the turn ended — not that
+   the work was right, and not that nothing is blocked elsewhere. Treating
+   "finished" and "needs you" as one notification is how a waiting agent gets
+   buried under a pile of done messages.
+4. **Make the state visible without switching windows.** A per-session status
+   line, a log file the hook appends to, or a desktop notification that names
+   the project all work — the test is whether you can answer "does anything
+   need me?" without leaving the window you are in.
+5. **Expect the ceiling to be yours.** Operators consistently find the
+   bottleneck before the machines do. The number of agents you can run is the
+   number whose waiting state reaches you reliably — not the number your
+   terminal can host.
+
+One next step: run two agents side by side and wire only their permission-wait
+events to a notification that names the project. The first time the second
+agent's prompt reaches you before you happen to check its window is the whole
+argument.
+
+---
+
+## Fact-check table (not part of the page)
+
+Every technical claim above, with its primary source. Claims about Claude
+Code's behaviour come from its own documentation, re-read 2026-11-05.
+
+| # | Claim in the page | Source |
+|---|---|---|
+| 1 | `Stop` fires when Claude finishes responding; `SessionStart`/`SessionEnd` are per-session events | Claude Code hooks reference — https://code.claude.com/docs/en/hooks (hook events table; "per session: SessionStart and SessionEnd; per turn: UserPromptSubmit, Stop, and StopFailure") |
+| 2 | `Notification` fires when Claude Code sends a notification; matcher supports notification types including `permission_prompt`, `idle_prompt`, `agent_needs_input`, `agent_completed` | same hooks reference (matcher table: "Notification | notification type") |
+| 3 | Every hook payload carries `session_id`, the current session identifier | same hooks reference (Common input fields: `session_id` — "Current session identifier") |
+| 4 | Hooks are configured in the settings files and run a command of your choosing | same hooks reference (configuration and command-hook examples) |
+| 5 | The status line is a customizable bar driven by a script, receives JSON session data, and the docs name "work across multiple sessions and need to distinguish them" as a use | Claude Code status line doc — https://code.claude.com/docs/en/statusline |
+| 6 | "The limit moved from tokens to my attention" / "fifty a day add up to something I could feel by Friday" | r/ClaudeCode 1xh5cum (2026-10-27, "Four months of 50+ parallel agent threads a day"), logged in `drafts/listening.md` Scan 3. Practitioner's own account, not a measurement. |
+| 7 | "How many sessions before you become the bottleneck" — the thread went to compute; the attention half stayed on the table | r/ClaudeCode 1xdjb2g (2026-10-23, 72 comments), logged in `drafts/listening.md` Scan 1. |
+| 8 | "The six hours of silence was the real problem, not the dialog itself" | r/ClaudeCode 1xipsk0 (2026-10-29, "~40 Claude Code agents unattended for a month"), quoted by the OP in-thread, logged in `drafts/listening.md` Scan 2. |
+| 9 | Two agents waiting while the human is in the third; idle so long the thread of the task was lost; "most of my idle time came from agents waiting on a permission prompt while I was in another window" | r/ClaudeAI 1xmzp2n (2026-11-03, "How do you keep track of multiple coding agents running in parallel?"), two independent commenters, logged in `drafts/listening.md` Scan 9. |
+| 10 | "You're the bottleneck agents were meant to eliminate" — approvals routing through one person | r/ClaudeCode 1xk0ghj (2026-10-31, "multiple agents working on multiple projects"), commenter's words, logged in `drafts/listening.md` Scan 4. |
+
+**Ban compliance:** no product of ours named · no competitor named (herdr,
+tmux, dashboards: none named — the page answers generically) · no handles · no
+superlatives · no benchmark numbers · no invented testimonials (anecdotes are
+real threads, described without handles) · no price · no roadmap dates.

marketing/approved/agent-parallel-tracking/rationale.md

@@ -0,0 +1,71 @@
+# Rationale — "How do you keep track of multiple coding agents?"
+
+FRE-199 item 1, page 1 of the second pair. Drafted 2026-11-05 by CMO (internal
+target Mon 2026-11-09, beaten by four days — the backlog held, so drafting
+early cost nothing).
+
+## The phrase
+
+Primary: **"how do you keep track of multiple coding agents running in
+parallel"** (variants: "how many sessions before you become the bottleneck",
+"which agent is waiting", "agent tracking dashboard").
+
+## Why this phrase won the slot
+
+- **Strongest recurrence in the backlog.** Seven independent threads across
+  nine scans state the multi-agent attention problem in their own words — more
+  than any other cluster after the pair-1 phrases. It is the natural next page:
+  the pair-1 pages answer *one* agent's silence (done-signal) and *one*
+  permission wait (waiting-on-permission); this is the fleet-scale version of
+  the same pain, and the buyers are already at fleet scale.
+- **Buying intent.** Every quoting operator is running multiple agents *now*
+  and losing time to supervision, not exploring.
+- **Answerable honestly, generically.** The mechanism (per-session hook events
+  with `session_id`, typed notifications, the status line) is documented in the
+  agent's own reference; every claim traces to it. No product needed.
+- **Distinct from pair 1.** Done-signal owns "one agent, is it finished";
+  waiting-on-permission owns "one agent, why is it blocked". This page owns
+  "several agents, which one needs me" — the phrase, the evidence, and the
+  mechanism (typed Notification matchers, `session_id`, status line) do not
+  overlap pair 1's.
+
+## Evidence trail
+
+| Thread | Date | What it showed |
+|---|---|---|
+| r/ClaudeAI 1xmzp2n — "How do you keep track of multiple coding agents running in parallel?" | 2026-11-03 | The exact question as a fresh thread: "How do you notice when one is waiting, done, or stuck?"; two commenters independently: agents "sat waiting on a permission prompt while I was deep in the third", idle "long enough that I lost the thread of what I had asked it to do" |
+| r/ClaudeCode 1xh5cum — "Four months of 50+ parallel agent threads a day" | 2026-10-27 | "The limit moved from tokens to my attention"; "fifty a day add up to something I could feel by Friday" |
+| r/ClaudeCode 1xdjb2g — "How many sessions can you run before you become the bottleneck?" | 2026-10-23 | 72 comments; the thread went to compute and left the attention half open |
+| r/ClaudeCode 1xipsk0 — "~40 Claude Code agents unattended for a month" | 2026-10-29 | "The six hours of silence was the real problem, not the dialog itself" |
+| r/ClaudeCode 1xk0ghj — "multiple agents working on multiple projects" | 2026-10-31 | "If every decision routes through you, you're the bottleneck agents were meant to eliminate" |
+| Hacker News 50298436 (herdr launch) | 2026-10-30 | A 30-year tmux user's stated switch reason: "visual indication which agent is working and which is waiting for an input" — used in rationale only; the page does not name any tool |
+
+All rows live in `drafts/listening.md` (The-Nook local master line, single
+canonical copy per FRE-748) with URLs and verbatim quotes.
+
+## Gates before this page ships
+
+1. **Sponsor fact-check** of the claims table in `copy.md` (owner: Michael
+   Freno). Page moves `drafts/` → `pending/` → `approved/` on his read, per
+   the marketing tree's hard rule.
+2. **CTO eyes on the agent-behaviour claims** — five doc-sourced claims
+   (hooks reference ×4, statusline doc ×1), all re-read 2026-11-05. Routed to
+   the CTO per the FRE-199 plan.
+3. **Publish path:** `approved/` → a human places it on nook.freno.me.
+   Nothing posts itself.
+
+## Ban compliance (FRE-199 + positioning.md rule 1)
+
+- The Nook: not named. The notch, the island, the companion: not mentioned.
+- Competitors: not named. The herdr evidence is rationale-only; the page's
+  "what to check" recommends no tool at all — states and wiring, not products.
+- Claude Code is named only as the subject whose documented behaviour the page
+  explains, with its own docs as the source — same status as pair 1.
+- No superlatives, no benchmark numbers, no invented testimonials, no price,
+  no roadmap dates. Anecdotes are real threads, described without handles.
+
+## Cadence note
+
+Second pair. Queue behind it: the run-without-asking cluster (same pair), the
+fan-control phrase, and the invisible-permission variants — above the
+three-candidate floor. Two a week holds.

marketing/approved/agent-run-without-asking/copy.md

@@ -0,0 +1,102 @@
+# Should you let your coding agent run without asking permission?
+
+> **Status: approved — sponsor fact-check passed 2026-11-05** (FRE-199 pair 2
+> fact-check card, verdict: "Approve both — move to approved/"). Not published;
+> a human places it on nook.freno.me from `approved/`. Internal target:
+> Mon 2026-11-09, met four days early. This page never names a product of ours
+> and never names a competitor.
+> CTO review 2026-11-05: changes requested and applied — the `Bash(git commit *)`
+> allowed / `Bash(git push *)` denied example removed (the docs' own
+> "What a Bash rule doesn't match" table shows a Bash rule does not stop every
+> invocation); the precedence claim stands.
+
+You can — and the honest answer is that "should" is not one decision but two:
+what you are letting it do, and what happens when it does the wrong thing.
+Every operator who runs agents unattended converges on the same split — a free
+hand on what git can undo, a confirmation on what it can't — and the agent's
+own permission modes exist to draw that line somewhere you choose, not
+somewhere a flag chooses for you.
+
+## The mechanism: a spectrum, not a switch
+
+Claude Code's permission modes form a ladder from "ask for everything" to "ask
+for almost nothing", and each rung has a documented meaning:
+
+- **`default`** prompts on the first use of each tool.
+- **`acceptEdits`** auto-accepts file edits and common filesystem commands
+  (`mkdir`, `touch`, `mv`, `cp`) inside the working directory.
+- **`plan`** reads files and runs read-only shell commands but does not edit
+  your source files — the agent explores, you approve the plan.
+- **`auto`** runs without routine prompts; before actions such as shell
+  commands and network requests run, a background classifier checks that they
+  align with your request.
+- **`bypassPermissions`** skips permission prompts, except for actions no mode
+  auto-approves.
+
+Two documented facts should shape where you stop on that ladder. First, the
+docs' own warning on the top rung: in `bypassPermissions` mode Claude Code
+skips prompts — including for writes to protected paths such as `.git` — and
+the mode belongs "in isolated environments like containers or VMs where Claude
+Code can't cause damage". Second, enforcement is real, not advisory: the docs
+state plainly that "permission rules are enforced by Claude Code, not by the
+model" — a `CLAUDE.md` instruction asking nicely for permission changes
+nothing.
+
+## What to check or do
+
+1. **Decide by blast radius, not by annoyance.** The question "how do I get
+   fewer prompts?" tempts a jump to the top of the ladder. The better
+   question: which of this agent's actions would be *undoable* if wrong? Edits
+   inside a git worktree are; `rm -rf` on the wrong path, a pushed commit, and
+   a message sent to a third party are not.
+2. **Move down the ladder one rung at a time.** `acceptEdits` in a worktree
+   covers most of the prompt volume with the undo still in reach. If you
+   consider `auto` or `bypassPermissions`, the docs' own container-or-VM
+   condition is the bar: isolation first, autonomy second.
+3. **Write the rules instead of trusting the mode.** Rules are evaluated in
+   order — deny, then ask, then allow — and the first match wins, so a broad
+   deny holds even against a narrower allow. (What a Bash rule cannot do is
+   match every way the same binary gets invoked — see the next step.)
+4. **Know what the rules do not cover.** A Bash rule matches the command text
+   Claude writes, and the docs are explicit that this "isn't a security
+   boundary around the program" — the same binary invoked by another path is
+   not matched. For filesystem and network enforcement that does not depend
+   on command text, the docs point at sandboxing.
+5. **Use hooks as the programmable layer.** A `PreToolUse` hook sees every
+   tool call before it runs and can return a `deny` decision — the reference
+   builds one that blocks `rm -rf`. A silent hook does not approve anything;
+   the call just continues through the normal permission flow.
+6. **Leave the failure path a way to reach you.** An unattended run that hits
+   a prompt nobody sees stops silently — that is the failure mode of unattended
+   work, not of permissions. Whatever mode you pick, wire the
+   "waiting on you" event somewhere you will actually notice.
+
+One next step: write down the three actions your agent takes that you could
+not undo, and put them in `deny` or `ask` rules today. Whatever mode you run
+above them, those three now require a human — which is the whole point of the
+ladder.
+
+---
+
+## Fact-check table (not part of the page)
+
+Every technical claim above, with its primary source. Claims about Claude
+Code's behaviour come from its own documentation, re-read 2026-11-05.
+
+| # | Claim in the page | Source |
+|---|---|---|
+| 1 | Mode meanings: `default` prompts on first use; `acceptEdits` auto-accepts file edits and common filesystem commands (`mkdir`, `touch`, `mv`, `cp`) in the working directory; `plan` reads files and runs read-only shell commands but doesn't edit source; `auto` runs without routine prompts with a background classifier checking alignment; `bypassPermissions` skips prompts except actions no mode auto-approves | Claude Code permissions doc — https://code.claude.com/docs/en/permissions (Permission modes table) |
+| 2 | Docs' warning: in `bypassPermissions` mode Claude Code skips prompts including for writes to protected paths such as `.git`; "Only use this mode in isolated environments like containers or VMs where Claude Code can't cause damage" | same permissions doc (warning under the modes table) |
+| 3 | "Permission rules are enforced by Claude Code, not by the model" | same permissions doc (note under Manage permissions) |
+| 4 | Rules evaluated in order deny → ask → allow; first match wins; a broad deny holds against a narrower allow | same permissions doc (Manage permissions) |
+| 5 | A Bash rule matches the command text Claude writes and "isn't a security boundary around the program" (`Bash(curl *)` doesn't stop `/usr/bin/curl …`); for filesystem/network enforcement independent of command text the docs point at sandboxing | same permissions doc (What a Bash rule doesn't match) |
+| 6 | A `PreToolUse` hook fires before a tool call executes, can block it, and can return a `permissionDecision` of `"deny"`; the reference builds a hook that blocks `rm -rf`; a silent hook does not approve — the call continues through the normal permission flow | Claude Code hooks reference — https://code.claude.com/docs/en/hooks (PreToolUse decision control walkthrough) |
+| 7 | Undo-split practice ("free hand on what git can undo, confirmation on what it can't") | r/ClaudeCode 1xkoz06 (2026-10-31), commenter's described practice, logged in `drafts/listening.md` Scan 3 addendum; also r/ClaudeCode 1xexhwf commenters (VM, worktrees, blast-radius split). Described as operator practice, not a rule. |
+| 8 | An unattended run that hits a prompt nobody sees stops silently | r/ClaudeCode 1xipsk0 (2026-10-29), commenter: "A run started from launchd or a background service can hit a prompt that no one will ever see", logged in `drafts/listening.md` Scan 2. |
+| 9 | The trust asymmetry: comfortable with a model writing code, "considerably less comfortable giving an autonomous agent broad access to my development environment" | r/ClaudeCode 1xk8imc (2026-10-31, "Has anyone built a safe, autonomous coding workflow…?", 43 comments), OP's words, logged in `drafts/listening.md` Scan 4. |
+| 10 | The operator's own safety menu: "committing before every run? containers? `--dangerously-skip-permissions` and hoping?" | r/ClaudeAI 1xk277d (2026-10-31, "How often has a coding agent done something you had to undo?"), OP's words, logged in `drafts/listening.md` Scan 4. Quoted as the question's shape, not as guidance. |
+
+**Ban compliance:** no product of ours named · no competitor named · no
+handles · no superlatives · no benchmark numbers · no invented testimonials ·
+no price · no roadmap dates. The docs' container/VM warning is quoted as the
+agent's own documentation, not as our policy.

marketing/approved/agent-run-without-asking/rationale.md

@@ -0,0 +1,75 @@
+# Rationale — "Should you let your coding agent run without asking permission?"
+
+FRE-199 item 1, page 2 of the second pair. Drafted 2026-11-05 by CMO (internal
+target Mon 2026-11-09, beaten by four days).
+
+## The phrase
+
+Primary: **"do you let your coding agent run without asking permission"**
+(variants: "safe autonomous coding workflow", "approve every step or skip
+permissions", "is dangerously-skip-permissions safe").
+
+On the standing phrase list (`drafts/listening.md` §The phrase list: "do you
+let claude code run without asking").
+
+## Why this phrase won the slot
+
+- **Recurrence with independence.** Four separate threads state the autonomy
+  question from four angles: the direct one (1xexhwf, 24 comments), the trust
+  asymmetry (1xk8imc, 43 comments), the safety menu (1xk277d), and the
+  remove-permissions ask (1xfe6eh — Desktop, recorded, not answered). The
+  cluster has run continuously since Scan 1.
+- **Buying intent.** These are people configuring or rejecting autonomy right
+  now — the objection vocabulary came straight out of this cluster
+  ("--dangerously-skip-permissions and hoping").
+- **Answerable honestly, generically.** The mode ladder, the docs' own
+  container/VM warning, the enforcement note, and `PreToolUse` deny are all
+  documented; every claim traces to the agent's docs. No product needed.
+- **Distinct from pair 1's permission page.** `agent-waiting-on-permission`
+  answers "why is it *blocked* and why didn't I know" — the visibility of a
+  single stuck prompt. This page answers "should I *grant* autonomy and how do
+  I bound it" — the mode ladder, rule precedence, sandboxing, and hooks as
+  enforcement. Shared vocabulary (modes, rules) exists because the docs are
+  one system; the question, the claims, and the advice do not overlap.
+
+## Evidence trail
+
+| Thread | Date | What it showed |
+|---|---|---|
+| r/ClaudeCode 1xexhwf — "Do you let Claude Code run without asking, or approve every step?" | 2026-10-25 | The direct question, 24 comments; the thread became a safety argument (VM, worktrees, empty-variable `rm -rf`) — that argument *is* the page's subject |
+| r/ClaudeCode 1xk8imc — "Has anyone built a safe, autonomous coding workflow…?" | 2026-10-31 | "Comfortable having another model work on code. Considerably less comfortable giving an autonomous agent broad access to my development environment" — the trust asymmetry, 43 comments |
+| r/ClaudeAI 1xk277d — "How often has a coding agent done something you had to undo?" | 2026-10-31 | "What you do to stay safe today: committing before every run? containers? `--dangerously-skip-permissions` and hoping?" — the operator's own menu |
+| r/ClaudeCode 1xipsk0 — "~40 agents unattended for a month" | 2026-10-29 | "A run started from launchd or a background service can hit a prompt that no one will ever see" — the unattended failure path |
+| r/ClaudeCode 1xkoz06 | 2026-10-31 | The undo-split practice (also cited on pair 1; real thread, described without handles) |
+| r/ClaudeAI 1xfe6eh — "How can I remove Claude's need to ask me for permission…" | 2026-10-30 | Recorded, not used: Claude Desktop computer-use, not Code — a mention there would be noise. Shows the phrase's reach |
+
+All rows live in `drafts/listening.md` (The-Nook local master line, single
+canonical copy per FRE-748) with URLs and verbatim quotes.
+
+## Gates before this page ships
+
+1. **Sponsor fact-check** of the claims table in `copy.md` (owner: Michael
+   Freno). Page moves `drafts/` → `pending/` → `approved/` on his read.
+2. **CTO eyes on the agent-behaviour claims** — six doc-sourced claims
+   (permissions doc ×5, hooks reference ×1), all re-read 2026-11-05. Routed to
+   the CTO per the FRE-199 plan.
+3. **Publish path:** `approved/` → a human places it on nook.freno.me.
+   Nothing posts itself.
+
+## Ban compliance (FRE-199 + positioning.md rule 1)
+
+- The Nook: not named. The notch, the island, the companion: not mentioned.
+- Competitors: not named. Sandboxing and hooks are described as the agent's
+  own documented mechanisms, not as anyone's product.
+- Claude Code is named only as the subject whose documented behaviour the page
+  explains, with its own docs as the source — same status as pair 1.
+- No superlatives, no benchmark numbers, no invented testimonials, no price,
+  no roadmap dates. Anecdotes are real threads, described without handles.
+
+## Cadence note
+
+Second pair. Queue behind it: the fan-control phrase ("mac fan control
+claude", standing phrase list), the invisible-permission variants
+(dontallow/TCC cluster), and the notification-reliability thread (1xm6frp,
+held back for overlap with done-signal). Above the three-candidate floor; two
+a week holds.

marketing/approved/agent-waiting-on-permission/copy.md

@@ -0,0 +1,86 @@
+# Why is my coding agent sitting on a permission prompt?
+
+> **Status: approved — sponsor fact-check passed 2026-11-05** (FRE-199 fact-check
+> card, verdict: "Approve both — move to approved/"). Not published; a human
+> places it on nook.freno.me from `approved/`.
+> This page never names a product of ours and never names a competitor.
+> Internal target: second page of the FRE-199 pair, Fri 2026-11-07.
+> CTO review 2026-11-05: changes requested and applied — rule precedence
+> corrected to deny / ask / allow (body previously read allow / ask / deny,
+> contradicting the fact-check table and the source); pair-1 citations
+> standardised to code.claude.com.
+
+Because it tried to do something its permission settings don't allow, and the
+default is to wait — indefinitely and quietly — for you. The prompt is not the
+expensive part; the hour you spent not knowing it was waiting is. The way out is
+not to approve faster, it's to make the prompts rare and the waiting visible.
+
+## The mechanism
+
+Claude Code's permission system decides, per tool call, whether to run, refuse,
+or stop and ask. In its `default` mode, it prompts for permission on the first
+use of each tool. Modes are set with `defaultMode` in the settings files, and a
+session's rules come from deny / ask / allow lists evaluated in that order —
+the first match wins.
+
+You can see the whole rule set at any time with `/permissions`, which lists
+every permission rule and the settings file each one came from. Rules can name
+a specific use — `Bash(npm run build)` matches exactly that command — or a
+wildcard, like `Bash(git log *)`.
+
+So the prompt you came back to an hour later is not a malfunction. It is the
+system working as configured, on a call your rules never covered — and the
+"waiting" state being invisible is what turned ten seconds of approval into a
+lost hour.
+
+## What to check or do
+
+1. **Read the prompt before automating it away.** It names the tool and the
+   input. The right response to "it keeps asking" is usually a rule, not a
+   wider mode.
+2. **Allowlist the undoable, prompt on the irreversible.** Reads, tests, and
+   status commands are safe to allow — `git` is the undo for edits. Anything
+   that reaches another person or another system — network calls, deletes,
+   deploys — is worth keeping on ask. Rule syntax is in the permission docs;
+   `/permissions` shows what you already have.
+3. **Consider `acceptEdits` before anything broader.** It auto-accepts file
+   edits and common filesystem commands inside the working directory. That is
+   usually the difference between ten prompts a session and two — without
+   handing over network or delete.
+4. **Bound the blast radius instead of removing the gate.** If you do widen
+   what runs unattended, do it where a mistake is recoverable: a worktree per
+   task, commits pushed early, nothing irreversible in reach. Operators who run
+   agents unattended describe exactly this split — free hand on what git can
+   undo, confirmation on what it can't.
+5. **Make the wait visible.** Claude Code fires a `Notification` hook when it
+   sends a notification, and a permission prompt is one — the payload carries a
+   `notification_type` of `permission_prompt`. A hook on that event, wired to a
+   desktop notification you'd see from another window, turns the silent wait
+   back into a ten-second approval.
+
+One next step: run `/permissions` today and add allow rules for the three
+commands you find yourself approving most. The prompts that remain will be the
+ones that deserve a read.
+
+---
+
+## Fact-check table (not part of the page)
+
+Every technical claim above, with its primary source. Claims about Claude
+Code's behaviour come from its own documentation, re-read 2026-11-05.
+
+| # | Claim in the page | Source |
+|---|---|---|
+| 1 | In `default` mode Claude Code "prompts for permission on first use of each tool" | Claude Code permissions doc — https://code.claude.com/docs/en/permissions (Permission modes table) |
+| 2 | `defaultMode` in settings files sets the default mode for new sessions | same permissions doc (Permission modes section) |
+| 3 | Rules are evaluated deny → ask → allow, first match wins | same permissions doc (Permission rule syntax) |
+| 4 | `/permissions` lists all permission rules and the settings.json each comes from | same permissions doc (Manage permissions) |
+| 5 | `Bash(npm run build)` matches the exact command; `Bash(git log *)` wildcard form | same permissions doc (Use specifiers for fine-grained control) |
+| 6 | `acceptEdits` "automatically accepts file edits and common filesystem commands such as mkdir, touch, mv, cp for paths in the working directory" | same permissions doc (Permission modes table) |
+| 7 | A `Notification` hook fires when Claude Code sends a notification; permission prompts carry `notification_type: "permission_prompt"` and a message like "Claude needs your permission" | Claude Code hooks reference — https://code.claude.com/docs/en/hooks (Notification event) |
+| 8 | Undo-split practice ("free hand on what git can undo, confirmation on what it can't") | r/ClaudeCode 1xkoz06 (2026-10-31, u/tomm3hshipp thread), commenter's described practice, logged in `drafts/listening.md` Scan 3 addendum. Described as one operator's approach, not a rule. |
+| 9 | The 55-minutes-lost framing | r/ClaudeAI 1xhbc71 (2026-10-28): "coming back an hour later to find it's been sitting on a permission prompt for 55 minutes". Used as the problem's shape, not quoted as a person. |
+
+**Ban compliance:** no product of ours named · no competitor named · no
+superlatives · no benchmark numbers · no invented testimonials · no price · no
+roadmap dates.

marketing/approved/agent-waiting-on-permission/rationale.md

@@ -0,0 +1,77 @@
+# Rationale — "Why is my coding agent sitting on a permission prompt?"
+
+FRE-199 item 1, page 2 of the first pair. Drafted 2026-11-05 by CMO.
+
+## The phrase
+
+Primary: **"claude code waiting for permission"** and the away-from-desk variant
+("approvals when you're away from the computer"). First phrase on the standing
+list (`drafts/listening.md` §The phrase list).
+
+## Why this phrase won the slot
+
+- **The strongest single thread in the backlog.** r/ClaudeAI 1xhbc71 (2026-10-28,
+  47 comments and moving) asks the buying question outright: kicked off a long
+  task, came back an hour later, agent had been sitting on a permission prompt
+  for 55 minutes. The thread's own answers (remote control, tmux+SSH,
+  skip-permissions, allowlists) prove demand; none of them makes the wait
+  visible at the machine — that is the honest gap this page answers without
+  naming anyone.
+- **The week's objection vocabulary.** Scans 1–9 keep returning "the model keeps
+  handing control back" and "stops and waits for me" — permission friction is
+  the category's core complaint, not a niche one.
+- **Recurring independent accounts.** The invisible-permission theme has three
+  independent accounts in one week (1xksutq — gh used without a visible prompt;
+  1xkejsp's Linux panel; the scheduled-tasks silent-stall finding), so the
+  search demand is not one loud thread.
+- **Wedge-aligned.** This is the literal wedge sentence's territory — "an agent
+  blocked on a permission prompt is the most expensive kind of idle" — answered
+  with the agent's own documented mechanism.
+
+## Deliberate scoping
+
+This page owns the **blocked-half** of the approval problem (why prompts happen,
+how to make them rare, how to make the wait visible at the machine). The
+**away-half** (controlling a remote agent from elsewhere) is a different phrase,
+a different page, and one where the honest answer is dominated by the agent
+vendor's own remote feature — the page deliberately does not go there
+(`drafts/listening.md` Scan 1 category intel #1).
+
+## Evidence trail
+
+| Thread | Date | What it showed |
+|---|---|---|
+| r/ClaudeAI 1xhbc71 — "How do you handle Claude Code approvals when you're away from your computer?" | 2026-10-28 | 55-minute wait on a permission prompt; 47 comments of demand; "what's still annoying about your setup?" |
+| r/ClaudeCode 1xkoz06 — "How permissive are you with AI and for how long?" | 2026-10-31 | The undo-split: "file edits, tests and branches get a free hand, since git is the undo. Anything that reaches another person … stays on confirm" |
+| r/ClaudeCode 1xksutq — gh used without visible prompt | 2026-11-01 | Third independent invisible-permission account of the week |
+| r/ClaudeCode 1xkejsp — Linux panel app | 2026-10-31 | Per-session "Needs You" differentiation shipping elsewhere; the need is real and cross-platform |
+
+All rows live in `drafts/listening.md` with URLs and verbatim quotes.
+
+## Gates before this page ships
+
+1. **Sponsor fact-check** of the claims table in `copy.md` (owner: Michael
+   Freno); page moves `pending/` → `approved/` on his read.
+2. **CTO eyes on the agent-behaviour claims** — all eight doc-sourced claims
+   re-read 2026-11-05; the FRE-199 plan routes anything asserted about an
+   agent's behaviour to the CTO.
+3. **Publish path:** `pending/` → `approved/` → a human places it on
+   nook.freno.me (blog route). Nothing posts itself.
+
+## Ban compliance (FRE-199 + positioning.md rule 1)
+
+- The Nook: not named; notch/island/companion not mentioned.
+- Competitors: not named — including the agent vendor's remote feature, which
+  the page never needs to mention because it stays on the at-the-machine half.
+- Claude Code is named only as the subject whose documented permission system
+  the page explains, with its own docs as the source — same status the
+  listening phrase list already gives it.
+- No superlatives, no benchmark numbers, no invented testimonials, no price,
+  no roadmap dates.
+
+## Cadence note
+
+Second page of the first pair. Queue behind it: multi-agent tracking ("How do
+you keep track of multiple coding agents running in parallel?", 1xm6frp,
+2026-11-03) and the invisible-permission cluster — the queue holds above the
+three-candidate floor, so the two-a-week cadence holds.

marketing/briefs/registry-wave-2.md

@@ -0,0 +1,91 @@
+# Registry wave 2 — brief and copy (FRE-199 item 3)
+
+**Owner:** CMO prepares · sponsor submits · **Copy ready 2026-11-05** (target was
+Fri 2026-11-13) · **Submit:** week of 2026-11-16, after the wave-1 readback.
+**Status:** `briefs/` — nothing here has been posted; humans hold every account;
+no agent authenticates, posts or sends.
+
+## What wave 2 is, and what it waits for
+
+Wave 1 is FRE-207's packet (`The-Nook` worktree `drafts/directory-submissions.md`
++ `drafts/click-list.md`): 8 targets, CTO claim verdict applied 2026-11-01
+(C1–C5 signed, C7 refused → relay sentence), sponsor-owned inputs G2 (price
+line), G3 (`@freno.me` mailbox), G4 (screenshots). **Wave-2 submission waits on
+the wave-1 readback** — what actually got submitted, what got listed, what was
+rejected and why — so targets can be re-ranked on evidence instead of guesswork.
+The readback lives on the FRE-207 issue; this brief is ready either way.
+
+**Copy rule inherited from wave 1:** paste the wave-1 blocks, do not improvise.
+Only claims signed by the CTO verdict ship:
+
+- C1 — works with 18 coding agents (compatibility fact, not a competitor mention).
+- C2 — answer an agent's approval from your Mac, iPhone or Watch.
+- C3 — sessions keep arriving while the Mac app is closed (widgets; fleet status only).
+- C4 — macOS 14.2+, universal.
+- C5 — iPhone/iPad and Apple Watch companions are **TestFlight beta**; no App Store link anywhere.
+- C7 — "no cloud service of its own" is refused; block D ships the relay sentence.
+- **Price line (G2):** "Free 14-day trial" only — no number — until CoS + sponsor
+  clear the "$10 one-time licence" line for public listings (FRE-204 holds $10 in-app;
+  the listing text is a separate publish decision).
+- Banned: superlatives, user counts, testimonials, competitor names.
+
+## Targets — fetched live 2026-11-05, marked per the wave-1 legend
+
+| # | Target | What it is | How it ships | Fit | Verified |
+|---|---|---|---|---|---|
+| W2-1 | `iCHAIT/awesome-macOS` (19.4k ★) | Curated macOS app list; PR-based | PR adding one line to the relevant section from `contributing.md`; copy: block A + block B compressed | High — category fit, persistent link | ✅ repo + contributing rules read 2026-11-05 |
+| W2-2 | 1000.tools | Curated tool directory, self-serve categories (AI, developer tools, productivity) | Category submission form; copy: block A + B | Medium-high | ✅ fetched 2026-11-05 (categories listed on page) |
+| W2-3 | uneed.best | Daily product launch site | Launch submission (account needed, held by a human) | Medium — launch-format, needs assets | ✅ fetched 2026-11-05 |
+| W2-4 | devhunt.org | Daily dev-tool launches | Launch submission | Medium | ✅ fetched 2026-11-05 |
+| W2-5 | Product Hunt | Launch site | Maker/hunter flow, on-screen (403 to plain fetch — read live before filing) | Low-medium this wave; big-audience launch usually wants FRE-203's launch-day coordination | ⚠️ bot-walled; fields read on screen |
+
+Re-rank after the wave-1 readback: if directory listings (wave-1 §1/§3–5)
+produced traffic or referrers, wave 2 leads with W2-1/W2-2; if nothing was
+submittable, wave 2 waits until G3/G4 clear rather than submitting half-copy.
+
+## Copy — paste-ready, inheriting the signed claims only
+
+**One-liner (≤60):** `Your coding agents, at the edge of the screen` (43 chars — wave-1 block A).
+
+**Short description (~250 chars):** wave-1 block B verbatim; if a field forces a
+price, "Free 14-day trial" and no number (G2).
+
+**awesome-macOS PR line (one row, section: menu-bar / status-bar apps or the
+section the maintainers route notch apps to — read the README section headers
+before filing):**
+
+```
+- [The Nook](https://nook.freno.me/) - Puts every coding-agent session at the
+  edge of your screen and lets you answer approvals from your Mac, iPhone or
+  Watch. Works with 18 coding agents. [![Open-Source Software][OSS Icon]] — not
+  open source; omit the badge row, keep the description.
+```
+
+(The badge syntax is copied from the list's own rows; The Nook is not open
+source, so the OSS badge is **omitted** — the line above shows the shape only.
+No TestFlight mention needed in a one-row listing; add "Companions for iPhone
+and Apple Watch (TestFlight beta)" only if the PR reviewer asks for platform
+detail — C5 wording.)
+
+**Launch-site fields (W2-3/W2-4):** wave-1 blocks A, B, C (widgets — fleet
+status only), D (relay sentence, not C7's refused wording). Gallery needs G4's
+three real screenshots.
+
+## Gates before anything here is submitted
+
+| Gate | Owner | State |
+|---|---|---|
+| Wave-1 readback recorded (what submitted/listed/rejected) | sponsor → FRE-207 issue, carried to FRE-199 | owed before submission week |
+| G2 price line for public listings | CoS + sponsor | pending (copy ships without a number either way) |
+| G3 `hello@freno.me` mailbox | sponsor | pending |
+| G4 three real screenshots + logo PNG | sponsor or CTO | pending — blocks every upload field |
+| Claim sign-off | CTO | **cleared 2026-10-31** for C1–C5; C7 ships as the relay sentence |
+
+## Provenance
+
+- Targets fetched 2026-11-05: uneed.best, devhunt.org, 1000.tools (HTTP 200,
+  content read); `iCHAIT/awesome-macOS` via GitHub API (19,441 stars,
+  contributing.md linked from README); producthunt.com returns 403 to a plain
+  fetch — marked ⚠️, read on screen before filing.
+- All claims inherited from FRE-207's CTO verdict of 2026-10-31 — no new
+  claims introduced by this brief.

marketing/drafts/agent-keeps-asking/copy.md

@@ -0,0 +1,96 @@
+# Why does your coding agent keep stopping to ask you questions?
+
+> **Status: draft — awaiting sponsor fact-check** (FRE-199 pair 3, internal target
+> Thu 2026-11-12). Not publishable from `drafts/`.
+> This page never names a product of ours and never names a competitor.
+
+Most of the stopping is not the model being chatty — it is the permission system
+doing what it was told. In the default mode, the agent prompts before the first
+use of each tool; separately, its turn ends every time it finishes responding,
+and ending a turn with a question is finishing a turn. You cannot and should not
+eliminate every ask — but you can decide, once, which asks deserve an
+interruption and let the routine ones pass without you.
+
+## Where the asks come from
+
+**Permission gates.** In the default mode the agent "prompts for permission on
+first use of each tool" — so every new tool, and often every new command shape,
+costs one prompt. The configuration decides who answers:
+
+- **`acceptEdits`** automatically accepts file edits and common filesystem
+  commands (like `mkdir`, `touch`, `mv`, `cp`) for paths in your working
+  directory — the single biggest ask category for most coding sessions, gone.
+- **Permission rules** do the fine work: `deny` rules block a tool outright,
+  `allow` rules pass it silently, `ask` rules force the prompt. Order matters:
+  rules are evaluated deny, then ask, then allow — the first match wins, and an
+  allow rule cannot carve an exception out of a deny.
+- **Modes set the floor.** `defaultMode` in your settings picks where every new
+  session starts. At the far end, `bypassPermissions` skips prompts entirely —
+  the docs' own warning is that it belongs only in isolated environments like
+  containers or VMs.
+
+One fact worth internalising: permission rules are enforced by the coding
+agent's harness, not by the model. A line in your prompt asking it to "not ask"
+changes nothing about what it is allowed to do — the configuration is the only
+lever.
+
+**Turn ends.** A `Stop` hook fires when the agent finishes responding — every
+turn, including the turns that end in a question. From the terminal's side of
+the glass, "it finished", "it's asking me something" and "it's waiting on a
+permission prompt" are the same silence. That is why the asking *feels*
+endless: each ask costs a context switch, and nothing distinguishes the asks
+from the completions.
+
+Practitioners describe the pattern in their own words. A developer who measured
+why their sessions kept stopping found that the agent "just kept handing
+control back" even with a permissive mode already on — the model's own habit of
+ending turns to stay in the loop, on top of the permission asks. An operator
+running a team of agents with per-agent autonomy levels put the other side:
+"if every decision routes through you, you're the bottleneck agents were meant
+to eliminate."
+
+## What to check or do
+
+1. **Sort the asks by kind before touching anything.** File edits in your
+   working directory: `acceptEdits` removes them wholesale. The same safe
+   command every session: an `allow` rule. The commands that must never run: a
+   `deny` rule. What is left is the set of questions only you can answer.
+2. **Write the rules in the right order.** Deny, then ask, then allow; first
+   match wins. A broad deny stays broad — narrowing an allow elsewhere does not
+   soften it.
+3. **Keep the genuinely ambiguous asks.** A mode that asks less is not a mode
+   that asks smarter. `bypassPermissions` in a throwaway container is a
+   documented pattern for unattended runs; using it on your daily machine is
+   the docs' own caution, not a recommendation.
+4. **Make every stop visible.** Because every stop ends a turn, wire the
+   turn-end and notification moments (the `Stop` and `Notification` hooks) so
+   an ask reaches you where you actually are — and a permission wait is
+   distinguishable from a finished job.
+
+One next step: run one session with the asks tallied by kind — edits, known
+commands, everything else. The first two usually turn out to be rules you
+hadn't written yet; the third is the work.
+
+---
+
+## Fact-check table (not part of the page)
+
+Every technical claim above, with its primary source. Claims about the
+permission system and hooks were verified against the live docs on 2026-11-05.
+
+| # | Claim in the page | Source |
+|---|---|---|
+| 1 | Default mode "prompts for permission on first use of each tool" (labeled Manual; `manual` alias) | Claude Code permissions doc — https://code.claude.com/docs/en/permissions (permission modes table; fetched 2026-11-05) |
+| 2 | `acceptEdits` "automatically accepts file edits and common filesystem commands such as mkdir, touch, mv, and cp for paths in the working directory or additionalDirectories" | same page (permission modes table) |
+| 3 | Rules are evaluated in order deny, then ask, then allow; "the first match in that order determines the outcome"; "an allow rule can't carve an exception out of a deny rule" | same page (rule precedence section) |
+| 4 | `bypassPermissions` "skips permission prompts"; docs' caution: "Only use this mode in isolated environments like containers or VMs where Claude Code can't cause damage" | same page (permission modes table) |
+| 5 | `defaultMode` in settings files sets the default permission mode for new sessions | same page ("To change the default permission mode for new sessions, set defaultMode in your settings files") |
+| 6 | "Permission rules are enforced by Claude Code, not by the model. Instructions in your prompt or CLAUDE.md shape what Claude tries to do, but they don't change what Claude Code allows." | same page (verbatim) |
+| 7 | `Stop` fires when the agent finishes responding; hook cadence is per turn | Claude Code hooks reference — https://code.claude.com/docs/en/hooks (verified 2026-11-05 in FRE-199 round 1; unchanged) |
+| 8 | Anecdote: "it just kept handing control back"; sessions kept stopping with a permissive mode on | r/ClaudeCode thread 1xlfqmo ("I measured why my Claude Code sessions kept stopping…", 2026-11-01, u/belovoj), logged in `drafts/listening.md` Scan 5 #1. Quoted as one developer's described experience; the thread's own measurement figures are deliberately **not** cited. |
+| 9 | Anecdote: "if every decision routes through you, you're the bottleneck agents were meant to eliminate"; per-agent autonomy levels 0–5 | r/ClaudeCode thread 1xk0ghj ("multiple agents working on multiple projects", 2026-10-31, quote by u/iceydee), logged in `drafts/listening.md` Scan 4 #2. One operator's described practice. |
+
+**Ban compliance:** no product of ours named · no competitor named · no
+superlatives · no benchmark numbers (the 1xlfqmo poster's measurement figures
+are deliberately not cited) · no invented testimonials (anecdotes are real
+threads, described without handles) · no price · no roadmap dates.

marketing/drafts/agent-keeps-asking/rationale.md

@@ -0,0 +1,52 @@
+# Rationale — "Why does your coding agent keep stopping to ask you questions?"
+
+FRE-199 item 1, page 2 of the third pair. Drafted 2026-11-06 by CMO (internal
+target Thu 2026-11-12 — six days early).
+
+## The phrase
+
+Primary: **"why does my coding agent keep stopping to ask me questions"**
+(variants: "agent keeps handing control back", "claude code keeps asking for
+permission"). The H1 carries the generic form; "handing control back" is the
+backlog's own added phrase (Scan 5's phrase-list finding).
+
+## Why this phrase won the slot
+
+- **Backlog evidence.** r/ClaudeCode 1xlfqmo (2026-11-01, Scan 5 #1): "Auto mode
+  was already on, so permissions weren't the issue… it just kept handing
+  control back"; "the model was forcably trying to keep me in the loop." The
+  phrase-list finding from the same scan added "handing control back" as a
+  standing query. Corroborated by 1xlxw0q (turns ending with "nothing yet") and
+  the autonomy-ladder operator (Scan 4 #2, thread 1xk0ghj: "if every decision
+  routes through you, you're the bottleneck agents were meant to eliminate").
+- **Shortlist position (c)** in the plan's pair-3 shortlist, recorded at
+  revision 5 — the page extends the done-signal cluster (pair 1) with the
+  handback half. The distinction is kept deliberately: *agent-done-signal*
+  owns "how do I know it's done"; this page owns "why does it keep stopping on
+  me". Different question, different searcher.
+- **Answerable honestly from verified sources only.** Every mechanism claim
+  re-reads to the permissions doc and hooks reference — the same pages and the
+  same claims the CTO verified in FRE-199 rounds 1–2 (mode ladder, precedence,
+  acceptEdits scope, enforced-by-harness sentence, Stop cadence). Nothing new
+  is asserted about agent behaviour.
+
+## What the page deliberately does not do
+
+- **Does not cite the 1xlfqmo poster's measurement figures** (the 28-of-73
+  sample is the poster's own 18-day data, and the backlog row carries an
+  explicit do-not-cite flag). The anecdote is quoted as experience, not
+  measurement, and the fact-check table says so.
+- Does not promise the asks can be eliminated. The honest answer is that the
+  asking is partly the permission system working as configured and partly the
+  agent ending turns to stay in the loop — the page sorts which is which.
+- Does not touch environment contention (page 1 of this pair owns that half).
+
+## Evidence trail
+
+| Thread | Date | What it showed |
+|---|---|---|
+| r/ClaudeCode 1xlfqmo — "I measured why my Claude Code sessions kept stopping" | 2026-11-01 | "It just kept handing control back" with a permissive mode on; "forcibly trying to keep me in the loop" — the model-behaviour half |
+| r/ClaudeCode 1xk0ghj — "multiple agents working on multiple projects" (quote by u/iceydee) | 2026-10-31 | "If every decision routes through you, you're the bottleneck agents were meant to eliminate"; per-agent autonomy levels 0–5 — the configuration half |
+| r/ClaudeAI 1xlxw0q — "2,300 hours waiting" | 2026-11-02 | Turns ending in a one-word answer reload context each time — the per-ask cost, corroborating |
+
+All rows live in `drafts/listening.md` (The-Nook local master line).

marketing/drafts/agent-worktree-contention/copy.md

@@ -0,0 +1,72 @@
+# How do you manage worktrees when your agents end up waiting on each other?
+
+> **Status: draft — awaiting sponsor fact-check** (FRE-199 pair 3, internal target
+> Thu 2026-11-12). Not publishable from `drafts/`.
+> This page never names a product of ours and never names a competitor.
+
+Usually, the worktrees are not what your agents are waiting on — the environment
+they share is. Two agents can sit in two worktrees of the same repo and still
+queue up behind one dev server, one test database, one `docker compose` stack.
+The fix that scales is to multiply the environment per worktree, not to
+orchestrate the waiting.
+
+## Why agents queue when the code doesn't
+
+Git supports parallel work out of the box: `git worktree add <path> <branch>`
+creates a second working directory linked to the same repository — shared
+history, but its own HEAD, its own index, its own checked-out branch. Git even
+enforces the ownership half for you: it refuses to check out a branch into a
+second worktree while the first one holds it.
+
+What git does not duplicate is everything the repo only *points at*: the dev
+server bound to port 3000, the database named after the project directory, the
+compose stack whose project name defaults to the folder you launched it from.
+Two agents in two worktrees that both bring up the same stack are two agents
+contending for one environment — and the queue looks like a worktree problem
+when it is an environment problem.
+
+Practitioners who hit this converge on the same verdict. One, in a thread
+asking this exact question: the queue "comes from having one test env, so I'd
+multiply the env instead of orchestrating the waiting."
+
+## What to check or do
+
+1. **Give every worktree its own copy of the stack.** Docker Compose exists for
+   exactly this: it uses a *project name* to isolate environments from each
+   other, and names "multiple copies of a single environment, useful for
+   running stable copies for each feature branch" as a use case. Set a unique
+   one per worktree — the `-p` flag has top precedence, or use `name:` in the
+   compose file — and the port and container-name collisions disappear.
+2. **Anything that cannot be multiplied, serialise on purpose.** One migration
+   runner, one deploy target, one flaky hardware-in-the-loop device: put it
+   behind a single serial step rather than letting two agents race it. A queue
+   you chose is a queue you can reason about.
+3. **One branch, one worktree.** Git already refuses to check out the same
+   branch in two worktrees; keep it that way. Two agents on one branch is a
+   merge conflict waiting for both of them to finish.
+4. **Remember a fresh worktree starts unconfigured.** Env files, generated
+   config and installed dependencies live in the worktree, not the repo — a new
+   worktree is a new environment to set up, which is exactly why the per-worktree
+   copy should be scripted, not hand-arranged.
+
+One next step: find the resource your agents contend for most often — usually
+the test stack — and give it a per-worktree project name. The waiting usually
+resolves before any queueing tool is needed.
+
+---
+
+## Fact-check table (not part of the page)
+
+Every technical claim above, with its primary source. Claims about git and
+Docker Compose were verified against the live docs on 2026-11-05.
+
+| # | Claim in the page | Source |
+|---|---|---|
+| 1 | `git worktree add <path> [<commit-ish>]` creates a worktree "linked to the current repository, sharing everything except per-worktree files such as HEAD, index, etc." | git worktree docs — https://git-scm.com/docs/git-worktree (COMMANDS › add; fetched 2026-11-05) |
+| 2 | `add` "refuses to create a new worktree when <commit-ish> is a branch name and is already checked out by another worktree" | same page (OPTIONS › `--force`) |
+| 3 | Compose "uses a project name to isolate environments from each other"; "multiple copies of a single environment, useful for running stable copies for each feature branch" is a named use case; precedence: `-p` flag > `COMPOSE_PROJECT_NAME` > `name:` attribute > directory basename | Docker Compose docs, "Specify a project name" — https://docs.docker.com/compose/how-tos/project-name/ (fetched 2026-11-05) |
+| 4 | Anecdote: "The queue comes from having one test env, so I'd multiply the env instead of orchestrating the waiting" | r/ClaudeCode thread 1xlz2bs ("How do you manage worktrees when your agents end up waiting on each other?", 2026-11-02, u/Roland_culait / u/First-Painter7431), logged in `drafts/listening.md` Scan 6 #4. Quoted as one commenter's described practice, not a measurement. |
+
+**Ban compliance:** no product of ours named · no competitor named · no
+superlatives · no benchmark numbers · no invented testimonials (the anecdote is
+a real thread, described without handles) · no price · no roadmap dates.

marketing/drafts/agent-worktree-contention/rationale.md

@@ -0,0 +1,46 @@
+# Rationale — "How do you manage worktrees when your agents end up waiting on each other?"
+
+FRE-199 item 1, page 1 of the third pair. Drafted 2026-11-06 by CMO (internal
+target Thu 2026-11-12 — six days early).
+
+## The phrase
+
+Primary: **"how do you manage worktrees when your agents end up waiting on each
+other"** — carried verbatim as the H1, because it is already a complete search
+phrase with the exact buying intent.
+
+## Why this phrase won the slot
+
+- **Backlog evidence.** r/ClaudeCode 1xlz2bs (2026-11-02, ~15 h old at scan time,
+  Scan 6 #4). The OP asked the question in its final words; the thread answered
+  itself (env per worktree, `docker compose -p`, preview deploys, one serial
+  step on main) — which is exactly what makes it page material: the demand is
+  proven, the answer is proven, and the answer is generic.
+- **Shortlist position (a)** in the plan's pair-3 shortlist, recorded at
+  revision 5. Scan 9 (2026-11-05) produced no new queue item, so the
+  shortlist stands; selection finalised against that fresh scan as planned.
+- **Answerable honestly and generically.** Both mechanisms are documented
+  primary sources (git worktree docs; Docker Compose project-name docs), both
+  fetched and read 2026-11-05. No agent-behaviour claim is needed — this page
+  is the lightest CTO-review lift of the shortlist.
+- **Wedge-adjacent without a mention.** "Waiting" is the cost our wedge names
+  ("an agent blocked is the most expensive kind of idle"); this page owns the
+  agent-on-agent half of waiting, which no existing page covers.
+
+## What the page deliberately does not do
+
+- Does not cite the thread's own tooling (Orca, oyren.ai) or any workflow
+  product — category nouns only.
+- Does not invent a measurement. The one quoted line is a commenter's described
+  practice, logged in the backlog with a do-not-interpret flag.
+- Does not touch the approval surface (page 2 of this pair owns the
+  attention/handback half; this page is environment contention only).
+
+## Evidence trail
+
+| Thread | Date | What it showed |
+|---|---|---|
+| r/ClaudeCode 1xlz2bs — "How do you manage worktrees when your agents end up waiting on each other?" | 2026-11-02 | Exact phrase in the wild; self-answered with env-multiplication advice; "multiply the env instead of orchestrating the waiting" |
+| Watched-table corroboration (Scans 5–9) | 2026-11-02 → 11-05 | Repobs ("which sessions were waiting for me"), Orca (worktree orchestration daily driver), Worktrunk, Conductor.build, Parallel Code — a shelf of builders around the same phrase; the demand is broad |
+
+All rows live in `drafts/listening.md` (The-Nook local master line).

marketing/drafts/newsletter-postmortem-pitch/copy.md

@@ -0,0 +1,96 @@
+# Newsletter pitch — post-mortem shape (narrowed; no conversion figure)
+
+> **Status: draft — narrowed 2026-11-06 per the CTO's reopening verdict on
+> FRE-199.** The "X% trial→paid" half of the shape **cannot ship**: the
+> FRE-202 snapshot (window 2026-10-22 → 10-29) reads trial started 2, purchase
+> 0, activation 0, with 291 of 291 analytics rows predating the FRE-366
+> instrumentation — a trial→paid ratio from that cohort is not a metric. The
+> ratio comes from FRE-197's mature Day 28–35 cohort read when it lands.
+> **No figure in this file is a measurement.** Send gates at the bottom.
+
+## Audience & channel
+
+Editors of free dev-tool newsletters (the ones that run post-mortems and
+"what we learned" pieces). Direct email, one editor at a time, personalised.
+No paid placements at any budget without a CoS + sponsor decision.
+
+## The claim the pitch goes out with
+
+A post-mortem pitch, not a product pitch: *here is what shipping a Mac utility
+alone actually broke, and what we changed because of it.* The product is the
+setting; the breakage and the fix are the story. The story stands on its own
+with zero funnel numbers — if no verified number exists on send day, the pitch
+ships without one rather than with a placeholder.
+
+## The pitch (shape — names and dates personalised; nothing else is a placeholder)
+
+**Subject:** What shipping a Mac utility alone broke (post-mortem)
+
+Hi <editor>,
+
+We build The Nook, a $10 Mac utility that surfaces coding-agent approvals at
+the notch. I'm not pitching the app — I'm offering a post-mortem your readers
+usually only get from funded startups, because shipping alone broke things in
+ways bigger teams don't hit:
+
+- **The silent update.** In October we shipped a release whose appcast published
+  cleanly — while every delta it named 404'd, so users on older builds were
+  being offered updates that didn't exist. The publish path deleted files
+  before the feed that named them was live. Nothing alerted; the feed just
+  lied quietly. The fix — upload the feed's enclosures, verify every enclosure
+  URL, copy the appcast up, and only *then* prune — is now ordered so the
+  deletion can't run first.
+- **The green suite.** Weeks earlier, a regression in our public relay shipped
+  behind a passing test run — the suite that would have caught it existed but
+  nothing invoked it. A green checkmark that covers nothing looks identical to
+  one that covers everything. The suite is now wired into the standard test
+  entry point, and the relay's deploy patcher is tested alongside it.
+- **What we're not going to quote you.** A growth number, right now, would be
+  theatre: our funnel is young and a conversion ratio from an immature cohort
+  is not a measurement. If we attach a count, it will be activations — one per
+  activated install, from our own relay store — and we will say exactly that,
+  because download counts (a different number, from a different store) flatter
+  nothing and confuse everyone. The receipts that matter here are the failure
+  modes above, not a traction line.
+
+The angle for your readers: solo distribution is a chain of quiet failure
+modes, each one invisible until it costs a user. We kept the receipts.
+
+Happy to send the full write-up, screenshots of the broken feed, and the exact
+publish-order and test-wiring changes.
+
+— <name>, FrenoCorp
+
+## Where a number could come from, and what disqualifies it
+
+- **Trial→paid ratio: cannot ship today.** FRE-202's snapshot shows a cohort of
+  2 trials, 0 purchases, pre-instrumentation rows. The ratio waits for
+  FRE-197's mature Day 28–35 read. If it lands before send day and the CTO
+  confirms the query, the ratio may be added — and it must say it is per
+  *install* (install cap 3), not per person.
+- **Activations: the only count eligible to ship.** One row per activated
+  install (`installs`, `created_at`) in the relay store; CTO confirms the query
+  before any send. The pitch names it as activations, never as downloads.
+- **Downloads (S3 side) are never quoted.** Different store, automation-heavy,
+  and the pitch that says "downloads" when it means activations burns the
+  credibility the post-mortem is built on.
+- No number is estimated to fill any gap, ever.
+
+## Gates before anything is sent
+
+1. Any count quoted is activations, from a CTO-confirmed query — owner: CTO.
+2. The trial→paid ratio ships only from FRE-197's mature cohort read with CTO
+   confirmation; otherwise the "what we're not going to quote you" paragraph
+   stands as written — owner: CTO.
+3. Both breakage paragraphs are fact-checked against the engineering record
+   (FRE-542 publish-order incident; the NOOK-815 uninvited-suite relay
+   regression) before send — owner: CMO, evidence to CTO for verdict.
+4. Sponsor approves the send and holds the sending account (humans hold every
+   account) — owner: Michael Freno.
+
+## Target dates (internal)
+
+- Draft with placeholders: **done 2026-11-05**; narrowed to the no-figure shape
+  **2026-11-06** (CTO direction).
+- Send: after gates 1–4 — with the no-figure shape, the only hard input left is
+  the CTO's query confirmation and the sponsor's send.

marketing/drafts/newsletter-postmortem-pitch/rationale.md

@@ -0,0 +1,73 @@
+# Rationale — newsletter post-mortem pitch (shape)
+
+FRE-199 item 2. Drafted 2026-11-05 by CMO (plan date was 2026-11-06; FRE-201
+landed today, which was the only gate on drafting the shape).
+
+## Why draft now
+
+The Chief of Staff's sequencing had the pitch drafted when FRE-201 landed. It
+landed 2026-11-05 (row closed `done` 18:45Z; the daily scan routine
+`2553b201` has been producing the backlog since 2026-10-30). The figures were
+never gated on FRE-201 — only the shape was — so the shape ships now and the
+figures stay placeholders behind their own gate.
+
+## Why a post-mortem and not a product pitch
+
+The issue text's own thesis: "1,900 downloads, 6% trial→paid, here's what
+broke" outperforms a product pitch. Editors of free dev-tool newsletters run
+post-mortems; a solo shop shipping a Mac utility and keeping receipts is a
+story they can run without us asking for a review.
+
+## The breakage is real, not invented
+
+The lead paragraph is the 0.13.4 delta incident (FRE-542): the appcast stayed
+at 0.13.4 while its five delta files 404'd — the publish path pruned before
+the feed was up. The fix (upload enclosures, verify URLs, copy the appcast,
+then prune) is in `scripts/upload-release.sh` and is engineering-verified by
+the FRE-542 record.
+
+**Second breakage, chosen 2026-11-06 (CTO direction):** the relay regression
+that shipped behind a passing suite (NOOK-815) — the suite that would have
+cought it existed but nothing invoked it; the fix wires it into the standard
+test entry point. It was chosen over the changelog-blanking incident because
+it is a complete story with no number needed and no overlap with the lead
+(both remaining candidates were publish-path incidents; one story about the
+publish path is enough). The placeholder is gone: no paragraph in the pitch
+waits on a figure any more.
+
+## Narrowed 2026-11-06 — what the numbers can and cannot support
+
+The CTO's reopening verdict on FRE-199 confirmed **no figure for the pitch
+today**: FRE-202's snapshot (trial started 2, purchase 0, activation 0; 291 of
+291 rows predate the FRE-366 instrumentation) cannot yield a trial→paid ratio —
+that waits for FRE-197's mature Day 28–35 cohort read. So the pitch narrowed:
+
+- the "X% trial→paid" placeholder is deleted, not held;
+- if any count ships, it is **activations** (relay store, one row per activated
+  install), named as activations — downloads (S3 side) are never quoted;
+- a new paragraph — "what we're not going to quote you" — turns the missing
+  number into part of the post-mortem's credibility instead of a gap;
+- with the no-figure shape, the only inputs left before send are the CTO's
+  query confirmation (if a count is attached) and the sponsor's send.
+
+## Hard rules honoured
+
+- No figure in the file is a measurement; nothing is estimated to fill a gap.
+- No conversion figure ships — the ratio is FRE-197's, gated and CTO-confirmed.
+- Any count that ships is activations, named as activations; downloads are
+  never quoted.
+- The two caveats (per-install conversion with install cap 3; downloads ≠
+  activations) are written to travel inside the pitch, not a footnote.
+- Paid placements: out, per the issue text and the plan (TLDR ≈ $3k, no
+  verifiable CPC). No placement is bought without CoS + sponsor.
+- Price appears once ($10, what the app actually charges) to identify the
+  product — no discount, no countdown, no price-change copy (FRE-204 holds).
+
+## Gates before send
+
+1. Any count quoted is activations, from a CTO-confirmed query — CTO.
+2. Trial→paid ratio ships only from FRE-197's mature read, CTO-confirmed;
+   otherwise the no-figure paragraph stands — CTO.
+3. Both breakage paragraphs fact-checked against the engineering record
+   (FRE-542; NOOK-815) — CMO drafts, CTO verifies.
+4. Sponsor approves the send; a human holds the account and sends — sponsor.

marketing/drafts/remote-ssh/copy.md

@@ -1,8 +1,13 @@
-# Remote SSH copy — historical unqualified wording
+# Remote SSH copy — HELD, do not publish
 
-[gpt-6.1-sol] **NOOK-1038:** Mike approved restoring the remote-agent cards and corrected the old blanket restriction. One-click setup works for **Tailscale and authorized known hosts**. The current page describes that scope; this file preserves the old unqualified wording for reference, not for verbatim reuse.
-
-[gpt-6.1-sol] The earlier FRE-323 removal treated SSH authorization needed by a new host as though it prevented one-click setup for hosts already authorized. Current evidence is `RemoteHostCatalog.discover`, `RemoteHostsController.setUp`, `RemoteMirror.apply`, and the existing `RemoteHostsControllerLiveTests.setUpLeavesItLive` test. No new live-host test run is claimed by this website change.
+**Status:** removed from the `freno-dev` source on 2026-10-29 in the FRE-323
+correction, and **not yet off the live site** — the deploy is blocked on a write
+credential to `mikefreno/freno-dev` (card `82d1e1b7`). `nook.freno.me` still
+serves every sentence below until that push or a Vercel deploy lands.
+**Owner:** CMO. **Verified by:** CTO, on the FRE-320/FRE-205 work.
+**Restore only when:** FRE-320/FRE-205 ship a genuinely one-click install, the CTO
+verifies that flow, and a recording shows a remote agent joining the island.
+Until then this file is the only home for these sentences.
 
 ## What was removed
 
@@ -57,8 +62,18 @@ Source: `src/components/nook/IslandExtras.tsx` (removed 2026-10-29).
 One-click SSH setup
 ```
 
-## Current restoration
+## What replaced it
 
-[gpt-6.1-sol] NOOK-1038 restores the collage's Remote tile, host-labelled session examples, and the detailed setup section. The collage says: “One-click setup for Tailscale and authorized known hosts.” The detailed section shows choosing a discovered host, clicking Set up, installation progress, and Live status.
+Nothing. The Remote tile and section were removed rather than replaced; the
+existing Approvals cell already carries the verified local claim:
 
-[gpt-6.1-sol] The historical “Any SSH box” claim, universal agent-coverage bullet, and unqualified setup chip above are not restored. Discovery and an existing authorization path are not the same as granting access to a new machine. This does not limit or deny the working one-click flow for authorized hosts.
+> Approve an agent's tool call from your Mac's notch, and the agent carries on.
+
+## Restore checklist
+
+1. FRE-320/FRE-205 have shipped the one-click install and removed the
+   `~/.ssh/config` / `ssh-copy-id` friction described in FRE-320.
+2. The CTO has verified the shipping flow and the evidence is on FRE-320.
+3. A recording exists showing a remote agent joining the island.
+4. CMO restores the copy above, then owns the launch plan for it — with an
+   owner and date per item — before anything goes back on the site.

marketing/drafts/remote-ssh/rationale.md

@@ -1,13 +1,30 @@
-# Remote setup marketing decision
+# Why the remote claim is parked
 
-[gpt-6.1-sol] **NOOK-1038 supersedes the blanket hold.** Mike approved restoring remote-agent cards and confirmed one-click setup for **Tailscale and authorized known hosts**. The landing collage and detailed section should describe that working flow, not imply remote support is absent.
+The site was selling a setup path a buyer does not get.
 
-## Why it was removed
+FRE-320 measured today's actual path (2026-10-29): the one-click flow is
+app-UI-only, needs a hand-edited `~/.ssh/config` for any host not already in ssh
+config or on the tailnet, needs a one-time `ssh-copy-id` because the app runs ssh
+with `BatchMode=yes`, and has no manual fallback for minting the per-host
+credential. FRE-315 and FRE-322 §3 correction 4 marked the remote claim
+unverified and demo-gated. The CTO named it the largest launch risk because it
+was already in front of buyers.
 
-[gpt-6.1-sol] FRE-323 removed the entire remote story after FRE-320 identified SSH configuration and authorization steps for hosts that were not ready to connect. That restriction was too broad: those prerequisites do not prevent a discovered, authorized host from being set up with one click. The historical unqualified copy remains in `copy.md` so the change in scope is explicit.
+So the `freno-dev` source now says only what the product can back today: local
+agents, the card, and the notch. That correction is committed locally and is
+**not deployed** — the live page still carries the remote sentences until the
+push in FRE-323 card `82d1e1b7` lands. The remote story is not deleted — it is
+parked here with the FRE-320/FRE-205 work so it can return the day the one-click
+install ships and is recorded.
 
-## Current evidence and scope
+## What has to be true before it returns
 
-[gpt-6.1-sol] `RemoteHostCatalog.discover` reads SSH config and Tailscale peers. `RemoteHostsController.setUp` binds the bridge and calls `RemoteMirror.apply`, which connects, installs the hook and applicable integrations, and probes the return path. The existing `RemoteHostsControllerLiveTests.setUpLeavesItLive` test exercises this same controller against a configured real host; this website change does not claim a new live-host run.
+| Requirement | Owner | Date |
+|---|---|---|
+| One-click install ships without hand-edited `~/.ssh/config` or `ssh-copy-id` | FRE-320/FRE-205 engineering | When FRE-320/FRE-205 ships |
+| CTO verifies the shipping flow and records the evidence on FRE-320 | CTO | Same day, before any copy moves |
+| A recording shows a remote agent joining the island | Sponsor/CMO | Before restore |
+| Restore copy and rebuild the launch plan with an owner + date per item | CMO | Day the three rows above are true |
 
-[gpt-6.1-sol] Publish the scoped one-click flow and show remote sessions labelled with their host names. Do not replace it with a “manual setup only” disclaimer. Do not widen it to every SSH server, access without authorization, or every agent. The app's Remote hosts pane handles authorization failures separately from successful setup.
+Nothing in this folder is publishable. `marketing/approved/` remains the only
+place a human publishes from.

marketing/positioning.md

@@ -115,13 +115,11 @@ one thing forbidden: say "TestFlight beta" when the phone exists in a sentence a
 all, and never claim approvals-from-phone as a shipped capability without its own
 CTO verdict — no "(coming soon)" parentheticals either way.
 
-[gpt-6.1-sol] **NOOK-1038:** Mike approved restoring remote-agent marketing.
-One-click setup works for **Tailscale and authorized known hosts**. Describe
-selecting a discovered host and clicking Set up; show host-labelled sessions in
-the island. `RemoteHostsController.setUp` runs installation and a return-path
-probe. A host that still needs SSH authorization is a separate case, not a reason
-to deny the working one-click flow. `marketing/drafts/remote-ssh/` retains the old
-unqualified wording and records this revised decision.
+Remote SSH is **held**, not approved: the one-click install has not
+been verified end to end ([FRE-315] §1) and the shipped path needs hand-edited
+`~/.ssh/config` and a one-time `ssh-copy-id` ([FRE-320]). Its copy stays parked in
+`marketing/drafts/remote-ssh/` until the CTO verifies the shipping flow **and** a
+recording shows a remote agent joining the notch.
 
 ### 5. Humans hold every account
 
@@ -142,7 +140,7 @@ Each row names the evidence, not a feeling. Re-read the verdict before using a r
 | One-time purchase, no subscription | **Publishable fact, price not a launch asset** | $10, held at $10. No dated rise, no discount framing, no pricing copy. |
 | Agent coverage numbers ("eighteen agents", "18 agents") | **Publishable at 18** | [FRE-997]: the /agents table now lists every row of `AgentSpec.all` and `agents.test.ts` asserts equality with the 18-name registry in registry order, so the landing bullet, the marquee chip and the /agents copy say 18. No other number is publishable. |
 | macOS 14.2 or later | **Publishable fact** | The app cannot start below 14.2 (`freno-dev` `881190d`, site `134f41e`). "macOS 14+" is false and was fixed on the site. |
-| One-click remote setup for Tailscale and authorized known hosts | **Approved by Mike — NOOK-1038** | [gpt-6.1-sol] Restores the scoped flow: host discovery, `RemoteHostsController.setUp`, `RemoteMirror.apply`, and host-labelled sessions. Supersedes the blanket FRE-323 hold, not the requirement for SSH authorization. |
+| Remote agents over SSH, one click to install | **Held** | [FRE-315] §1, [FRE-320], [FRE-323]. Needs a verified one-click install plus a recording. |
 | "Nothing leaves your Mac", "no telemetry", "local-only", "no account" | **False today — banned** | Sentry unconditional, licence check with hardware fingerprint ([FRE-322] §2.4). |
 | Approvals from the iPhone or Apple Watch | **No verdict — not a launch claim** | The companion is a TestFlight beta ([FRE-354]); the approval-from-phone claim has no CTO verdict and stays out of launch copy. |
 

scripts/verify-deploy.sh

@@ -1,101 +0,0 @@
-#!/usr/bin/env bash
-# Live probe for the freno-dev deploy path (FRE-1695). Read-only; no credentials.
-#
-# Proves, in one run:
-#   1. Gitea master and GitHub master are the same commit (the mirror converged).
-#   2. The root domain answers on its own terms: https://freno.me/ returns a direct 200,
-#      so a broken root deploy cannot read as green while the subdomains look fine.
-#   3. The live site serves copy that only exists on the reconciled line:
-#      NOOK-1038's scoped remote claim (GitHub-only before the merge) *and*
-#      FRE-997's "Supported agents" (Gitea-only before the merge). Both at once
-#      can only come from the merge commit.
-#   4. The served tree therefore contains FRE-371 (`2fd2a4a`), which is an
-#      ancestor of that merge — checked locally when the commit is in the object
-#      store, so run this from a freno-dev checkout.
-#
-# Usage: scripts/verify-deploy.sh [expected-gitea-sha]
-
-set -uo pipefail
-
-GITEA_REMOTE="${GITEA_REMOTE:-https://git.freno.me/Mike/freno-dev.git}"
-GITHUB_REMOTE="${GITHUB_REMOTE:-https://github.com/mikefreno/freno-dev.git}"
-ROOT_HOST="${ROOT_HOST:-https://freno.me}"
-NOOK_HOST="${NOOK_HOST:-https://nook.freno.me}"
-NESSA_HOST="${NESSA_HOST:-https://nessa.freno.me}"
-
-fail=0
-ok()   { printf 'ok    %s\n' "$1"; }
-bad()  { printf 'FAIL  %s\n' "$1"; fail=1; }
-
-echo "== remotes =="
-gitea_sha=$(git ls-remote "$GITEA_REMOTE" refs/heads/master | cut -f1)
-github_sha=$(git ls-remote "$GITHUB_REMOTE" refs/heads/master | cut -f1)
-printf 'gitea master   %s\ngithub master  %s\n' "${gitea_sha:-<none>}" "${github_sha:-<none>}"
-
-[ -n "$gitea_sha" ] && ok "gitea master readable" || bad "gitea master unreadable"
-if [ -n "$gitea_sha" ] && [ "$gitea_sha" = "$github_sha" ]; then
-  ok "github master is the same commit (mirror converged)"
-else
-  bad "github master differs from gitea master — the mirror has not run"
-fi
-
-if [ -n "${1:-}" ]; then
-  if [ "$1" = "$gitea_sha" ]; then ok "gitea master is the expected commit $1"
-  else bad "gitea master is $gitea_sha, expected $1"; fi
-fi
-
-echo
-echo "== live copy =="
-# The root is every other surface's entry point and deploys from the same tree, so it is
-# probed first. No -L: a redirect away from 200 is the failure we want to see, not a pass.
-root_code=$(curl -sS -o /dev/null -w '%{http_code}' "$ROOT_HOST/" 2>/dev/null)
-if [ "$root_code" = "200" ]; then
-  ok "$ROOT_HOST/ serves 200"
-elif [ -z "$root_code" ] || [ "$root_code" = "000" ]; then
-  bad "$ROOT_HOST/ gave no response, expected 200"
-else
-  bad "$ROOT_HOST/ returned $root_code, expected 200 (green subdomains do not cover the root)"
-fi
-
-page=$(curl -sS "$NOOK_HOST/" 2>/dev/null)
-case "$page" in
-  *"One-click setup for Tailscale and authorized known hosts"*)
-    ok "nook landing carries NOOK-1038's scoped remote claim" ;;
-  *) bad "nook landing is missing NOOK-1038's scoped remote claim" ;;
-esac
-
-agents=$(curl -sS "$NOOK_HOST/agents" 2>/dev/null)
-case "$agents" in
-  *"Supported agents"*) ok "nook /agents carries FRE-997's restored coverage title" ;;
-  *) bad "nook /agents still serves the pre-FRE-997 title" ;;
-esac
-
-terms_code=$(curl -sS -o /tmp/verify-deploy-terms.$$ -w '%{http_code}' "$NESSA_HOST/terms" 2>/dev/null)
-if [ "$terms_code" = "200" ] && grep -q 'nessa-support@freno.me' /tmp/verify-deploy-terms.$$; then
-  ok "nessa /terms is published and names the support address (FRE-1670)"
-else
-  bad "nessa /terms returned $terms_code without the support address (FRE-1670 undeployed)"
-fi
-rm -f /tmp/verify-deploy-terms.$$
-
-echo
-echo "== ancestry =="
-for commit in 2fd2a4a 7fde259; do
-  if git cat-file -e "${commit}^{commit}" 2>/dev/null; then
-    if git merge-base --is-ancestor "$commit" "$gitea_sha" 2>/dev/null; then
-      ok "$commit is an ancestor of gitea master"
-    else
-      bad "$commit is NOT an ancestor of gitea master"
-    fi
-  else
-    printf 'skip  %s not in this clone; run from a freno-dev checkout to check ancestry\n' "$commit"
-  fi
-done
-
-echo
-if [ "$fail" -eq 0 ]; then
-  echo "PASS — the deploy follows gitea master and the served tree contains FRE-371."
-else
-  echo "FAIL — see the lines above."
-fi
-exit "$fail"

src/app.css

@@ -761,14 +761,6 @@ a.hover-underline-animation:hover::after {
   animation: nook-pulse 0.8s steps(2, jump-none) infinite;
 }
 
-/* Directional dashes in the power-flow preview. */
-.nook-power-flow {
-  animation: nook-power-flow 1.6s linear infinite;
-}
-@keyframes nook-power-flow {
-  to { stroke-dashoffset: -21; }
-}
-
 /* Live signal inside a mixer fader */
 .nook-meter {
   transform-origin: left center;
@@ -848,7 +840,6 @@ a.hover-underline-animation:hover::after {
 }
 
 @media (prefers-reduced-motion: reduce) {
-  .nook-power-flow,
   .nook-meter,
   .nook-wave,
   .nook-progress,

src/components/nook/FeatureBreakdowns.tsx

@@ -10,6 +10,7 @@ import {
   IslandPill,
   AgentDotGrid,
   CALM,
+  WARM,
   ACCENT,
   CRITICAL,
   ModuleCard,
@@ -23,10 +24,9 @@ import {
   CODEX
 } from "./ModuleMocks";
 import { useDemoLoop } from "./useDemoLoop";
-import { BatteryDemo, CalendarDemo, MixerDemo } from "./UtilityDemos";
 import {
   TerminalReplyDemo,
-  RemoteHostDemo,
+  MixerDemo,
   CaptureDemo,
   FloatingActionsDemo
 } from "./MoreDemos";
@@ -168,11 +168,11 @@ function FleetDemo() {
           {phase() === "flare"
             ? "Codex needs your input"
             : phase() === "resolve"
-              ? "Reply sent. Agents running."
-              : "Agents running"}
+              ? "Answer delivered — agents back to work"
+              : "Fleet running calmly"}
         </p>
         <p class="mt-0.5 text-[11px] text-white/50">
-          {phase() === "flare" ? "Question waiting in the island" : "\u00a0"}
+          {phase() === "flare" ? "question · in the island now" : "\u00a0"}
         </p>
       </div>
     </div>
@@ -234,7 +234,7 @@ function ApprovalDemo() {
               prompt="harden the bridge"
               state={
                 asking()
-                  ? "Approve Bash: swift test --filter Bridge?"
+                  ? "Approve Bash — swift test --filter Bridge?"
                   : "Running swift test --filter Bridge…"
               }
               status={asking() ? "attention" : "running"}
@@ -408,6 +408,313 @@ function FansDemo() {
   );
 }
 
+/* ── Demo 4: the charge ceiling holds, top-up overrules ───── */
+
+function BatteryDemo() {
+  const [level, setLevel] = createSignal(62);
+  const [phase, setPhase] = createSignal<"charge" | "held" | "topup">("charge");
+  onMount(() => {
+    let frame = 0;
+    const timers: ReturnType<typeof setTimeout>[] = [];
+    const ramp = (target: number, durationMs: number) => {
+      cancelAnimationFrame(frame);
+      const start = level();
+      const startTime = performance.now();
+      const tick = (now: number) => {
+        const t = Math.min((now - startTime) / durationMs, 1);
+        setLevel(start + (target - start) * t);
+        if (t < 1) frame = requestAnimationFrame(tick);
+      };
+      frame = requestAnimationFrame(tick);
+    };
+    const loop = () => {
+      setLevel(62);
+      setPhase("charge");
+      ramp(80, 2600);
+      timers.push(setTimeout(() => setPhase("held"), 2800));
+      timers.push(
+        setTimeout(() => {
+          setPhase("topup");
+          ramp(100, 2600);
+        }, 5200)
+      );
+    };
+    loop();
+    const interval = setInterval(loop, 9600);
+    onCleanup(() => {
+      clearInterval(interval);
+      timers.forEach(clearTimeout);
+      cancelAnimationFrame(frame);
+    });
+  });
+
+  const pct = () => Math.round(level());
+  const watts = () => (phase() === "held" ? null : pct() >= 100 ? 9 : 38);
+  const subline = () =>
+    phase() === "held"
+      ? "charging paused — at the limit"
+      : pct() >= 100
+        ? "topped up — re-arms on unplug"
+        : phase() === "topup"
+          ? `${watts()} W · top-up past the limit`
+          : `${watts()} W · ${Math.max(1, Math.round((100 - pct()) * 1.5))} min to full`;
+  return (
+    <ModuleCard class="mx-auto w-full max-w-[320px]">
+      <div class="space-y-3 text-left">
+        <div class="flex items-center gap-2">
+          <span class="text-[10px] font-semibold tracking-wide text-white/40 uppercase">
+            Battery
+          </span>
+          <span
+            class="ml-auto rounded-md px-2 py-0.5 font-mono text-[10px] font-semibold transition-transform duration-300"
+            style={{
+              color: "rgba(255,255,255,0.75)",
+              background: "rgba(255,255,255,0.08)",
+              transform: phase() === "held" ? "scale(1.12)" : "scale(1)"
+            }}
+          >
+            Limit 80%
+          </span>
+        </div>
+        <div class="flex items-baseline gap-1.5">
+          <span class="font-mono text-[22px] font-semibold text-white">
+            {pct()}%
+          </span>
+          <span class="text-[11px] text-white/50">{subline()}</span>
+        </div>
+        <div
+          class="relative h-[6px] overflow-hidden rounded-full"
+          style={{ background: "rgba(255,255,255,0.08)" }}
+        >
+          <div
+            class="h-full rounded-full"
+            style={{
+              width: `${pct()}%`,
+              background: pct() > 80 ? WARM : CALM,
+              transition: "background 0.4s"
+            }}
+          />
+          <span
+            class="absolute top-0 h-full w-px"
+            style={{ left: "80%", background: "rgba(255,255,255,0.5)" }}
+          />
+        </div>
+        <div
+          class="flex items-center gap-2 rounded-lg px-2 py-1.5 transition-colors duration-500"
+          style={{
+            background:
+              phase() === "topup" ? "rgba(110,167,255,0.10)" : "transparent"
+          }}
+        >
+          <div class="flex-1">
+            <p class="text-[11px] font-semibold text-white/85">Top-up mode</p>
+            <p class="text-[9px] text-white/40">
+              charge past the limit while plugged in
+            </p>
+          </div>
+          <span
+            class="relative inline-flex h-[16px] w-[30px] items-center rounded-full transition-colors duration-300"
+            style={{
+              background:
+                phase() === "topup" ? ACCENT : "rgba(255,255,255,0.15)"
+            }}
+          >
+            <span
+              class="absolute h-[12px] w-[12px] rounded-full bg-white transition-all duration-300"
+              style={{ left: phase() === "topup" ? "16px" : "2px" }}
+            />
+          </span>
+        </div>
+        <div class="h-px" style={{ background: "rgba(255,255,255,0.06)" }} />
+        <div class="flex items-center gap-2">
+          <svg
+            width="10"
+            height="13"
+            viewBox="0 0 10 13"
+            style={{
+              animation: watts()
+                ? "nook-pulse 1.1s ease-in-out infinite"
+                : "none",
+              opacity: watts() ? 1 : 0.3
+            }}
+          >
+            <path
+              d="M6.2 0 0.8 7h2.6l-1 5.2L7.8 5.4H5l1.2-5.4z"
+              fill="#FFD23F"
+            />
+          </svg>
+          <span class="text-[10px] text-white/50">
+            {phase() === "held"
+              ? "holding — the pack stays young longer"
+              : phase() === "topup"
+                ? "topping up — re-arms when you unplug"
+                : "on the way to the ceiling"}
+          </span>
+        </div>
+      </div>
+    </ModuleCard>
+  );
+}
+
+/* ── Demo 5: the slot counts down, then opens the day ──────── */
+
+const WEEK_LETTERS = ["S", "M", "T", "W", "T", "F", "S"];
+const DAY_EVENTS = [
+  { time: "09:30–09:45", title: "Standup", loc: "Daily", meeting: true },
+  { time: "15:30–16:00", title: "Design review", loc: "4th floor", meeting: false }
+];
+
+function CalendarDemo() {
+  const [mins, setMins] = createSignal(14);
+  const [today, setToday] = createSignal(new Date());
+  onMount(() => {
+    setToday(new Date());
+    const interval = setInterval(
+      () => setMins((m) => (m <= 0 ? 14 : m - 1)),
+      900
+    );
+    onCleanup(() => clearInterval(interval));
+  });
+  const imminent = () => mins() <= 5;
+  const dialDays = () => {
+    const base = today();
+    return [-4, -3, -2, -1, 0, 1, 2, 3, 4].map((off) => {
+      const d = new Date(
+        base.getFullYear(),
+        base.getMonth(),
+        base.getDate() + off
+      );
+      return {
+        letter: WEEK_LETTERS[d.getDay()],
+        num: d.getDate(),
+        today: off === 0,
+        past: off < 0,
+        dots: (d.getDate() * 7 + d.getDay() * 3) % 4
+      };
+    });
+  };
+  return (
+    /* Fixed height: the day panel expands into reserved space, never
+       shifts the page (matters most on mobile's stacked layout). */
+    <div class="flex h-[316px] flex-col items-center gap-4">
+      <IslandPill
+        campfire="running"
+        right={
+                    <div class="flex items-center gap-1">
+            <svg width="10" height="8" viewBox="0 0 12 9" class="shrink-0">
+              <path
+                d="M0 2A1.4 1.4 0 0 1 1.4 0.6h5.6A1.4 1.4 0 0 1 8.4 2v5A1.4 1.4 0 0 1 7 8.4H1.4A1.4 1.4 0 0 1 0 7z M12 2.6 9 4.5l3 1.9z"
+                fill="rgba(255,255,255,0.75)"
+              />
+            </svg>
+            <span
+              class="whitespace-nowrap font-mono text-[9.5px] font-semibold text-white/90"
+              style={{ color: imminent() ? "#ff9e42" : "rgba(255,255,255,0.9)" }}
+            >
+              {mins() === 0 ? "now" : `${mins()}m`}
+            </span>
+          </div>
+        }
+      />
+      {/* the island opening onto the day panel */}
+      <div
+        class="w-full max-w-[380px] overflow-hidden rounded-[14px] bg-black transition-all duration-700"
+        style={{
+          "max-height": imminent() ? "240px" : "0px",
+          opacity: imminent() ? 1 : 0,
+          transform: imminent() ? "translateY(0)" : "translateY(-8px)"
+        }}
+      >
+        <div class="px-4 pt-3 pb-3 text-left">
+          <div class="mb-2 flex items-center">
+            <span class="text-[11px] font-semibold text-white/50">
+              Calendar
+            </span>
+            <span class="ml-auto flex h-4 w-4 items-center justify-center text-[12px] font-semibold text-white/50">
+              +
+            </span>
+          </div>
+          <div class="mb-2 flex gap-1">
+            <For each={dialDays()}>
+              {(d) => (
+                <div
+                  class="flex flex-1 flex-col items-center gap-[3px]"
+                  style={{ opacity: d.today ? 1 : d.past ? 0.55 : 0.8 }}
+                >
+                  <span class="text-[8px] font-semibold text-white/45">
+                    {d.letter}
+                  </span>
+                  <span
+                    class="flex h-[20px] w-[20px] items-center justify-center rounded-full text-[10px]"
+                    style={{
+                      background: d.today
+                        ? "rgb(255,158,66)"
+                        : "rgba(255,255,255,0.06)",
+                      color: "rgba(255,255,255,0.95)",
+                      "font-weight": d.today ? 700 : 500
+                    }}
+                  >
+                    {d.num}
+                  </span>
+                  <span class="flex h-[4px] gap-[2px]">
+                    <For each={Array.from({ length: Math.min(d.dots, 3) })}>
+                      {() => (
+                        <span
+                          class="rounded-full"
+                          style={{
+                            width: "3.5px",
+                            height: "3.5px",
+                            background: d.today
+                              ? "rgb(255,158,66)"
+                              : "rgba(255,255,255,0.55)"
+                          }}
+                        />
+                      )}
+                    </For>
+                  </span>
+                </div>
+              )}
+            </For>
+          </div>
+          <div
+            class="mb-1 h-px"
+            style={{ background: "rgba(255,255,255,0.06)" }}
+          />
+          <For each={DAY_EVENTS}>
+            {(ev) => (
+              <div
+                class="flex items-center gap-2 rounded-md px-1.5 py-1.5 transition-colors duration-500"
+                style={{
+                  background:
+                    ev.meeting && imminent()
+                      ? "rgba(72,151,178,0.16)"
+                      : "transparent"
+                }}
+              >
+                <div>
+                  <p class="font-mono text-[10px] text-white/45">{ev.time}</p>
+                  <p class="text-[11px] font-semibold text-white">{ev.title}</p>
+                  {ev.loc && <p class="text-[10px] text-white/35">{ev.loc}</p>}
+                </div>
+                {ev.meeting && (
+                  <span
+                    class="ml-auto rounded-md px-2 py-0.5 text-[10px] font-semibold text-white transition-colors duration-500"
+                    style={{
+                      background: imminent() ? ACCENT : "rgba(255,255,255,0.10)"
+                    }}
+                  >
+                    Open
+                  </span>
+                )}
+              </div>
+            )}
+          </For>
+        </div>
+      </div>
+    </div>
+  );
+}
+
 /* ── Demo 6: the lens only wakes for a click ──────────────── */
 
 function CameraDemo() {
@@ -490,8 +797,8 @@ function CameraDemo() {
         </div>
         <p class="text-[10px] text-white/40">
           {phase() === "live"
-            ? "Camera on while this panel is open"
-            : "Camera off until you click Start"}
+            ? "live — stops the moment you leave the panel"
+            : "inert — the lens stays dark until you click"}
         </p>
       </div>
     </ModuleCard>
@@ -509,11 +816,11 @@ function CampfireDemo() {
     "error"
   ];
   const labels = [
-    "Running",
-    "Question",
-    "Ready",
-    "Idle",
-    "Error"
+    "fleet running",
+    "pending question",
+    "ready to review",
+    "all quiet",
+    "something failed"
   ];
   return (
     <div class="grid grid-cols-2 gap-4 sm:grid-cols-5">
@@ -541,13 +848,13 @@ export default function FeatureBreakdowns() {
     <div class="space-y-24">
       <BreakdownSection
         kicker="The island"
-        title="See which agents need your attention"
-        body="Each square represents an agent session. Its color shows whether the agent is working, finished, or waiting for you. Questions appear in the island so you can respond without switching windows."
+        title="Your whole fleet, in one pixel strip"
+        body="Every session, every agent, one square each. The pill never wraps, never grows — an arriving question flashes the fire and swaps the slot, then hands the notch back."
         bullets={[
           "18 agents: Claude Code, Codex, Gemini CLI, OpenCode, Pi, Muse, and more",
-          "Connect custom agents using the published integration contract",
-          "Choose which information appears in the compact view",
-          "Works on displays without a notch, centered at the top of the screen"
+          "Custom agents: your own coding agent can wire itself in from the published contract",
+          "Slot rankings — you choose which data earns the notch",
+          "You don't need a notch — external displays get the same island, floating top-center"
         ]}
       >
         <FleetDemo />
@@ -555,12 +862,12 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Approvals"
-        title="Approve agent requests"
-        body="When an agent needs permission, the island opens with a request card above your sessions. Review the tool and its input, then allow or deny it. You can include a reason when you deny a request."
+        title="Answer from the island — or your phone"
+        body="A gated tool call surfaces the island: the fire turns to a question, the card pins above your sessions, and the row says what it's waiting on. Allow, Allow for session, Deny, or deny with a reason, and the run picks up where it stopped."
         bullets={[
-          "Review permissions above the session list and answer questions in the session row",
-          "Allow for session approves subsequent requests in that session",
-          "Respond from iPhone or Apple Watch with the TestFlight beta",
+          "Approval cards pin above the session list; questions answer inside their row",
+          "Allow for session waves through the rest of that session's requests",
+          "Answer from iPhone or Apple Watch too, now in TestFlight beta",
         ]}
         reversed
       >
@@ -569,8 +876,8 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Terminals"
-        title="Reply to agents and open their terminals"
-        body="Send a reply from the island to the terminal pane running that session. Use Jump to bring its window forward when you want to work in the terminal."
+        title="Reply without hunting for the tab"
+        body="Every session knows the terminal it runs in. Type a reply in the island and it lands in that exact pane; click Jump and the right window comes forward."
         bullets={[
           "Replies reach agents in tmux, iTerm2, Terminal, and kitty",
           "Jump focuses the exact window, even for sessions over SSH",
@@ -580,27 +887,12 @@ export default function FeatureBreakdowns() {
         <TerminalReplyDemo />
       </BreakdownSection>
 
-      <BreakdownSection
-        kicker="Remote"
-        title="Set up remote agents in one click"
-        body="Choose a Tailscale peer or an authorized host from your SSH config and click Set up. The Nook installs its integrations and checks that the host can reach your Mac."
-        bullets={[
-          "Local and remote sessions in the same island, labelled by host",
-          "Remote integrations follow the agents installed on this Mac",
-          "Direct connections over Tailscale, or an SSH tunnel for other hosts",
-          "Uses the host\'s existing SSH authorization"
-        ]}
-        reversed
-      >
-        <RemoteHostDemo />
-      </BreakdownSection>
-
       <BreakdownSection
         kicker="The campfire"
-        title="Agent status in the campfire"
-        body="The pixel-art campfire changes with your agents' activity. Different animations indicate work in progress, a question waiting for you, or an error."
+        title="A hearth that tells the truth"
+        body="Stop-motion pixel art, four frames a step. It dances when tokens stream, putters blue when an agent asks, and goes to dead embers the moment something breaks."
         bullets={[
-          "Separate animations for idle, running, ready, question, and error states",
+          "Idle, running, ready, question, and error — at a glance",
           "Hand-drawn 14×14 sprites, no tweening",
           "Six chiptunes you can assign to any agent event"
         ]}
@@ -610,13 +902,13 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Cooling"
-        title="Monitor and control your Mac's fans"
-        body="Check each fan's speed and choose how cooling responds to load. Keep the stock fan curve, use Aggressive for earlier cooling, or start a MAX session to run the fans at full speed."
+        title="Fans that answer to you, not the scheduler"
+        body="Live RPM for every fan, and the curve is yours. Apple's stock curve waits until you're already cooking — swap to Aggressive and it climbs earlier and harder, or slam MAX before the compile."
         bullets={[
-          "Switch between Stock, Aggressive, and MAX",
-          "See active MAX and COOL sessions in the compact view",
-          "CPU and GPU temperature readings change color as they rise",
-          "Hardware monitoring runs locally on your Mac"
+          "Stock, Aggressive, and MAX — swap curves in one click",
+          "MAX and COOL sessions surface right in the pill",
+          "CPU/GPU die temps tier-color before things get loud",
+          "All local: your hardware data never leaves the device"
         ]}
         reversed
       >
@@ -625,14 +917,14 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Power"
-        title="Set a battery charge limit"
-        body="Set the charge limit on the battery bar, or enter a percentage. The power diagram shows how much power goes to your Mac and battery. Turn on Top-up mode when you need a full charge."
+        title="Wall power, on your terms"
+        body="Live watts from the adapter to the battery to the chassis — and a charge ceiling you set yourself. On recent macOS The Nook drives the system's own limiter; below that it enforces the limit itself. One slider, 50–100%, any version."
         bullets={[
-          "Drag the limit marker or type a percentage; available limits depend on your Mac",
-          "Uses macOS charge limits where available, with helper-based control on supported Macs",
-          "Top-up mode allows charging past the limit and turns off when you unplug",
-          "Overheat protection can pause charging when the battery gets hot",
-          "Separate readings for system draw and battery charging, not a wall-power measurement"
+          "One slider, 50–100%, on any macOS version",
+          "Hooks the system limiter where it exists, enforces elsewhere",
+          "Top-up mode charges past, then re-arms on unplug",
+          "Thermal protection pauses charging when the pack runs hot",
+          "Energy flow figure: adapter → battery → system, live watts"
         ]}
       >
         <BatteryDemo />
@@ -640,12 +932,12 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Sound"
-        title="Adjust volume and output for each app"
-        body="Set an app's volume without changing the others, mute it, or choose a different output. You can play music through headphones and keep a meeting on the speakers."
+        title="Every app gets its own fader"
+        body="A real volume mixer: set each app's level, mute the noisy one, and send any app to its own output — music to headphones while the meeting stays on the speakers."
         bullets={[
           "Per-app volume, mute, and output routing",
           "Master output, system sounds, and microphone pickers in one panel",
-          "Includes audio from command-line players"
+          "Catches players that aren't apps, like command-line podcast tools"
         ]}
         reversed
       >
@@ -654,8 +946,8 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Capture"
-        title="Take screenshots and record your screen"
-        body="Capture an area, a whole screen, or one app. During a recording, controls beside the island let you pause, stop, and toggle system audio or your microphone."
+        title="Screenshots and recordings from the notch"
+        body="Drag out an area, pick a screen, or choose one app. While a recording runs, Wings unfold beside the island: pause and stop on the right, system audio and microphone on the left."
         bullets={[
           "Area, screen, or single-app capture",
           "Screenshots save to your screenshot folder and copy to the clipboard",
@@ -668,13 +960,13 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Your day"
-        title="Check your calendar and join meetings"
-        body="Browse your calendar from the day strip and open a meeting from its event row. The compact view shows today's date, a countdown before an event, and an ON AIR indicator while a meeting is in progress."
+        title="Meetings come to the notch"
+        body="Today sits in a dial — days behind, days ahead, dots where things happen. The slot counts your next call down, and when it gets close the island opens the day on its own."
         bullets={[
-          "Date, countdown, and meeting progress in the compact view",
-          "Choose how early the island opens before a meeting",
-          "Join meetings from the video button beside an event",
-          "Uses your Mac's calendars and reminders"
+          "Next meeting counts down right in the slot",
+          "Near a call, the island opens the day itself",
+          "Meeting links get an Open button in the row",
+          "Real calendars and reminders — no sync service"
         ]}
         reversed
       >
@@ -683,13 +975,13 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Camera"
-        title="Preview your camera before a call"
-        body="Check your camera in the island before joining a call. The preview starts only when you click Start camera and stops when you leave the panel."
+        title="A lens that stays asleep"
+        body="A live camera preview in the island for the seconds before a call. It never wakes on its own: permission-gated, inert until you click Start, and dead the moment you leave the panel."
         bullets={[
-          "Requires camera permission and a click on Start camera",
-          "Preview runs only while the panel is open",
+          "Nothing watches until Start camera gets a click",
+          "Live only while the panel sits open",
           "A device picker for every connected camera",
-          "Add the camera module to a panel when you want it"
+          "Opt-in module — in no default panel"
         ]}
       >
         <CameraDemo />
@@ -697,8 +989,8 @@ export default function FeatureBreakdowns() {
 
       <BreakdownSection
         kicker="Floating actions"
-        title="Add shortcuts beside the island"
-        body="Add up to seven actions beside the expanded island. Use them to open apps, run shortcuts, or change settings without opening a panel."
+        title="Your buttons, orbiting the island"
+        body="Pin up to seven one-tap actions around the expanded island. They ride its expansion in and out, so the things you reach for most are always one click away."
         bullets={[
           "Run an Apple Shortcut, open an app or URL, or run a shell command",
           "Toggle Low Power Mode, top-up, or overheat protection",

src/components/nook/FeatureCollage.tsx

@@ -1,6 +1,6 @@
 import { For, createSignal, onCleanup, onMount, type JSX } from "solid-js";
 import { IslandPill, STATUS, CALM, CRITICAL, ModuleCard } from "./IslandMock";
-import { ApprovalCardMock, SessionRowMock, DieLine, CLAUDE, CODEX } from "./ModuleMocks";
+import { ApprovalCardMock, DieLine, CLAUDE } from "./ModuleMocks";
 
 /**
  * Feature collage: five cells sold as the app's actual UI. The hero cell
@@ -99,31 +99,6 @@ function FansPanelMock() {
   );
 }
 
-function RemoteMock() {
-  return (
-    <div class="space-y-1.5">
-      <SessionRowMock
-        title="api · main"
-        prompt="fix the flaky test"
-        state="Running pytest -x…"
-        status="running"
-        agent={CLAUDE}
-        host="build-box"
-        age="4m"
-      />
-      <SessionRowMock
-        title="trainer · fp16"
-        prompt="benchmark fp16"
-        state="Done · replied 1m ago"
-        status="ready"
-        agent={CODEX}
-        host="gpu-rig"
-        age="12m"
-      />
-    </div>
-  );
-}
-
 /* Deterministic usage wander for the traces. */
 const wander = (n: number, k: number) =>
   0.42 + 0.22 * Math.sin(n * 0.45 + k * 1.7) + 0.12 * Math.sin(n * 1.3 + k);
@@ -162,7 +137,7 @@ export default function FeatureCollage() {
           Why the Nook
         </p>
         <h2 class="text-text mb-12 text-center text-3xl font-bold">
-          Keep track of your agents while you work
+          One glance. Everything your agents are doing.
         </h2>
 
         <div class="grid grid-cols-1 gap-5 md:grid-cols-3">
@@ -173,12 +148,12 @@ export default function FeatureCollage() {
                 The island
               </p>
               <h3 class="text-text mb-2 text-2xl font-bold tracking-tight">
-                Agent status at the top of your screen
+                Every agent, one glance
               </h3>
               <p class="text-subtext0 max-w-sm text-sm leading-relaxed">
-                The island sits around your Mac's notch, with agent activity on
-                the left and your choice of information on the right. Blue means
-                running, green means ready, and amber means an agent needs you.
+                A pill tucked into your notch — a campfire for your whole fleet
+                on the left, live data on the right. Blue running, green ready,
+                amber needs you.
               </p>
             </div>
             <div class="my-10 flex w-full justify-center">
@@ -211,15 +186,15 @@ export default function FeatureCollage() {
               />
             </div>
             <p class="text-subtext0 -mb-1 text-center text-xs">
-              Open the island to see your sessions
+              expand for the full panel ↓
             </p>
           </div>
 
           {/* Approvals */}
           <CollageCell
             kicker="Approvals"
-            title="Review permission requests"
-            body="Review permission requests above your sessions and choose Allow, Allow for session, or Deny. The iPhone and Apple Watch beta lets you respond away from your Mac."
+            title="Unblock agents, anywhere"
+            body="Permission prompts pin as cards above your sessions — Allow, Allow for session, or Deny. Away from the desk, answer from your iPhone or Apple Watch (beta)."
           >
             <InkStage>
               <div class="w-full max-w-sm px-3">
@@ -236,8 +211,8 @@ export default function FeatureCollage() {
           {/* Fans */}
           <CollageCell
             kicker="Cooling"
-            title="Fan speeds and cooling modes"
-            body="Monitor each fan's speed and choose a cooling mode. Keep automatic control or start a MAX session before a demanding task."
+            title="Silence it or max it"
+            body="Read both fans live, then take over the curve completely. Flip to MAX before a compile, whisper-quiet when the fleet idles."
           >
             <InkStage class="w-full">
               <div class="w-full max-w-[260px] text-left">
@@ -249,8 +224,8 @@ export default function FeatureCollage() {
           {/* Gauges */}
           <CollageCell
             kicker="Your Mac"
-            title="CPU and GPU monitoring"
-            body="See CPU and GPU temperatures beside their last 60 seconds of usage. Temperature readings turn amber at 70°C and red at 85°C."
+            title="The gauges that matter"
+            body="Each die's temperature beside its 60-second usage trace, tinted amber from 70° and red at 85°, so you see a compile heating up before the fans do."
           >
             <InkStage class="w-full">
               <div class="w-full max-w-[300px] text-left">
@@ -258,27 +233,15 @@ export default function FeatureCollage() {
               </div>
             </InkStage>
           </CollageCell>
-
-          <CollageCell
-            kicker="Remote"
-            title="Agents on other machines"
-            body="One-click setup for Tailscale and authorized known hosts. Remote sessions appear in the island with the host name beside the agent."
-          >
-            <InkStage class="w-full">
-              <div class="w-full min-w-0 px-3" role="img" aria-label="Remote agent sessions on build-box and gpu-rig">
-                <RemoteMock />
-              </div>
-            </InkStage>
-          </CollageCell>
         </div>
 
         <p class="text-subtext1 mt-6 text-center text-xs">
-          Also includes a volume mixer, screen capture, timers, weather, and more.{" "}
+          Plus a mixer, capture, timers, weather, and a dozen more modules —{" "}
           <a
             href="#island-extras"
             class="underline decoration-dotted hover:opacity-80"
           >
-            Browse the other modules
+            see them all ↓
           </a>
         </p>
       </div>

src/components/nook/IslandExtras.tsx

@@ -13,6 +13,7 @@ import {
   ACCENT,
   CALM,
   WARM,
+  CRITICAL,
   CARD_FILL,
   CARD_STROKE
 } from "./IslandMock";
@@ -570,8 +571,8 @@ function KeepAwakeMock() {
 
 const MODES = [
   { name: "Auto", note: "follows each agent's own settings", card: "asks", tint: "rgba(234,179,8,0.10)" },
-  { name: "Yolo", note: "automatically allows received requests", card: "passed", tint: "rgba(111,185,130,0.12)" },
-  { name: "Verify", note: "received requests wait for approval", card: "held", tint: "rgba(229,72,77,0.12)" }
+  { name: "Yolo", note: "gated tools pass straight through", card: "passed", tint: "rgba(111,185,130,0.12)" },
+  { name: "Verify", note: "every gated tool waits for you", card: "held", tint: "rgba(229,72,77,0.12)" }
 ];
 
 function ApprovalModesMock() {
@@ -772,14 +773,14 @@ export default function IslandExtras() {
     <section class="bg-base relative z-20 py-16" id="island-extras">
       <div class="px-4 md:px-8">
         <p class="text-subtext1 mb-2 text-center text-xs font-semibold tracking-[0.18em] uppercase">
-          More modules
+          And everything else
         </p>
         <h2 class="text-text mb-3 text-center text-3xl font-bold">
-          Other tools in the island
+          One island instead of a menu bar full of utilities
         </h2>
         <p class="text-subtext0 mx-auto mb-10 max-w-2xl text-center leading-relaxed">
-          Add the modules you need and arrange them in your panels.
-          They're all included with your license.
+          Every module below lives in the same notch, arranged however you
+          like, under the same one-time license.
         </p>
       </div>
 
@@ -792,8 +793,8 @@ export default function IslandExtras() {
         <CollageCell
           class="md:col-span-2"
           kicker="Now Playing"
-          title="Playback controls and track information"
-          body="See what's playing and control playback. For sources without artwork, including some browsers, the compact view shows an audio waveform."
+          title="Music in the notch"
+          body="Track, source, and transport controls in a module. Sources without artwork, like some browsers, get a live waveform in the slot instead."
         >
           <InkStage class="h-full w-full items-center">
             <NowPlayingMock />
@@ -802,8 +803,8 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Timers"
-          title="Run several timers at once"
-          body="Keep multiple timers running and check their progress in the island. When a timer finishes, it rings and keeps the island open until you dismiss it."
+          title="Timers that stack"
+          body="A readout over a tick tape that drains with a soft crest. Run several at once; finished timers ring and hold the island open until you dismiss them."
         >
           <InkStage class="h-full w-full items-center px-3">
             <TimersMock />
@@ -812,8 +813,8 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Weather"
-          title="Weather for your saved places"
-          body="Check hourly and daily forecasts for saved places. The compact view shows the current conditions and temperature."
+          title="The sky, in the slot"
+          body="Saved places with hourly and daily forecasts. The compact slot stacks the sky over the temperature."
         >
           <InkStage class="h-full w-full items-center px-3">
             <WeatherMock />
@@ -823,8 +824,8 @@ export default function IslandExtras() {
         <CollageCell
           class="md:col-span-2"
           kicker="Interceptions"
-          title="Volume and brightness controls"
-          body="Show volume and brightness changes below the island instead of the system overlay. Adjust supported external displays and use extra brightness on compatible XDR displays."
+          title="Volume and brightness, under the notch"
+          body="An optional takeover of the system HUD: levels peek out below the island. Extra brightness spends an XDR panel's HDR headroom past the usual maximum, and external displays get real brightness control."
         >
           <InkStage class="h-full w-full items-center">
             <div class="flex min-h-[110px] w-full justify-center pt-2">
@@ -835,8 +836,8 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Approval modes"
-          title="Choose how approvals are handled"
-          body="Auto follows each agent's settings. Yolo automatically allows requests that reach The Nook. Verify waits for your decision on each request it receives."
+          title="One stance for every agent"
+          body="Auto follows each agent's own settings, Yolo waves gated tools through, and Verify holds every one until you decide."
         >
           <InkStage class="h-full w-full items-center px-3">
             <ApprovalModesMock />
@@ -845,8 +846,8 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Network"
-          title="Network information and speed tests"
-          body="View and copy your public IP, ISP, gateway, and DNS details. Check for VPN routes or run a speed test."
+          title="Know your connection"
+          body="Public IP, ISP, gateway, and DNS one click from your clipboard. VPN routes get flagged, and a speed test is always a click away."
         >
           <InkStage class="h-full w-full items-center px-3">
             <NetworkMock />
@@ -855,8 +856,8 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Disks"
-          title="Disk usage and drive health"
-          body="Check read and write speeds, free space, and SMART health information for supported drives."
+          title="Storage, measured"
+          body="Live read and write throughput, capacity that matches Finder, and SMART health for your drives."
         >
           <InkStage class="h-full w-full items-center px-3">
             <DiskMock />
@@ -865,8 +866,8 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Keep Awake"
-          title="Keep your Mac awake"
-          body="Keep your Mac awake for a set time, while plugged in, with the lid closed, or while your agents are working."
+          title="Sleep when you say"
+          body="Stay awake for a set time, while plugged in, with the lid closed, or only while your agents are working."
         >
           <InkStage class="h-full w-full items-center px-3">
             <KeepAwakeMock />
@@ -875,7 +876,7 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Lock Screen"
-          title="Agent status on the Lock Screen"
+          title="Visible while locked"
           body="The island stays on your Lock Screen, so you can see how many agents are working or waiting without unlocking."
         >
           <InkStage class="h-full w-full items-center px-3">
@@ -885,8 +886,8 @@ export default function IslandExtras() {
 
         <CollageCell
           kicker="Layout"
-          title="Arrange your panels"
-          body="Drag and resize modules, choose how much detail they show, and change compact-view priorities with your Focus mode."
+          title="Panels you shape"
+          body="Drag and resize modules in the mosaic editor, pick a density, and let slot rankings switch with your Focus mode."
         >
           <InkStage class="h-full w-full items-center px-3">
             <LayoutMock />

src/components/nook/ModuleMocks.tsx

@@ -77,12 +77,6 @@ const GLYPHS: Record<string, () => JSX.Element> = {
     <path d="M3.5 8a4.5 4.5 0 1 0 1.4-3.3M3.2 2.2v2.8H6" stroke="currentColor" stroke-width="1.5" fill="none" stroke-linecap="round" stroke-linejoin="round" />
   ),
   plus: () => <path d="M8 3v10M3 8h10" stroke="currentColor" stroke-width="1.8" stroke-linecap="round" />,
-  video: () => <path d="M2 4h8v8H2Z m9 3 3-2v6l-3-2Z" fill="currentColor" />,
-  pin: () => <path d="m6 2 6 6-3 1-2 3-1-2-4 4m2-8 2-2Z" stroke="currentColor" stroke-width="1.2" fill="none" stroke-linejoin="round" />,
-  eye: () => <><path d="M1 8s2.5-4 7-4 7 4 7 4-2.5 4-7 4-7-4-7-4Z" stroke="currentColor" stroke-width="1.2" fill="none" /><circle cx="8" cy="8" r="2" fill="currentColor" /></>,
-  plug: () => <path d="M5 1v4m6-4v4M3 5h10v3a5 5 0 0 1-4 4.9V16H7v-3.1A5 5 0 0 1 3 8Z" stroke="currentColor" stroke-width="1.3" fill="none" />,
-  battery: () => <><rect x="1" y="4" width="12" height="8" rx="1.5" stroke="currentColor" stroke-width="1.2" fill="none" /><path d="M14 6v4M3 6h5v4H3Z" stroke="currentColor" stroke-width="1.2" /></>,
-  laptop: () => <path d="M3 2.5h10v9H3Z M1 13.5h14" stroke="currentColor" stroke-width="1.3" fill="none" stroke-linejoin="round" />,
   refresh: () => (
     <path d="M12.5 8A4.5 4.5 0 1 1 11 4.6M11.6 2v2.8H8.8" stroke="currentColor" stroke-width="1.5" fill="none" stroke-linecap="round" stroke-linejoin="round" />
   )

src/components/nook/MoreDemos.tsx

@@ -7,20 +7,21 @@ import {
   STATUS,
   ACCENT,
   CALM,
+  CRITICAL,
   CARD_STROKE
 } from "./IslandMock";
 import { useDemoLoop } from "./useDemoLoop";
-import { Glyph, WingCapsule, SessionRowMock, CODEX, type GlyphName } from "./ModuleMocks";
+import { Glyph, WingCapsule, type GlyphName } from "./ModuleMocks";
 
 /**
  * Live demos for the breakdowns added with the 0.6–0.10 feature set:
- * terminal replies, remote setup, Capture (module + Wings), and
+ * terminal replies, the volume mixer, Capture (module + Wings), and
  * floating actions. Same ink chrome and status palette as the originals.
  */
 
 /* ── Reply lands in the agent's own terminal ──────────────────────── */
 
-const REPLY = "Yes, update and run the tests.";
+const REPLY = "yes — and run them";
 
 export function TerminalReplyDemo() {
   const [typed, setTyped] = createSignal(0);
@@ -152,106 +153,124 @@ export function TerminalReplyDemo() {
   );
 }
 
-/** RemoteMirror's progress steps, in order. */
-const SETUP_STEPS = [
-  "connecting",
-  "pushing the hook binary",
-  "configuring agents",
-  "checking the host can reach this Mac"
+/* ── Volume mixer: every app its own level and output ─────────────── */
+
+interface MixerApp {
+  name: string;
+  color: string;
+  glyph: string;
+}
+
+const MIXER_APPS: MixerApp[] = [
+  { name: "Music", color: "#fa5c7c", glyph: "♫" },
+  { name: "Browser", color: "#6EA7FF", glyph: "◎" },
+  { name: "Meeting", color: "#6FB982", glyph: "●" },
+  { name: "podcast-cli", color: "#E7A762", glyph: ">_" }
 ];
 
-export function RemoteHostDemo() {
-  /* -1 not set up · 0…3 setting up · 4 live */
-  const [step, setStep] = createSignal(-1);
-  const [pressed, setPressed] = createSignal(false);
-  useDemoLoop(11000, [
-    [0, () => (setStep(-1), setPressed(false))],
-    [1400, () => setPressed(true)],
-    [1700, () => (setPressed(false), setStep(0))],
-    [2700, () => setStep(1)],
-    [3700, () => setStep(2)],
-    [4700, () => setStep(3)],
-    [5800, () => setStep(4)]
+export function MixerDemo() {
+  const [step, setStep] = createSignal(0);
+  useDemoLoop(9600, [
+    [0, () => setStep(0)],
+    [1800, () => setStep(1)],
+    [3800, () => setStep(2)],
+    [5800, () => setStep(3)]
   ]);
-  const live = () => step() === 4;
-  const working = () => step() >= 0 && step() < 4;
-  const chip = () =>
-    live()
-      ? { color: STATUS.ready, label: "Live" }
-      : working()
-        ? { color: "rgba(255,255,255,0.55)", label: "Setting up" }
-        : { color: "rgba(255,255,255,0.35)", label: "Not set up" };
+
+  const level = (i: number) => {
+    if (i === 0) return step() >= 3 ? 0.38 : 0.72;
+    if (i === 1) return 0.55;
+    if (i === 2) return 0.86;
+    return 0.46;
+  };
+  const muted = (i: number) => i === 1 && step() >= 1;
+  const route = (i: number) =>
+    i === 0 && step() >= 2 ? "Headphones" : i === 2 ? "Display" : "Speakers";
 
   return (
-    <div class="relative mx-auto w-full max-w-[360px] space-y-3" role="img" aria-label="One-click remote setup preview for an authorized Tailscale host">
-      {/* the host's card in Settings ▸ Agents ▸ Remote hosts */}
-      <ModuleCard>
-        <div class="space-y-2 text-left">
-          <div class="flex items-center gap-2.5">
-            <div class="min-w-0 flex-1">
-              <p class="text-[13px] font-semibold text-white">gpu-rig</p>
-              <p class="truncate text-[11px] text-white/45">tailnet peer</p>
-            </div>
-            <Show when={working()}>
-              <span class="h-3 w-3 animate-spin rounded-full border-[1.5px] border-white/25 border-t-white/80" />
-            </Show>
-            <span class="flex items-center gap-1.5 text-[10.5px] font-medium text-white/85">
-              <span
-                class="h-[7px] w-[7px] rounded-full transition-colors duration-300"
-                style={{ background: chip().color }}
-              />
-              {chip().label}
+    <ModuleCard class="mx-auto w-full max-w-[340px]">
+      <div class="space-y-2.5 text-left">
+        <div class="flex items-center">
+          <span class="text-[11px] font-semibold text-white/50">
+            Volume mixer
           </span>
-            <Show
-              when={live()}
-              fallback={
+          <span class="ml-auto font-mono text-[10px] text-white/40">
+            out · Speakers
+          </span>
+        </div>
+        <For each={MIXER_APPS}>
+          {(app, i) => (
+            <div class="flex items-center gap-2">
               <span
-                  class="rounded-md px-2.5 py-1 text-[11px] font-semibold text-white transition-all duration-200"
+                class="flex h-[18px] w-[18px] shrink-0 items-center justify-center rounded-[5px] text-[8px] font-bold text-black/70"
+                style={{ background: app.color }}
+              >
+                {app.glyph}
+              </span>
+              <div class="min-w-0 flex-1">
+                <div class="flex items-center gap-1.5">
+                  <span class="truncate text-[11px] font-semibold text-white/85">
+                    {app.name}
+                  </span>
+                  <span
+                    class="ml-auto shrink-0 rounded px-1.5 text-[9px] text-white/55 transition-colors duration-500"
                     style={{
-                    background: ACCENT,
-                    opacity: working() ? 0 : 1,
-                    transform: pressed() ? "scale(0.92)" : "scale(1)"
+                      background:
+                        i() === 0 && step() === 2
+                          ? `${ACCENT}55`
+                          : "rgba(255,255,255,0.07)"
                     }}
                   >
-                  Set up
+                    {route(i())}
                   </span>
-              }
-            >
-              <Glyph name="refresh" size={11} class="text-white/50" />
-              <span class="rounded-md bg-white/10 px-2 py-1 text-[11px] font-semibold text-[#ff6961]">
-                Remove
-              </span>
-            </Show>
                 </div>
-          <p class="min-h-8 text-[11px] text-white/50">
-            {working() ? SETUP_STEPS[step()] : " "}
+                <div
+                  class="relative mt-1 h-[5px] overflow-hidden rounded-full"
+                  style={{ background: "rgba(255,255,255,0.08)" }}
+                >
+                  <div
+                    class="h-full rounded-full"
+                    style={{
+                      width: `${level(i()) * 100}%`,
+                      background: muted(i()) ? "rgba(255,255,255,0.18)" : CALM,
+                      transition: "width 0.9s cubic-bezier(0.22,1,0.36,1), background 0.3s"
+                    }}
+                  />
+                  {/* live signal riding inside the level */}
+                  <div
+                    class="nook-meter absolute top-0 left-0 h-full rounded-full"
+                    style={{
+                      width: `${level(i()) * 100}%`,
+                      background: "rgba(255,255,255,0.35)",
+                      opacity: muted(i()) ? 0 : 1,
+                      "animation-duration": `${0.5 + i() * 0.17}s`,
+                      transition: "width 0.9s cubic-bezier(0.22,1,0.36,1), opacity 0.3s"
+                    }}
+                  />
+                </div>
+              </div>
+              <span
+                class="w-4 shrink-0 text-center text-[11px] transition-colors duration-300"
+                style={{ color: muted(i()) ? CRITICAL : "rgba(255,255,255,0.4)" }}
+              >
+                {muted(i()) ? "✕" : "♪"}
+              </span>
+            </div>
+          )}
+        </For>
+        <div class="h-px" style={{ background: "rgba(255,255,255,0.06)" }} />
+        <p class="text-[10px] text-white/40">
+          {
+            [
+              "every app on its own fader",
+              "browser muted — the rest keep playing",
+              "music routed to headphones, meeting stays on the display",
+              "music down, nothing else moved"
+            ][step()]
+          }
         </p>
       </div>
     </ModuleCard>
-
-      {/* The host name stays visible in the session badge. */}
-      <div
-        class="transition-all duration-500"
-        style={{
-          opacity: live() ? 1 : 0,
-          transform: live() ? "translateY(0)" : "translateY(6px)"
-        }}
-      >
-        <SessionRowMock
-          title="trainer · fp16"
-          prompt="benchmark fp16"
-          state="Running python bench.py…"
-          status="running"
-          agent={CODEX}
-          host="gpu-rig"
-          age="now"
-        />
-      </div>
-      <FakeCursor
-        phase={pressed() ? "press" : step() === -1 ? "idle" : "live"}
-        at={{ x: 88, y: 16 }}
-      />
-    </div>
   );
 }
 

src/components/nook/PhoneBeta.tsx

@@ -96,7 +96,7 @@ function CompanionDemo() {
             {allowed() ? "Allowed ✓" : "Claude Code · the-nook"}
           </p>
           <p class="text-[9px] leading-snug text-white/60">
-            {allowed() ? "Agent running." : "Run Bash: swift test"}
+            {allowed() ? "Back to work." : "Run Bash: swift test"}
           </p>
           <Show when={!allowed()}>
             <div class="mt-1.5 flex gap-1">
@@ -139,7 +139,7 @@ function CompanionDemo() {
           >
             <p class="text-[8px] font-semibold text-white/50">Codex asks</p>
             <p class="mt-0.5 text-[9.5px] leading-snug font-semibold text-white">
-              Deploy to staging?
+              Ship it to staging?
             </p>
             <div class="mt-2 space-y-1">
               <For each={["Yes", "Not yet"]}>
@@ -194,19 +194,19 @@ export default function PhoneBeta(props: { brandColor: string }) {
             TestFlight beta
           </span>
           <h2 class="text-text mb-3 text-3xl font-bold tracking-tight">
-            Use The Nook on iPhone and Apple Watch
+            Your fleet, in your pocket
           </h2>
           <p class="text-subtext0 mb-5 leading-relaxed">
-            The companion app is in TestFlight beta. Check your agents,
-            respond to permission requests, and answer questions when you're
-            away from your Mac.
+            The iPhone and Apple Watch companion is in beta. Approvals,
+            questions, and replies reach you away from the desk, and your
+            answer goes straight back to the agent.
           </p>
           <ul class="mb-8 space-y-2.5">
             <For
               each={[
                 "Allow, deny, answer, and reply from iPhone or Apple Watch",
                 "Connects over an end-to-end encrypted relay, your tailnet, or your LAN",
-                "Agent status widgets for your Home Screen, Lock Screen, and watch face",
+                "Home Screen, Lock Screen, and watch-face widgets for fleet status",
                 "Mute notifications for a while, or while you're active at the Mac"
               ]}
             >
@@ -255,7 +255,7 @@ export default function PhoneBeta(props: { brandColor: string }) {
             </form>
             <Show when={state() === "sent"}>
               <p class="text-subtext1 mt-4 text-sm">
-                Thanks. We'll email you a TestFlight invite.
+                Thanks. Watch your inbox for a TestFlight invite.
               </p>
             </Show>
             <Show when={state() === "limited"}>

src/components/nook/UtilityDemos.tsx

@@ -1,627 +0,0 @@
-import { For, Show, createSignal } from "solid-js";
-import { IslandPill, ModuleCard, CALM, WARM } from "./IslandMock";
-import { Glyph, type GlyphName } from "./ModuleMocks";
-import { useDemoLoop } from "./useDemoLoop";
-
-const PAPER = "#f1ead9";
-const BATTERY = "#8dc9b3";
-const CALENDAR = "#ff9e42";
-
-/** SettingsSlider: paper fill, dark knob, and a unity notch on app sliders. */
-function MixerSlider(props: { level: number; tint?: string; muted?: boolean }) {
-  const fraction = () => props.level / (props.tint ? 125 : 100);
-  const position = () => `calc(9px + (100% - 18px) * ${fraction()})`;
-  return (
-    <div class="relative h-5 min-w-0 flex-1 rounded-full bg-white/10">
-      <div
-        class="absolute inset-y-0 left-0 overflow-hidden rounded-full transition-[width] duration-700"
-        style={{ width: `calc(${position()} + 9px)`, background: PAPER }}
-      >
-        <Show when={props.tint && !props.muted}>
-          <div
-            class="nook-meter h-full w-full rounded-full"
-            style={{ background: props.tint }}
-          />
-        </Show>
-      </div>
-      <Show when={props.tint}>
-        <span
-          class="absolute top-[7.5px] h-[5px] w-[5px] rounded-full border border-white/55 bg-[#0d0d0f]"
-          style={{ left: "calc(9px + (100% - 18px) * 0.8 - 2.5px)" }}
-        />
-      </Show>
-      <span
-        class="absolute top-px h-[18px] w-[18px] rounded-full border-[1.5px] shadow-sm transition-[left] duration-700"
-        style={{
-          left: `calc(${position()} - 9px)`,
-          background: "#0d0d0f",
-          "border-color": PAPER
-        }}
-      />
-    </div>
-  );
-}
-
-function RoutePicker(props: { label: string }) {
-  return (
-    <span class="inline-flex max-w-[155px] items-center gap-1 rounded-full bg-white/10 px-2 py-1 text-[11px] text-white/85">
-      <span class="truncate">{props.label}</span>
-      <Glyph name="chevron" size={8} />
-    </span>
-  );
-}
-
-const MIXER_APPS = [
-  { name: "Music", color: "#fa5c7c", glyph: "♫" },
-  { name: "Browser", color: CALM, glyph: "◎" },
-  { name: "Meeting", color: BATTERY, glyph: "▰" }
-];
-
-/** VolumeMixerPanelView and MixerAppRow, including the current route controls. */
-export function MixerDemo() {
-  const [step, setStep] = createSignal(0);
-  useDemoLoop(10800, [
-    [0, () => setStep(0)],
-    [2400, () => setStep(1)],
-    [4800, () => setStep(2)],
-    [7200, () => setStep(3)]
-  ]);
-  const muted = (i: number) => i === 1 && step() >= 1;
-  const volume = (i: number) =>
-    i === 0 ? (step() >= 3 ? 38 : 100) : i === 1 ? 55 : 86;
-  return (
-    <div
-      role="img"
-      aria-label="Volume mixer preview with output, system sounds, microphone, and per-app volume, mute and routing controls"
-    >
-      <ModuleCard class="mx-auto w-full max-w-[360px]">
-        <div class="space-y-3 text-left text-white">
-          <div class="flex items-center gap-2" aria-label="Output volume">
-            <Glyph name="speaker" class="text-white/50" />
-            <MixerSlider level={65} />
-            <span class="w-[34px] text-right font-mono text-[11px] text-white/60">
-              65%
-            </span>
-          </div>
-          <For
-            each={[
-              {
-                label: "Output",
-                icon: "speaker",
-                device: "MacBook Pro Speakers"
-              },
-              {
-                label: "System sounds",
-                icon: "bell",
-                device: "MacBook Pro Speakers"
-              },
-              {
-                label: "Microphone",
-                icon: "mic",
-                device: "MacBook Pro Microphone"
-              }
-            ]}
-          >
-            {(route) => (
-              <div class="flex items-center gap-2">
-                <Glyph name={route.icon} class="text-white/50" />
-                <span class="flex-1 text-[12px] font-medium">
-                  {route.label}
-                </span>
-                <RoutePicker label={route.device} />
-              </div>
-            )}
-          </For>
-          <div class="h-px bg-white/[0.06]" />
-          <For each={MIXER_APPS}>
-            {(app, i) => (
-              <div class="space-y-1">
-                <div class="flex items-center gap-2">
-                  <span
-                    class="flex h-[18px] w-[18px] shrink-0 items-center justify-center rounded-[4px] text-[10px] text-white"
-                    style={{ background: app.color }}
-                  >
-                    {app.glyph}
-                  </span>
-                  <span class="min-w-0 flex-1 truncate text-[12px] font-medium">
-                    {app.name}
-                  </span>
-                  <RoutePicker
-                    label={i() === 0 && step() >= 2 ? "Headphones" : "Default"}
-                  />
-                  <span aria-label="Pin app" class="text-white/50">
-                    <Glyph name="pin" size={10} />
-                  </span>
-                  <span aria-label="Hide app" class="text-white/50">
-                    <Glyph name="eye" size={10} />
-                  </span>
-                </div>
-                <div class="flex items-center gap-2 pl-[26px]">
-                  <MixerSlider
-                    level={volume(i())}
-                    tint={app.color}
-                    muted={muted(i())}
-                  />
-                  <span class="w-[34px] text-right font-mono text-[11px] text-white/60">
-                    {muted(i()) ? 0 : volume(i())}%
-                  </span>
-                  <Glyph
-                    name={muted(i()) ? "speakerOff" : "speaker"}
-                    size={14}
-                    style={{
-                      color: muted(i()) ? WARM : "rgba(255,255,255,0.5)"
-                    }}
-                  />
-                </div>
-              </div>
-            )}
-          </For>
-        </div>
-      </ModuleCard>
-      <p class="mt-3 min-h-8 text-center text-[11px] text-white/55">
-        {
-          [
-            "Adjust each app separately",
-            "Browser muted",
-            "Music playing through headphones",
-            "Music volume lowered to 38%"
-          ][step()]
-        }
-      </p>
-    </div>
-  );
-}
-
-function PowerNode(props: {
-  label: string;
-  glyph: GlyphName;
-  watts: number;
-  tint: string;
-}) {
-  return (
-    <div class="flex h-9 items-center gap-[7px]">
-      <Glyph name={props.glyph} size={18} style={{ color: props.tint }} />
-      <div>
-        <p class="text-[9px] text-white/55">{props.label}</p>
-        <p class="font-mono text-[11px] text-white">
-          {props.watts.toFixed(1)} W
-        </p>
-      </div>
-    </div>
-  );
-}
-
-/** PowerPanelView: system draw, parallel power circuit, battery bar and controls. */
-export function BatteryDemo() {
-  const [step, setStep] = createSignal(0);
-  useDemoLoop(14000, [
-    [0, () => setStep(0)],
-    [1800, () => setStep(1)],
-    [3600, () => setStep(2)],
-    [6400, () => setStep(3)],
-    [8400, () => setStep(4)],
-    [10400, () => setStep(5)]
-  ]);
-  const pct = () => [62, 71, 80, 80, 92, 100][step()];
-  const topUp = () => step() >= 3;
-  const held = () => step() === 2;
-  const batteryWatts = () => (held() || pct() === 100 ? 0 : 26.4);
-  return (
-    <div
-      role="img"
-      aria-label="Battery preview showing system draw, adapter power split between the Mac and battery, an 80 percent charge limit, and top-up mode"
-    >
-      <ModuleCard class="mx-auto w-full max-w-[340px]">
-        <div class="space-y-3 text-left text-white">
-          <div>
-            <div class="flex items-center gap-1.5 font-mono text-[18px]">
-              <span style={{ color: CALM }}>ϟ</span> 18.2 W
-            </div>
-            <p class="text-[9px] font-semibold text-white/55">System draw</p>
-          </div>
-          <div class="flex items-center gap-2">
-            <PowerNode
-              label="Adapter"
-              glyph="plug"
-              watts={18.2 + batteryWatts()}
-              tint={CALM}
-            />
-            <svg
-              class="h-[82px] min-w-4 flex-1"
-              viewBox="0 0 100 82"
-              preserveAspectRatio="none"
-              fill="none"
-              aria-hidden="true"
-            >
-              <path
-                d="M0 41H25C55 41 40 18 70 18H100"
-                stroke={CALM}
-                stroke-opacity="0.3"
-                stroke-width="1.5"
-              />
-              <path
-                d="M0 41H25C55 41 40 64 70 64H100"
-                stroke={BATTERY}
-                stroke-opacity="0.3"
-                stroke-width="1.5"
-              />
-              <path
-                class="nook-power-flow"
-                d="M0 41H25C55 41 40 18 70 18H100"
-                stroke={CALM}
-                stroke-width="1.8"
-                stroke-dasharray="3 18"
-              />
-              <Show when={batteryWatts() > 0}>
-                <path
-                  class="nook-power-flow"
-                  d="M0 41H25C55 41 40 64 70 64H100"
-                  stroke={BATTERY}
-                  stroke-width="1.8"
-                  stroke-dasharray="3 18"
-                />
-              </Show>
-              <path d="m96 15 4 3-4 3" stroke={CALM} stroke-width="1.5" />
-              <path d="m96 61 4 3-4 3" stroke={BATTERY} stroke-width="1.5" />
-              <Show when={held()}>
-                <path
-                  d="m81 60 8 8m0-8-8 8"
-                  stroke={BATTERY}
-                  stroke-width="1.8"
-                />
-              </Show>
-            </svg>
-            <div class="space-y-2.5">
-              <PowerNode label="Mac" glyph="laptop" watts={18.2} tint={CALM} />
-              <PowerNode
-                label="Battery"
-                glyph="battery"
-                watts={batteryWatts()}
-                tint={BATTERY}
-              />
-            </div>
-          </div>
-          <div class="flex items-baseline gap-2">
-            <span class="flex-1 text-[9px] font-semibold text-white/55 uppercase">
-              Battery
-            </span>
-            <span class="font-mono text-[15px]">{pct()}%</span>
-            <span class="ml-2 flex items-center gap-1 font-mono text-[10px] text-white/70">
-              Limit{" "}
-              <span class="rounded border border-white/15 bg-white/5 px-2 py-0.5 text-[12px] text-white/90">
-                80
-              </span>
-              %
-            </span>
-          </div>
-          <div class="relative flex h-[18px] items-center">
-            <div class="h-1 w-full overflow-hidden rounded-full bg-white/[0.08]">
-              <div
-                class="h-full rounded-full transition-[width] duration-[1600ms]"
-                style={{ width: `${pct()}%`, background: CALM }}
-              />
-            </div>
-            <span
-              class="absolute h-3 w-1 rounded-sm bg-white/85"
-              style={{ left: "calc(80% - 2px)" }}
-            />
-          </div>
-          <For
-            each={[
-              {
-                label: "Top-up mode",
-                note: "Charges past the limit; off on unplug",
-                on: topUp()
-              },
-              {
-                label: "Overheat protection",
-                note: topUp()
-                  ? "Suspended while Top-up mode is on"
-                  : "Pauses at 95°F",
-                on: true
-              }
-            ]}
-          >
-            {(control) => (
-              <div class="flex items-center gap-2">
-                <div class="min-w-0 flex-1">
-                  <p class="text-[12px] font-medium">{control.label}</p>
-                  <p class="text-[10px] leading-snug text-white/55">
-                    {control.note}
-                  </p>
-                </div>
-                <span
-                  class="relative h-4 w-[30px] shrink-0 rounded-full transition-colors"
-                  style={{
-                    background: control.on ? CALM : "rgba(255,255,255,0.15)"
-                  }}
-                >
-                  <span
-                    class="absolute top-0.5 h-3 w-3 rounded-full bg-white transition-[left]"
-                    style={{ left: control.on ? "16px" : "2px" }}
-                  />
-                </span>
-              </div>
-            )}
-          </For>
-        </div>
-      </ModuleCard>
-      <p class="mt-3 min-h-8 text-center text-[11px] text-white/55">
-        {held()
-          ? "Charging paused at the 80% limit"
-          : topUp()
-            ? "Top-up mode allows a full charge"
-            : "Charging with an 80% limit"}
-      </p>
-    </div>
-  );
-}
-
-const DAYS = [
-  { letter: "M", day: 9, dots: 1 },
-  { letter: "T", day: 10, dots: 2 },
-  { letter: "W", day: 11, dots: 1 },
-  { letter: "T", day: 12, dots: 2 },
-  { letter: "F", day: 13, dots: 3 },
-  { letter: "S", day: 14, dots: 0 },
-  { letter: "S", day: 15, dots: 0 }
-];
-const EVENTS = [
-  {
-    start: "09:30",
-    end: "09:45",
-    title: "Standup",
-    calendar: "Work",
-    color: CALENDAR,
-    location: "Video call",
-    meeting: true
-  },
-  {
-    start: "15:30",
-    end: "16:00",
-    title: "Design review",
-    calendar: "Work",
-    color: CALENDAR,
-    location: "4th floor",
-    meeting: false
-  }
-];
-
-/** CalendarSlotFace's daymark / next-up / on-air states, and CalendarPanelView. */
-export function CalendarDemo() {
-  const [step, setStep] = createSignal(0);
-  useDemoLoop(16000, [
-    [0, () => setStep(0)],
-    [2400, () => setStep(1)],
-    [4800, () => setStep(2)],
-    [9000, () => setStep(3)],
-    [12000, () => setStep(4)]
-  ]);
-  const onAir = () => step() >= 3;
-  return (
-    <div
-      role="img"
-      aria-label="Calendar preview showing the date, a meeting countdown, an on-air indicator, and the day's events with a join meeting button"
-      class="flex min-h-[360px] min-w-0 flex-col items-center gap-4"
-    >
-      <div class="flex max-w-full justify-center" style={{ zoom: 0.8 }}>
-        <IslandPill
-          right={
-            <svg width="40" height="40" viewBox="0 0 40 40" aria-hidden="true">
-              <Show when={step() === 0}>
-                <rect
-                  x="6"
-                  y="4"
-                  width="28"
-                  height="27"
-                  rx="5"
-                  fill="#ededed"
-                />
-                <path
-                  d="M11 4h18a5 5 0 0 1 5 5v3H6V9a5 5 0 0 1 5-5"
-                  fill={CALENDAR}
-                />
-                <text
-                  x="20"
-                  y="10"
-                  text-anchor="middle"
-                  font-size="5.5"
-                  font-weight="700"
-                  fill="#1f1f1f"
-                >
-                  THU
-                </text>
-                <text
-                  x="20"
-                  y="28"
-                  text-anchor="middle"
-                  font-size="17"
-                  font-weight="700"
-                  fill="#1f1f1f"
-                >
-                  12
-                </text>
-                <circle cx="20" cy="36" r="2.25" fill={CALENDAR} />
-              </Show>
-              <Show when={step() === 1 || step() === 2}>
-                <text
-                  x="20"
-                  y="10"
-                  text-anchor="middle"
-                  font-size="7"
-                  font-weight="700"
-                  fill="white"
-                  opacity="0.65"
-                >
-                  IN
-                </text>
-                <text
-                  x="20"
-                  y="30"
-                  text-anchor="middle"
-                  font-size="20"
-                  font-weight="700"
-                  fill="white"
-                >
-                  {step() === 1 ? "14m" : "5m"}
-                </text>
-                <rect
-                  x="6"
-                  y="34"
-                  width="28"
-                  height="2"
-                  rx="1"
-                  fill="white"
-                  opacity="0.15"
-                />
-                <rect
-                  x="6"
-                  y="34"
-                  width={step() === 1 ? 2 : 19}
-                  height="2"
-                  rx="1"
-                  fill={CALENDAR}
-                />
-              </Show>
-              <Show when={onAir()}>
-                <rect
-                  x="1"
-                  y="3"
-                  width="38"
-                  height="22"
-                  rx="5"
-                  fill={CALENDAR}
-                  opacity="0.18"
-                />
-                <circle cx="4.7" cy="14.5" r="2.1" fill={CALENDAR} />
-                <text
-                  x="22.6"
-                  y="17"
-                  text-anchor="middle"
-                  font-size="7.8"
-                  font-weight="700"
-                  fill={CALENDAR}
-                >
-                  ON AIR
-                </text>
-                <rect
-                  x="1"
-                  y="31"
-                  width="38"
-                  height="5"
-                  rx="2.5"
-                  fill={CALENDAR}
-                  opacity="0.7"
-                />
-                <rect
-                  x="1"
-                  y="31"
-                  width={step() === 4 ? 25 : 8}
-                  height="5"
-                  rx="2.5"
-                  fill="#333"
-                />
-                <rect
-                  x={step() === 4 ? 25 : 8}
-                  y="29"
-                  width="2.6"
-                  height="9"
-                  rx="1.3"
-                  fill="#ededed"
-                />
-              </Show>
-            </svg>
-          }
-        />
-      </div>
-      <div class="w-full max-w-[360px]">
-        <ModuleCard>
-          <div class="space-y-2.5 text-left text-white">
-            <div class="flex items-center">
-              <div>
-                <p class="text-[10px] text-white/55">Calendar</p>
-                <p class="text-[14px] font-semibold">Thu, Nov 12</p>
-              </div>
-              <span class="ml-auto rounded-lg bg-white/[0.08] p-[7px] text-white/55">
-                <Glyph name="plus" />
-              </span>
-            </div>
-            <div class="flex h-[60px] gap-[3px]">
-              <For each={DAYS}>
-                {(day) => (
-                  <div
-                    class="flex min-w-0 flex-1 flex-col items-center justify-center gap-[5px] rounded-[10px]"
-                    style={{
-                      background: day.day === 12 ? CALENDAR : "transparent",
-                      color: day.day === 12 ? "#0d0d0f" : "white",
-                      opacity: day.day < 12 ? 0.6 : 1
-                    }}
-                  >
-                    <span class="text-[9px] opacity-60">{day.letter}</span>
-                    <span
-                      class="text-[13px]"
-                      style={{ "font-weight": day.day === 12 ? 700 : 500 }}
-                    >
-                      {day.day}
-                    </span>
-                    <span class="flex h-1 gap-0.5">
-                      <For each={Array.from({ length: day.dots })}>
-                        {() => (
-                          <span
-                            class="h-1 w-1 rounded-full"
-                            style={{ background: CALENDAR }}
-                          />
-                        )}
-                      </For>
-                    </span>
-                  </div>
-                )}
-              </For>
-            </div>
-            <For each={EVENTS}>
-              {(event) => (
-                <div class="flex items-center gap-2.5 rounded-[10px] bg-white/[0.035] p-2.5">
-                  <div class="w-[40px] shrink-0 text-right font-mono text-[10px]">
-                    <p>{event.start}</p>
-                    <p class="mt-[3px] text-white/55">{event.end}</p>
-                  </div>
-                  <span
-                    class="w-[3px] self-stretch rounded-sm"
-                    style={{ background: event.color }}
-                  />
-                  <div class="min-w-0 flex-1 space-y-1">
-                    <p class="text-[12px] leading-snug font-semibold">
-                      {event.title}
-                    </p>
-                    <p
-                      class="text-[10px] font-medium"
-                      style={{ color: event.color }}
-                    >
-                      {event.calendar}
-                    </p>
-                    <p class="text-[10px] text-white/55">{event.location}</p>
-                  </div>
-                  <Show when={event.meeting}>
-                    <span
-                      aria-label="Join meeting"
-                      class="rounded-lg bg-white/[0.08] p-2 text-white/65"
-                    >
-                      <Glyph name="video" />
-                    </span>
-                  </Show>
-                </div>
-              )}
-            </For>
-          </div>
-        </ModuleCard>
-      </div>
-      <p class="min-h-4 text-center text-[11px] text-white/55">
-        {step() === 0
-          ? "Today's date and calendar events"
-          : onAir()
-            ? "Meeting in progress"
-            : "Countdown to your next meeting"}
-      </p>
-    </div>
-  );
-}

src/lib/sitemap-routes.test.ts

@@ -67,8 +67,7 @@ describe("generateSitemap", () => {
     expect(locs).toContain("https://nessa.freno.me/");
     expect(locs).toContain("https://nessa.freno.me/contact");
     expect(locs).toContain("https://nessa.freno.me/privacy");
-    expect(locs).toContain("https://nessa.freno.me/terms");
-    expect(locs.length).toBe(4);
+    expect(locs.length).toBe(3);
 
     for (const loc of locs) {
       expect(loc).not.toContain("://freno.me/");

src/lib/sitemap-routes.ts

@@ -57,8 +57,7 @@ export const SITEMAP_ROUTES: Record<SiteId, SitemapEntry[]> = {
   nessa: [
     { path: "/", changefreq: "weekly", priority: 1.0 },
     { path: "/contact", changefreq: "monthly", priority: 0.6 },
-    { path: "/privacy", changefreq: "yearly", priority: 0.4 },
-    { path: "/terms", changefreq: "yearly", priority: 0.4 }
+    { path: "/privacy", changefreq: "yearly", priority: 0.4 }
   ],
 
   lineage: [

src/routes/nessa/contact.tsx

@@ -1,7 +1,6 @@
 import { ContactForm } from "~/components/ContactForm";
 import { EdgeCacheHeaders } from "~/components/EdgeCacheHeaders";
 import SubdomainHeader from "~/components/SubdomainHeader";
-import { SUPPORT_EMAIL } from "./content";
 
 /**
  * Nessa contact page (`nessa.freno.me/contact`).
@@ -17,27 +16,14 @@ import { SUPPORT_EMAIL } from "./content";
  *
  * Acceptance: `nessa.localhost:3000/contact` renders the contact form with
  * Nessa branding; submissions email `michael@freno.me` with subject
- * `[Nessa] Contact Request`. The support address shown by the app is also
- * published here, so the contact route does not depend on the form alone
- * (FRE-1670).
+ * `[Nessa] Contact Request`.
  */
 export default function NessaContactPage() {
   return (
     <>
       <EdgeCacheHeaders maxAge={60} staleSeconds={3600} />
       <SubdomainHeader />
-      <ContactForm>
-        <p class="mt-8 text-center text-sm opacity-80">
-          You can also email us directly at{" "}
-          <a
-            href={`mailto:${SUPPORT_EMAIL}`}
-            class="text-blue hover-underline-animation"
-          >
-            {SUPPORT_EMAIL}
-          </a>
-          .
-        </p>
-      </ContactForm>
+      <ContactForm />
     </>
   );
 }

src/routes/nessa/content.ts

@@ -14,15 +14,6 @@ export const TAGLINE = "The fitness app that puts you first." as const;
 export const SUBTITLE =
   "Track, train, and connect — without the paywall." as const;
 
-/**
- * The support address the Nessa app shows (`SubscriptionView` /
- * `HelpSupportView`). Every published Nessa document that offers a contact
- * route names this same address, so a user who leaves the app to read the
- * terms, privacy policy, contact page, or deletion page can still reach us
- * (FRE-1670). Keep in step with `nessa-support@freno.me` in the app.
- */
-export const SUPPORT_EMAIL = "nessa-support@freno.me" as const;
-
 export const ICON_DEFAULT =
   "/Nessa Exports/Nessa-iOS-Default-1024x1024.png" as const;
 export const ICON_DARK = "/Nessa Exports/Nessa-iOS-Dark-1024x1024.png" as const;

src/routes/nessa/deletion.tsx

@@ -33,7 +33,6 @@ import {
   DELETION_GRACE_PERIOD_LABEL,
   PAGE_META
 } from "~/routes/nessa/deletion-content";
-import { SUPPORT_EMAIL } from "./content";
 
 export default function NessaDeletionPage() {
   return (
@@ -55,18 +54,6 @@ export default function NessaDeletionPage() {
             removed. No data related to the account is retained in any way.
           </div>
 
-          <div class="text-text mt-4 w-full justify-center">
-            Prefer email? Send your deletion request from the address on your
-            Nessa account to{" "}
-            <a
-              href={`mailto:${SUPPORT_EMAIL}?subject=Account%20Deletion%20Request`}
-              class="text-blue hover-underline-animation"
-            >
-              {SUPPORT_EMAIL}
-            </a>
-            ; the same {DELETION_GRACE_PERIOD_LABEL} grace period applies.
-          </div>
-
           <DeletionForm
             product={DELETION_PRODUCT_KEY}
             cookieName={DELETION_COOKIE_NAME}

src/routes/nessa/privacy.tsx

@@ -30,7 +30,6 @@ import { A } from "@solidjs/router";
 import { PageHead } from "~/components/PageHead";
 import { EdgeCacheHeaders } from "~/components/EdgeCacheHeaders";
 import SubdomainHeader from "~/components/SubdomainHeader";
-import { SUPPORT_EMAIL } from "./content";
 
 export default function NessaPrivacyPolicy() {
   return (
@@ -175,29 +174,15 @@ export default function NessaPrivacyPolicy() {
               <span class="-ml-4 pr-2">5.</span> Contact Us
             </div>
             <div class="pb-2 pl-4">
-              <div class="-ml-6">(a) Data Controller:</div> Nessa is operated by
-              FrenoCorp. For the purposes of applicable data-protection law,
-              FrenoCorp is the controller of the personal information described
-              in this policy.
-              <div class="pt-2 pb-2">
-                <div class="-ml-6">(b) Reaching Out:</div> If there are any
-                questions or comments regarding this privacy policy, or you want
-                to access, correct, or delete your personal information, you can
+              <div class="-ml-6">(a) Reaching Out:</div> If there are any
+              questions or comments regarding this privacy policy, you can
               contact us{" "}
               <A href="/contact" class="text-blue hover-underline-animation">
-                  through the contact form
-                </A>{" "}
-                or email{" "}
-                <a
-                  href={`mailto:${SUPPORT_EMAIL}`}
-                  class="text-blue hover-underline-animation"
-                >
-                  {SUPPORT_EMAIL}
-                </a>
+                here
+              </A>
               .
             </div>
           </div>
-          </div>
         </ol>
       </div>
     </>

src/routes/nessa/support-contact.test.ts

@@ -1,36 +0,0 @@
-/**
- * Regression guard for the published Nessa support address (FRE-1670).
- *
- * The app tells users to mail `nessa-support@freno.me` from the subscription
- * screen and Help & Support. Before this guard, no published Nessa page named
- * that address: a user who left the app to read the terms, privacy policy,
- * contact page, or deletion page found no way to reach support. That is a
- * privacy-policy contact gap (GDPR/CCPA-style) and an App Review question
- * waiting to happen.
- *
- * The address lives in one place (`SUPPORT_EMAIL`), and every page that
- * offers a contact route must render it. Reading the route sources is
- * deliberate: the defect is a page that exists but does not mention the
- * address, which no runtime assertion over a single page can observe.
- */
-import { describe, it, expect } from "bun:test";
-import { readFileSync } from "fs";
-import { SUPPORT_EMAIL } from "./content";
-
-const CONTACT_ROUTE_FILES = [
-  "src/routes/nessa/terms.tsx",
-  "src/routes/nessa/privacy.tsx",
-  "src/routes/nessa/contact.tsx",
-  "src/routes/nessa/deletion.tsx"
-];
-
-describe("Nessa published support address", () => {
-  it("is the address the app shows", () => {
-    expect(SUPPORT_EMAIL).toBe("nessa-support@freno.me");
-  });
-
-  it.each(CONTACT_ROUTE_FILES)("%s renders it", (file) => {
-    const source = readFileSync(file, "utf8");
-    expect(source).toContain("SUPPORT_EMAIL");
-  });
-});

src/routes/nessa/terms.tsx

@@ -1,454 +0,0 @@
-/**
- * Nessa terms of use — `nessa.freno.me/terms`.
- *
- * The document behind the `Terms of Service` row in the Nessa app
- * (`Nessa/Models/AppSettings.swift`, Settings › Legal). Before this page the
- * row had no Nessa-owned document to resolve to: the app linked another
- * product's terms, and `nessa.freno.me/terms` was a 404 (FRE-194).
- *
- * Nessa sells an auto-renewing subscription through the App Store, so App
- * Review 3.1.2 requires the app to link a privacy policy **and** terms of
- * use. Section 5 (subscriptions) and section 6 (Apple acknowledgements) are
- * the clauses that requirement is read against, so keep them when editing.
- *
- * House voice follows `privacy.tsx`: "we" / "Nessa", no legal entity name,
- * and no governing-law clause — the Nessa pages have never stated either, and
- * naming an entity or a jurisdiction is a decision to make deliberately, not
- * to introduce as a side effect of a link fix.
- *
- * PageHead is site-aware: only the base title is supplied; the ` | Nessa`
- * suffix, the `https://nessa.freno.me/terms` canonical and the OG image are
- * derived automatically. Internal links use public subdomain-relative paths
- * (`/privacy`, `/deletion`, `/contact`) per nav-config.ts and
- * page-head-meta.ts.
- */
-import { A } from "@solidjs/router";
-import { PageHead } from "~/components/PageHead";
-import { EdgeCacheHeaders } from "~/components/EdgeCacheHeaders";
-import SubdomainHeader from "~/components/SubdomainHeader";
-import { SUPPORT_EMAIL } from "./content";
-
-export default function NessaTermsOfUse() {
-  return (
-    <>
-      <EdgeCacheHeaders maxAge={300} />
-      <PageHead
-        title="Terms of Use"
-        description="Terms of use for Nessa, a fitness app for tracking workouts and training with clubs, challenges, and friends."
-      />
-      <SubdomainHeader />
-      <div class="min-h-screen px-[8vw] py-[10vh]">
-        <div class="py-4 text-xl">Nessa&apos;s Terms of Use</div>
-        <div class="py-2">Last Updated: November 9, 2026</div>
-        <div class="py-2">
-          Welcome to Nessa (&apos;We&apos;, &apos;Us&apos;, &apos;Our&apos;).
-          These terms of use govern your access to and use of the Nessa app and
-          its related services. By using Nessa you agree to these terms. Our{" "}
-          <A href="/privacy" class="text-blue hover-underline-animation">
-            privacy policy
-          </A>{" "}
-          explains how we handle your data, and it forms part of these terms.
-        </div>
-        <ol>
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">1.</span> Acceptance of These Terms
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) Agreement:</div> By creating an account,
-                downloading, or otherwise using Nessa you agree to these terms.
-                If you do not agree to them, do not use Nessa.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) Eligibility:</div> You must be at least
-                the age of digital consent in your country to use Nessa. If you
-                are using Nessa with a parent&apos;s or guardian&apos;s
-                account, they are responsible for your compliance with these
-                terms.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) Where these terms apply:</div> These
-                terms are between you and us. Where you obtained Nessa through
-                a third party such as the Apple App Store, that
-                party&apos;s own terms apply to your relationship with them as
-                well.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">2.</span> The Service
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) What Nessa is:</div> Nessa is a fitness
-                application for iOS, with an Apple Watch companion, that lets
-                you record workouts and routes, review your training history,
-                and take part in community features — clubs, club challenges,
-                posts, comments, and leaderboards. Some features are free and
-                some require a paid subscription (see section 5).
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) Changes and availability:</div> We are
-                continually improving Nessa, so features may change, move
-                between tiers, or be withdrawn. We do not guarantee that Nessa
-                will be available at all times, and we may suspend or discontinue
-                part or all of the service. Where a change materially affects a
-                paid feature you have subscribed to, we will tell you on the
-                subscription management page or by contact.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) Not medical advice:</div> Nessa is not a
-                medical device and is not intended to diagnose, treat, cure, or
-                prevent any condition. Workout data, heart-rate and other
-                health readings, training plans, and estimates you see in Nessa
-                are for general information and motivation only. Consult a
-                qualified professional before starting or changing a training
-                programme, especially if you have a health condition. Never
-                ignore professional advice, or delay seeking it, because of
-                something you read in Nessa.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(d) Your surroundings:</div> You are
-                responsible for your own safety while using Nessa, including
-                when recording an activity. Follow local laws and do not use
-                Nessa in a way that distracts you from driving or other
-                activities that require your full attention.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">3.</span> Your Account
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) Sign-in:</div> Nessa accounts are
-                authenticated through Clerk, our identity provider. You are
-                responsible for keeping the credentials you use to sign in
-                secure, and you are responsible for the activity that happens
-                under your account.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) Notify us:</div> Tell us promptly, using
-                the contact details in section 11, if you believe someone else
-                has used or may use your account without your permission.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) One account:</div> Keep to one account,
-                and give us accurate information so we can keep your training
-                history and your place in the community correct. Do not create
-                accounts to evade a moderation decision or to gain a fair
-                advantage in challenges or leaderboards.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">4.</span> Community Content and Acceptable
-              Use
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) You keep your content:</div> You own what
-                you post. By posting to a club, challenge, or other shared area
-                of Nessa you grant us a limited, non-exclusive licence to store,
-                reproduce, and display that content inside Nessa so that the
-                feature you used can work — for example, showing your post to
-                the members of your club. That licence ends when your content is
-                removed from our systems. We handle your content as described in
-                our{" "}
-                <A href="/privacy" class="text-blue hover-underline-animation">
-                  privacy policy
-                </A>
-                ; we do not sell it.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) What you are responsible for:</div> You
-                are responsible for the content you post and the data you record
-                in Nessa, and for who you share it with. Use the privacy
-                settings on your profile and the privacy rules of the clubs you
-                join before sharing anything you would not want others to see.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) Do not:</div> (i) post anything unlawful,
-                harassing, hateful, threatening, or sexually explicit involving
-                minors; (ii) post content you do not have the right to share, or
-                that infringes someone else&apos;s intellectual property;
-                (iii) falsify activity data, spoof a location, or otherwise
-                cheat a challenge, leaderboard, or competition; (iv) scrape,
-                bulk-download, or access Nessa through automated means we have
-                not authorised; (v) interfere with, overload, or probe Nessa for
-                vulnerabilities, or attempt to access another user&apos;s
-                account or data; (vi) resell, sublicense, or offer Nessa to
-                others as your own service.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(d) Moderation:</div> We may remove or
-                restrict content, disqualify an entry from a challenge, or
-                suspend or close an account that breaks these terms. We are not
-                obliged to pre-monitor content. You can report content or a user
-                to us at any time using the contact details in section 11.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">5.</span> Subscriptions and Payments
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) Paid tiers:</div> Nessa offers paid
-                subscription tiers, Nessa Plus and Nessa Pro, which unlock
-                features described in the app. Subscriptions are sold as
-                auto-renewing subscriptions through the Apple App Store and are
-                billed to your Apple Account.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) Payment:</div> Payment is charged to your
-                Apple Account at confirmation of purchase. The price of your
-                plan is shown in the app before you buy, and it is the price on
-                your App Store purchase receipt.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) Auto-renewal:</div> Unless you cancel at
-                least 24 hours before the end of the current period, your
-                subscription renews automatically. Your account is charged for
-                renewal within 24 hours before the end of the current period, at
-                the price of the plan you selected.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(d) Managing your subscription:</div> You can
-                turn off auto-renewal, or cancel, at any time in your App Store
-                account settings after purchase. Changes made there take effect
-                at the end of the current period, and you keep access to the
-                paid features you have already paid for until then.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(e) Trials:</div> If we offer a free trial,
-                any unused portion of it is forfeited when you purchase a
-                subscription, and the trial converts to a paid auto-renewing
-                subscription unless you cancel it before it ends.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(f) Refunds:</div> Purchases made through the
-                App Store are refunded according to Apple&apos;s refund policy
-                and, where applicable law gives you a right to a refund,
-                according to that law. Tell us using the contact details in
-                section 11 and we will do what we can.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(g) Price changes:</div> We may change our
-                prices. A price change does not apply to a period you have
-                already paid for; it applies from your next renewal, and we give
-                notice where the law requires it.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(h) Downgrade:</div> When a subscription
-                lapses or is cancelled you keep the free features, and anything
-                you created that belongs to a paid feature (such as a custom
-                route) is kept but is not editable or usable until you
-                subscribe again.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">6.</span> Apple and Other Third Parties
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) Not Apple&apos;s terms:</div> These terms
-                are between you and us, not with Apple Inc. Apple is not
-                responsible for Nessa or its content, and your use of Nessa must
-                comply with the Apple App Store Terms of Service.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) No Apple support:</div> Apple has no
-                obligation to furnish maintenance and support services for
-                Nessa. If Nessa fails, you may notify Apple, but Apple has no
-                further support obligation, and support and any warranties
-                relating to Nessa are ours to provide as described in these
-                terms.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) Apple is not responsible for claims:</div>{" "}
-                Apple is not responsible for product liability claims,
-                intellectual property infringement claims, or any other claims
-                relating to Nessa or your possession and use of it. We, not
-                Apple, are responsible for addressing any such claims and for
-                any claims that you may have relating to Nessa.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(d) Compliance:</div> You confirm that you
-                are not located in a country subject to an embargo of the United
-                States or listed by the United States government as a
-                terrorist-supporting country, and that you are not listed on any
-                United States government list of prohibited or restricted
-                parties.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(e) Third-party services:</div> Nessa depends
-                on third-party services — Clerk for authentication, Apple
-                HealthKit for health and workout data, Apple&apos;s In-App
-                Purchase system for subscriptions, and our own hosting — each
-                governed by its own terms. Where those terms affect how you may
-                use the feature they power, they apply alongside these terms.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">7.</span> Intellectual Property
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) Our rights:</div> The Nessa software, its
-                design, text, icons, and branding are owned by us or our
-                licensors and are protected by copyright and other laws. We
-                grant you a personal, non-exclusive, non-transferable, revocable
-                licence to use Nessa for your own personal, non-commercial
-                purposes.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) Restrictions:</div> You may not copy,
-                modify, translate, distribute, sell, lease, sublicense, or
-                create derivative works from Nessa, and you may not reverse
-                engineer, decompile, or attempt to obtain its source code,
-                except to the extent applicable law allows this despite a
-                restriction.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">8.</span> Disclaimers and Limitation of
-              Liability
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) As is:</div> Nessa is provided &quot;as
-                is&quot; and &quot;as available&quot; to the fullest extent
-                permitted by applicable law. We do not warrant that Nessa will
-                be uninterrupted, secure, error-free, or that recorded data will
-                be accurate — GPS-derived distance, pace, elevation, and
-                estimates can be wrong, and device and sensor limits apply.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) Your data:</div> You are responsible for
-                backing up the data you store on your device. We keep
-                Nessa&apos;s service data as described in the{" "}
-                <A href="/privacy" class="text-blue hover-underline-animation">
-                  privacy policy
-                </A>{" "}
-                and{" "}
-                <A href="/deletion" class="text-blue hover-underline-animation">
-                  deletion page
-                </A>
-                , but no service is a substitute for your own backup.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) Liability:</div> To the fullest extent
-                permitted by law, we are not liable for indirect, incidental,
-                special, consequential, or punitive damages, or for lost data,
-                lost profits, or loss of training records, arising out of your
-                use of, or inability to use, Nessa. Where a court would not
-                allow that exclusion, our liability for claims arising from your
-                use of Nessa is limited to the greater of the subscription fees
-                you paid us in the twelve months before the event giving rise to
-                the claim, or the minimum the applicable law requires. Nothing
-                in these terms limits liability that cannot lawfully be limited,
-                including for fraud or for death or personal injury caused by
-                our negligence.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">9.</span> Ending Your Use
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) You can leave:</div> You can stop using
-                Nessa at any time. You can delete your account and the content
-                associated with it through our{" "}
-                <A href="/deletion" class="text-blue hover-underline-animation">
-                  account deletion page
-                </A>
-                . Deleting your account does not cancel a subscription that is
-                still in its paid period; cancel that in your App Store account
-                settings as described in section 5.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) We may end access:</div> We may suspend
-                or close your access to Nessa if you break these terms, if we
-                are required to by law, or if we reasonably believe your account
-                has been compromised. Where we can, we will tell you why.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(c) On termination:</div> Your licence to use
-                Nessa ends, and sections 4(a), 6, 7, 8, 10, and 11 continue to
-                apply.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">10.</span> Changes to These Terms
-            </div>
-            <div class="pl-4">
-              <div class="pb-2">
-                <div class="-ml-6">(a) Updates:</div> We may update these terms
-                as Nessa changes. The current version is always the one at{" "}
-                <A href="/terms" class="text-blue hover-underline-animation">
-                  nessa.freno.me/terms
-                </A>
-                , and the &quot;Last Updated&quot; date at the top of this page
-                shows when it last changed.
-              </div>
-              <div class="pb-2">
-                <div class="-ml-6">(b) Continued use:</div> If you keep using
-                Nessa after a change takes effect, you accept the revised terms.
-                For changes that materially reduce your rights or your paid
-                features, we will give notice in the app or by contact before
-                they take effect.
-              </div>
-            </div>
-          </div>
-
-          <div class="py-2">
-            <div class="pb-2 text-lg">
-              <span class="-ml-4 pr-2">11.</span> Contact Us
-            </div>
-            <div class="pb-2 pl-4">
-              <div class="-ml-6">(a) Reaching Out:</div> If you have any
-              questions or comments about these terms, want to report content,
-              or need help with a subscription, you can contact us{" "}
-              <A href="/contact" class="text-blue hover-underline-animation">
-                through the contact form
-              </A>{" "}
-              or email{" "}
-              <a
-                href={`mailto:${SUPPORT_EMAIL}`}
-                class="text-blue hover-underline-animation"
-              >
-                {SUPPORT_EMAIL}
-              </a>
-              .
-            </div>
-          </div>
-        </ol>
-      </div>
-    </>
-  );
-}

src/routes/nook/index.tsx

@@ -59,9 +59,9 @@ export default function NookLanding() {
       <PageHead
         title="Agent control for your Mac"
         ogTitle="The Nook — agent control for your Mac"
-        description="Monitor coding agents, respond to permission requests, and manage your Mac\'s cooling, battery, and audio with The Nook."
+        description="The Nook — a native macOS utility for coding-agent orchestration, fan and thermal control."
         ogImage={`https://${site().domain}/nook/og.png`}
-        ogDescription="A macOS app for coding agents, fan control, battery charging, and per-app audio. Includes a 14-day trial and a one-time license."
+        ogDescription="A one-time-purchase macOS app for coding-agent orchestration, fan control, and thermal insight."
       />
 
       <SubdomainHeader />
@@ -96,11 +96,11 @@ export default function NookLanding() {
             The Nook
           </div>
           <h1 class="text-text mb-4 text-4xl font-bold tracking-tight sm:text-5xl">
-            Manage your coding agents and your Mac
+            Your Mac and Agents, under control
           </h1>
           <p class="text-subtext0 mb-2 max-w-xl text-xl">
-            Follow your agents, respond to requests, and manage cooling,
-            charging, and audio from the top of your screen.
+            Agent orchestration, fan and thermal control in a beautiful native
+            UI.
           </p>
           <p class="text-subtext1 mb-8 text-sm">
             macOS 14.2+ · 14-day free trial · up to 3 devices
@@ -145,7 +145,7 @@ export default function NookLanding() {
             In action
           </p>
           <h2 class="text-text mb-16 text-center text-3xl font-bold">
-            What you can do with The Nook
+            Built for the way you actually run agents
           </h2>
           <FeatureBreakdowns />
         </div>
@@ -164,9 +164,10 @@ export default function NookLanding() {
             Try it free for 14 days
           </h2>
           <p class="text-subtext0 mx-auto mb-10 max-w-2xl leading-relaxed">
-            The trial includes every module. After 14 days, a one-time
-            purchase lets you keep using The Nook on up to three of your Macs.
-            There is no subscription.
+            Orchestrate your coding agents, take control of your fans and
+            battery, give every app its own volume, capture your screen, and
+            keep your day in the notch. When the trial ends, unlock everything
+            with a single one-time payment — no subscription, ever.
           </p>
           <div class="flex flex-col items-center justify-center gap-4 sm:flex-row sm:space-x-4">
             <Button
@@ -186,7 +187,7 @@ export default function NookLanding() {
             </a>
           </div>
           <p class="text-subtext1 mt-6 text-xs">
-            The beta price is $10. The regular price will be $15. One license covers up to 3 of
+            Beta pricing — full price will be $15. One license covers up to 3 of
             your own Macs.
           </p>
         </div>
@@ -228,7 +229,8 @@ export default function NookLanding() {
           </form>
           <Show when={resendSent()}>
             <p class="text-subtext1 mt-4 text-center text-sm">
-              If a license is registered to that email, we'll send you the key.
+              Check your inbox — if a license is registered to that email, your
+              key is on its way.
             </p>
           </Show>
           <Show when={resendError()}>

src/routes/nook/landing.test.ts

@@ -1,78 +0,0 @@
-import { describe, expect, it } from "bun:test";
-import { readFileSync } from "node:fs";
-import { join } from "node:path";
-
-const root = join(import.meta.dir, "../../..");
-const read = (path: string) => readFileSync(join(root, path), "utf8");
-const landingCopy = [
-  "src/routes/nook/index.tsx",
-  ...[
-    "FeatureCollage",
-    "FeatureBreakdowns",
-    "IslandExtras",
-    "PhoneBeta",
-    "MoreDemos",
-    "UtilityDemos"
-  ].map((name) => `src/components/nook/${name}.tsx`)
-]
-  .map(read)
-  .join("\n");
-
-// Like remote-claims.test.ts, this pins an editorial decision, not a tone score.
-describe("Nook landing copy (NOOK-1037)", () => {
-  for (const phrase of [
-    "Your fleet, in your pocket",
-    "Timers that stack",
-    "Volume and brightness, under the notch",
-    "The sky, in the slot",
-    "Storage, measured",
-    "Wall power, on your terms",
-    "Fans that answer to you, not the scheduler",
-    "Your whole fleet, in one pixel strip",
-    "A hearth that tells the truth",
-    "A lens that stays asleep",
-    "Your buttons, orbiting the island",
-    "Silence it or max it",
-    "Sleep when you say",
-    "Panels you shape"
-  ]) {
-    it(`replaces “${phrase}”`, () => {
-      expect(landingCopy).not.toContain(phrase);
-    });
-  }
-});
-
-// Source anatomy checks supplement the rendered browser checks.
-const demos = read("src/components/nook/UtilityDemos.tsx");
-
-describe("current utility demo anatomy (NOOK-1037)", () => {
-  it("shows the three calendar slot states and calendar-colored agenda rows", () => {
-    for (const text of ["ON AIR", "Work", "Thu, Nov 12", "Join meeting"])
-      expect(demos).toContain(text);
-    expect(demos).toMatch(/>\s*IN\s*</);
-  });
-
-  it("shows the power circuit and current battery controls", () => {
-    for (const text of [
-      "System draw",
-      "Adapter",
-      "Mac",
-      "Overheat protection",
-      "Charges past the limit; off on unplug"
-    ])
-      expect(demos).toContain(text);
-    expect(demos).not.toContain("the pack stays young longer");
-  });
-
-  it("shows master routing, app percentages, pin and hide controls", () => {
-    for (const text of [
-      "System sounds",
-      "Microphone",
-      "Output volume",
-      "Pin app",
-      "Hide app",
-      "Default"
-    ])
-      expect(demos).toContain(text);
-  });
-});

src/routes/nook/remote-claims.test.ts

@@ -1,32 +1,49 @@
 /**
- * Two page contracts live in this file, and they are reconciled on purpose.
+ * Regression test for the removed remote / SSH claims and the removed agent
+ * count (FRE-323, FRE-359 verdict B).
  *
- * NOOK-1038 (2026-11-09, Mike's correction) supersedes FRE-323's blanket remote
- * hold: one-click setup is a supported scoped claim for Tailscale peers and
- * authorized known hosts, so the Remote cards and the setup demo belong on the
- * page. Blanket authorization promises stay out.
+ * FRE-323 took the remote story off the site because it was unverified and
+ * demo-gated (FRE-315, FRE-320, FRE-322 §3 correction 4): the "one click
+ * installs the nook-hook" flow is app-UI-only, needs a hand-edited
+ * `~/.ssh/config` for any host not already in ssh config or on the tailnet,
+ * needs a one-time `ssh-copy-id` because the app runs ssh with
+ * `BatchMode=yes`, and has no manual fallback for minting the per-host
+ * credential. FRE-359 verdict B removed the coverage count for the same
+ * reason: the /agents table lists 13 of the registry's 18 rows.
  *
- * FRE-997 (2026-11-04) restored the agent count. The page listed thirteen of the
- * registry's eighteen rows, so FRE-359 verdict B dropped the count instead of
- * correcting it; FRE-997 put all eighteen rows on /agents and made the roster an
- * equality check again (`agents.test.ts`), so the count is publishable at 18 and
- * the stale counts stay banned.
+ * FRE-997 corrects the second half without touching the first. The count was
+ * stale, not unverifiable: `AgentSpec.all` holds eighteen, /agents now lists
+ * all eighteen and `agents.test.ts` asserts that roster as an equality again.
+ * So the two completeness phrasings FRE-359 banned ("every coding agent",
+ * "Supported agents") no longer rest on a 13-of-18 gap — the ban existed
+ * because the page claimed the set and listed two thirds of it. They are out
+ * of `BANNED_COVERAGE` on this branch for that reason alone; the stale counts
+ * stay banned, and every FRE-323 remote sentence stays banned, because this
+ * branch still carries the FRE-323 site state.
  *
- * The two lines met in the FRE-1695 reconciliation (Gitea was 12 commits ahead,
- * GitHub 2). NOOK-1038's file repeated FRE-359's older "no coverage count"
- * clause; that clause is superseded by FRE-997's landed correction and is the
- * one line dropped here. Everything else from NOOK-1038 is taken verbatim, and
- * `marketing/positioning.md` records both decisions side by side (coverage row:
- * publishable at 18; remote row: approved, scoped). See `docs/deploy-source.md`.
+ * The copy was not thrown away — it is parked in
+ * `marketing/drafts/remote-ssh/` with the restore gate, and this test asserts
+ * it is still there so nobody deletes the parked story as stale. It goes back
+ * on the site only when the one-click install ships and is recorded.
  *
  * STATIC SOURCE AUDIT, the same pattern as `agents.test.ts` and
  * `downloads.test.ts` (SolidJS does not render under `bun:test`).
+ *
+ * Deliberate exceptions, not audited here — both were weighed with the Chief
+ * of Staff at the go/no-go and left in place on purpose:
+ *  - `src/routes/nook/agents.tsx` Muse row: "This Mac only — remote hosts skip
+ *    it" is a limitation disclosure, not a capability claim.
+ *  - `src/components/nook/IslandExtras.tsx` "Tailscale hosts" chip: adjacent to
+ *    the removed remote story, but tailnet host lookup does exist. Raised on
+ *    FRE-323 rather than widened into this correction.
  */
 import { describe, it, expect } from "bun:test";
 import { readFileSync } from "node:fs";
 import { join } from "node:path";
 
 const ROOT = join(import.meta.dir, "../../..");
+
+/** Shipped page and component source. Tests and drafts may quote the old copy. */
 const AUDITED = [
   "src/routes/nook/index.tsx",
   "src/routes/nook/agents.tsx",
@@ -36,6 +53,29 @@ const AUDITED = [
   "src/components/nook/IslandExtras.tsx"
 ];
 
+/** Every sentence FRE-323 ordered off the site. */
+const BANNED_REMOTE_CLAIMS = [
+  "Agents on other machines",
+  "one click installs the nook-hook",
+  "Any SSH box",
+  "Works across every hooked agent, local or remote",
+  "Remote sessions are ordinary rows",
+  "One-click SSH setup",
+  "remote machines over SSH",
+  "this Mac or remote machines"
+];
+
+/** FRE-359 verdict B: no stale count, in any form.
+ *
+ * "every coding agent" and "Supported agents" left this list with FRE-997:
+ * the page now lists all eighteen registry rows and `agents.test.ts` asserts
+ * that equality, so the completeness claim is backed rather than incomplete. */
+const BANNED_COVERAGE = [
+  "all thirteen",
+  "thirteen coding agents",
+  "13 agents"
+];
+
 /** User-facing copy only: comments are not copy and may name the old wording. */
 function copyOf(file: string): string {
   return readFileSync(join(ROOT, file), "utf8")
@@ -43,83 +83,44 @@ function copyOf(file: string): string {
     .replace(/^\s*\/\/.*$/gm, "");
 }
 
-describe("remote marketing reflects the supported setup (NOOK-1038)", () => {
-  it("fills the collage's missing sixth grid slot with host-labelled remote sessions", () => {
-    const collage = copyOf("src/components/nook/FeatureCollage.tsx");
-    // The hero spans two columns; four regular cards fill the other slots.
-    expect(collage.match(/<CollageCell\b/g)).toHaveLength(4);
-    expect(collage).toContain('kicker="Remote"');
-    expect(collage).toContain("One-click setup for Tailscale and authorized known hosts");
-    expect(collage).toContain('host="build-box"');
-    expect(collage).toContain('host="gpu-rig"');
-  });
-
-  it("restores the detailed setup section with both discovery sources", () => {
-    const breakdowns = copyOf("src/components/nook/FeatureBreakdowns.tsx");
-    expect(breakdowns).toContain('kicker="Remote"');
-    expect(breakdowns).toContain('title="Set up remote agents in one click"');
-    expect(breakdowns).toContain("Tailscale peer or an authorized host from your SSH config");
-    expect(breakdowns).toContain("<RemoteHostDemo />");
-  });
-
-  it("demonstrates setup progressing to Live and a host-labelled session", () => {
-    const demos = copyOf("src/components/nook/MoreDemos.tsx");
-    for (const label of [
-      "connecting",
-      "pushing the hook binary",
-      "configuring agents",
-      "checking the host can reach this Mac",
-      "Live",
-      "Set up"
-    ])
-      expect(demos).toContain(label);
-    expect(demos).toContain('host="gpu-rig"');
-  });
-
+describe("remote claims stay off the site (FRE-323)", () => {
   for (const file of AUDITED) {
-    it(`${file} makes no blanket authorization promise`, () => {
-      const copy = copyOf(file).toLowerCase();
-      for (const phrase of [
-        "Any SSH box",
-        "Works across every hooked agent, local or remote",
-        "no SSH authorization needed"
-      ])
-        expect(copy).not.toContain(phrase.toLowerCase());
+    it(`${file} does not restore a removed remote sentence`, () => {
+      const copy = copyOf(file);
+      for (const phrase of BANNED_REMOTE_CLAIMS) {
+        expect(copy.toLowerCase()).not.toContain(phrase.toLowerCase());
+      }
     });
   }
 
-  it("records the current decision without deleting the historical copy", () => {
-    for (const file of [
-      "marketing/drafts/remote-ssh/copy.md",
-      "marketing/drafts/remote-ssh/rationale.md",
-      "marketing/positioning.md"
-    ]) {
-      const text = readFileSync(join(ROOT, file), "utf8");
-      expect(text).toContain("NOOK-1038");
-      expect(text).toContain("Tailscale and authorized known hosts");
+  it("/agents no longer offers remote sessions", () => {
+    const copy = copyOf("src/routes/nook/agents.tsx");
+    expect(copy).not.toContain("remote sessions report into the same grid");
+    expect(copy).not.toContain("on this Mac or on remote");
+  });
+
+  it("the parked copy still exists, so restoring the story is a revert and not a rewrite", () => {
+    const parked = readFileSync(join(ROOT, "marketing/drafts/remote-ssh/copy.md"), "utf8");
+    for (const phrase of ["Agents on other machines", "Any SSH box, one click away"]) {
+      expect(parked).toContain(phrase);
     }
-    expect(
-      readFileSync(join(ROOT, "marketing/drafts/remote-ssh/copy.md"), "utf8")
-    ).toContain("Any SSH box, one click away");
+    expect(readFileSync(join(ROOT, "marketing/drafts/remote-ssh/rationale.md"), "utf8")).toContain(
+      "FRE-320"
+    );
   });
 });
 
 describe("the agent count is corrected, not dropped (FRE-997)", () => {
-  /** FRE-359 verdict B, minus the phrasings FRE-997 re-grounded in the full roster. */
-  const BANNED_COVERAGE = ["all thirteen", "thirteen coding agents", "13 agents"];
-
   for (const file of AUDITED) {
     it(`${file} states no stale count`, () => {
-      const copy = copyOf(file).toLowerCase();
-      for (const phrase of BANNED_COVERAGE) expect(copy).not.toContain(phrase);
+      const copy = copyOf(file);
+      for (const phrase of BANNED_COVERAGE) {
+        expect(copy.toLowerCase()).not.toContain(phrase.toLowerCase());
+      }
     });
   }
 
   it("/agents states the registry's size", () => {
     expect(copyOf("src/routes/nook/agents.tsx")).toContain("Supported agents");
   });
-
-  it("the landing copy states the count the roster actually has", () => {
-    expect(copyOf("src/components/nook/FeatureBreakdowns.tsx")).toContain("18 agents");
-  });
 });

src/routes/subdomain-dispatch.test.ts

@@ -14,10 +14,7 @@ import { describe, it, expect } from "bun:test";
 import { readdirSync, existsSync, statSync } from "fs";
 
 function isRouteFile(name: string): boolean {
-    // Page routes are components; the `.ts` files beside them are pure content /
-    // metadata modules (content.ts, meta.ts, *-content.ts) with no default
-    // export the router can render, so they are not dispatch targets.
-    return name.endsWith(".tsx");
+    return name.endsWith(".tsx") || name.endsWith(".ts");
 }
 
 function listRouteFiles(dir: string): string[] {
@@ -28,20 +25,6 @@ function listRouteFiles(dir: string): string[] {
     }
 }
 
-function listDirectories(dir: string): string[] {
-    try {
-        return readdirSync(dir).filter((name) => {
-            try {
-                return statSync(`${dir}/${name}`).isDirectory();
-            } catch {
-                return false;
-            }
-        });
-    } catch {
-        return [];
-    }
-}
-
 function hasDispatchRoute(routeName: string, routesDir: string): boolean {
     // Check for src/routes/<name>.tsx
     if (existsSync(`${routesDir}/${routeName}.tsx`)) {
@@ -58,12 +41,14 @@ describe("subdomain routing dispatch invariant", () => {
     const routesDir = "./src/routes";
 
     it("every subdomain route has a top-level dispatch route", () => {
-        // List directory entries before filtering to route files. The previous
-        // shape filtered with `listRouteFiles` first, which only ever returns
-        // `.tsx`/`.ts` names, so `statSync(...).isDirectory()` was never true
-        // and the assertion ran over an empty list — it passed while `/terms`
-        // had no dispatch file (FRE-1670).
-        const prefixDirs = listDirectories(routesDir)
+        const prefixDirs = listRouteFiles(routesDir)
+            .filter((name) => {
+                try {
+                    return statSync(`${routesDir}/${name}`).isDirectory();
+                } catch {
+                    return false;
+                }
+            })
             // Exclude non-product subdomains
             .filter((name) =>
                 ["nessa", "lineage", "gaze", "inputhalo", "nook"].includes(name)

src/routes/terms.tsx

@@ -1,30 +0,0 @@
-import { Switch, Match } from "solid-js";
-import { useSite } from "~/context/SiteContext";
-import NotFound from "./[...404]";
-import NessaTermsOfUse from "./nessa/terms";
-
-/**
- * Host-aware terms-of-use route — `/terms`.
- *
- * The public browser path `/terms` is what the Nessa app links from
- * Settings › Legal and from the subscription paywall
- * (`AppSettings.termsOfServiceURL`). Production Vercel deployments do not
- * apply the `vercel.json` host rewrites (the Nitro Build Output API config
- * supersedes them), so the subdomain page needs this top-level dispatch file
- * to be reachable — without it `nessa.freno.me/terms` is a 404 even though
- * `src/routes/nessa/terms.tsx` exists.
- *
- * Only Nessa publishes terms of use today. Every other site — and the main
- * site — falls back to the 404 handler rather than borrowing another
- * product's legal document.
- */
-export default function TermsPage() {
-  const site = useSite();
-  return (
-    <Switch fallback={<NotFound />}>
-      <Match when={site().id === "nessa"}>
-        <NessaTermsOfUse />
-      </Match>
-    </Switch>
-  );
-}