Repository navigation
Closed
Labels
V1.1Milestone v1.1; mirrors the GitHub milestoneMilestone v1.1; mirrors the GitHub milestoneduplicateThis issue or pull request already existsThis issue or pull request already existsenhancementNew feature or requestNew feature or requestwontfixThis will not be worked onThis will not be worked on
Milestone
Description
What to build
把#80的explicit Session ownership与DSH-derived activity Projection接到真实UI,并叠加#115/#116提供的Memory Repository、Workspace Grant、PersonaBot Assignment access preset与per-Session permission snapshot。UI不维护第二套lifecycle,也不从cwd、最近页面活动或raw filesystem推断ownership/authority。
Scope
- Host read model:PersonaBot aggregate、owned Orchestrator/Assignment Sessions、DSH activity/lastRun、latest report、aggregate descendant activity。
- PersonaBot settings:当前Assignment default preset(workspace-write或danger-full-access)、last changed/audit summary、risk acknowledgement与revoke action。
- Assignment detail:single Workspace/primary cwd、Grant current validity、actual immutable permission snapshot、preset revision、revoked/unavailable/needs-repair。
- Orchestrator detail永远显示workspace-write + Memory Repository cwd;不能因PersonaBot preset显示full access。
- Memory navigation只显示Memory Service accepted head/history;dirty/raw Git state显示degraded/repair。
- Client先用action refresh + bounded polling;#67后续stream frames。
Acceptance criteria
- default workspace-write与danger-full-access在设置和Assignment detail中清晰区分。
- 开启full access前有显式风险确认;开启期间PersonaBot settings与每个相关Assignment持续显示警示及撤销入口。
- UI同时展示“PersonaBot当前默认preset”和“该Session实际snapshot”;设置变化后旧Session不得变色或被误报为新模式。
- Orchestrator永远显示workspace-write,即使PersonaBot default是danger-full-access。
- 每个Assignment detail只有一个primary Workspace/cwd;full access仍保留Grant/provenance且不显示成multi-cwd。
- Grant revoke/unavailable与preset revoke是不同facts;都不改写历史ownership或Session snapshot。
- Memory UI只显示accepted state;dirty/conflicted state明确degraded/repair。
- restart、断线/重连与unowned/ambiguous Session不污染任何PersonaBot。
- Assignment Report与Lifecycle Notice分开显示,不制造第二套AssignmentStatus。
- archive/recovery mode明确degraded/blocked,不显示可执行假象。
Blocked by
- Foundation:explicit Session ownership 与 DSH activity projection #80 explicit Session ownership/activity projection。
- Foundation: Git working tree as PersonaBot Memory #115 Memory Repository accepted-state projection。
- Workspace Grants: folder access UI and enforced PersonaBot file boundary #116 Workspace Grant / Assignment permission preset / one cwd。
- Bot Attention: causal aggregation, escalation and recovery acceptance #47 Messaging/Attention facts。
Related
- M3: Bot 模式 IA 与聊天外壳(列表/Section/DM/本地消息) #10;v1.1: read-model 实时同步流(post-commit frames) #67;设计:PersonaBot navigation / Assignments / recovery 的 DSH-native UI #75;Foundation:Assignment Runtime / Assignment Directory / Orchestrator tools #81;Wayfinder: Memory Repository / Workspace Grant / Assignment cwd #114。
Metadata
Metadata
Assignees
Labels
V1.1Milestone v1.1; mirrors the GitHub milestoneMilestone v1.1; mirrors the GitHub milestoneduplicateThis issue or pull request already existsThis issue or pull request already existsenhancementNew feature or requestNew feature or requestwontfixThis will not be worked onThis will not be worked on
Type
Projects
- StatusShow more project fieldsDone
Activity
DoodleBears commentedon Sep 18, 2026
六态展示仍要做,但真实状态来源改为 v1.1 的 Bot Inbox / Orchestrator 波次(session 生命周期事件)。M3 只保留 sidebar 聚合态与右侧面板的空态展示;本票改挂 v1.1。
[-]M3.4 六态实时刷新[/-][+]v1.1: 六态实时刷新(sidebar 聚合态 + 右侧面板)[/+][-]v1.1: 六态实时刷新(sidebar 聚合态 + 右侧面板)[/-][+]v1.1: PersonaBot / Work 实时状态投影与 UI 刷新[/+][-]v1.1: PersonaBot / Work 实时状态投影与 UI 刷新[/-][+]v1.1: PersonaBot / Assignment 实时状态投影与 UI 刷新[/+]2 remaining items
DoodleBears commentedon Sep 20, 2026
Closing as superseded and split across clearer authorities:
Keeping this broad mixed ticket open would recreate a second UI/runtime scope and duplicate the native dependency graph.