[sunrioa]

Summary

Refs #6716. Depends on #6724.

Fresh discovery Sessions avoid accumulating the entire investigation history, but they also need a way to recover previous progress, corrections and notification decisions. Otherwise, later investigations can repeat work or overlook user feedback.

Add DiscoveryMemory using the existing scheduler KV store. Investigations retain their outcomes and checkpoints, while the Bot can link corrections, notification decisions and user feedback to the original investigation.

• Give each new worker up to three short record previews, with explicit truncation and references for reading the complete material. Queries support text filtering, related records and pagination, including continuation after an empty filtered page.
• Commit investigation records together with settlement. Preserve unfinished checkpoints after failed execution, and discard checkpoints from cancelled investigations.
• Allow SendUser and sleep to record a discovery decision in the same call. Notification records require an actual outbox message; retries reuse its identity.
• Link feedback to an actual user message, retaining access to its original text and quotes. Add optional quotes to send, including quote-only and steering input, and update the generated SDK contracts.
• Scope shared records to the Bot’s source boundary. Changed workspace permissions or revoked Recall access cannot be bypassed through discovery memory.

The investigating worker still submits findings directly to the Bot, which decides whether to call SendUser. This adds no separate judgement Session.

This implements the shared-record and feedback portion of A2/A3 in #6716. Event-triggered discovery remains follow-up work.

Verification

Local macOS verification using Rust 1.98.0 and Node 26.13.0.

Check	Result
Agent Native, Agent API, Agent Facts and Scheduler library suites	467 passed, 0 failed; four existing manual/opt-in tests skipped
Final discovery-record regression rerun	7 passed
Generated SDK schemas and SDK/product TypeScript checks	Passed
Rust formatting, Biome, ASF headers and whitespace checks	Passed
Dependency-license policy and generated inventory	Passed
Clippy	Passed with three existing warnings in unchanged files

Integration tests use the real Host and local model fixtures. Coverage includes fresh-Session continuation, restart recovery, complete decision reasons, paginated quoted feedback, steering, cancellation, failed-investigation progress, permission and Recall revocation, and notification retry deduplication.

The final publication-retry adjustment was covered by the focused seven-test rerun. Windows validation, desktop E2E and live-provider evaluation were not performed.

AI use

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex assisted with implementation, regression tests, local verification and this description. The implementation commit includes a Generated-by: OpenAI Codex trailer.

Checklist

• Tests cover the change and fail without it
• Format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

简体中文

概述

关联 #6716，依赖 #6724。

每轮新建调查 Session 可以避免持续累积完整调查历史，但也需要恢复此前进度、修正和通知决策的途径，否则后续调查可能重复工作，或忽略用户反馈。

通过现有调度器 KV 存储增加 DiscoveryMemory。调查保存结果与进度检查点，Bot 可以将修正、通知决策和用户反馈关联到原始调查。

• 每个新 worker 最多携带三条简短记录预览，明确标记截断，并提供完整内容的读取入口。查询支持文本筛选、关联记录和分页；筛选结果为空时，也会保留后续读取入口。
• 调查记录与结算一起提交。执行失败时保留未完成的调查进度，取消调查时舍弃暂存进度。
• SendUser 和 sleep 可以在同一次调用中记录发现处理决策。通知记录必须关联实际存在的 outbox 消息，重试复用原消息身份。
• 反馈关联到真实用户消息，并保留原文和引用的读取入口。为 send 增加可选 quotes 字段，支持只有引用的消息及 steering 输入，同步更新生成的 SDK 契约。
• 共享记录受 Bot 的来源权限边界约束。工作区权限变化或 Recall 授权撤销后，不能通过调查记忆绕过限制。

调查 worker 仍直接将发现提交给 Bot，由 Bot 决定是否调用 SendUser，没有增加独立的判断 Session。

本次实现 #6716 中 A2/A3 的共享记录与反馈部分。事件触发的快速发现留在后续阶段。

验证

本地使用 macOS、Rust 1.98.0 和 Node 26.13.0 验证。

检查	结果
Agent Native、Agent API、Agent Facts 和 Scheduler 库套件	467 项通过、0 项失败；四项既有手工／需显式启用的测试跳过
最终共享记录定向回归复跑	7 项通过
生成的 SDK Schema、SDK／产品 TypeScript 检查	通过
Rust 格式、Biome、ASF 文件头及空白检查	通过
依赖许可证策略与生成清单	通过
Clippy	通过；未修改文件中保留三条既有告警

集成测试使用真实 Host 和本地模型夹具，覆盖新 Session 接续、重启恢复、完整决策理由、引用反馈分页、steering、取消、失败调查进度、权限和 Recall 撤销，以及通知重试去重。

最后的发送重试调整通过七项定向测试复验。尚未执行 Windows 验证、桌面 E2E 或真实供应商评估。

AI 使用说明

OpenAI Codex 协助完成实现、回归测试、本地验证及本说明起草。实现提交包含 Generated-by: OpenAI Codex 标记。

检查清单

• 测试覆盖本次改动，缺少相应实现时无法通过
• 格式、类型检查和受影响套件在本地通过

本 PR 存在行为变化，已在概述中说明。

[liugddx]

Blocking CI issue on the current head (c230b1b98cf9ac9c8e4bf4fec332e8ffec7a84df):

• native-windows fails terminal::desktop_new_session::desktop_file_gestures_preserve_drafts_and_stage_an_image (observed Null instead of the expected draft).
• root-tests cli slice 2 times out in terminal::keyboard::editor_copy_and_undo_precede_interrupt_and_ctrl_c_requires_confirming_the_current_run after about 72 seconds.

These failures are in existing desktop/keyboard paths, so it is not yet clear whether they are regressions from this PR or flaky/environment failures. Please rerun and document the diagnosis (or provide a justified waiver); until the required checks are green, this PR remains blocked from merge.

[liugddx]

Code-level review follow-up:

I traced the DiscoveryMemory write path (records.rs memory_append/discovery_memory) and the discovery settlement path (discovery.rs settle_discovery). The record, active-job deletion, completion marker, and outcome record are assembled into one storage batch with a head CAS, and decision writes use deterministic receipt keys. I did not find a confirmed P0/P1/P2 correctness defect in these paths.

The merge-relevant gap is coverage of the failure cases around that design. Please add or point to tests for:

• an OutcomeUnknown after the batch commits, followed by scheduler restart/retry;
• concurrent DiscoveryMemory append attempts and head-revision conflict recovery;
• Bot notification admission succeeding but the subsequent Notified decision receipt being uncertain;
• scope changes (permissions/binding/Recall boundary) between the worker's investigation and Bot feedback/notification.

The current red Windows/CLI checks remain a separate merge blocker.