View<->chat integration: views display, chat controls

[lalalune]

This workstream makes the MVP doctrine real: views are information surfaces the
agent (or the user via chat) drives; chat is the primary control surface. Every
view control must have a semantic chat action twin, so the view is a renderer of
state and the same mutation is reachable by typing, and — soon — by voice.

Doctrine / decisions adopted

• Semantic actions over synthetic DOM. The generic agent-click/agent-fill
  bridge (useAgentElement → view:interact) stays ONLY for third-party plugin
  view bundles. Every builtin view mutation (settings, LifeOps, knowledge,
  memories, files) must map to a registered agent action the planner can
  discover and a test can drive headless.
• View = pure renderer of state. Keep on-screen controls (elderly and
  children tap) but route each through the same use case as its action twin —
  one write path, no divergent client-side mutation (Clean Architecture Replace OpenAI Whisper with Whisper Turbo #2/Replace GPT-3.5 with Node Llama3 #3).
• Read-only diagnostics stay read-only. Logs, Runtime, Database,
  Trajectories, Transcripts get navigation + read providers, never manufactured
  write actions.
• Builds on landed views-redesign doctrine (feat(ui): enforce uniform top bar — icon-only ViewBackButton, ViewHeader everywhere, group-based secondary section-nav #13586 / refactor(ui): Settings — fold desktop rail into top-bar section nav, uniform header, strip CTAs, typed view actions #13590 / refactor(plugin-wallet-ui): Wallet — uniform header with centered title, calm empty states, view-scoped trade actions #13592 /
  feat(workflows): seed default workflow on first run, remove create-workflow CTA, uniform header #13597): uniform top bar, no side panels, no suggestion chips,
  agent-proactive-on-view-switch (reportUserViewSwitch → VIEW_SWITCHED
  already fires), view-scoped actions. This workstream extends "view-scoped
  actions" from navigation into mutation.
• Voice constraint drives today's design. Under bidirectional voice the agent
  manipulates views as shared screen context and narrates what it changed — with
  no DOM to click. So every view mutation is written as an action now, because a
  click handler is throwaway the day voice ships. The gap list is exactly the set
  of controls that would go mute under voice.

Research doc

Full inventory (view × interaction × chat-path), gap analysis, settings-section
write-coverage table, and the voice-first section:
packages/docs/ongoing-development/research/06-views-chat-integration.md

Issue list

1. [views] Add consolidated SETTINGS action + wire every settings write through one use case — P0
2. [views] Add DOCUMENT chat action so the Knowledge view is a pure state renderer — P1
3. [views] Add MEMORY delete/forget chat action to pair the Memories view control — P1
4. [views] Add FILES list/delete chat action so FilesView delete has a chat twin — P2
5. [views] Replace generic-bridge-only view controls (Tasks filter, Plugins enable/reorder) with semantic verbs — P2
6. [views] Ratchet: assert every builtin view on-screen mutation maps to a registered action — P2

Start with #1 (Settings is the biggest gap and unblocks the pattern). #2–#4 are
independent and parallelizable. #5 is confirm-then-extend (mostly verification).
#6 lands last, after #1–#4 close the current gaps, so the baseline is small.

How to claim work

1. Comment on the issue you're taking (one owner per issue).
2. Move its card to In Progress on project 15 — LifeOps Personal Assistant.
3. Before implementing, re-check the issue is still open and git log origin/develop
   on the target files — the swarm merges fast and an action may already exist.
4. Branch feat/<slug>; PR against develop; sync (git fetch && git rebase origin/develop) before opening/updating.

Evidence rules (inline in the PR — the committed .github/issue-evidence approach is retired)

Post evidence INLINE in the GitHub issue/PR. MP4 videos render inline; use JPG
for screenshots (not PNG). For each issue attach what applies:

• Real-LLM trajectory (live model, not the proxy/mock) showing the SEMANTIC
  action firing — NOT agent-fill/agent-click on a builtin field. This is the
  pass/fail signal for "views display, chat controls".
• JPG before + after full-page screenshots, desktop AND mobile — including
  the WRONG behavior for any bug (e.g. the control with no chat path).
• MP4 walkthrough: type the control change in chat, watch the view update
  live.
• Backend [ClassName] ... logs showing the use case firing.
• Domain artifact for state changes (document/memory/file/settings rows
  before+after).

No page ships needs-work/broken. Any evidence row that doesn't apply is
marked N/A - <reason>, never left blank.

Filed issues

• [views] Add consolidated SETTINGS action + wire every settings write through one use case #14364 — P0 [views] Add consolidated SETTINGS action + wire every settings write through one use case
• [views] Add DOCUMENT chat action so the Knowledge view is a pure state renderer #14365 — P1 [views] Add DOCUMENT chat action so the Knowledge view is a pure state renderer
• [views] Add MEMORY delete/forget chat action to pair the Memories view control #14366 — P1 [views] Add MEMORY delete/forget chat action to pair the Memories view control
• [views] Add FILES list/delete chat action so FilesView delete has a chat twin #14367 — P2 [views] Add FILES list/delete chat action so FilesView delete has a chat twin
• [views] Replace generic-bridge-only view controls (Tasks filter, Plugins enable/reorder) with semantic verbs #14368 — P2 [views] Replace generic-bridge-only view controls (Tasks filter, Plugins enable/reorder) with semantic verbs
• [views] Ratchet: assert every builtin view on-screen mutation maps to a registered action #14369 — P2 [views] Ratchet: assert every builtin view on-screen mutation maps to a registered action

---

Design doc · MVP board