Two tracker/tree mismatches at the seam, one closing and one opening.
1. The transaction cluster is delivered and still open in three repos
83b74e8 — "feat: add withConnectionTransaction for sibling storages on one handle. (#842)" — landed 2026-09-01 and was released in 0.4.6 (npm 2026-09-01T23:09:31Z).
$ find packages providers -name '*ConnectionTransaction*' -not -path '*/node_modules/*' | grep -v dist
packages/storage/src/tabular/withConnectionTransaction.ts
packages/storage/src/tabular/NativeConnectionTransaction.server.ts
packages/storage/src/tabular/NativeConnectionTransaction.browser.ts
packages/storage/src/tabular/defineNativeConnectionTransaction.ts
packages/storage/src/tabular/__tests__/withConnectionTransaction.test.ts
packages/storage/src/tabular/__tests__/runNativeConnectionTransaction.test.ts
packages/test/src/contract/tabular-storage/assertions/withConnectionTransaction.ts
$ grep -rn withConnectionTransaction packages/storage/src | wc -l
63
That file — packages/storage/src/tabular/withConnectionTransaction.ts — is the exact path #708's own plan named, and this review recorded it as "still does not exist" for four consecutive cycles. It exists, it has a contract assertion in packages/test, and sroussey/embarc-data already uses it in 6 places (grep -rn withConnectionTransaction src → 6, adopted at 2912f5d "Adopt @workglow/* 0.4.7, which carries the connection-transaction fix", 09-02T19:44Z — 1 h 0 min after 0.4.7 hit npm). Two further correctness follow-ups shipped on top in 0.4.9 (19a458c, 80eefe5, 4386d22, 42e395e).
Still open, all with updated_at == 2026-08-06:
| Issue |
Repo |
State |
| #708 |
libs |
open, untouched since 2026-08-06T23:48Z — the thing it asks for is published |
| #707 |
libs (umbrella) |
open, untouched since 2026-08-06T22:57Z, has_children: false |
| #247 |
workglow-dev/sec |
open — and its subject (EntityObserver, the observation tier) no longer exists in sec; raised as workglow-dev/sec#348 |
| #136 |
workglow-dev/sec |
open, stale duplicate of #247 |
| #34 |
sroussey/embarc-data |
open — this is the one surviving leg, and it is the repo that has the primitive |
Ask: close #708 as completed naming 83b74e8 / 0.4.6; re-scope #707 to whatever of the umbrella (KV, queue, text-index surfaces, best-effort backends) is genuinely outstanding, or close it; and comment on sroussey/embarc-data#34 that the dependency is released and adopted, so it is now plain downstream work. The sec legs are handled in workglow-dev/sec#348.
This is worth doing precisely because the work was good. As it stands the tracker says four weeks of inaction on a cluster whose upstream shipped, whose downstream adopted it in an hour, and whose middle repo no longer has the code.
2. registerWebStatusReadCleanup shipped with no consumer
6eb09f8 — "feat(cli): add registerWebStatusReadCleanup for managing widget cleanup after status reads" — landed between 0.4.7 and 0.4.8 and is published.
$ grep -rn registerWebStatusReadCleanup sec/src embarc-data/src builder/packages/*/src
(nothing)
Zero downstream call sites. The other six web-console seams are the opposite story and worth stating for contrast — they went 51 → 90 call sites this window (sec 18, embarc-data 72), which is the healthiest adoption number in this review series. registerCommandSchemaProvider remains at 0 in both consumers for a third cycle.
Not a defect. Flagging it as cycle 1 of the watch this review ran on the other six, which took seven days to go from 0 to 51 — so the bar is set by your own precedent.
References
Found during the 2026-09-07 cross-repo review. Snapshot: workglow-dev/prd → analysis/grades/2026-09-07/cross-repo-integration.md.
Two tracker/tree mismatches at the seam, one closing and one opening.
1. The transaction cluster is delivered and still open in three repos
83b74e8— "feat: add withConnectionTransaction for sibling storages on one handle. (#842)" — landed 2026-09-01 and was released in 0.4.6 (npm 2026-09-01T23:09:31Z).That file —
packages/storage/src/tabular/withConnectionTransaction.ts— is the exact path #708's own plan named, and this review recorded it as "still does not exist" for four consecutive cycles. It exists, it has a contract assertion inpackages/test, andsroussey/embarc-dataalready uses it in 6 places (grep -rn withConnectionTransaction src→ 6, adopted at2912f5d"Adopt @workglow/* 0.4.7, which carries the connection-transaction fix", 09-02T19:44Z — 1 h 0 min after 0.4.7 hit npm). Two further correctness follow-ups shipped on top in 0.4.9 (19a458c,80eefe5,4386d22,42e395e).Still open, all with
updated_at == 2026-08-06:has_children: falseEntityObserver, the observation tier) no longer exists in sec; raised as workglow-dev/sec#348Ask: close #708 as completed naming
83b74e8/0.4.6; re-scope #707 to whatever of the umbrella (KV, queue, text-index surfaces, best-effort backends) is genuinely outstanding, or close it; and comment on sroussey/embarc-data#34 that the dependency is released and adopted, so it is now plain downstream work. The sec legs are handled in workglow-dev/sec#348.This is worth doing precisely because the work was good. As it stands the tracker says four weeks of inaction on a cluster whose upstream shipped, whose downstream adopted it in an hour, and whose middle repo no longer has the code.
2.
registerWebStatusReadCleanupshipped with no consumer6eb09f8— "feat(cli): add registerWebStatusReadCleanup for managing widget cleanup after status reads" — landed between 0.4.7 and 0.4.8 and is published.Zero downstream call sites. The other six web-console seams are the opposite story and worth stating for contrast — they went 51 → 90 call sites this window (sec 18, embarc-data 72), which is the healthiest adoption number in this review series.
registerCommandSchemaProviderremains at 0 in both consumers for a third cycle.Not a defect. Flagging it as cycle 1 of the watch this review ran on the other six, which took seven days to go from 0 to 51 — so the bar is set by your own precedent.
References
83b74e8(Add withConnectionTransaction for sibling storages on one handle. #842),19a458c,80eefe5,4386d22,42e395e;packages/storage/src/tabular/withConnectionTransaction.ts6eb09f8;examples/cli/src/web/@workglow/storage0.4.6 (2026-09-01T23:09:31Z), 0.4.9 (2026-09-05T19:34Z)Found during the 2026-09-07 cross-repo review. Snapshot:
workglow-dev/prd→analysis/grades/2026-09-07/cross-repo-integration.md.