Harvested moss interface bank

These files preserve real moss interface states for the landing page and documentation. Reuse them before drawing a substitute interface.

File	State	Intended reuse
`editor.html`	Self-contained harvested editor with mock data and local command adapters	Live editor scenes and interaction reference
`app-editor.html`	Self-contained harvest of the app's own `editor.html` + `editor-main.ts`, with only the Tauri seams mocked — opening files, saving, the app's menus, and versions mode are the app's own code, backed by a real in-memory project per locale (`?lang=en` a William Blake project, `?lang=zh-hant`/`zh-hans` a 朱耷 project)	The docs demo (`demo/`); frames `editor-main`-only behavior (versions mode, real context menus, creating pages, saving/loading templates) the hand-assembled `editor.html` cannot
`[email protected]`	Static editor capture, 880 × 1120	Fallback when the HTML scene is too heavy or its interaction is irrelevant
`shell.html`	Self-contained harvested preview/publish shell	Live preview and publish scenes
`[email protected]`	Static preview capture, 1760 × 1120	Static preview fallback
`mark.svg`	moss mark used by the harvested shell	Interface chrome only
`demo/`	`<moss-editor-demo>` + `<moss-demo-marker>` — the one editor a documentation page shows, and the markers that hand it a scene	User-started documentation demos around a harvested fixture; see `demo/README.md`

The editor guide uses ../assets/guides/editor-ui-source.png and ../assets/guides/choose-page-source.png directly. capture-manifest.json records the desktop source commit, source paths, visible states, and derivation. The older editor-map.svg documentation montage remains in the bank but is not used by the guide.

Refresh recipe

Rebuild or export the desktop editor and preview as self-contained HTML, preserving the app CSS, icons, locale strings, mock command boundary, and the exact state being documented.
Serve site/ through the native moss preview, then run PLAYWRIGHT_MODULE=/path/to/node_modules/playwright/index.mjs node scripts/capture-editor-guide-assets.mjs --preview=http://localhost:PORT/. When Playwright is installed in this repository, omit PLAYWRIGHT_MODULE.
The script sets and focuses the sample through window.__editor, captures the compact editor state, clicks the real breadcrumb summary, waits for the expanded tree, captures that state, and closes the browser in finally.
Update capture-manifest.json with the source commit and visible state. Never animate a gesture the harvested state does not implement.

Current state manifest

Editor fixture: a William Blake site with a selected Markdown page, breadcrumb/file tree, property chips, title, body, and bottom toolbar.
Shell fixture: the matching generated site in its preview and publish chrome.
shell.html stays the harvest. What the landing page adds to it lives with the landing, in site/landing-shell.js, which the landing loads into its scene 2 shell, so a refresh keeps it. That script leans on the shell's window.__shell (its ring's set, paint, svg and host) and on the app's publish receipt stylesheet rules the harvest carries; check-landing-desktop-pace fails if a refresh changes either under it.
Locale: interface chrome is English. The localized landing scene supplies separate Chinese content; these banked files are not translated screenshots.
Interaction boundary: editor.html is a deterministic mock of the captured editor, suitable for the interactions it exposes. It is not the desktop application and must not be used as proof of filesystem, Git, deploy, or operating-system behavior.
Demo contract: links ending in #scene=… become <moss-demo-marker> controls for the page's single <moss-editor-demo> surface. Any pointer or key press inside the editor stops scripted playback and keeps its current state. Reduced motion applies scene steps instantly. Full contract: demo/README.md.
Guide loading: .moss/theme/script.js upgrades authored #scene= links and loads the modules in demo/ through window.mossTheme.base; each module resolves its stylesheet, scene data, and harvested iframe from import.meta.url, preserving deployment subpaths.
Source of truth for behavior: current desktop code and release documentation. When either disagrees with a capture, refresh the capture or use text instead.

The source manifest distinguishes the captured fixture's commit from the desktop commit used to verify the written instructions.

demo

A documentation page shows one real moss interface once, pinned beside the text.