perf(client-runtime): halve server config bootstrap traffic

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}

[Adamulek123]

What changed

Client sessions requested the full server config twice during startup. This PR uses one subscribeServerConfig stream for bootstrap and later updates, while keeping each incremental event type.

The web client still opts into environment theme events. Mobile does not request that payload. Theme updates and deletion now work for live delivery, late replay, slow subscriber recovery, and reconnect snapshots. Replay keeps "not received yet" different from "the environment published an empty set."

Session and cached state now use one config projection reducer. Shared subscriptions require an exact structural payload match, so a current or future option cannot be dropped. If the owned stream fails, dies, or ends, the existing connection supervisor recovers the session instead of serving stale config.

This keeps the original work from @Adamulek123 and updates it for the environment theme contract on main.

Validation

• 109 focused tests passed
• Client runtime, web, and mobile TypeScript checks passed
• Focused lint and formatting passed
• Server WebSocket and config payload compatibility tests passed

Updated with GPT-5.6 Sol through the Codex harness.

---

Note

Medium Risk
Changes core connection bootstrap, shared config streaming, and session teardown semantics; regressions could affect reconnects, theme UI, or duplicate-subscription edge cases, though coverage is extensive.

Overview
RpcSession now bootstraps from a single owned subscribeServerConfig stream instead of a separate serverGetConfig call. The first snapshot on that stream drives initialConfig, while a PubSub plus replay state fan out live updates and replay snapshots (and the latest environmentThemesUpdated when opted in) to multiple subscribers without opening duplicate websocket subscriptions.

RpcSession exposes subscribeServerConfig(input) on the session object; environment RPC subscribe for that method routes through the session-managed stream when the input matches the session’s owned subscription payload. Connection.layerWithOptions({ environmentThemes }) threads the flag through the connection stack—the web client enables environmentThemes: true; the default layer keeps {}. Mismatched inputs still open a one-off protocol subscription (e.g. themes vs non-themes).

Server config projection moves to serverConfigProjection.ts (shared by session buffering and durable environment state). Session closed also completes when the owned config stream ends or fails, surfacing ConnectionAttemptError (including permission blocks) so the supervisor reconnects rather than serving stale config.

Tests and mocks across client-runtime and web were updated for the new RpcSession shape and the new streaming/replay/theme behaviors.

^{Reviewed by Cursor Bugbot for commit 9114a74. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Halve server config bootstrap traffic by sharing subscription in RpcSession

• Session now opens one subscribeServerConfig stream at bootstrap and replays the latest snapshot and updates to all subscribers, instead of each caller opening its own protocol subscription.
• New layerWithOptions(options) in layer.ts and session.ts lets callers pass RpcSessionOptions (e.g. environmentThemes: true); default export preserves previous behavior.
• Config projection logic extracted to serverConfigProjection.ts, handling snapshot/section updates and authoritative environmentThemes events.
• Session readiness now gates on receiving the initial config snapshot; subscribeDynamic in client.ts routes WS_METHODS.subscribeServerConfig to the session-managed stream.
• Risk: RpcSession.closed error type broadened from ConnectionTransientError to ConnectionAttemptError, and the session now closes when the config stream ends or fails. mapSessionRpcError maps additional subscription error sources. Callers that expect the session to survive config stream termination should verify error handling in session.ts.

^{Macroscope summarized 9114a74.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: efe67bf0-412a-481c-b0ed-6345b2657b90

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes client connection bootstrap, config-stream multiplexing, replay/buffering, and session recovery semantics across existing runtime paths. The web client also changes its default connection behavior to request environment-theme events, so the scope and lifecycle impact warrant human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78fadda. Configure here.}