feat(agents): 完善恢复费用与云资源交互
This commit is contained in:
@@ -12,6 +12,8 @@
|
||||
|
||||
## Scope
|
||||
|
||||
- Resumed 2026-09-10 to finish the remaining-scope assessment, including product maintenance. Budget policy confirmed: optional per-Agent per-root-request and daily Token Points ceilings across all call sources, with no extra limit for existing Agents. The user authorized two bounded implementers and one fresh independent Reviewer for this batch; root owns client/integration/docs and all final Git operations.
|
||||
|
||||
- Complete the native cloud Agent workspace: configuration/preview, conversations/files/approval, publication/user sharing/application API, schedules/activity/cost; all cloud traffic and credentials remain Main-owned.
|
||||
- User explicitly requested all remaining first-release modules, not another draft-only slice. Build on the reviewed entry commit recorded above; verify all accepted personal/share/API/scheduled/goal-tool paths before claiming completion.
|
||||
|
||||
@@ -25,27 +27,24 @@
|
||||
|
||||
## Outcome
|
||||
|
||||
- Completed native Agents workspace: My/Received/Activity, configuration and preview, formal conversations, approval/questions, attachments and downloadable artifacts, personal KB documents/indexing, publication/share/application credentials, creator costs and scheduled goals/history.
|
||||
- Main owns exchanged credentials, actual cloud transport/SSE, account cancellation, local file dialogs/writes and desktop notifications; Renderer uses typed Host operations. Unsaved/unsent input and uncertain requests are preserved through explicit leave/retry flows; niancode Agent links route through login and server authorization.
|
||||
- Implementation and verification are complete. The user explicitly authorized one fresh independent read-only Reviewer and commits after fixes. The fresh Reviewer reviewed the full three-repository scope and returned final PASS after confirming all findings were fixed. No unresolved review finding remains; no production deployment, push or merge was performed.
|
||||
- 已补齐 Main 按账号磁盘保存未确认操作/原输入及最近精确位置,恢复 UI 和排队状态;费用上限/统计、应用调用元数据、聊天日程建议与时间输入及启用确认;个人 MCP/Skill/子智能体、知识维护、归档、版本比较和旧版恢复。Renderer 只使用 typed Host API,凭据不写恢复日志。
|
||||
- 本批实现与验证已完成;获授权的全新只读 Reviewer completion_review(不继承开发上下文)审查三端完整增量,并复核待审批会话归档及手动日程默认停用两处修复后返回 PASS,无未解决 actionable finding。
|
||||
- 完整补全结果、行为边界和发布验收范围记录在 WS 同任务 evidence 的 `20260910-personal-agent-platform-60a1e3e6__completion-evidence.md`。旧 `__remaining-scope.md` 已标为历史核对。
|
||||
|
||||
## Verification
|
||||
|
||||
- Passed: 32 tests across Main, draft/UI workflows and deep links. Includes stable retry intent, native batched SSE, approval restore, schedule enable intent, cost-service partial failure, actual temporary file bytes through mocked native dialogs, account switch cancellation and notification deduplication.
|
||||
- Review fixes verified: new conversations appear immediately in history; unsent preview messages survive configuration edits; conversation changes protect approval answers and temporary attachments; cancelling file selection creates no empty conversation. The final attachment case verifies that only confirmation creates the conversation and associates the file. Renderer typecheck, targeted ESLint and Vite build passed again after this last fix.
|
||||
- Passed: Renderer TypeScript; Vite build for Renderer/Main/preload/utility; real Electron Playwright scenario creates/saves/publishes an Agent, shows formal Markdown chat and creates an enabled schedule. The Host backend is explicitly stubbed in Electron coverage.
|
||||
- Passed: targeted ESLint with no errors (2 non-blocking CloudChat warnings). Main TypeScript has the same 61 pre-existing errors, none in cloud Agents; this does not represent a clean repository-wide Main typecheck.
|
||||
- Electron screenshots were inspected. No packaged installation, OS protocol registration or live three-service integration was executed.
|
||||
- 本批 39 项 Main/页面/工作流/资源维护单元通过;真实 electron-store 临时磁盘重建 Main 后可读回,跨账号不可读,原操作标识保留且不自动重试。审查修复手动新建任务默认停用,与聊天建议一致;用户须显式勾选启用。
|
||||
- 最后补丁后 Renderer TypeScript、Vite 完整构建及改动 lint 通过;Electron Playwright 1 passed,覆盖创建/发布、Markdown 对话、恢复、费用、建议及手动新建默认关闭、确认启用。Host 后端明确为替身;截图已查看。
|
||||
- targeted ESLint 无错误、3 个非阻塞警告。Main 全仓 tsc 保留 61 个既有诊断,cloud Agent 文件没有诊断;不宣称全仓 Main 类型检查通过。
|
||||
- 没有安装包/系统协议注册、真实账号跨设备或真实三端生产验收。
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- 2026-09-10 用户要求核对剩余功能:本次只核对已提交代码、原交互方案及既有证据,没有修改运行代码或重跑产品测试。此前 Outcome 中“Implementation and verification are complete”仅适用于已实现的核心链路与已执行验证,不能代表原首期所有交互或 P6 已完成。
|
||||
- 核对结果:最近使用定位、聊天转自动任务建议、启用前完整说明、完整重启恢复和费用/应用使用统计未闭合;云资源维护另有产品完善项。
|
||||
- 三端完整剩余清单保存在 WS 本任务的 `50-evidence/topics/20260910-personal-agent-platform-60a1e3e6__remaining-scope.md`。恢复、交互和统计缺口是待实现事项;真实模型/沙盒/安装包是待验收事项,需分别跟踪。Ready for Integration 表示此源码及核对记录可交接,不表示产品已完成上线验收。
|
||||
|
||||
- Hand off the reviewed result as committed feature branches for a separately authorized integration/release. Keep the worktrees and branches; no push, merge, deployment or further Reviewer is implied.
|
||||
- Release-environment follow-up: actual one-api/paid-model reconciliation, provisioner sandbox execution, installable client packaging and production migration/rollback exercise. Current local validation does not claim these deployment outcomes.
|
||||
- 本批已完成独立审查与补丁验证;结果作为本地 feature 提交交接。三个任务的文档所有权边界检查通过,分支和工作树保留供后续集成。
|
||||
- 发布环境验收:真实 one-api/付费模型与创建者账单对账,完整服务进程/ARQ/provisioner 沙盒及重启恢复,安装包/OS 协议/跨设备流程,生产配置和迁移回退。
|
||||
- 费用按预占准入;供应商超预占进入现有 pending_review,不自动超额扣款。异常供应商报告与人工核对保持原账本契约,不能宣称供应商账单绝对封顶。
|
||||
- 保留隔离分支/工作树用于后续集成。未授权推送、合并、部署或操作生产数据;未执行这些动作。
|
||||
|
||||
## Promotion Candidates
|
||||
|
||||
- Target: integrated state and owning Agent/auth/billing/runtime architecture records. Proposal: complete the user-approved personal cloud platform using existing Yuxi capability/Request/Run/scheduling and WS accounting owners; document the cloud module's scope alongside the existing WS Gateway. Evidence: this task's final source and meaningful HTTP/PG/worker/Electron validation. Future impact: future modules consume one runtime and one ledger. Semantic conflicts: earlier planning fields and draft-only scope are superseded by implementation; existing unrelated product contracts remain. Human confirmation: product direction is already approved; canonical promotion remains a serialized integration task.
|
||||
- Target: 集成 current-state、原个人云平台决策及身份/计费/运行/资源架构。Proposal: 按最终补全源码与验证取代旧功能缺口及“每日预算未定”,记录按 Agent、根 Request、北京时间准入日计费和个人资源所有权。Evidence: 本任务三端代码、HTTP/PG/worker/Electron 结果及本批最终审查。Future impact: 后续功能复用同一运行体系和账本。Semantic conflicts: 原缺口清单仅为历史事实,原费用范围已被本次用户决定补足,不改变其他模块产品方向。Human confirmation: 产品范围已确认;共享文档提取必须走独立 Integration Gate,本 feature 不直接修改 accepted ADR/canonical memory。
|
||||
|
||||
Reference in New Issue
Block a user