docs: republish Pages and match shipped Rhizome

[tuckcode]

Why Pages stopped

The Landing page workflow (.github/workflows/pages.yml) only runs on push to main when these paths change:

• website/**
• docs/assets/**
• src/assets/brand/rhizome-organic-hero.png
• .github/workflows/pages.yml

Last success: 2026-09-27 11:36 UTC on 8ed9817. Later main commits did not touch those paths, so GitHub queued no run. This is not a disabled workflow and not a failing deploy.

Checked live 2026-10-11:

• Repo is public (private: false), so the if: !github.event.repository.private skip does not apply.
• Pages is build_type: workflow, URL https://tuckcode.github.io/rhizome-agent/ .
• The live page still describes a Prime-only app.

A merge of this PR touches website/ and the workflow file, so the next push to main should deploy.

What knispo must do by hand

Nothing in Pages settings. Merge this PR. Confirm Actions → Landing page runs on the merge commit.

If a run does not appear: Actions → Landing page → Run workflow (workflow_dispatch is already there).

Do not change the Pages source. It is already workflow-based.

What this PR changes

Docs / site / workflow only. No app code.

Site

• website/index.html — Rhizome is the harness; Prime is optional; Hermes is not a usable engine; Free tier (auto); Earth dark; Views 1–4; vault is read/diff only; keys in the keychain.
• .github/workflows/pages.yml — comment that records the path-filter cause.

User docs

• README.md
• docs/start/README.md
• docs/PUBLIC-PREVIEW.md
• docs/GETTING-STARTED.md (prerequisites + “What ships now”)
• docs/for-agents/README.md

Tests / handoff

• src/lib/leftover-website-copy.test.ts — locks the Prime-as-harness regression.
• docs/plans/handoffs/2026-10-11-1115-cursor-grok-4-6-pages-docs.md
• HANDOFF.md not edited.

Verified against main (not the brief alone)

• Native engine exists and sends without Prime (chatEngineAllowsSendWithoutPrime). Settings still default Chat to Prime until Chat engine is switched.
• Hermes is not in PRODUCT_AI_AGENT_DEFINITIONS. Not a usable engine.
• Free-tier UI label is Free tier (auto). Taproot is not on main.
• Earth dark default; Earth light; Loam; Match system.
• Views: Research, Graph, Mycelium, History. Ctrl+Cmd+1–4 / Ctrl+Shift+1–4 (not 1–5). Changes next to Notes.
• Native write tool is create_note. No agent vault search or Mycelium-session search.
• Provider keys: OS keychain (ADR-0185). Legacy JSON migrates on first read.

QA

• bash website/build.sh /tmp/rhizome-pages-site — index.html, hero, demo, icon, .nojekyll.
• pnpm handoff:check
• pnpm exec vitest run src/lib/leftover-website-copy.test.ts src/lib/leftover-public-preview-claims.test.ts — 6 passed.
• sh .husky/pre-push — frontend, Rust, Playwright lanes OK (17m 8s). Chunk sidecar unavailable; local fallback.

Localization: none — English only (C18).
PostHog: no event needed because this is docs and the Pages workflow.
Codacy: docs/workflow/copy-lock test only; no new Critical/High source surface.
ADRs: none.
Demo vault dirt: none.

  

[repowise-bot]

🔍 1 thing to check

1. This PR introduces dry violation in src/lib/leftover-website-copy.test.ts line 20

✅ Health of changed files: 9.7

Check	Result
Coverage	Not set up · add one CI step
Tests	No changed source files
Security	No new findings on changed lines
Doc drift	3 refuted claims in a doc this PR edits

Doc drift

• docs/GETTING-STARTED.md line 364 refers to src/mock-tauri.ts, which the tree no longer has (medium confidence)
• docs/GETTING-STARTED.md line 624 refers to src/components/MyComponent.tsx, which the tree no longer has (medium confidence)
• docs/GETTING-STARTED.md line 627 refers to src/components/MyComponent.test.tsx, which the tree no longer has (medium confidence)

---

📊 See the full report for this PR
_{Blast radius, every caller of the contracts it changes, and health before and after. No sign-in.
Plain markdown for agents}

_{Settings and updates}

_{Updated 2026-10-11 11:25 UTC
Silence one PR with [skip repowise] in the title · Bot settings
⭐ Star Repowise · 📥 Install on another repo}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

No blocking implementation findings were identified, and Codacy reports the PR as up to standards. However, several acceptance criteria remain unverified because the Pages build, workflow triggers, and broader documentation behavior lack automated tests.

About this PR

• Broaden the documentation regression coverage to validate the required shipped behavior, including UI defaults, keychain handling, and vault limitations.
• Add automated validation for the Pages build and workflow trigger behavior; the current regression test does not verify the broader acceptance criteria or deployment path.

Test suggestions

• The copy regression test rejects Prime-as-harness, Prime-required, and stale Hermes marketing claims while checking the updated Rhizome, Free tier, Earth, vault, and keychain copy.
• The Pages website build produces a deployable site containing the landing page and required assets.
• The Pages workflow triggers for changes to the listed paths and supports manual workflow dispatch.
• Documentation accurately preserves the documented UI behavior, engine defaults, keychain behavior, and vault limitations.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. The Pages website build produces a deployable site containing the landing page and required assets.
2. The Pages workflow triggers for changes to the listed paths and supports manual workflow dispatch.
3. Documentation accurately preserves the documented UI behavior, engine defaults, keychain behavior, and vault limitations.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}