Documented release
v54.1.0
world/profile continuity patch
Release date 2026-04-15
Outcome
Outcome
v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
Changes
What changed
a valid session cookie now produces an authenticated loading snapshot
a valid session cookie now produces an authenticated loading snapshot
Technical and authority boundary
a valid session cookie now produces an authenticated loading snapshot
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- a valid session cookie now produces an authenticated loading snapshot
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
signed-in users no longer see public-visitor copy or auth CTA…
signed-in users no longer see public-visitor copy or auth CTA chrome while the real world bootstrap is still in flight
Technical and authority boundary
signed-in users no longer see public-visitor copy or auth CTA chrome while the real world bootstrap is still in flight
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- signed-in users no longer see public-visitor copy or auth CTA chrome while the real world bootstrap is still in flight
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
the route can still reconcile into the richer /api/world/me payload…
the route can still reconcile into the richer /api/world/me payload as soon as it lands 2. The Loading Shell Stays On The Real World Snapshot Path This patch does not reintroduce a fake shell:
Technical and authority boundary
the route can still reconcile into the richer /api/world/me payload as soon as it lands 2. The Loading Shell Stays On The Real World Snapshot Path This patch does not reintroduce a fake shell:
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- the route can still reconcile into the richer /api/world/me payload as soon as it lands 2. The Loading Shell Stays On The Real World Snapshot Path This patch does not reintroduce a fake shell:
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
/world/loading.tsx still renders WorldRouteSnapshot
/world/loading.tsx still renders WorldRouteSnapshot
Technical and authority boundary
/world/loading.tsx still renders WorldRouteSnapshot
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- /world/loading.tsx still renders WorldRouteSnapshot
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
deterministic bootstrap data remains the fallback graph for first paint
deterministic bootstrap data remains the fallback graph for first paint
Technical and authority boundary
deterministic bootstrap data remains the fallback graph for first paint
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- deterministic bootstrap data remains the fallback graph for first paint
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
the loading shell and the real page continue sharing the…
the loading shell and the real page continue sharing the same world-shell contract instead of splitting into unrelated UIs 3. Market-To-Profile Navigation Behaves Like The Rest Of The App The market route should not have its own browser-reload exception:
Technical and authority boundary
the loading shell and the real page continue sharing the same world-shell contract instead of splitting into unrelated UIs 3. Market-To-Profile Navigation Behaves Like The Rest Of The App The market route should not have its own browser-reload exception:
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- the loading shell and the real page continue sharing the same world-shell contract instead of splitting into unrelated UIs 3. Market-To-Profile Navigation Behaves Like The Rest Of The App The market route should not have its own browser-reload exception:
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
bottom-bar profile navigation now uses the same client-side route behavior…
bottom-bar profile navigation now uses the same client-side route behavior as wallet and the other signed-in tabs
Technical and authority boundary
bottom-bar profile navigation now uses the same client-side route behavior as wallet and the other signed-in tabs
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- bottom-bar profile navigation now uses the same client-side route behavior as wallet and the other signed-in tabs
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
market no longer hard-switches the browser to /profile with window.location.assign
market no longer hard-switches the browser to /profile with window.location.assign
Technical and authority boundary
market no longer hard-switches the browser to /profile with window.location.assign
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- market no longer hard-switches the browser to /profile with window.location.assign
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
profile continuity from the bottom bar now matches the rest…
profile continuity from the bottom bar now matches the rest of the app’s signed-in navigation model 4. Release Surfaces Stay Canonical This release also performs the version move cleanly:
Technical and authority boundary
profile continuity from the bottom bar now matches the rest of the app’s signed-in navigation model 4. Release Surfaces Stay Canonical This release also performs the version move cleanly:
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- profile continuity from the bottom bar now matches the rest of the app’s signed-in navigation model 4. Release Surfaces Stay Canonical This release also performs the version move cleanly:
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
package metadata, service worker defaults, public badges, offline verifier surfaces…
package metadata, service worker defaults, public badges, offline verifier surfaces, and release docs all move together to v54.1.0
Technical and authority boundary
package metadata, service worker defaults, public badges, offline verifier surfaces, and release docs all move together to v54.1.0
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- package metadata, service worker defaults, public badges, offline verifier surfaces, and release docs all move together to v54.1.0
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
the release-lock gate remains the source of truth for that surface inventory
the release-lock gate remains the source of truth for that surface inventory
Technical and authority boundary
the release-lock gate remains the source of truth for that surface inventory
- Why
- v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
- Capability enabled
- the release-lock gate remains the source of truth for that surface inventory
- Compatibility
- The v54.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v54.1.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
v54.1.0 is the world/profile continuity patch release. It keeps the broader v54.0.0 operating-system baseline intact, then closes two route-continuity gaps: a signed-in user could briefly see the public visitor shell while /world was loading, and the market bottom-bar profile action could still force a browser-level page load instead of using the same client-side navigation path as the rest of the signed-in app.
Available outcomes
Capabilities now available
a valid session cookie now produces an authenticated loading snapshot
a valid session cookie now produces an authenticated loading snapshot
signed-in users no longer see public-visitor copy or auth CTA…
signed-in users no longer see public-visitor copy or auth CTA chrome while the real world bootstrap is still in flight
the route can still reconcile into the richer /api/world/me payload…
the route can still reconcile into the richer /api/world/me payload as soon as it lands 2. The Loading Shell Stays On The Real World Snapshot Path This patch does not reintroduce a fake shell:
/world/loading.tsx still renders WorldRouteSnapshot
/world/loading.tsx still renders WorldRouteSnapshot
deterministic bootstrap data remains the fallback graph for first paint
deterministic bootstrap data remains the fallback graph for first paint
the loading shell and the real page continue sharing the…
the loading shell and the real page continue sharing the same world-shell contract instead of splitting into unrelated UIs 3. Market-To-Profile Navigation Behaves Like The Rest Of The App The market route should not have its own browser-reload exception:
bottom-bar profile navigation now uses the same client-side route behavior…
bottom-bar profile navigation now uses the same client-side route behavior as wallet and the other signed-in tabs
market no longer hard-switches the browser to /profile with window.location.assign
market no longer hard-switches the browser to /profile with window.location.assign
profile continuity from the bottom bar now matches the rest…
profile continuity from the bottom bar now matches the rest of the app’s signed-in navigation model 4. Release Surfaces Stay Canonical This release also performs the version move cleanly:
package metadata, service worker defaults, public badges, offline verifier surfaces…
package metadata, service worker defaults, public badges, offline verifier surfaces, and release docs all move together to v54.1.0
the release-lock gate remains the source of truth for that surface inventory
the release-lock gate remains the source of truth for that surface inventory
Primitive boundary
Primitives affected
- identity
- settlement
- provenance
- verification
- public-witness
- local-truth
- continuity
- market
- note
Compatibility
Compatibility
Archive compatibility evidence boundary
No dedicated compatibility record is bound to this projection.
Treat compatibility as unknown; version or date proximity is not evidence.
Migration
Migration
Required: unknown
No explicit migration source is bound; no migration is inferred from dates.
Qualification
Conformance
No immutable conformance evidence is assigned in this projection.
Control boundary
Governance
- Verification
- Unknown
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Publication, deployment, production smoke, and attestation remain independent evidence dimensions unless exact sources establish them.
Registry boundary
Registry
No registry is bound where the canonical release family does not carry one.
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- identity · settlement · provenance · verification · public-witness · local-truth · continuity · market · note
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Absent
- Package publication
- Unknown
- Deployment
- Unknown
- Production smoke
- Unknown
- Signed attestation
- Unknown
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 c046121aac3b77be590f68dde9c4f746070e042dbc427079a2e7b3fc1258e23a. Source-family inventory: complete.
SHA-256 66c08a3677b458849fe912097e55b1bdef0b308a5d843a95b872b32b1ea73d3eSHA-256 f00930902ab198eec17bb62e2fafae8eedb52d271c37217efd9a5cc45899872eSHA-256 bbc673274826f62a6aa23d4aedb6f1da5231a20e8fda9ea57056a25e65a08b78