Repository navigation
[ATT-04] Aggregate attention across connected environments #6
Description
ID: ATT-04 (F-004). Priority: P0. Blocked by: #5. Backlog: #1.
Scope and reuse
Aggregate current attention in packages/client-runtime, reusing upstream
environment connection ownership and ScopedThreadRef. Do not open competing
connections or merge environments because they host the same repository.
Acceptance criteria
- Key items by environment plus attention ID and threads by scoped thread ID.
Identical local IDs on two environments never collide. - One bootstrap/cursor/cache per environment. A not-yet-complete snapshot stays
explicitly loading/partial; the combined badge is not presented as complete. - After synchronization, aggregate by blocking/error, warning, time and stable
tie-breakers. Keep unique actionable-thread count separate from item count:
two approvals in one thread mean one badge thread and two actionable items. - Frontend connection loss marks retained rows stale; it creates no canonical
failure. Reconnect atomically replaces/updates only that environment. - Direct state takes precedence over relay hints. Out-of-order/lower revisions
cannot resurrect a resolved item. Do not merge a hint lacking matching scoped
identity into an unrelated direct item. - Removing an environment or losing authorization evicts its inaccessible cache.
One unavailable environment does not discard healthy environments. - Tests cover collisions, partial bootstraps, stale caches, reordering, counts,
filtering, removal and direct/relay disagreement without full thread loads.
Coverage and non-goals
Shared state for web/desktop/mobile; provider-independent canonical events.
All existing connection modes; no coordinator or replacement connection
registry. No UI, synchronized seen state, OS notifications or polling.
Activity
jdbencardinop commentedon Sep 29, 2026
ATT-04 completed locally
Implemented on
phase2/attention-aggregation:ddb58554bd50457be2a54345a413f3524244e834.13fb9f08c3c50621fd8d6cedef604690859180e5.c87189e978856b8fd6043f42e296d2cf312cb6cc.Behavior and approved decisions
The shared client-runtime workspace observes the existing environment registry.
It owns one attention subscription on each enabled environment's existing
supervisor, never a competing connection or a full-thread hydration.
Web/desktop and mobile export one lazy shared state instance for later UI use.
Items are scoped by environment/attention ID; summaries, navigation references
and unique-thread counts reuse ScopedThreadRef. Canonical repository grouping
does not combine environment authority. Approval/input/failure share the
blocking-error tier, followed by disconnect warnings; sorting is oldest-first
with stable environment/thread/item tie-breakers. Scoped environment/project/
thread, kind and priority filters use the same item versus thread-count rules.
Only completed fences publish. Each environment retains its last complete
snapshot as explicitly stale during disconnection or refresh, while healthy
environments remain usable. Item/thread totals expose separate live/stale
counts and remain incomplete until every selected enabled environment is live.
Transport loss creates no canonical failure item.
Disable/removal/target replacement cancels and evicts only the affected cache.
Authorization loss clears inaccessible data and stops retrying. Unsupported
capability, loading, syncing, stale and protocol errors stay explicit.
Old-session frames and delayed configuration cannot overwrite replacement
state. Complete same-session caches may resume; replacement RPC sessions use
a fresh bootstrap because delivery tokens bind server authentication.
Recoverable stream resets/unavailability/completion reuse the existing
3/4/8/16-second capped retry timings on the same socket. Transport failure waits
for the supervisor. Authorization, identity/protocol and oversized-message
faults stop until connection/session renewal. No polling or socket retry loop
was introduced.
Existing relay rows lack canonical attention IDs/revisions. A separate
validated advisory selector never creates items or changes counts and
suppresses hints once a complete direct cache exists, including empty/stale
caches. Unknown/unscoped hints are rejected. This does not add relay fetching
or modify upstream mobile Live Activities.
Evidence and boundaries
and RPC helper files. The new aggregation file contains 15 focused cases.
7b5f4af3501d89b42b840f875917c09db4f786cebaseline, not just this increment.tunnel transports keep existing ownership. Desktop shares the web export.
branch push or PR. The earlier packaged qualification still refers to its
frozen product SHA, not this new implementation slice.
#7 is now ready for the web/desktop inbox; #15 is unblocked but remains queued.
Implemented with GPT-6 Astra through GitHub Copilot CLI; no delegated inference.