* feat(ui): add shared seeded paper gradients
Centralize the Paper mesh and grain wrappers so React and Solid apps can reuse the same deterministic seed-based visuals without repeating shader config. Add a standalone demo surface and update existing consumers so the shared package is easier to validate and evolve.
* fix(ui): resolve shared package from source
Point the shared UI package exports at source files so Next builds do not depend on a prebuilt dist directory. Add Next transpilation for @openwork/ui in Landing and Den Web so monorepo and Vercel builds resolve the package consistently.
---------
Co-authored-by: src-opn <src-opn@users.noreply.github.com>
Align the legacy v1 bundle publish routes with the scoped Next API protections so older deployment paths stop accepting wildcard origins or host-derived share URLs.
Co-authored-by: src-opn <src-opn@users.noreply.github.com>
Unify bundle naming across share and team-template paths so the shell only wires the flow and workspace bundles describe their portable files consistently.
Route template publish/fetch through the OpenWork server so shared setup links carry template files and keep local or remote imports on the same contract.
Keep BotId and the share rewrites in one canonical Next config so public /v1 routes keep resolving after security hardening changes.
Co-authored-by: Omar McAdam <omar@OpenWork-Studio.localdomain>
The share app was missing a favicon (browser tabs showed default icon)
and had no fallback OpenGraph/Twitter metadata in the root layout.
This meant any route without explicit OG tags had no social card when
shared on X, Slack, or messaging apps.
- Add favicon using existing openwork-mark.svg (matches landing/den-web)
- Add fallback OpenGraph metadata (type, siteName) to root layout
- Add Twitter card defaults with @getopenwork site attribution
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* refactor(repo): move OpenWork apps into apps and ee layout
Rebase the monorepo layout migration onto the latest dev changes so the moved app, desktop, share, and cloud surfaces keep working from their new paths. Carry the latest deeplink, token persistence, build, Vercel, and docs updates forward to avoid stale references and broken deploy tooling.
* chore(repo): drop generated desktop artifacts
Ignore the moved Tauri target and sidecar paths so local cargo checks do not pollute the branch. Remove the accidentally committed outputs from the repo while keeping the layout migration intact.
* fix(release): drop built server cli artifact
Stop tracking the locally built apps/server/cli binary so generated server outputs do not leak into commits. Also update the release workflow to check the published scoped package name for @openwork/server before deciding whether npm publish is needed.
* fix(workspace): add stable CLI bin wrappers
Point the server and router package bins at committed wrapper scripts so workspace installs can create shims before dist outputs exist. Keep the wrappers compatible with built binaries and source checkouts to avoid Vercel install warnings without changing runtime behavior.
