Skip to content

v1.1: PersonaBot / Assignment 实时状态投影与 UI 刷新 #43

Closed

Description

@DoodleBears

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

Related

Activity

  1. added this to the v1.0 milestone on Sep 18, 2026
  2. DoodleBears commented on Sep 18, 2026

    @DoodleBears
    ContributorAuthor

    六态展示仍要做,但真实状态来源改为 v1.1 的 Bot Inbox / Orchestrator 波次(session 生命周期事件)。M3 只保留 sidebar 聚合态与右侧面板的空态展示;本票改挂 v1.1。

  3. modified the milestones: v1.0, v1.1 on Sep 18, 2026
  4. changed the title [-]M3.4 六态实时刷新[/-] [+]v1.1: 六态实时刷新(sidebar 聚合态 + 右侧面板)[/+] on Sep 18, 2026
  5. changed the title [-]v1.1: 六态实时刷新(sidebar 聚合态 + 右侧面板)[/-] [+]v1.1: PersonaBot / Work 实时状态投影与 UI 刷新[/+] on Sep 19, 2026
  6. changed the title [-]v1.1: PersonaBot / Work 实时状态投影与 UI 刷新[/-] [+]v1.1: PersonaBot / Assignment 实时状态投影与 UI 刷新[/+] on Sep 20, 2026
  7. 2 remaining items

  8. added
    enhancementNew feature or request
    duplicateThis issue or pull request already exists
    wontfixThis will not be worked on
    and removed
    needs-triageMaintainer needs to evaluate this issue
    on Sep 20, 2026
  9. DoodleBears commented on Sep 20, 2026

    @DoodleBears
    ContributorAuthor

    This was generated by AI during triage.

    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.

  10. moved this from Todo to Done in Roadmapon Sep 20, 2026
  11. added
    V1.1Milestone v1.1; mirrors the GitHub milestone
    on Sep 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    V1.1Milestone v1.1; mirrors the GitHub milestoneduplicateThis issue or pull request already existsenhancementNew feature or requestwontfixThis will not be worked on

    Type

    No type

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions