- geocode_location/fly_to/save_favorite/list_favorites/remove_favorite/set_filter/clear_filter/get_plugin_filters now document inputs, output shape, and a usage example
- bump 2.46.1 -> 2.46.2
- Drop trailing export { readSessionCatalog } from catalog/route.ts (Next.js App Router rejects non-route-handler exports -> TS2344 in generated route types)
- Trim now-unused readSessionCatalog import (only existed to support the re-export)
- All consumers already import readSessionCatalog from @/lib/mcpSessionCatalog
- Bump 2.45.0 -> 2.45.1
- collectCatalog gathers getFilterDefinitions() from each loaded plugin (D-05)
- filter-only plugins now publish (early-return guards on tools AND filterDefinitions empty)
- catalog route validates and forwards optional filterDefinitions, identity still from auth only
- gives get_plugin_filters a data source
- searchEntities applies filters on full GeoEntity.properties via matchFilterValue before SearchResult conversion (D-07/D-08)
- limit counts only matching entities; missing property key fails filter
- search_entities MCP tool exposes optional filters inputSchema via filterValueSchema
- SearchOptions type gains optional filters field
- 4 new filters tests GREEN, no regression
- Import and call registerGeocodingTools + registerFavoritesTools in handleMcpRequest registration seam
- SAFE-01 confirmed: isDemo gate (line 144) fires before createMcpServer and all registrars
- Full test suite GREEN (715 tests), tsc clean
- Bump version to 2.38.0
- Add flyTo case to useGlobeCommandBridge dispatchCommand: bbox emits cameraFlyToBbox, point emits cameraGoTo with lon:cmd.lng mapping and 15000m default alt
- Subscribe to cameraFlyToBbox in useCameraActions, flying to Rectangle.fromDegrees
- Bump version to 2.37.0
- Add registerFavoritesTools registrar: save_favorite, list_favorites, remove_favorite
- save_favorite upserts prisma.favorite; pluginName defaults to pluginId (FAV-01)
- list_favorites reports per-entity live/stale via readActiveSessions + getEntityDetails; all stale when no session (FAV-02, D-04/D-05)
- remove_favorite deletes row scoped to ctx userId (FAV-03)
- userId sourced exclusively from ctx, never tool args; direct prisma, no HTTP (SAFE-02)
- Add @/lib/prisma re-export and manual test mock; align RED test session mock shape
- Bump 2.34.0 -> 2.35.0
- checkRateLimit(userId) prunes via zremrangebyscore(key,-inf,now-WINDOW)
- records request via zadd, bounds key with expire(key,5), counts via zcard
- returns { error: rate_limited, retryAfterMs } when count > MAX_REQUESTS=1
- fails open on Redis error (best-effort, advisory limit)
- makes geocodingRateLimit.test.ts GREEN; bump 2.32.0 -> 2.33.0
- Add flyTo member: { type: "flyTo"; lat; lng; alt?; bbox? }
- Add flyTo case to isValidGlobeCommand with lat/lng/alt/bbox validation
- bbox must be 4-element array of finite numbers within valid WGS84 bounds
- Add 8 RED->GREEN test cases in flyTo validator describe block
- Add zremrangebyscore(key, min, max): Promise<number> after zrem
- Add zcard(key): Promise<number> for sorted-set cardinality
- ioredis implements both natively; cast picks them up at runtime
- Auth: add ensureLocalUserPersisted() (idempotent upsert in authorize())
and persistDemoAdminIfNeeded() (upsert in jwt callback) so session userId
always has a DB row before FK-constrained inserts
- api-keys POST: map Prisma P2003 on user_api_keys_userId_fkey to 401
session_user_not_found instead of 500; other FK violations still 500
- api-keys GET/POST: add isDemo gate returning 403 before auth
- Tests: full coverage for all new paths (16 tests, 2 files)
Add the MCP server `instructions` block so a connecting agent learns the
session-discovery workflow up front: read the globe://sessions resource to
list active tabs, then pass an optional sessionId to target one specific
tab (omit to target the most-recently-active tab). Enrich the four globe
command tools' sessionId descriptions and the data-query tool descriptions
(empty result means no match or no live data, not an error). Bump the
advertised MCP server version to 1.2.0.
Harden coordinate validation across every MCP coordinate surface via a new
shared coordinateSchemas module: latitude [-90,90], longitude [-180,180],
altitude > 0, rejecting NaN/Infinity. Applied to pan_globe, focus_entity,
get_entities_in_region, and the /api/v1/entities/region route, with a
defense-in-depth runtime guard in isValidGlobeCommand. Fixes a UAT finding
where pan_globe accepted lat=999.
Quiet the useGlobeCommandBridge SSE onerror handler so it logs only on a
terminal close (readyState CLOSED, e.g. an unauthenticated tab), not on the
designed ~16s stream reconnect.
Addresses tech debt surfaced by the v1.2 milestone audit and the
code/security reviews of the fixes:
- mcpRelay: make enqueueToolInvocation atomic via multi().rpush().expire().set()
and apply the same atomicity to postToolResult's result write (was two
separate non-atomic writes that could leak on partial failure)
- redis: add set() to the RedisMultiChain interface to support the above
- v1 entities (search + region): add dual-auth (NextAuth session primary,
Bearer fallback) matching globe/commands route; add isDemo 403 gate before
auth; guard limit against NaN from non-numeric ?limit input; document that
entity data is global/public so userId gates access but is not a query filter
- useGlobeStateSync: fire one immediate pushState on mount (ran-once ref guard)
to close the session-registration race where resolveActiveSessionId returned
null before the first heartbeat
- useMcpCatalogPublisher: wire getNamespacedTools instead of inline pluginId__name
string building (DRY); catalog payload shape unchanged
- remove dead export pluginToolsList.ts (composePluginToolsList had zero
production callers; McpServer auto-generates tools/list from registered tools)
643/643 tests pass, tsc clean, lint clean.
Replace 1500ms setInterval poll loop in useGlobeCommandBridge with a
persistent EventSource (Server-Sent Events) connection. Commands are
pushed within 200ms of enqueue instead of up to 1500ms.
- New GET /api/globe/commands/stream route: ReadableStream with poll-
with-deadline loop, 15s keepalive, 16s max duration, cancel callback
for client-disconnect cleanup, same dual-auth + isDemo gate order
- useGlobeCommandBridge: replaced setInterval/fetch with EventSource;
dispatchCommand unchanged; envelope shape validation in onmessage
- globeCommandsStreamLimiter: 10 req/60s for the SSE endpoint
- GET /api/globe/commands poll route: added missing isDemo 403 gate
- 654/654 tests pass, 0 regressions
Replaced the window-level mousemove/mouseup/pointermove/pointerup
listeners (gated on an isDragging state flag) with element-level
pointer capture on the resize handle. setPointerCapture routes all
subsequent pointermove/pointerup events to the element regardless of
where the pointer travels, which is required for webkit: without
capture, webkit drops synthetic pointermove events during Playwright
drags and during fast real-user drags that leave the element bounds.
This was a pre-existing failure on main (run 26639956515) reproduced
identically on this branch. The fix is correct production behaviour,
not a test workaround.
Bumps version 2.29.2 -> 2.29.3.
CodeQL flagged two alerts in src/lib/data-query/service.ts: user-controlled
pluginId was interpolated directly into a fetch URL (SSRF, critical) and into
console.error template literals (format string, high). Added validatePluginId()
which enforces an alphanumeric+hyphen+underscore allowlist, uses URL constructor
to build safe paths, and removed user-controlled values from log template strings.
Add MCP "globe command" system tools so an authenticated agent can act on
an open globe: pan, focus an entity, toggle a layer, and scrub the timeline.
Transport is poll-based (no WebSocket, no custom server.ts): tools RPUSH a
validated command to a per-session Redis list (TTL 60s), the browser polls
GET /api/globe/commands on an interval, drains atomically (MULTI lrange+del),
re-validates, and dispatches to the Cesium camera (DataBus) and Zustand store.
This is the durable transport; WebSocket push (19b) can layer on later without
rewriting the type guard, tools, sessionId resolution, or browser dispatch.
Covers CTRL-04 + CTRL-05. 19b (WS push) remains deferred.
- GlobeCommand discriminated union + isValidGlobeCommand guard (never throws;
validates timeWindow against the literal set and currentTime as a real date)
- globeCommandQueue: atomic enqueue (multi.rpush.expire) + drain + session resolve
- registerGlobeCommandTools: 4 MCP tools, userId from auth ctx only, graceful
no-session result, z.enum for timeWindow
- GET /api/globe/commands: dual-auth (session primary, Bearer fallback),
UUID sessionId 400 guard, dedicated globeCommandsLimiter
- useGlobeCommandBridge: 1500ms poll with in-flight guard + unmount cleanup
- route.ts: third per-request registrar call (R-1)
Reviewed by code-reviewer + security-reviewer (no Critical/High; auth provenance,
gate ordering, and tenant isolation verified). Suite 573/0.
- Add model UserApiKey with uuid PK, userId FK (Cascade), tenantId String?,
prefix String @unique, hashedSecret, name, createdAt, lastUsedAt DateTime?
- Add @@map("user_api_keys") following project snake_case convention
- Add apiKeys UserApiKey[] relation to User model
- Bump version 2.24.6 -> 2.25.0 (minor: new feature)
* fix(setup): write .env.local not .env, fix npm->pnpm in completion message
setup.mjs was writing AUTH_SECRET to the git-tracked .env file instead of
.env.local, creating a security risk for users who commit their fork.
Also fixes the completion message which incorrectly instructed users to run
npm run dev instead of pnpm dev (project uses pnpm@9).
* ci: add multi-OS matrix for pnpm setup, fix stale action versions
Adds ubuntu/windows/macos matrix to test-setup job so the install
instructions are verified on all three platforms on every PR. Fixes
actions/checkout, pnpm/action-setup, and actions/setup-node all
pointing at non-existent @v6. Splits into two jobs: test-setup
(3 OS) and test-dev (ubuntu-only, needs Docker).
* fix(ci): use pnpm run setup not pnpm setup
pnpm setup is pnpm's built-in shell config command (writes to .bashrc).
pnpm run setup runs the project script. All three occurrences fixed.
* fix(dev): load .env.local in dev.mjs before spawning workers
Turbopack workers inherit process.env at spawn time, before Next.js
completes its own .env.local loading. If ENCRYPTION_MASTER_KEY is not
already in process.env when concurrently spawns next dev, the
instrumentation.ts startup check sees it as unset and crashes the server.
Fix: loadEnv('.env.local') in dev.mjs after loading .env so all secrets
are present in process.env before any child processes are spawned.
Also fix CI idempotency test: pnpm setup calls pnpm's built-in shell
config command, not the project setup script. Changed to pnpm run setup.
* fix(e2e): guard marketplace webServer and exclude per-app tests from main Playwright config
Root cause: playwright.config.ts unconditionally started the marketplace dev server at
../worldwideview-marketplace. In CI only worldwideview is checked out, so spawn() received
a non-existent cwd which Node.js surfaces as "spawn /bin/sh ENOENT", crashing the entire
test run before any browser launched.
Two targeted fixes:
1. Wrap the marketplace webServer entry in fs.existsSync(MARKETPLACE_DIR) so CI skips it
gracefully. Use playwright.marketplace.config.ts to run cross-app marketplace tests locally.
2. Add testIgnore for web-auth.spec.ts and marketplace-from-instance.spec.ts — both target
sibling repos (worldwideview-web / worldwideview-marketplace) and have their own dedicated
configs (playwright.web.config.ts / playwright.marketplace.config.ts). The main config
should only exercise the worldwideview app itself.
* feat(09-02): add playwright.cross-app.config.ts and .env.test for cross-origin specs
- Add playwright.cross-app.config.ts with dual webServer array (wwv.local:3001 + marketplace.wwv.local:3002)
- testMatch targets both upcoming cross-app spec files; baseURL set to marketplace.wwv.local:3002
- Create worldwideview/.env.test with PLAYWRIGHT_TEST_EMAIL + PLAYWRIGHT_TEST_PASSWORD (gitignored)
- Add explicit .env.test entry to .gitignore (was not covered by existing .env/.env.local patterns)
- Bump version 2.20.2 -> 2.21.0 (feat: minor)
* feat(09-02): add cross-app Playwright specs for redirect handshake and sign-out (REQ-16)
- Add marketplace-redirect-handshake.spec.ts: 2 tests verifying next= param construction and login-then-redirect-back flow
- Add marketplace-sign-out.spec.ts: 1 test verifying avatar dropdown sign-out clears session and returns to marketplace home
- Update playwright.cross-app.config.ts to load .env.test credentials via fs (no dotenv package required)
- All specs target https://marketplace.wwv.local:3002 (never localhost:3002) for correct .wwv.local cookie domain
- 3 tests total listed by playwright --list
* feat: add planning-sync hook script for .planning branch isolation
* fix: guard planning-sync against missing .planning, wrong repo, and silent checkout failures
- Exit early if .planning/.git doesn't exist (avoids false-success on machines without the private repo)
- Exit early if CWD is not a worldwideview repo or worktree (prevents syncing from wwv-data-engine etc.)
- Wrap both checkout calls in exit-code checks so failures emit WARNING messages instead of false success
* feat: add post-checkout hook for .planning auto-sync
* fix: add existence guard to post-checkout hook before calling planning-sync
* docs: add .planning branch convention to worktree-bootstrap skill
* feat(11-01): add LegalFooter component and .legal-footer CSS class
- Create src/components/layout/LegalFooter.tsx as a Server Component
- Export named function LegalFooter with two external anchors
- Both anchors use target="_blank" rel="noopener noreferrer" (T-11-01)
- Links target locked URLs: privacy-policy and cloud-terms-of-service
- Append .legal-footer + a + a:hover rules to globals.css
- position:fixed bottom:0 z-index:10 per UI-SPEC
- Bump version 2.23.2 -> 2.23.3
* feat(11-01): remove Vercel Analytics, mount LegalFooter in root layout
- Remove @vercel/analytics/next import from layout.tsx (D-02)
- Remove {process.env.VERCEL && <Analytics />} JSX (D-02, T-11-02)
- Add import { LegalFooter } from @/components/layout/LegalFooter
- Render <LegalFooter /> as last child of <body> (D-04)
- Remove @vercel/analytics from dependencies in package.json
- Regenerate pnpm-lock.yaml after dependency removal
- AdSense block (lines 27-37) untouched per D-03
- Bump version 2.23.3 -> 2.23.4
* fix(worktree): fix link_planning hook path conversion for Windows
Worktrunk substitutes {{ worktree_path }} as a Unix-style path
(/c/dev/...) which cmd.exe cannot resolve. It also strips $ sigils
from variable names before executing hook commands, making inline
PowerShell variables unusable.
Extract junction logic to .agents/scripts/link-planning.ps1 and
unlink-planning.ps1. The hooks now call powershell -File with
the path as an argument, avoiding both issues entirely.
* docs: add ADR-004 and phase-2 implementation plans
Adds the Supabase session cookies httponly ADR alongside the six
implementation plan documents produced during the auth gate phase.
* feat(auth): implement Phase 2 cloud auth gate (ADR-003 closeout)
- Cloud edition login page redirects to NEXT_PUBLIC_AUTH_HOST_URL;
local/demo editions keep the NextAuth credentials form
- Delete signup pages and Supabase PKCE callback route from worldwideview
(auth host owns them per ADR-003)
- Add Supabase SSR helpers (cookieOptions, server, client) with
httpOnly:true cookies per ADR-004
- Dual-dispatch install-redirect and grant-token: Supabase on cloud,
NextAuth on local/demo; redirect param unified to ?next=
- Add streaming mode to safeFetch for MJPEG camera proxy streams
- Extract LoginForm into its own component
- Update Playwright config to conditionally start marketplace dev server
* fix(types): cast undici ReadableStream body to BodyInit to satisfy DOM types
node:stream/web ReadableStream is structurally incompatible with the DOM
ReadableStream expected by the Response constructor -- the pipeThrough
signature differs on the T | undefined generic bound. Cast to BodyInit
(which is the correct type for the streaming pass-through) to resolve
the TS2345 error in ssrf.ts line 112.
* fix(e2e): exclude cross-app marketplace specs from default Playwright run
marketplace-redirect-handshake.spec.ts and marketplace-sign-out.spec.ts
require a running marketplace.wwv.local:3002 instance (cross-app
environment). They were being picked up by playwright.config.ts in CI
where that host does not exist, causing ERR_NAME_NOT_RESOLVED failures.
Added both files to testIgnore alongside the existing exclusions; they
should be run via playwright.cross-app.config.ts only.
* fix: add pointer event support to bottom panel resize for webkit
Playwright's webkit engine dispatches pointermove/pointerup reliably
during synthetic drags but mousemove sometimes does not fire. Add
pointermove and pointerup listeners alongside the existing mouse
listeners, and add onPointerDown to the drag handle, so the resize
test passes across all three browser engines.
* feat(marketplace): pass from_instance origin when opening marketplace
BrowseLink in PluginsTab now appends ?from_instance=<origin> so the
marketplace can silently capture the instance URL into localStorage,
skipping the manual InstanceConfig modal for users arriving from the app.
* test(e2e): add marketplace instance auto-discovery E2E tests
- playwright.marketplace.config.ts: standalone config that starts only
the marketplace on port 3002, no Docker/Postgres required
- tests/marketplace-from-instance.spec.ts: 4 marketplace-side tests
(capture valid URL, reject javascript: protocol, reject self-origin,
skip when no param) + 1 full-flow test (worldwideview -> marketplace,
auto-skipped when running under marketplace-only config)
- NEXT_PUBLIC_MARKETPLACE_URL env var in BrowseLink lets tests point
to localhost:3002 instead of the production marketplace
- data-testid="browse-plugins-btn" for stable Playwright selector
- playwright.config.ts updated with both webServers for full E2E
Run marketplace tests (no Docker): pnpm exec playwright test --config=playwright.marketplace.config.ts
Run full E2E (Docker required): pnpm test:e2e
* feat: implement Phase 2 install auth gate (ADR-003 closeout)
Closes the three foundational auth gaps that blocked a proper install gate:
2A - SSR session persistence:
- Add @supabase/ssr; create src/lib/supabase/{cookieOptions,server,client}.ts
mirroring the marketplace recipe so both repos issue the same cookie type
- Migrate login/actions.ts from @supabase/supabase-js to createServerClient
(previously the Supabase session was discarded; no cookie was ever set)
- Fix getSafeRedirect to allow trusted subdomain callbacks via
NEXT_PUBLIC_WWV_COOKIE_DOMAIN so marketplace ?callbackUrl= round-trips work
- Add NEXT_PUBLIC_WWV_COOKIE_DOMAIN and NEXT_PUBLIC_AUTH_HOST_URL to .env.example
2B - Signup route at auth host:
- Add /signup page and server action (supabase.auth.signUp with emailRedirectTo)
- Add /auth/callback route to handle Supabase PKCE email verification exchange
- Add "Sign up" link to login page preserving ?callbackUrl=
2C - Install auth gate:
- Swap NextAuth auth() for Supabase getSupabaseUser() in install-redirect route
(local/demo edition still uses NextAuth)
2D - Sweep:
- httpOnly: true added to buildCookieOptions()
- cloud-auth-architecture.md superseded section collapsed to forward-pointer
- ADR-003 status updated to Accepted with implementation notes
* chore: exclude .planning from git (moved to private repo)
* chore(05-01): add Playwright config and E2E specs for worldwideview-web auth UI
- playwright.web.config.ts: targets https://wwv.local:3001 with ignoreHTTPSErrors
- tests/web-auth.spec.ts: 4 describe groups covering reset-password form, /accounts redirect, /auth/verify no-code error, /auth/reset-password/confirm no-hash timeout
- bump version 2.20.0 -> 2.20.1
* fix(gc): narrow mdc-ref detector to eliminate false positives
Pattern now requires a quoted string context (['\"].*\.mdc['\"]) and
only scans .ts/.tsx files, excluding scripts/. Prevents the scanner
from flagging its own source code and rule documentation that explain
the anti-pattern rather than violating it.
Special characters (Š, Č, Ž, Đ, etc.) were rendering as garbled glyphs
in the UI because the display environment lacks font coverage for those
code points. Adds a shared transliterate() utility that decomposes
characters via NFD and strips combining diacritical marks, with a
supplemental map for characters that don't decompose cleanly (Đ, Ø, Ł,
ß, etc.). Applied at both Places API routes (search + details) and the
GeoJSON entity converter so all place/airport name sources are covered.
Fixes: [email protected] report – May 13-14 2026 Discord.
Co-authored-by: Claude <[email protected]>
* fix(camera): fix camera stream not displaying — CSP frame-ancestors and HTTP SSRF block
- next.config.ts: add path-scoped header override for /api/camera/proxy/:path*
setting frame-ancestors 'self' and X-Frame-Options SAMEORIGIN so proxy iframe
responses are not blocked by the global frame-ancestors 'none' policy
- ssrf.ts: extend validateOrigin to accept http:// URLs; the stream proxy is a
server-side bridge that must fetch plain-HTTP camera feeds before re-serving
them over HTTPS to the browser to avoid mixed-content blocks
- ssrf.spec.ts: update validateOrigin tests to match new HTTP-allowed behaviour;
add explicit rejection tests for ftp://, file://, data://, javascript://
- scripts/boot-db.mjs: create .env from .env.example in worktrees when missing
so DATABASE_URL injection block is never silently skipped
* fix(camera): sandbox proxied iframes and unblock external stylesheets
The CSP override for /api/camera/proxy/:path* still inherited the app's
restrictive style-src/script-src, which blocked external stylesheets and
scripts inside proxied iframes (YouTube, third-party players, etc).
Relax proxy CSP to default-src * while keeping frame-ancestors 'self'.
Because the proxy iframe is same-origin with the host app, this widened
CSP would have let upstream HTML reach window.parent.localStorage / DOM.
Add sandbox="allow-scripts allow-popups allow-presentation" (no
allow-same-origin) to proxied iframes so they run in an opaque origin
and cannot touch the host app. Major-platform iframes (YouTube/Twitch/
Vimeo) bypass the proxy and remain unsandboxed since the browser already
isolates them via cross-origin.
- next.config.ts: proxy CSP -> default-src * 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self'
- CameraStream.tsx: add sandbox attribute to proxied (non-major-platform) iframes
* fix(camera): add youtube-nocookie.com to major-platform bypass list
getYouTubeEmbedUrl() converts youtube.com watch URLs to youtube-nocookie.com
embed URLs, but the majorPlatformHosts allowlist in CameraStream.tsx was
missing youtube-nocookie.com. This caused YouTube embeds to be routed
through the iframe proxy + sandbox, which broke the YouTube player (Cache
Storage disabled, RUM analytics blocked, writeEmbed not defined).
youtube-nocookie.com is now treated the same as youtube.com: loaded
cross-origin directly without proxying, relying on the browser's same-origin
policy for isolation.
* fix(camera): fix camera stream not displaying — CSP frame-ancestors and HTTP SSRF block
- next.config.ts: add path-scoped header override for /api/camera/proxy/:path*
setting frame-ancestors 'self' and X-Frame-Options SAMEORIGIN so proxy iframe
responses are not blocked by the global frame-ancestors 'none' policy
- ssrf.ts: extend validateOrigin to accept http:// URLs; the stream proxy is a
server-side bridge that must fetch plain-HTTP camera feeds before re-serving
them over HTTPS to the browser to avoid mixed-content blocks
- ssrf.spec.ts: update validateOrigin tests to match new HTTP-allowed behaviour;
add explicit rejection tests for ftp://, file://, data://, javascript://
- scripts/boot-db.mjs: create .env from .env.example in worktrees when missing
so DATABASE_URL injection block is never silently skipped
* fix(camera): sandbox proxied iframes and unblock external stylesheets
The CSP override for /api/camera/proxy/:path* still inherited the app's
restrictive style-src/script-src, which blocked external stylesheets and
scripts inside proxied iframes (YouTube, third-party players, etc).
Relax proxy CSP to default-src * while keeping frame-ancestors 'self'.
Because the proxy iframe is same-origin with the host app, this widened
CSP would have let upstream HTML reach window.parent.localStorage / DOM.
Add sandbox="allow-scripts allow-popups allow-presentation" (no
allow-same-origin) to proxied iframes so they run in an opaque origin
and cannot touch the host app. Major-platform iframes (YouTube/Twitch/
Vimeo) bypass the proxy and remain unsandboxed since the browser already
isolates them via cross-origin.
- next.config.ts: proxy CSP -> default-src * 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self'
- CameraStream.tsx: add sandbox attribute to proxied (non-major-platform) iframes
* fix(incidents): add mapWebsocketPayload default to BaseIncidentPlugin
Default unwraps three WsClient-visible payload shapes:
- scheduler envelope { source, fetchedAt, items, totalCount } -> items
- GeoJSON FeatureCollection { features: [...] } -> normalised GeoEntity[]
- flat GeoEntity[] -> passthrough (with timestamp normalisation)
Resolves the silent-drop bug that left the earthquakes plugin showing an empty
layer when the scheduler's standard wrapping was used. Subclasses can still
override mapWebsocketPayload for domain-specific shapes (iranwarlive pattern
preserved by 2 override tests).
Test deltas:
- 2 it.fails tests flipped to passing (scheduler-wrap, GeoJSON unwrap).
- 2 'currently drops' companion tests deleted (bug is fixed, companions obsolete).
- 1 structural test updated: 'does NOT have mapWebsocketPayload' -> 'has mapWebsocketPayload defined'.
- Net: 12 tests -> 10 tests, all passing.
* test(ssrf): replace placeholder assertions with real tests for DNS pinning and size limits
The two expect(true).toBe(true) stubs in ssrf.spec.ts are replaced with
assertions that verify actual SSRF guard behavior:
- "enforces maxSize" — mocks undici.fetch to return an 11-byte body with a
10-byte limit; verifies response.text() rejects with "size exceeded"
- "does not follow redirects" — mocks dns.lookup + undici.fetch; verifies
redirect:manual is passed, fetch is called once, and the 301 is returned
without being followed; also asserts dispatcher is set (DNS pinning)
Uses vi.hoisted + vi.mock to patch dns/promises and undici at module level.
360/360 tests pass.
* fix(security): close Phase 3 audit blockers and unregistered flags
- WsClient.ts: guard subscribe() against sending frames while awaitingWelcome=true;
prevents pre-auth subscribe race when a second plugin subscribes mid-handshake
- connect/route.ts + callback/route.ts: set PKCE cookie path="/" to satisfy
RFC 6265bis __Host- prefix requirement (Chromium silently rejects __Host- + path!=/)
- pkce.spec.ts: update assertion to match corrected path="/"
- docs/plans/03-SECURITY.md: security audit report (13 closed, 1 fixed, 3 flags filed)
* fix(incidents): add mapWebsocketPayload default to BaseIncidentPlugin
Default unwraps three WsClient-visible payload shapes:
- scheduler envelope { source, fetchedAt, items, totalCount } -> items
- GeoJSON FeatureCollection { features: [...] } -> normalised GeoEntity[]
- flat GeoEntity[] -> passthrough (with timestamp normalisation)
Resolves the silent-drop bug that left the earthquakes plugin showing an empty
layer when the scheduler's standard wrapping was used. Subclasses can still
override mapWebsocketPayload for domain-specific shapes (iranwarlive pattern
preserved by 2 override tests).
Test deltas:
- 2 it.fails tests flipped to passing (scheduler-wrap, GeoJSON unwrap).
- 2 'currently drops' companion tests deleted (bug is fixed, companions obsolete).
- 1 structural test updated: 'does NOT have mapWebsocketPayload' -> 'has mapWebsocketPayload defined'.
- Net: 12 tests -> 10 tests, all passing.
* test(ssrf): replace placeholder assertions with real tests for DNS pinning and size limits
The two expect(true).toBe(true) stubs in ssrf.spec.ts are replaced with
assertions that verify actual SSRF guard behavior:
- "enforces maxSize" — mocks undici.fetch to return an 11-byte body with a
10-byte limit; verifies response.text() rejects with "size exceeded"
- "does not follow redirects" — mocks dns.lookup + undici.fetch; verifies
redirect:manual is passed, fetch is called once, and the 301 is returned
without being followed; also asserts dispatcher is set (DNS pinning)
Uses vi.hoisted + vi.mock to patch dns/promises and undici at module level.
360/360 tests pass.
* docs: add ADR-003 document and update cloud-auth-architecture superseded notice
* chore: bump version for ADR-001 Workstream C
* fix: remove stray 'r' prefix on import in places/details route
rimport typo on line 1 of src/app/api/places/details/route.ts caused
TS1435 (unknown keyword), ESLint parse error, and a webpack build failure
in Docker CI. Corrected to a valid import statement.
* fix: add id-token write permission and fix invalid inputs in GC workflow
The claude-code-action@v1 uses OIDC for OAuth token auth, which requires
id-token: write in workflow permissions. Without it ACTIONS_ID_TOKEN_REQUEST_URL
is not set and the action fails after 3 retry attempts.
Also moves model and allowed_tools from unsupported top-level inputs into
claude_args where they are valid CLI flags for claude-code-action@v1.
* fix(gc): show agent output and explicit dry-run issue posting
- Add show_full_output: true so Claude responses appear in CI logs
- Replace vague dry-run instruction with explicit gh issue create/comment
commands so output has a concrete destination (tracking issue)
- Bake DRY_RUN value into prompt at workflow-expansion time to eliminate
ambiguity about env var reading
* docs: mark cloud-auth-architecture.md as superseded by ADR-003
* fix(docker): guard community seeder cd and add ENCRYPTION_MASTER_KEY default
- Wrap `cd $SEEDERS_DIR/community` in an existence check so the
data-engine container no longer crashes when local-seeders/community/
is an empty or uncloned nested git repo. The container was entering
Docker's exponential-backoff restart loop (2s→60s) on every boot.
- Add ENCRYPTION_MASTER_KEY to the wwv environment block with a
local-dev fallback, matching the AUTH_SECRET pattern. Without it the
Next.js instrumentation hook throws at startup and the app never
serves a request.
* fix(docker): auto-baseline P3005 when schema exists without migration history
Wraps prisma migrate deploy in the container entrypoint to detect P3005
(schema populated by pnpm dev / prisma db push before the Docker stack was
started). When detected, runs prisma migrate diff to confirm zero schema
drift, then marks each migration as applied via migrate resolve --applied
and retries deploy. Exits with a clear error if drift is found.
Also documents the auto-baseline behavior in database-migrations.md and
fixes duplicate section numbering in that file.