The FRE-323 correction took the remote story off the site against claims the
copy never made: hosts do come from ~/.ssh/config and Tailscale
(RemoteHostDiscovery), the one-time ssh-copy-id is a prerequisite the row
hands the user as a command (RemoteHostStatus.fixCommand), the per-host
credential is minted and copied over (RemoteMirror), and a remote host
mirrors this Mac's integrations (RemoteMirrorReconcile). The removals also
dropped the agent count instead of correcting it: the page said thirteen,
AgentSpec.all holds eighteen.
- Revert c1c498e: the Remote collage tile and its mock, the "Any SSH box, one
click away" breakdown with its RemoteHostDemo, and the "One-click SSH setup"
chip are back.
- Revert c718370: /agents says remote sessions report into the same grid.
- The approvals bullet no longer claims "every hooked agent"; it names the
three agents that cannot mirror. Muse, Cline and Amp are .unsupported for
remote in AgentSpec.remote, so Cline and Amp rows now disclose it too.
- Count is 18 on the landing bullet, the marquee chip and all of /agents
(title, description, ogTitle, H1 paragraph).
- The five missing rows are on /agents: Kimi, GitHub Copilot CLI, Crush,
Cursor and Amp, events and gating taken from hook/setup.go,
hook/normalize.go, hook/normalize_hosts.go, Sources/NookCore/Agents/
HookConfigInstaller.swift and plugins/amp/index.ts. All five are Observe:
kimi/copilot PreToolUse+PermissionRequest fire before the host's own check
(awaitPolicyTable has no entry; kimi's PermissionRequest is
notification-only), Crush documents one event, a silent Cursor permission
hook blocks the action, Amp's plugin API has no permission-wait event.
- agents.test.ts asserts equality with the 18-name registry again, and the
count; remote-claims.test.ts keeps only the two guards worth keeping (no
universal remote claim, no stale thirteen).
- positioning.md: the held remote row becomes a publishable row with its
backing, the count row becomes publishable at 18, and
marketing/drafts/remote-ssh/ is deleted.
bun test src/routes/nook: 17 pass, 0 fail. Against d44133f with these two
test files the same suites give 10 fail (7 pass), so the guards prove the fix.
bun run build: ✔ build done (router client, SSR, server-fns, vercel preset).
bun test src/routes: 124 pass / 20 fail / 2 errors; the same 20 fail and 2
errors on d44133f, so they are pre-existing environment failures.
copy.md said the sentences were "removed from the live site" and
rationale.md said "the landing page now says only what the product can back
today". Neither is true: nook.freno.me still serves all of them (HTTP 200,
re-fetched 2026-10-29T14:20Z) because the push is blocked on a write
credential (card 82d1e1b7). Both files now say committed-not-deployed, and
positioning.md's excluded-count row records FRE-359 verdict B and where the
count was removed.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
FRE-323. The one-click remote install is app-UI-only and needs hand-edited ~/.ssh/config plus a one-time ssh-copy-id (FRE-320); FRE-315 and FRE-322 hold the claim unverified and demo-gated.
- drop the Remote tile and its mock from the feature collage
- drop the "Any SSH box, one click away" breakdown, its demo and bullets
- drop "Works across every hooked agent, local or remote"
- drop the "One-click SSH setup" chip
- move the copy to marketing/drafts/remote-ssh/ and mark remote held in marketing/positioning.md
No replacement claim was added. Deploy waits on a push credential for the GitHub repo Vercel builds.
One voice, one place, so agent-drafted assets stop inventing framing
per artifact. positioning.md carries the wedge, the category-noun rule
(freno-dev/AGENTS.md competitor ban), claims each backed by code, the
honest privacy scoping and the voice/banned-phrasings list. The tree
adds calendar.json, per-channel briefs, drafts → pending → approved →
posted, metrics and listening — with the hard rule up front: approved/
is the only thing a human ever publishes from, nothing posts itself.
Issue: FRE-17
