[jfet97]

Why

A live query can refresh for the first repository write and then miss later changes, leaving dashboards stale even though the server publishes the correct dependencies. Synchronous refresh callbacks can replace their registration while dispatch is still iterating the subscriber Map.

What

Keeps each write or source reset limited to the subscriptions present when dispatch began. Replacement registrations remain available for the next event.

How

Snapshots registered queries before invoking refresh callbacks, preserving repository-read intersection and existing delay behavior. Observed-query coverage exercises successive writes, a source reset, and another write with both awaited and soft invalidation. Includes a patch changeset for @effect-app/vue.

Remarks

This is the dependency for Scanner SA-529. Scanner must adopt the published release before its dashboard's final browser validation. Both pull requests remain unmerged.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[pkg-pr-new]

Open in StackBlitz

@effect-app/cli

npm i https://pkg.pr.new/@effect-app/cli@930

effect-app

npm i https://pkg.pr.new/effect-app@930

@effect-app/eslint-codegen-model

npm i https://pkg.pr.new/@effect-app/eslint-codegen-model@930

@effect-app/eslint-shared-config

npm i https://pkg.pr.new/@effect-app/eslint-shared-config@930

@effect-app/infra

npm i https://pkg.pr.new/@effect-app/infra@930

@effect-app/vue

npm i https://pkg.pr.new/@effect-app/vue@930

@effect-app/vue-components

npm i https://pkg.pr.new/@effect-app/vue-components@930

commit: fcc1faa