Repository navigation
N5: Mobile Activity inherits Chats scope with honest count coverage #2198
Description
Parent
What to build
Make Activity content and its bottom badge use Chats' selected environment while preserving current category paging and count preferences. Demonstrate the supported Computer scope and All aggregation of available sources; clearly distinguish missing Cloud capability instead of borrowing another source's feed or number.
Acceptance criteria
- Activity has no environment selector; it inherits Chats selection. Horizontal paging remains action/replies/unread and does not change the environment.
- Feed and badge use the same inherited scope and existing count preferences; read/action behavior continues through the owning HumanAttention/public API.
- For the supported Computer fixture, an actual pending item and its resolution produce matching feed/badge changes with public API/CLI readback; no content from a different Computer appears.
- All deduplicates by source-qualified identity and exposes partial/stale/unsupported coverage. Unsupported Organization scope shows that state, never an unrelated Computer feed or an apparent authoritative zero.
- Account replacement/logout/removal, pending responses, offline/resume and restart cannot reuse an old scope count or content. Source selection persists according to the shared mobile scope owner.
- Existing count category preferences, keyboard/layout and native category gestures survive. No new channel read/pin authority or Bot wake behavior is introduced.
- Native UAT demonstrates Chats Computer → Activity → category swipe → Chats Organization → Activity unsupported state → All; screenshots and regression evidence distinguish actual counters from capability gaps.
- This slice does not complete Cloud attention parity or simultaneous multi-Computer aggregation. Keep those hub gaps open and coordinate Conversations: synchronize read progress and pins through their source #2181 rather than inventing service events/read state.
Blocked by
Delivery and testing boundary
Planning only; do not implement until the Human authorizes this slice. Milestone v2.0; Open Cloud Groups Project. One issue = one implementation PR. UAT only; no Prod/merge authorization. Use existing source owners/public API and CLI readback for business facts, focused behavioral regressions and exact-head native evidence. Reserve the shared device lane; report iOS/Android/physical/Human and large-text/keyboard/accessibility results separately. Preserve unrelated work. Do not infer native success from source tests.
Execution order
Scheduled after N4 for sequential feedback. Its only technical blocker is N1; N2–N4 are not fabricated dependency edges. No sibling work starts automatically.
Activity