* ✨ feat(share): extract share pages into a standalone SSR micro app
`/share/t/:id` and `/share/page/:id` were client-only routes inside the main
SPA, so a shared link opened on a blank shell and link previews carried the
generic app card. They now live in `apps/share`, built the same way as
`apps/workbench`: a React Router framework-mode app that server-renders on a
Cloudflare Worker for cloud, plus a plain SPA build that Next serves for
self-hosted deployments.
What the server renders is the shell, the hero and a complete meta set — title,
description and the OG/Twitter card — resolved from the route loader through a
per-request tRPC client. The conversation and page-viewer stacks stay on the
client: `clientOnly()` gates them and, in the SSR environment, a resolver stub
cuts every `*.client` module out of the worker graph entirely. Gating the render
alone does not help, because the dynamic import still pulls the graph into the
bundle.
Keeping that worker deployable took three more cuts, each found by tracing the
module graph rather than guessing:
- `@/store/user` is stubbed for SSR — `GroupAvatar` reads the viewer profile,
and the store drags the model catalog and every provider behind it (39MB→19MB)
- `shiki` and `shiki/wasm` are stubbed for SSR — the `@lobehub/ui` barrel reads
the bundled-language catalog at module scope, registering ~400 grammars for a
highlighter the server never runs (19MB→7.6MB, 1.78MB gzip)
- SSR i18n resolves only the namespaces the shell renders; the generic loader
would register every locale x namespace pair as a worker chunk
The conversation list keeps its `headerSlot` while it shows the skeleton. It
returned early before, so mounting the list to fetch blanked a title the server
had already rendered.
`/share` is removed from the desktop and mobile routers and rewritten by the
Next middleware to `/spa-share/<locale>/…`, mirroring how `/verify` reaches
workbench. The cloud worker is published from lobehub-cloud, which builds this
same app against its business overlay, so this repo ships no deploy workflow
for it.
* 🐛 fix(share): preload the error namespace so the boundary renders translated
The root ErrorBoundary reaches for the `error` namespace, which SSR did not
bundle, so a failed share page rendered `error.title error.desc error.retry`
verbatim. Fetching it on demand does not fix that case: a chunk-load failure is
exactly when the client can never load the dictionary to correct itself.
* 🐛 fix(share): drop the dev template fetch that served the main SPA
The handler asked the main Vite server for `/index.share.html`, which does not
exist at the repo root. Vite answers that with the HTML fallback — 200, main SPA
shell — so `/share/*` in `bun run dev` silently booted an app that no longer has
those routes. Share is developed against its own Vite server, so the branch goes
rather than the file being added.
`spaDevShells.test.ts` guards both directions: every remaining dev template must
exist at the root and point at its own app entry, and share must not reintroduce
one.
* 📝 docs(skill): record the cloud-overlay split in split-micro-app
Share is the second micro app and the first whose rendering code lives in the
lobehub-cloud business overlay, so the skill needed the ownership rules that
decides which repo builds and deploys, and the Vite 8 tsconfig-nearest-importer
landmine that makes an overlay build ship the open-source fallback with a green
build.
Also folds in what the extraction turned up: the full Docker chain, the dev shell
that answers 200 with the wrong app, shiki and @lobehub/ui bundle cuts, the error
namespace, hydration and virtualized-prefill rules, the asset prefix convention,
and the prod promote gate.
* ♻️ refactor(spa): extract verify/acceptance into apps/workbench
Move the Workbench SPA into apps/workbench and serve /verify and
/acceptance from that runtime for every web UA. The main SPA no
longer registers those page routes, so they drop out of its bundle.
* 🔧 chore(docker): wire the workbench workspace into image builds
Copy apps/workbench/package.json before pnpm i so Docker can resolve
the extracted SPA. Keep generateSpaTemplates optional for Cloud, and
require the HTML only when WORKBENCH_REQUIRED=1 (build:docker).
* ♻️ refactor(workbench): hard-navigate only from markdown entity links
Keep Link and useWorkspaceAwareNavigate in-router. Markdown verify,
acceptance, and mobile agent-doc links document-navigate. Drop the
__WORKBENCH__ Vite define; Electron still skips hard-nav for portals.
* ♻️ refactor(verify): slot-inject origin conversation and decouple shared components
* 🐛 fix(i18n): make vite glob loaders independent of the vite root
* ✨ feat(workbench): React Router framework mode SSR on Cloudflare Workers
* 🐛 fix(verify): render viewer-timezone timestamps only after hydration
* 💚 ci(workbench): deploy with affected detection and PR build verification
* 📝 docs(skills): micro-app split and gateway routing playbook
* 🐛 fix(workbench): track app/lib swallowed by the root lib/ ignore rules
* ✨ feat(workbench): signed-in acceptance list sidebar on detail pages
* 🐛 fix(workbench): survive shared-origin gateway quirks in client navigation
* 💄 style(workbench): surface error detail on the boundary page
* 💄 style(workbench): adopt the shared ErrorCapture page for the root boundary
* 💄 style(verify): drop the app-home back arrow from the acceptance list panel
* 🔧 chore(workbench): persist only error logs in wrangler observability
* 📝 docs(skills): record Docker vs Cloud hosting for micro apps
OSS Docker still builds and serves the SPA in-image. Cloud Next must
not build, rewrite, or CDN-upload it — gateway routes to the Worker.
* 💄 style(workbench): pin the acceptance logo while the list panel slides
* 🐛 fix(workbench): only show the acceptance sidebar when signed in
* 🐛 fix(verify): drop namespace prefix on bound verify translations
Innei