docs: propose one ongoing conversation per cloud agent

.project-docs/30-worklog/tasks/20260928-agent-single-chat-27da516b.md

@@ -0,0 +1,56 @@
+# Task: Design one ongoing conversation per user and cloud agent
+
+## Identity
+
+- Task ID: 20260928-agent-single-chat-27da516b
+- Mode: Feature
+- Branch: codex/20260928-agent-single-chat-27da516b-agent-single-chat
+- Worktree: D:\Datas\OthersProjects\.codex-worktrees\makelore\20260928-agent-single-chat-27da516b
+- Base commit: b26e25c9ed26bf30f4d0bc03869c223f0fe34386
+- Owner: codex
+- Status: Ready for Integration
+
+## Scope
+
+- Source-grounded design for one ongoing conversation per user and delivered agent.
+- Cover UI, identity, per-turn project/version context, history, persistence, cloud threads and observer integration.
+- No product code changes, deployment, paid model calls, subagents, merge or cleanup.
+
+## Intent And Constraints
+
+- Interpret user + agent as cross-project continuity; keep Pi conversations project-owned and tools scoped to each accepted question.
+- Stable delivered config identity, account isolation and student payer remain; no fixed teacher/friend roles.
+- Official isolated start succeeded after unowned dirty main correctly refused a claim. Existing foreign documents were untouched.
+- Planning Gate passed. All 128 peer task records were inspected. Observer implementation overlaps semantically; consultation-scope peer remains template/unknown. No peer code inspected or changed.
+- Design proposes revisions to accepted project-topic/version policy. No canonical promotion or implementation is claimed.
+
+## Outcome
+
+- Completed [single-conversation proposal](../../10-decisions/proposals/20260928-agent-single-chat-27da516b__single-conversation.md).
+- Confirmed topics currently bind project, version and cloud thread ID; proposed user-agent chat with separately frozen turn contexts and internal execution segments.
+- Specified paged history, per-turn events, idempotent migration retaining original files, draft/reference provenance and observer delivery.
+- Defined actual failure scenarios for implementation acceptance.
+- Product implementation has not started; cross-device synchronization is outside the proposed first increment.
+
+## Verification
+
+- Inspected committed DTO, Main store/service/cloud-runner, Host API, Renderer panel and companion at recorded base.
+- Read relevant positioning, teacher ADR, architecture/domain and evidence/reflection/commitment context.
+- Yuxi server internals and installed/cloud behavior were not verified in this design-only task.
+- No product tests/builds: product code unchanged. Task-aware check_doc_drift passed; working changes contain only this record and the task-owned proposal.
+
+## Follow-ups
+
+- User may approve implementation or adjust the proposed cross-project semantics.
+- Before product edits, refresh observer/consultation-scope ownership and inspect actual Yuxi version, compaction and recovery contracts.
+- Implement focused regressions and Electron scenarios from the proposal, preserving cancellation and billing semantics.
+- Existing data-flow six-batch wording is stale relative to accepted protocol2 ADR; do not propagate it into new contracts.
+
+## Promotion Candidates
+
+- Targets: ADR-2026-09-22-coding-teacher.md, system-overview.md, data-flow.md, business-rules.md, README.md.
+- Proposal: after implementation acceptance, use one account-agent conversation with per-turn project/version and unified observer messages.
+- Evidence: user's screenshot/request and verified source seams listed in proposal.
+- Future impact: history lifecycle, config refresh, unread/draft ownership, cloud context and project-bound actions.
+- Semantic conflicts: changes accepted topic-level project/version binding; concurrent observer and unknown consultation-scope ownership require coordination before coding.
+- Human confirmation: implementation/semantic acceptance required before promotion. Current result is a design proposal only.