M4: 演示闭环（Orchestrator → Assignment → Report → Reply） #11

What to build

一个可重复的单目录Workspace端到端演示：Human在DSH Web中向“研究助手”PersonaBot提问；PersonaBot已自动拥有真实Git-backed Memory Repository，Orchestrator以该repository为cwd且永远workspace-write；Human已给该Bot一个durable Workspace Grant；Orchestrator创建或复用一个以该Workspace为唯一primary cwd、默认workspace-write的Assignment Session读取材料；Assignment Agent通过report_to_orchestrator汇报；Orchestrator向来源DM回复。

全程使用真实Session ownership、Memory Service accepted commits、Workspace Grant、DSH lifecycle facts、Assignment Directory与PersonaBot Activity Projection，不靠mock/cwd/UI sending flag猜测，不使用模型可见Memory tools。

Acceptance criteria

• 演示脚本：创建Bot → 自动创建Memory Repository → Orchestrator cwd固定到repo → 授权Workspace Grant → 通过 UI Tracer: Channel composer island 与 PersonaBot activity region #129 composer island发送请求 → create/reuse one-cwd Assignment Session → progress/terminal report → 来源回复。
• Orchestrator使用普通file/Shell/grep/git处理Memory；没有memory_read/write/edit等模型tools。
• Assignment只使用Grant指向的单目录primary cwd；默认workspace-write。danger-full-access不是本演示前置，且不允许改变Orchestrator、existing Session或制造multi-cwd。
• execution activity 来自 Foundation：explicit Session ownership 与 DSH activity projection #80/Bot activity: Orchestrator and Assignment aggregation #123 的 DSH-derived PersonaBot Projection；waiting-human、blocked、approval 与 report/terminal facts保持独立。
• sidebar、Channel row 与 composer island 使用 Bot activity: shared snapshot and live DM presence #120 的同一 activity revision；Orchestrator等待Assignment时能看到 handoff，完成后回到Orchestrator/idle。
• Bot activity: safe tool summaries and effects #122 的 tool-aware effect 与安全文字摘要可展开，但不显示 raw reasoning/arguments/results。
• UI Foundation: BotHarness motion preference（System / Reduce / Full） #128 可在 Follow system / Reduce motion / Full motion 切换；Reduce 下所有状态仍由静态indicator、text与ARIA完整表达。
• 若演示 Group Channel，Group activity: live facepile, safe summaries and details #124 facepile能分别识别多个active PersonaBots；DM-only最小演示不得伪造Group fixture。
• Assignment Report与Host Lifecycle Notice provenance可区分；完整transcript只在DSH SessionPersistence。
• 需要Human的provider Service Action通过capability/grant/attention呈现；Reply不要求模型选择provider。
• 若演示产生Memory变更，只有Memory Service验证并接受的Memory Commit进入durable history/query；Source Event/Assignment Report不自动蒸馏。
• restart后可重建ownership/activity/directory、Memory accepted head与Workspace Grant references，且不会silently duplicate Assignment Session。
• revoke Grant后新的create/request/resume/wake fail closed；不把Assignment静默迁移到Memory repo或其他Workspace。

Blocked by

• M3.5: 本地安装验证门（DSH 实机 + 插件 UI 冒烟） #24：真实bundle安装、Activity/Presence/composer/motion与UI验证门。
• Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81：Assignment Runtime / Assignment Directory / Orchestrator tools。

#24 已通过 native dependency 等待 #119；#81 已等待 #80、#115、#116。

References

• Wayfinder: Memory Repository / Workspace Grant / Assignment cwd #114、Foundation: Git working tree as PersonaBot Memory #115、Workspace Grants: folder access UI and enforced PersonaBot file boundary #116、[Retired] Orchestrator: V1.0 PersonaBot Activity、Presence 与 Output Events #119、UI Foundation: BotHarness motion preference（System / Reduce / Full） #128、UI Tracer: Channel composer island 与 PersonaBot activity region #129
• #71中的ownership/messaging原则
• ADR-0035、ADR-0045