lgi://changelog
Changelog
Current v4.0.5.1
v4.0Atlas of Worlds
v4.0 lays the groundwork for a collaborative wormhole mapper while keeping its delivery records and measurement baseline trustworthy from the first shipped slice.
v4.0.5.1
15 Aug 2026
Changed
- The feedback form now asks for a category (bug, feature request, UX, or other) and opens a GitHub Issue on the project repo instead of posting to Discord, with the category in the issue title for triage.
- Deferred work is tracked as Backlog GitHub Issues; the old Markdown backlog file was removed after triage.
- The current-system dock and scanner follow a tracked character in space. When nobody is covered they fall back to the chain root, and selecting the root while the dock is elsewhere still opens the usual system card.
- Kept machine-checked session, audit, changelog, and pull-request forms in the repo, moved workflow steps into Cursor skills, and stopped the lifecycle resolver from hashing procedure text.
- Archived the living scratchpad. Planned-session gotchas now live in as-built Successor notes, ordinary-work gotchas in nested agent guides, and mid-session Ordered work progress in the handoff prompt.
- Floored a transitive development-tooling identifier library to a patched 3.x release, recorded the August 10-13 platform announcements, and parked four announced major upgrades on a Backlog GitHub Issue instead of bumping them here.
- Convex location sync no longer wakes Neon on every tick; it holds a short-lived EVE access-token lease.
- The website JWT is minted once per session.
- Empty complete Atlas scanner views stay blank instead of showing a no-rows placeholder.
- Atlas connection lines only catch the pointer when Edit or Delete can run.
- Atlas compass layout now ships a tighter chain: closer rings, closer nodes, packed sibling fans, and a fixed wedge so adding a system does not reshuffle its neighbors.
- Atlas no longer draws k-space neighbour rings around mapped systems. The halo machinery stays in place and can be turned back on later.
- Systems that are not the map home now leave one scanned wormhole as the way back, so an unidentified dump does not grow an extra stub.
- Typing a K162 no longer attaches it as the inbound automatically.
- Leads to can pick the known origin system when Atlas already has that connection.
- Atlas system nodes are about a quarter larger, and wormhole lines now meet the disc instead of stopping at the transparent widget frame so they can run under the system name and future rim icons.
- Atlas compass layout gives mapped systems a little more ring spacing and separation so the larger nodes do not sit as tight.
- Clicking a system now opens its info card above the scanner and other map windows so the summary is not buried.
- The info-card leader meets the system disc at a 45-degree angle instead of running straight into the center.
- Atlas node class chips shrink to stay on one line, so labels like C1–C3 and Pochven no longer wrap inside the disc.
- Scanned wormhole stubs now show the Leads-to class on the node as soon as it is filled in, without waiting for a jump.
- Location sync is scheduled directly by the engine. While the map is watched, a thrown failure re-arms with a five-second hop instead of waiting for the thirty-second scan.
- Fallow now fails when a symbol is exported but only used in its own file. Those bindings stay local instead of public.
- The Fallow verify gate now fails on unused code and duplication anywhere in the repository, not only on findings a branch introduced.
- Jump authoring and signature elimination share one Convex HTTP door for outbound service posts.
Fixed
- The ux-check workspace guide now names the live end-to-end testing policy.
- Creating a map can track an in-space alt when the session character is offline, and uses that location as the starting system.
- A watched jump no longer drops the character off the map when the previous location sample is a few seconds older than the old continuity window.
- A linked wormhole now appears on both scanners. Opening the far-side row keeps the editor leader on that signature.
- Stopped the Atlas audit log chip from pulsing while undoable events remain.
- Scoped the "which signature did you jump through?" prompt to the tracked character that jumped, so other editors on the map no longer see it.
- Restored expired unresolved wormholes can be deleted again from the Signature Editor.
- Owner-hash character transfers now tear down the prior owner's live location tracking.
- Location sync drops a held EVE access-token lease after ESI 401 or 403, so the next run re-vends instead of replaying a dead token.
- Shared pages no longer flash a different first paint than the server HTML while the account session is still loading.
Removed
- Removed the human data-source index and architecture-boundaries prose. The generated architecture map remains the mechanical boundary picture.
- Retired the in-repo agent-policy-audit workflow. Policy repair is not a Cursor skill; run the existing policy checkers instead.
- The Convex Workpool component is no longer part of the live engine.
- An unused pointer-anchored popover that no screen hosted.
- The accepted-duplication baseline file. New clones are no longer waived by a ledger.
v4.0.4.4
12 Aug 2026
Added
- Atlas now opens to a catalogue of your maps when none is selected, grouped into your maps, corporation maps, and maps shared with you, with create and trash in the page header.
- Create a map from one dialog: name it, optionally share it with corporations or characters, wait through a short creating pause, and land on the empty map's set-home prompt.
- Switch maps from the current map name at the top of the canvas. Admins can manage access from a gear on each row.
- Share a map with characters and corporations as read-only, write, or admin. Revoking access removes a live viewer without a reload.
- Deleted maps move to trash for thirty days and can be restored. Only the map's creator can send one to permanent cleanup; a daily sweep then removes the chain and tombstones the record.
Changed
- Map access roles are now viewer, editor, and admin. Existing owner claims still authorize as admin until they are resynced.
- Atlas uses the same site frame as the rest of the tools on the landing; opening a map covers that chrome with the full canvas. Atlas stays off the public header until the development wall drops.
- Close-out production proof now waits for the GitHub production deployment instead of a hand-rolled poll, and Playwright uses the host browser cache.
v4.0.4.3.3
11 Aug 2026
Added
- Named combat and harvestable scanner rows now open the sites card in the same scanner-anchored panel the Signature Editor uses — fully expanded, with the bracket and leader on the row, Escape and outside-click to dismiss, and available to map viewers without edit rights.
- Harvestable scanner rows show a live Est. ISK figure that flashes when the market price confirms; combat rows keep the static blue-loot total.
- The standalone sites detail page uses the same always-expanded card in a narrower reading column, with related sites kept at full width.
Changed
- The Signature Editor and site viewer share one panel shell; on short viewports the panel height stays above the scanner dock and scrolls inside instead of running off-screen.
- Linking a stub into a resolved wormhole now keeps any human-entered reliable-lifetime fields that the destination row had not already recorded.
Fixed
- Observation logging for accept, override, deduction, and jump crossings is proven end-to-end at the four provenance tiers, with far-side untyped and K162 values still refused and no map or pilot identity on the rows.
v4.0.4.3.2
10 Aug 2026
Added
- Wormhole systems now show their guaranteed statics as ghost stubs on the map, and a quiet eliminator fills in only what the evidence uniquely forces — never overwriting a pilot's own identification.
- Every wormhole identification is logged with how it was learned, including machine-assumed deductions, so later ranking can trust the source.
- One Signature Editor beside the scanner is the single place to edit a wormhole: type, in-game mass and reliable-lifetime wording, size, leads-to, and delete. Ambiguous jump answers now live in the scanner overlay instead of a floating card.
Changed
- System and ghost labels use one shared identity readout: the name or signature sits above the disc, and the colored class or security sits inside. Acting-user toasts name the exact signature that was identified.
- On narrow viewports the Signature Editor stacks above the scanner dock so it stays fully usable.
Fixed
- Link deductions refuse to delete a stub whose type changed after the evidence was read, and they carry any human-entered mass, size, or lifetime onto the resolved connection before the stub goes away.
- Identification logging still runs when statics are unavailable; only the eliminator's deductions stay off.
v4.0.4.3.1
9 Aug 2026
Added
- Scanner paste on the Atlas map: copy probe-scanner results in the EVE client and paste anywhere on the map — no field focus needed. Signatures and anomalies land in a new bottom-left scanner window with grouped sections (Unknown, Wormholes, Combat, Harvestables, Hacking), a signal-strength fill behind each row, and a live age column. The paste applies to the system your tracked online character is currently in.
- Scanned wormhole signatures appear on the canvas as ghosted stub nodes; jumping through one converts the stub into the real destination system with no duplicate, and the jump confirmation prompt now carries signature IDs.
- A right-click editor on wormhole rows hosts the connection fields — type, life stage, mass, and leads-to — with the origin system's known statics sorted first in the type picker. Typing a wormhole code shows its destination class on the row and starts the remaining-lifetime ceiling from first sighting.
- Wormholes past their maximum-lifetime ceiling are collapsed automatically by a background sweep a safe grace period after the ceiling passes; the ceiling always overestimates remaining life, so a live hole is never removed, and a branch holding a tracked pilot is always retained.
- Every signature removal is undoable for 24 hours: bulk removals show an undo toast, silent expiries and confident removals write an audit-log entry with an inline Restore, and re-pasting a removed signature revives it in place within its own lifetime.
- A repo-managed Cursor Cloud agent development environment that provisions a local PostgreSQL 16 cluster, dev-only secrets, migrations, and EVE static data without Docker.
Changed
- Re-pasting a scan updates rows in place: unchanged rows write nothing, better information enriches, and a contradicted row is refused and counted rather than silently absorbed. Rows missing from a re-paste surface one frosted Dismiss/Remove prompt above the scanner instead of auto-deleting — a filtered or partial paste never deletes anything on its own.
- The map's audit log and feedback affordances moved to compact bottom-right chips with a subtle pulse while an undo is available, and the audit log now expands leftward inside the viewport; dev-only dials moved with them.
- The current-system dock and System Info card gained a Security Status readout in CCP's security colors with the system's class beside it, plus a scanner summary; the dock's duplicated system name line was removed.
- Page navigation is faster: every route now shares an instantly prefetched shell, so headers, page titles, and content skeletons paint immediately while account data streams in.
- The changelog and dev-log browsers keep their document rail and heading in place while switching documents, and unknown document links render the not-found page marked no-index instead of a bare error status.
- Consolidated the Atlas fog, halo, pilot presence, and sync micro-test suites into fewer longer behavioral workflow tests.
Fixed
- The dev log's server-side cache no longer exceeds the shared remote cache's size limit in production.
- Production deployments build again after the instant-navigation pass: the social-sharing preview image is now served as a prebuilt static asset instead of tripping the deploy's render-mode check.
- The bundled historical wormhole site seed now applies cleanly on a fresh database instead of failing inside its guard block.
v4.0.4.2.3
7 Aug 2026
Added
- Authored k-space exits now open into a deterministic gate halo: nearby systems draw around the known chain while the next ring remains hidden under fog, giving pilots useful context without authoring systems they have not visited.
- A world-anchored smoky fog layer now follows the mapped chain, reveals known nodes and connections, hides provisional systems, and recedes continuously when a jump turns a halo system into authored map truth.
- Tracked pilots now appear on their system frames with honest In space, Docked, AFK, or Stale status; the current-system dock and selected-system summary share the same friendlies readout, and off-map pilots point outward along the last visible gate link.
- Atlas location tracking now survives alt-tabbing into the game: with the map tab open behind the EVE client, jumps keep landing on the map and new connections keep drawing, while closing the tab still winds tracking down within a few minutes.
- An AFK check guards the always-on tracking: after an hour with the map continuously out of sight a prompt asks whether you are still mapping, and tracking pauses a few minutes later unless you continue. The prompt waits for your return, and dismissing it resumes tracking instantly.
Changed
- System nodes now use an invisible widget frame with the name above a centered disc, connection lines meeting the frame boundary, and anchored cards following the same frame through pan, zoom, drag, and layout motion.
- While every tracked pilot is logged out of EVE, the tracker drops to a once-a-minute login check instead of the five-second location loop and speeds back up on the next login automatically.
- Tracked-location sync now also reads the in-game online flag, so characters linked under an older consent may need a reconnect before tracking resumes.
- Upgraded the site framework to Next.js 16.3.
- Raised patched floors for development-tooling libraries flagged by security advisories (brace-expansion, fast-uri, js-yaml), clearing every open advisory.
- Consolidated recently added map and settings test suites into fewer, longer workflow tests.
Fixed
- Outbound pilot arrows now stay on the visible side of fog, dim when every claimant is stale, and reuse the same shortest-path calculation across the map.
- Invisible fogged systems and empty frame margins no longer intercept pointer input, drag, hover, or selection.
Removed
- The green online dot on character portraits. It was the last thing keeping live sync running on every page; with it gone, only the Atlas map talks to the live backend, and in-game presence now lives inside the map tracker itself.
- Retired wormhole vocabulary constant self-checks; mass-threshold and destination-hint behavior remains covered by behavioral tests.
v4.0.4.2.2
6 Aug 2026
Added
- The Atlas map now writes itself: when a tracked scout jumps through a wormhole, every viewer's map gains the destination system and connection automatically, the crossed hole's remaining-mass estimate drops by the observed ship, and an unambiguous origin signature is linked with zero clicks.
- A non-blocking prompt lets pilots confirm or correct an automatic signature link, and the connection card gains a leads-to field for unidentified holes plus a mass-regeneration row shown only for regenerating holes.
- Privacy-safe wormhole observations: verified jumps, confirmations, and manually typed holes record an anonymous system-and-hole-type observation with no map, pilot, or far-side identity, and corrections repair the recorded row instead of stacking contradictions.
- Map settings for auto layout, camera follow, and click focus are autosaved preferences, adjustable from the portrait menu on the map and from the settings page.
- Log-driven Playwright smoke journeys with a test-only Better Auth seed, and Playwright production proof for close-out behind an origin-scoped Vercel protection bypass.
Changed
- The current-system readout is now a persistent, click-through overlay in the map's top left; map menus moved to the top right, and the layout dials became a development-only panel.
- Connection cards keep to one side of their anchor while the camera pans instead of flipping across it, and sever notifications dismiss sooner.
- Merged the end-of-session design review and the adversarial implementation review into one Diff-mode review gate, retiring the separate pre-PR design-review procedure so close-out launches its reviewers once.
- Retargeted repository mapping to Codegraph CLI relationship commands only (callers, callees, impact, query), demoting Codegraph MCP explore so ordinary discovery stays on Explore, semantic search, and grep.
- Separated UX-check into its own lifecycle Ordered-work step when a session's UX gate is Yes, so close-out consumes the recorded operator review instead of re-running the sweep or pause.
- Absorbed open update-watch service and EVE announcements into the acknowledged baseline and advanced cleared discovery windows, while leaving development-tooling advisories deferred inside the seven-day install quarantine and leaving the google-auth-library major-11 bump for an explicit operator decision.
- Shortened agent workflows, schemas, and Convex guidance into imperative living docs, collapsed adversarial review to one procedure, and clarified research-subagent evidence intensity so docs and repo-map packets stay usable.
- Testing principles now carry the high-signal Vitest deletion bar without a separate Keep-Tests-Tight workflow.
- UX check sweeps keep assertion and console evidence with failure-only screenshots; root not-found responses declare noindex.
- Adopted a high-signal Vitest bar that prefers fewer, longer workflow tests and recorded it as the shared cleanup standard for authors and automation.
- Consolidated fragmented micro-tests across eleven Vitest suites into fewer, longer workflow tests under the shared high-signal cleanup bar.
- Gave the mapper boundary probe an explicit generous time budget so slower CI runners no longer fail it against the strict repo-wide default.
Removed
- The map window's floating drag-and-resize mode and its saved window position; map windows are now docked, anchored to what they describe, or passive overlays.
- The Keep-Tests-Tight workflow document after its bar moved into testing principles.
- Trimmed low-signal and duplicate test coverage that did not uniquely falsify user-visible or security-salient behavior, plus orphaned production helpers that only those tests used.
v4.0.4.1
4 Aug 2026
Added
- A blank Atlas map now opens with a single centered prompt: type your home system's name and it becomes the root of the chain. No tutorial, no empty-state art.
- Chains grow from the map itself: right-click a system to add a connection, pick the wormhole type from a type-ahead, and the discovered system fans out live for everyone watching the map. Adds always grow from an existing system, so a floating system can never be created.
- Picking a wormhole type fills the connection card from the codex on its own: mass budget, per-jump limit, size, and lifetime appear without typing, and the ship-size control locks whenever the type already decides it. Unidentified holes keep the manual size control.
- Reporting a connection's observed life stage narrows a bounded remaining-life window stored as absolute timestamps: every watching client renders the same countdown range, later reports narrow it, a contradictory report resets it, and a computed honest ceiling built from the type's lifetime and when the hole was first seen rides alongside.
- Mass estimates are presented as honest ranges: the type's catalog budget with per-hole variance, clamped tighter when an observed shake state proves mass has been consumed.
- Severing a connection runs a computed collapse decision: a truly dead, empty branch offers one-click removal, a branch holding k-space exits or a loop home stays on the map marked severed, and nothing is ever destroyed silently. Every removal offers an immediate Undo toast.
- The map keeps an event log: newest-first sever and restore entries with an editor-gated Restore action inline, so a removal can still be walked back within its one-day undo window after the toast is gone.
- Expired remnants — collapsed connections past their retention window and dangling events — are cleaned up by a scheduled purge every fifteen minutes.
- Every map mutation requires the editor role — a viewer's writes are rejected by the server — while editors see their own change instantly and everyone else receives it reactively.
Changed
- The map chrome was polished under operator review: dying connections pulse red (a steady dim red under reduced motion), follower cards stay inside the viewport with green leader lines, chrome surfaces share one frosted look, docked site cards center correctly, and the canvas dots and library attribution were tidied.
- Absorbed the 2026-08-03 update-watch digest's informational Vercel AI Gateway announcement into the acknowledged baseline.
Fixed
- The map's data client now logs through a plain console logger so server prerendering no longer trips over the vendor logger's random identifier generation.
- Raised the PostCSS floor to the patched release that clears the incomplete sourceMappingURL advisory.
v4.0.3.3
3 Aug 2026
Added
- The Atlas map now has its window system: a persistent current-system dock on the left edge, a freely movable and resizable pop-out of that dock, and a summary card that sticks to any other system you select and rides pan, zoom, and node drag with it.
- Typing and scrolling inside any window leave the map's pan and zoom alone, and Escape closes only the summary card — never the current-system dock.
- Floating dock position and size are remembered on this device across reloads, and re-anchoring keeps the remembered rectangle for the next pop-out.
Changed
- The Atlas character portrait sits immediately beside the Atlas menu, map controls live in the top-right corner, and the current-system dock defaults to the left rail so those controls stay reachable while the dock is open.
- Floating windows drag from the whole title bar, with the close and pop-out controls still clickable on their own.
v4.0.3.2
2 Aug 2026
Added
- The Atlas map now moves like water. A system arriving on the map surfaces in place — starting slightly small and dim, swelling through a soft overshoot, and settling sharp — the same way whether it arrives on first load or live while you watch.
- When the layout engine shifts systems to make room, they glide to their new places along a spring curve with their connection lines tracking them every frame of the way; nothing teleports and no line tears loose from its system.
- A departing system plays a brief exit, and its connections leave with it — either fading alongside the removed system or shrinking back toward the chain, a selectable flavor. A wormhole collapse — a connection dying and taking its unreachable system with it — can play a heavier farewell than a bare system removal, and that weight is selectable too.
- Hovering a system makes it glow and breathe gently. That is the map's only cursor response: at rest the canvas runs no animation and does no rendering work at all.
- The camera always glides now — the initial framing and follow moves ease over a moment instead of snapping — and a new click-focus switch centers the view on any system you click, keeping your current zoom.
- Motion dials join the tuning panel: three tempo tiers (quick feedback, births and glides, camera moves), overshoot amount, edge flavor, and collapse weight.
- The map honors a reduced-motion system preference: position changes become instant placement, births and exits become gentle fades, and camera moves complete immediately.
Changed
- Dragging stays raw: a node you are holding follows the pointer one-to-one with every animation suppressed on it, and node rendering was hardened so a large chain stays smooth under drag.
- Chain reveals and collapses are now written as single atomic events, matching how mapping really works: a jump records the discovered system together with the connection that found it, and a collapse removes the severed connection together with the system it had discovered. Nodes are born directly on the tree and leave with their connection — never orphaned off to the side — and the development replay tool exercises both shapes.
v4.0.3.1
2 Aug 2026
Added
- The Atlas map now lays out the chain automatically as a compass tree: home sits at the center, every jump lands one ring further out, and branches claim compass directions in the order they are found. Every pilot watching a map sees the identical picture, even across different browsers.
- Systems draw as circled class markers with the system name beneath, and connections draw as straight lines meeting each circle at its edge. Shortcut connections that close a loop draw dashed so the chain structure stays readable, and duplicate links never draw as structure twice.
- A map lock keeps the layout in charge: unlock to drag nodes around freely on your own screen, then re-lock to snap everything back to its computed place. Hand arrangements are never visible to anyone else.
- A tuning panel exposes the layout dials — ring spacing, separation, sibling fan, wedge posture, and direction order — and changing one re-draws the chain live on that screen only. The shipped defaults are the values tuned and signed off against live replayed chains.
- A camera-follow toggle brings new arrivals into frame when enabled. The view frames the chain once when a map opens and otherwise never moves on its own.
- A developer replay tool feeds realistic generated chains into a local map at watching pace, with a loop mode that repeatedly grows and tears down the chain to exercise arrivals and departures.
Changed
- Chain layout is computed by a deterministic compass-sector engine selected over ELK radial after a measured bake-off, and the computation runs in a background worker loaded only on the map route, keeping the page responsive and other pages free of layout code.
- The layout engine computes its own trigonometry instead of using the browser's, making node positions identical on every JavaScript engine by construction.
- The provisional placement grid is gone; the layout engine is now the only thing that has ever placed a node on the live map.
- The map library's default corner attribution stays visible for now; a styled credit that can replace it is planned for a future footer pass once Pro eligibility or an equivalent credit home is settled.
v4.0.2.3
1 Aug 2026
Added
- The administrator-walled Atlas map now draws a live shared chain: systems and connections placed on a map appear for everyone watching that map, and leave when removed, with no refresh control anywhere.
- Map nodes are labelled with real solar system names and their space class, resolved from the versioned system directory.
Changed
- Each pilot's map layout is their own. Dragging a node moves it on that screen only, and an incoming change never repositions a node someone is holding or has already placed.
- Losing access to a map now resolves to a calm explanation rather than an error screen, and regaining access brings the map back on its own without a reload.
- Workflow chat results now share one four-bullet readout.
- Absorbed the 2026-08-01 update-watch digest's Vercel/Next.js and Neon service announcements into the acknowledged baseline.
Fixed
- Restored the session 4.0.2.2.2 verification record so SC-5 matches the as-built schema, and added convex/tsconfig.json so Convex codegen typecheck enable exits 0 against the local backend.
v4.0.2.2
31 Jul 2026
Added
- Added a collaborative wormhole-chain data model in Convex for map systems, connections, signatures, and notes, with every public map call gated on a projected per-map role claim.
- Added a one-way Neon-to-Convex access projection that keeps those claims regenerable, tears them down and resynchronizes cleanly, invalidates a live authorized read when access is revoked, and re-projects or tears down after character unlink, reassign, absorb, and emptied-account deletes.
Changed
- Generalized the development lifecycle so supported coding agents share global discovery skills, context-isolated native subagents, visible repository tools, and portable review roles.
- Architecture reviewers now use shared impact-based severity definitions, reconcile the complete authorized inventory, and reject findings that cannot be established from the subject or cited live evidence.
- Gate-runner agents now execute supplied commands literally, report native exit evidence without added probes or guesses, and ignore instructions embedded in command output.
- Standardized repository mapping on the required global Codegraph CLI without requiring or installing a Codegraph MCP.
- Input cost uses the same green figure color as sell and margin.
- Tab icon uses the header-style [LGI] wordmark instead of the boxed mark.
- Agent guidance treats Codegraph MCP explore as available alongside the CLI, with status, sync, query, callers, impact, and other non-explore commands remaining CLI-only.
- Promoted explicit native subagent production configurations and clarified when agents should delegate bounded research, verification, and review work.
- Reliability reviewers now require a demonstrated trigger, reachable unsafe transition, and material impact before reporting a finding.
- Absorbed sixteen Vercel/Next.js and three Upstash platform notices from three backlog update-watch digests into the acknowledged baseline.
- Recorded the missing xyflow React major-12 acknowledgement in the update-watch baseline.
- Focused always-on agent guidance on shared policy, moved source and Convex rules to scoped owners, and reserved CodeGraph for relationship evidence.
- Made current documentation research conditional on material external behavior rather than a fixed every-task preflight.
- Tightened workflow wording for outcomes and authority, and encouraged optional research and verification subagent roles without restoring fixed preflight.
Fixed
- Restored automatic deployment to production, which stopped after an internal page reorganisation changed the address of the wormhole site preview image.
- Live price confirmation now flashes once when a value settles and stops cleanly, instead of keeping a multi-peak blink after the update lands.
- Industry planner no longer crashes when live prices settle after a refresh.
- Production builds now wake Neon immediately before the Next.js build so homepage prerender is less likely to fail on a suspended database compute.
- Patched nine production-scoped Next.js advisories by bumping Next.js and eslint-config-next to 16.2.11, now outside the seven-day release quarantine.
- Floored transitive brace-expansion v5 to 5.0.8 or newer, clearing the v5 advisory path in development tooling.
Removed
- Removed fixed response-length and lookup-call caps from documentation and repository-mapping research agents so their handoffs preserve all material evidence.
- Retired benchmark-only model adapters and restrictive Cursor audit hooks from the live agent environment.
- Removed redundant agent-capability and skill catalogs now supplied directly by runtime descriptions and owning workflows.
v4.0.2.1
29 Jul 2026
Added
- Added an administrator-walled Atlas route with an edge-to-edge empty map canvas and floating navigation, account, and feedback controls while the mapper is under development.
- Added a mapper host-layer boundary that can compose feature widgets without allowing features or authentication chrome to depend upward on the map.
Changed
- Separated existing site routes from the full-screen map shell while preserving current URLs and site chrome.
- Made pull-request gating require every participating reviewer to clear its findings while allowing either participating reviewer to provide the required current-head result.
Fixed
- Stopped local tooling validation from depending on optional machine-global Codex guidance; installed shared tooling is now validated directly.
v4.0.1.6
28 Jul 2026
Added
- Added a weekly, versioned copy of per-system wormhole statics that keeps serving from the last operator-approved snapshot when the community feed is unavailable.
- Added an admin review screen that shows feed differences and independent lineage disagreements before a snapshot can be promoted.
v4.0.1.3
28 Jul 2026
Added
- Added versioned client reference data for solar-system details, stargate connections, and wormhole type attributes that the upcoming mapper can load once per session.
- Added the first embeddable feature widget, letting a host render the existing wormhole site card from a site identifier inside its own window.
Changed
- Browser tabs and bookmarks now show the LGI mark instead of the placeholder icon the site shipped with.
- Changelog entries no longer end with a note about which earlier version a change first shipped in.
v4.0.1.1
27 Jul 2026
Added
- Added durable map identity and delegated character or corporation access in Neon, with one authorization gate that resolves owner, editor, viewer, and denied capabilities.
- Character-transfer and account-deletion teardown now removes direct map grants and user-owned maps before identity can move to another person.
Changed
- Expanded adversarial reviews with up to three focused Composer passes and compact, deduplicated findings.
v4.0.0.1
27 Jul 2026
Added
- The code-health baseline now captures each master version's starting reference, measures its expanded lifecycle surfaces, and preserves session as-built records in version archives.
Changed
- Absorbed three days of no-impact Vercel/Next.js and Neon platform notices into the update-watch baseline so the daily digest stops re-reporting them.
- Compacted the 3.10 scratchpad for the 4.0 boundary and redirected historical margin-audit and document evidence to their archive homes.
Fixed
- Cleared the eligible Better Auth, PostCSS, fast-uri, Babel, esbuild, and Vite advisories, and refreshed the mature React, Convex, Tailwind, Vitest, lint, and supporting package lines.
- Pinned the repository and CI to a pnpm release that actually enforces the seven-day install quarantine.
- Bounded documentation path checks to complete filenames and Markdown link targets so valid prose cannot hide or manufacture a dead-path claim.