feat(web): proactive reload affordance after web hot-swap (draft)

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197

[patroza]

Item 4 of the independent-web-deploy work (builds on #293 + ops hot-swap). Proactively tells open clients a new web bundle is being served so they can reload, instead of only reloading passively on a failed chunk import.

What

• contracts: webVersionChanged added to ServerLifecycleStreamEvent (payload = webVersion hash of index.html).
• server: webVersionWatcher polls the served index.html hash every 10s and publishes on change; the current version seeds the lifecycle snapshot so a connecting client learns the version it's running. serverLifecycleEvents snapshot now keeps the latest event of each type.
• client: projects the latest webVersion off the lifecycle stream; WebUpdateBanner compares it to the version the tab booted with and shows an unobtrusive "Reload" affordance. Never auto-reloads — vitePreloadRecovery still handles the genuinely-broken-chunk case.

Tests

• projectServerWebVersion accumulation (ignores non-web lifecycle events).
• isWebUpdateAvailable decision matrix.
• vp check clean; full recursive typecheck clean.

Why draft

The reload affordance is client-visible; per the repo's client-visible-verification rule it needs a test-t3-app pass (launch env, hot-swap dist/client, confirm the banner appears and Reload works) before promoting to ready. Also pending: the no-cache/immutable header behavior is unchanged, so passive reload already works without this — this is the proactive UX layer.

🤖 Generated with Claude Code

[patroza]

@omegent fix ci

[omegent-app]

Fixed in 7c2b11cee.

The CI failure was apps/web/src/AppRoot.test.tsx still asserting 3 top-level children after WebUpdateBanner was added to AppRoot. I updated the test to expect the new fourth child and assert that it is WebUpdateBanner.

Local verification:

• vp test run apps/web/src/AppRoot.test.tsx

GitHub has already picked up the new SHA and reran checks on PR #294; Fork CI / Test is queued on 7c2b11ceee1811c0b7da377faeb3713c09550c7c.

gpt-5.4 · 1m 20s · ↑48k ↓197