Commit Graph
28 Commits
Author SHA1 Message Date
szski 7a262c617c Merge pull request #79 from szski/feat/agent-bus
feat(agent): SSE-based AgentBus for external-tool UI control
2026-05-13 16:07:41 -04:00
Antigravity AI 5e542c3ca6 fix(docker): Remove obsolete copy command for deleted script 2026-05-12 19:24:40 +12:00
SapphireandClaude Opus 4.7 1845a1ced9 feat(agent): SSE-based AgentBus for external-tool UI control
Adds an opt-in agent integration surface that lets a trusted external
tool (running as the same logged-in user) drive the running WWV browser
session — fly the globe, toggle layers, focus entities — by POSTing
JSON actions to the server, which fans them out over SSE to every
connected browser tab belonging to that user.

The motivating use case is an MCP server (a Model Context Protocol
adapter): an LLM agent calls a tool like `globe_fly_to({lat, lon})`,
the MCP server posts to `/api/agent/publish`, the browser subscriber
re-emits the action onto the existing client-side `dataBus`, and the
React + Cesium app handles it the same way it would handle any UI
button click. Read-only camera / engine queries already work via the
existing REST surface — this PR adds the missing write path.

What's added:

- `src/lib/agent/bus.ts` — process-local AgentBus singleton, scoped
  per user. Subscriptions live in a `Map<userId, Map<connId, sub>>`
  so user A's publish never reaches user B's stream, even though
  both run on the same Node process.

- `src/app/api/agent/stream/route.ts` — SSE channel. Auth-gated. Sends
  initial `:connected` + `retry:3000` directives and a `:hb` heartbeat
  every 25s so intermediary proxies (Caddy, Nginx, CDNs) don't tear
  down a "stalled" connection.

- `src/app/api/agent/publish/route.ts` — POST endpoint. Accepts JSON
  AgentAction shapes (`fly_to`, `face_towards`, `layer_toggle`,
  `highlight_layer`, `select_entity`, `ping`), broadcasts only to the
  publishing user's bus bucket. Returns `{delivered, subscribers}` so
  the caller knows how many tabs received the command.

- `src/components/layout/AgentBusSubscriber.tsx` — browser EventSource
  client. Re-emits received actions onto `dataBus` (`cameraGoTo`,
  `cameraFaceTowards`, `layerToggled`, `entitySelected`) — every plugin
  is already listening on those channels, so no plugin changes needed.

- `AppShell.tsx` — mounts `AgentBusSubscriber` next to the existing
  `DataBusSubscriber`. Two lines.

- `src/app/api/build/route.ts` — `/api/build` returns build id +
  timestamp + public flag state. Pairs with a one-line console.log
  the subscriber prints on mount so a stale-bundle / config-mismatch
  is visible at a glance instead of looking like a feature regression.

Default off via `NEXT_PUBLIC_WWV_AGENT_BUS_ENABLED=true`. An unintended
deployment doesn't open a remote-control channel for users who didn't
opt in.

What's changed in the Dockerfile:

- Adds ARG declarations for the new vars (`NEXT_PUBLIC_WWV_AGENT_BUS_ENABLED`,
  `NEXT_PUBLIC_WWV_BUILD_ID`, `NEXT_PUBLIC_WWV_BUILD_AT`).
- Stamps the build with millisecond-precision id + ISO timestamp
  (`/app/.build-id`, `/app/.build-at`); both copied into the runner
  stage for `/api/build` to read.
- Writes `/app/.env.production.local` from declared ARGs *before*
  `next build` runs. Docker doesn't reliably promote ARGs into the
  Node child-process environment for the build command, so
  `process.env.NEXT_PUBLIC_*` references that previously inlined
  through Webpack's DefinePlugin sometimes fell back to runtime
  polyfill access (`tV.env.NEXT_PUBLIC_X`) that resolves to `undefined`
  in the browser. Writing the env file is the documented Next.js path
  and behaves the same on every host.

Default-off, no schema changes, no plugin changes, fully backwards-compatible
on operators who don't opt in.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-05-12 00:40:12 -04:00
Antigravity AI 6a3b143614 feat(build): add healthcheck, fix cesuim spz-loader octal error, and remove sentry
- fix(build): Add pnpm override for @spz-loader/core to 0.3.0 to bypass Octal escape sequences error during build

- feat(healthcheck): Add /api/health endpoint and HEALTHCHECK directive to Dockerfile and docker-compose.yml for Coolify monitoring

- refactor(build): Remove Sentry config from next.config.ts to avoid webpack plugin conflicts with wasm compilation
2026-05-10 15:32:45 +12:00
Silvertakana e0ac5041c2 fix: install prisma globally in docker to prevent offline network failures (#53)
* fix(core): install prisma globally in docker to prevent offline network failures [Patch]

* fix(core): allow universal CORS access in marketplace [Patch]

- allow any origin in marketplace bridge to ensure universal connectivity [Patch]
- remove dead origin filter code [Patch]
- bump version to 1.20.5 [Patch]
2026-05-10 11:29:10 +12:00
031a073cf9 fix(plugins): surface NEXT_PUBLIC_WWV_PLUGIN_* vars to plugin context (#60)
`PluginManager.registerPlugin` builds `ctx.env` for each plugin by iterating
`Object.entries(process.env)` and copying entries whose keys start with
`NEXT_PUBLIC_WWV_PLUGIN_`. In the browser bundle this loop comes back
empty even when those vars are set at build time, because Next.js only
inlines `process.env.NEXT_PUBLIC_*` at *static reference sites* — and
`Object.entries(process.env)` isn't a static reference. The result: any
plugin reading `ctx.env.SOMETHING` to override a default URL silently
gets `undefined` and falls back to its hardcoded cloud URL.

Concrete impact: setting `NEXT_PUBLIC_WWV_PLUGIN_DATA_ENGINE_URL` to a
self-hosted data-engine URL has no effect on the marketplace plugins that
read `ctx.env.DATA_ENGINE_URL` (e.g. `wwv-plugin-aviation`) — they keep
calling `https://dataengine.worldwideview.dev/data/...` even when the
operator has explicitly redirected away from it.

Add explicit static references so the values land in `envVars`. Done as
a small allow-list (currently just `DATA_ENGINE_URL`) so adding new keys
is one line.

Also declare `ARG NEXT_PUBLIC_WWV_PLUGIN_DATA_ENGINE_URL` in the
Dockerfile next to the existing public-arg block. Without it, the build
arg passed in via compose isn't visible to Next.js at build time, so
Webpack inlines `undefined` even when the operator sets the env var.

Co-authored-by: Sapphire <sapphire@tiktokcoach>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
2026-05-10 11:02:56 +12:00
dependabot[bot] 82cc79fa45 build(deps): bump node from 22-alpine to 26-alpine (#69)
Bumps node from 22-alpine to 26-alpine.

---
updated-dependencies:
- dependency-name: node
  dependency-version: 26-alpine
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-05-10 10:57:40 +12:00
Antigravity AI 78fb1dc484 fix(core): update legacy migration script and Dockerfile for Prisma 7 [Patch]
- fix migrate-legacy.mjs to use explicit pg adapter and accept db path arg [Patch]

- copy migrate-legacy.mjs to final docker image [Patch]
2026-05-10 00:06:33 +12:00
Antigravity AI 5fb36069ac fix(core): migrate changes and resolve cors issues [Patch]
- fix marketplace CORS by allowing x-marketplace-ping header [Patch]

- update setup page and docker entrypoint for legacy migrations [Patch]
2026-05-09 23:30:18 +12:00
Silvertakana c4207bd6e1 feat(core): migrate to Prisma 7 and unify PostgreSQL architecture (#56)
* feat(cloud): implement Postgres DB adapter, fix static build crashes, and containerize NextAuth/Stripe integrations

* test(marketplace): fix mocks and assertions for multi-tenant Postgres architecture

* feat: rsa jwt license key verification and state integration

* feat: add internal workspace validation route for Edge Functions

* refactor: clean up hub routes and finalize db proxy/adapter for multi-tenant cloud deploy

* feat(cloud): finalize multi-tenant Prisma extensions and workspace routing

* fix(db): correct Prisma 7 better-sqlite3 adapter initialization [Patch]

- update better-sqlite3 adapter instantiation to use configuration object ({ url }) required by Prisma 7 instead of raw Database instance [Patch]
- fix PrismaClientConstructorValidationError by generating client with adapter support [Patch]

* fix(auth): support dynamic origins for local proxies and multi-tenant subdomains [Patch]

- prioritize forwarded headers and request host over hardcoded envOrigin in getRequestOrigin to support subdomain routing [Patch]
- allow ALLOWED_DEV_ORIGIN in marketplace install redirect checks to fix local network development login flows [Patch]

* fix(marketplace): enable dynamic CORS reflection for marketplace API [Patch]

- remove explicit origin array, replacing with origin header reflection to allow marketplace hosted on any domain or local IP [Patch]

- remove global wildcard CORS headers from next.config.ts to harden security against broader app injection [Patch]

* feat(db): create initial postgresql migration

* refactor(db): update remaining files for postgresql

* feat(db): unify database adapter to PostgreSQL-only [Minor]

- replace SQLite adapter with PostgreSQL PrismaPg [Minor]
- remove better-sqlite3 dependencies [Patch]
- finalize docs and implementation plan [Patch]

* fix: resolve prisma client generation and script execution issues with tsx and type module

* feat(db): port tenant isolation logic to new PostgreSQL adapter

* docs: add rule for transparent and narrated agent actions

* BREAKING CHANGE(core): migrate to PostgreSQL and add auto-migration pipeline [Major]

- unified database adapter to exclusively use PostgreSQL [Major]
- implement auto-migration pipeline to pipe legacy SQLite data to Postgres [Major]
- add sqlite to runner stage to support extraction pipeline [Patch]

* feat(core): migrate to Prisma 7 and unify PostgreSQL architecture [Minor]

- removed legacy Prisma SQLite driver and all Better-Sqlite dependencies [Minor]
- updated schema to utilize purely postgresql providers [Patch]
- modified migration scripts to seamlessly convert local sqlite DBs to PostgreSQL containers using keinos/sqlite3 [Minor]
- updated deployment scripts, Coolify pipelines, and Nginx proxy support [Patch]
- injected Prisma Client Extensions for multi-tenant Row Level Security isolation [Minor]
- stabilized PrismaClient initialization utilizing the official adapter-pg runtime pattern [Patch]
- bumped version to 2.1.0

* fix(core): resolve TypeScript compilation errors for CI [Patch]

- fixed NextResponse.json() 3-arg calls to use 2-arg ResponseInit form [Patch]
- replaced invalid 'developer' TrustTier with 'unverified' in parseWwvManifest and load-unpacked route [Patch]
- removed non-existent pluginManager.hotReload() call in DevModeSubscriber, replaced with disable/reload cycle [Patch]
- updated Stripe API version from '2024-04-10' to '2026-04-22.dahlia' to match installed SDK [Patch]
- excluded local-scripts/ from tsconfig to prevent debug scripts from breaking CI [Patch]

* fix(ci): resolve pnpm version conflict in GitHub Actions [Patch]

- removed explicit version: 9 from pnpm/action-setup@v4 — v4 auto-reads packageManager from package.json [Patch]
- updated build job DATABASE_URL from SQLite to PostgreSQL format [Patch]

* fix(docker): add explicit Prisma generator output path for Docker builds [Patch]

- Prisma 7 changed default output location, causing COPY --from=builder to fail
- added output = '../src/generated/prisma' to generator block for consistency

* fix(prisma): update client import path and resolve CI type errors [Patch]

- updated PrismaClient import in db.ts to point to custom generated output path
- resolved implicit 'any' error in marketplace check-updates route
- verified clean local build with tsc --noEmit

* chore(deps): sync Prisma versions to 7.6.0 [Patch]
2026-05-09 22:44:30 +12:00
Silvertakana 138ea6c721 feat: local Docker HTTPS proxy for Firefox marketplace bridge compatibility (#50)
* feat: implement local docker HTTPS proxy for marketplace bridge

Generates self-signed certs automatically in docker-entrypoint and spins up a native Node HTTPS proxy on port 3001 to resolve Firefox Mixed Content blocks when fetching from local containers via the live marketplace.

* fix(core): fix docker build and marketplace origin parsing [Patch]

- fix pnpm run generate script failure in Dockerfile [Patch]
- implement robust origin parsing for marketplace endpoints [Patch]
2026-05-09 11:02:46 +12:00
Antigravity AI 7684d23398 fix(deploy): fix Coolify Next.js env var inlining, CSP, and Analytics 2026-04-06 01:33:20 +12:00
Antigravity AI de60ed3ffe perf(build): optimize Next.js docker build memory limits 2026-04-05 12:21:50 +12:00
silvertakana 682c21296c fix(docker): remove redundant node_modules copy, fix prisma generate env, fix hydrate script typings 2026-04-02 13:46:01 +13:00
silvertakana aec6f20edc chore: optimize dockerfiles for faster deployments via layer caching and BuildKit 2026-04-02 12:31:14 +13:00
silvertakana ded3ae9416 fix(docker): inject pnpm workspaces to build step 2026-04-01 22:55:39 +13:00
silvertakana 50228a43c8 chore: update Dockerfiles to use pnpm for installation 2026-03-29 22:33:00 +13:00
silvertakana afe89f8c0e fix: add VOLUME declaration for /app/data for Coolify/Dockerfile deployments 2026-03-26 17:29:02 +13:00
silvertakana d65600786f fix(docker): future-proof Prisma + Next.js standalone setup
- Add prisma package to serverExternalPackages in next.config.ts
- Replace manual node_modules cherry-picking with full production install
- Copy pre-built node_modules from deps stage and prune dev dependencies
- Ensures all Prisma CLI runtime dependencies are always available
2026-03-26 16:42:03 +13:00
silvertakana d10c68004a feat(docker): add persistent volume for sqlite db to retain installed plugins across restarts 2026-03-26 14:14:10 +13:00
silvertakana b7d76b5e58 fix: run prisma migrations at build time, remove runtime entrypoint 2026-03-19 15:36:59 +13:00
silvertakana 86b7550c38 fix: skip database query on demo edition in setup-status 2026-03-19 15:15:29 +13:00
silvertakana c6b26d20bc fix: add DATABASE_URL env and prisma deps to Docker runner stage 2026-03-19 14:40:52 +13:00
silvertakana 614d3af796 fix: add error handling to setup-status and fix Dockerfile for Prisma 2026-03-19 14:28:12 +13:00
silvertakana bc05d93ce8 fix: add error handling to setup-status and fix Dockerfile for Prisma 2026-03-19 14:21:06 +13:00
silvertakana c0789f831c fix: externalize native modules and add prisma generate to Docker build 2026-03-18 23:11:16 +13:00
silvertakana 7db1980e0f fix: prevent Docker build failure during Next.js build traces
- Remove CopyPlugin from next.config.ts (was copying Cesium assets during
  webpack build, causing Next.js to trace thousands of files and OOM/timeout)
- Add outputFileTracingExcludes for public/cesium/**
- Copy Cesium assets via copy-cesium.mjs after build in Dockerfile instead
2026-03-13 15:35:23 +13:00
silvertakana a3e19cecef deploy: add Dockerfile for standalone Next.js deployment 2026-03-08 22:21:00 +13:00