Skip to content

feat([issue-5500]): ship Eidoverse World Design V2 - #5508

Open
atomantic wants to merge 20 commits into
mainfrom
next/issue-5500
Open

feat([issue-5500]): ship Eidoverse World Design V2#5508
atomantic wants to merge 20 commits into
mainfrom
next/issue-5500

Conversation

@atomantic

Copy link
Copy Markdown
Owner

Summary

  • replace the generic dark projection with an illuminated dawn world organized into eight legible PortOS districts and a central Nexus
  • project bounded, privacy-safe aggregate PortOS signals through deterministic layered reconciliation with checkpointed rollback
  • ship a versioned asset recipe and install-local resolution lock, never bundled model bytes, so every PortOS install can benefit while Eidoverse owns fetching and caching
  • migrate V1 worlds safely through the normal update path while preserving valid user customization and surfacing unsupported legacy values
  • add an immersive world UI, spatial legend, management drawer, asset controls, update status, and actionable remediation

Verification

  • server: 36,311 passed; 23 skipped
  • client: 10,473 passed
  • focused Eidoverse/migration/storage suite: 65 passed
  • client lint: 2,377 files, zero warnings
  • production client build, syntax checks, and git diff --check passed

Closes #5500

Make PortOS installations project a legible, illuminated world with semantic districts, privacy-safe live signals, and staged reconciliation.

Ship only a versioned asset recipe and deterministic local lock so Eidoverse owns model downloads and caches. Add upgrade-safe migration, rollback, management UI, documentation, and complete runtime coverage.
Keep install-local asset locks materialized during projection, retire automatic V1 ownership, skip fresh-install boot projection, and scope polling cleanup to its own generation.
Reapply PortOS components after asset-driven respawns and keep existing unsaved world-design edits through refresh and projection actions.
…rrides

Carry forward only customized V1 terrain leaves, migrate stale V1 submissions, and make semantic district assets authoritative and resettable.
Merge scoped resets without losing unrelated edits, expose removable legacy asset overrides, validate source aggregation states, and make shipped appearance defaults form-valid.
Report incompatible legacy asset paths without activating them and retain source-adapter priority before bounded signal selection.
Pace verbs across stages, prioritize recent activity, honor feature disablement at boot, and persist all writable V2 recipe fields.
Recognize the source adapters canonical attention status so warning aggregates retain their visual and motion cues.
Project persisted district overrides, protect manual light ids, normalize folded model defaults, and parity-test client reset maps.
…ting

Give authored districts finite semantic defaults so projection converges, and preserve the last valid appearance values while numeric fields are temporarily cleared during editing.
Use theme-aware Eidoverse HUD surfaces, keep migration 323 from wedging later migrations on damaged optional state, reconcile authored district resets from the effective recipe, and preserve valid source caps during transient blank edits.
Honor feature affordance controls, compare nested recipe contracts canonically so reordered keys do not pin installs to old defaults, and reserve the hard live-entity budget for stale-held signals before projecting fresh data.
Retire unsanitized V1 projection entities without charging the V2 budget, share one per-connection verb pacer across ownership and projection operations, and name the mobile refresh action for assistive technology.
Keep routine pending and unread aggregates in the steady visual channel, and surface draft dirtiness so projection and asset refresh actions require saving the visible world configuration first.
Prove online boot reconciliation upgrades a V1 world, distinguish retryable runtime startup failures from protocol incompatibility, and poll persisted projection checkpoints through a lightweight endpoint instead of repeating PM2 and filesystem discovery.
Make retired-owner demotion best-effort so unreachable prior worlds cannot permanently block projection, retain a privacy-safe partial-cleanup report, and make full reset clear ownership recovery state. Give staged reconciliation progress an accessible name and cover both recovery paths.
Distribute saturated live-signal budgets fairly and report omissions, clamp oversized V1 caps, tolerate renamed and size-less library candidates, retry retired-owner cleanup with bounded recovery, mark interrupted projections on boot, and keep HTTP preflight on the configured Eidoverse runtime origin.
Allocate stale and current source buckets together so unavailable data cannot evict the rest of the living world, use theme-aware HUD ink on every overlay, and give each district reset action a unique accessible name.
@atomantic atomantic changed the title Ship Eidoverse World Design V2 feat([issue-5500]): ship Eidoverse World Design V2 Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ship PortOS World Design V2 as the upgrade-safe default for every Eidoverse install

1 participant