[ATT-05] Add the web and desktop attention inbox #7

Activity

1. jdbencardinop

   added

   fork-backlogMaintainer backlog for the multi-machine forkMaintainer backlog for the multi-machine fork

   status:blockedRelease or dependency gate remains; no implementation yetRelease or dependency gate remains; no implementation yet

   priority:P0Stable reconciliation and attention coreStable reconciliation and attention core

   on Sep 14, 2026
2. jdbencardinop

   added a parent issue on Sep 14, 2026

   • Fork workspace backlog: stable reconciliation, attention, TWS and tags #1
3. jdbencardinop

   marked this as blocked on Sep 14, 2026

   • [ATT-04] Aggregate attention across connected environments #6
4. jdbencardinop

   marked this as blocking on Sep 14, 2026

   • [ATT-06] Extend upstream notifications with canonical attention policy #8
5. jdbencardinop

   added

   status:readyScope ready and all implementation gates satisfiedScope ready and all implementation gates satisfied

   status:in-progressActively implementing the scoped issueActively implementing the scoped issue

   and removed

   status:blockedRelease or dependency gate remains; no implementation yetRelease or dependency gate remains; no implementation yet

   status:readyScope ready and all implementation gates satisfiedScope ready and all implementation gates satisfied

   on Sep 29, 2026
6. jdbencardinop commented on Sep 29, 2026

   

   jdbencardinop

   on Sep 29, 2026

   Author

   More actions

   ATT-05 completed locally

   Implemented on phase2/attention-inbox:

   • UI source: baf051d9690fc377e641cbbe82cfbd25b12049b6.
   • Documentation anchor repair: 76ef157f4a18b4288665b98f4e43c4c9afa175df.
   • Complete inbox-root attestation: 33470ce56485904bc4c42b1ee73f17e7fcd05de4.
   • Clean verified tip: d7d039d261191ecb035f2f0582d6dc4cdffe4422.

   Delivered behavior

   The /attention inbox and persistent sidebar badge use the existing single
   client-runtime attention workspace. The badge counts actionable threads; rows
   represent individual requests/failures. Live/stale counts, incomplete totals,
   unsupported/unauthorized environments and empty/filter-empty states are explicit.

   Environment, scoped project, kind and severity filters preserve canonical
   ordering. LegendList virtualizes rows, with scoped stable keys, keyboard
   Up/Down/Home/End/Enter navigation and mounted active-descendant accessibility.
   Only visible rows read shell titles; thread detail is loaded only after opening
   the owning scoped route. Respond through the existing thread approval/input UI;
   there is no synthetic resolve command or duplicate response interface.

   Current and legacy sidebars, Settings and the command palette reach the same
   route action. attention.open is configurable through existing Keybindings
   Settings with no default shortcut. Desktop reuses web UI; mobile UI remains #15.

   Seen/unseen is device-local revision-based emphasis, capped at 2000 recent
   marks. Opening marks seen, Mark unseen reverses it, and a changed revision is
   unseen again. Counts do not change. Cleanup requires a complete live snapshot
   or previously observed environment removal; an initially empty catalog during
   startup is not evidence that persisted marks should be erased.

   Evidence

   • 192 tests passed across six focused inbox/palette/keybinding/notification-badge
     files, including a 5000-item scope/count case and cold-catalog seen regression.
   • Web, contracts, server and mobile typechecks passed; new-code lint passed.
     Pre-existing effect warnings in large integration components were unchanged.
   • Production web build passed; existing chunk-size/plugin timing warnings remain.
   • Approved integrated browser pass against a disposable server:
     2402 items / 1200 threads, 14 rendered attention rows, exactly one
     attention.subscribe, no thread-detail subscription before navigation.
   • Real keyboard endpoints, scoped navigation, all four filters, reversible seen
     marks, persistence after reload, current/legacy/Settings/palette/custom-binding
     entry points, offline stale badge, reconnect and narrow layout passed.
   • The pass found and fixed a real reload race in seen cleanup. Earlier fixture
     setup needed required model metadata; this was fixture-only. An unrelated
     provider-update toast was dismissed, not treated as an inbox defect.
   • Six maintained tpatch roots verify; the DAG has zero violations.

   The approved separate attention-inbox root retains its complete 16-path intent
   from c87189e978856b8fd6043f42e296d2cf312cb6cc, with Foundation as hard parent
   and session search as soft ordering. Parent canonical patches were not rewritten:
   new documentation was moved outside their replay anchors so both still verify.

   No OS notification coordination, relay mutation, native provider turn, live
   database access, branch push or PR. The disposable browser and dev stack were
   stopped; screenshots and sanitized traffic evidence remain session-local.
   The prior packaged qualification still applies only to its frozen product SHA.

   #8 is ready for canonical attention notification policy using the existing
   notification coordinator; #9, #11 and #15 remain unblocked but queued.

   Implemented with GPT-6 Astra through GitHub Copilot CLI; no delegated inference.
7. jdbencardinop

   removed

   status:in-progressActively implementing the scoped issueActively implementing the scoped issue

   on Sep 29, 2026
8. jdbencardinop

   closed this as completedon Sep 29, 2026