@wowyuarm/dsh-agent-team 0.1.15 → 0.2.1

package/packages/client-agent-team/lib/types/client/locales.d.ts

@@ -64,13 +64,11 @@ export declare const zh: {
     readonly resumeAgent: "恢复";
     readonly restartAgent: "重启";
     readonly restartStillUnavailable: "重启已执行，成员仍不可用：{diagnostic}";
-    readonly restartRefusedNoRestart: "会话日志被确定拒绝，修复无可用项，重启无法解决：{detail}";
     readonly restartFailed: "重启执行失败：{message}";
     readonly archiveAgent: "归档";
     readonly archiveAgentTitle: "归档 Agent：{name}";
     readonly archiveAgentNotice: "将把 {name} 从所有列表收起：会话与私有记忆保留在磁盘上、活跃 Claim 会释放，但暂无恢复入口。";
     readonly archiveAgentConfirm: "归档";
-    readonly archiveAgentFailed: "归档失败：{message}";
     readonly archiveChannel: "归档频道";
     readonly archiveChannelTitle: "归档频道：{name}";
     readonly archiveChannelNotice: "将把 {name} 及其全部讨论从所有列表收起：数据保留、所有成员在此频道的活跃 Claim 会释放，但暂无恢复入口。";
@@ -111,9 +109,9 @@ export declare const zh: {
     readonly timelineLabel: "消息时间线";
     readonly taskClosedNotice: "任务已关闭，重新打开后可继续讨论";
     readonly human: "Human";
-    readonly humanSettingsNav: "我的资料";
-    readonly humanSettingsTitle: "我的资料";
-    readonly humanSettingsIntro: "这是 Agent Team 的资料页：名字用在 Team 的消息与成员列表里，头像出现在你发出的消息旁。";
+    readonly teamSettingsNav: "团队";
+    readonly teamSettingsTitle: "团队";
+    readonly teamSettingsIntro: "你在 Team 里的身份，以及 jev 要用的端点。";
     readonly humanSettingsName: "名字";
     readonly humanSettingsNameHint: "Agents 用这个名字 @ 到你；改名只对之后的消息生效。";
     readonly humanSettingsNameEmpty: "名字不能为空。";
@@ -133,13 +131,44 @@ export declare const zh: {
     readonly humanSettingsUnavailable: "资料读不出来：{message}";
     readonly humanSettingsVersion: "版本 {version}";
     readonly humanSettingsUpdateAvailable: "有新版本 {version}，去查看发布说明";
+    readonly teamJudgeGroupTitle: "jev";
+    readonly teamJudgeGroupHint: "判断隔了很久之后这一步是否仍是同一件事。调用发往 apiBase 下的 /systemone，换端点通常要同时换 model；留空沿用部署默认值。";
+    readonly teamJudgeReady: "jev 已就绪";
+    readonly teamJudgeNoKey: "未配置 key，填入即启用";
+    readonly teamJudgeUnavailable: "jev 不可用：检查 apiBase 与 model";
+    readonly teamJudgeApiBase: "apiBase";
+    readonly teamJudgeModel: "model";
+    readonly teamJudgeKey: "key";
+    readonly teamJudgeKeyHint: "只写不回显：留空保存不会改动已存的 key。";
+    readonly teamJudgeKeySet: "已配置";
+    readonly teamJudgeKeyUnset: "未配置";
+    readonly teamJudgeClearKey: "清除 key";
+    readonly teamJudgeClearHint: "清除后 jev 立即卸载，不再判断。";
+    readonly teamJudgeClearBlocked: "先保存，再清除。";
+    readonly teamJudgeClearFailed: "没能清除，请重试。";
+    readonly teamSettingsOverridden: "已覆盖";
+    readonly teamSettingsReset: "重置";
+    readonly teamSettingsInvalid: "这个值不被接受。";
+    readonly teamSettingsUnavailable: "这台部署没有提供 Team 的设置文档。";
+    readonly teamSettingsReadOnly: "当前设置是只读的。";
+    readonly teamSettingsSaveFailed: "保存没有被接受，请检查后重试。";
+    readonly teamSettingsSave: "保存";
+    readonly teamSettingsSaving: "保存中…";
+    readonly environmentOkTitle: "在支持范围内";
+    readonly environmentOkDetail: "正在运行的 DSH {version} 在我们声明的支持范围内。";
+    readonly environmentOutOfRangeTitle: "不在支持范围内";
+    readonly environmentOutOfRangeDetail: "正在运行的 DSH {version} 不在我们声明的支持范围内——这套组合未经我们认证，可能出问题。";
+    readonly environmentRange: "支持范围：{lower} 起、{upper} 之前。";
+    readonly environmentTested: "我们实测认证的组合：Agent Team {bundle} × DSH {dsh}。";
+    readonly environmentUndeterminedTitle: "无法判定运行环境";
+    readonly environmentUndeterminedDetail: "读不到正在运行的 DSH 版本，或无法确定我们的支持范围，因此不做判断。";
+    readonly environmentReleaseNotes: "查看发布说明";
     readonly taskStatusTodo: "待处理";
     readonly taskStatusInProgress: "进行中";
     readonly taskStatusInReview: "待验收";
     readonly taskStatusDone: "已完成";
     readonly taskStatusClosed: "已关闭";
     readonly taskLabel: "Task #{number}";
-    readonly taskPending: "Task …";
     readonly openTask: "打开 Task #{number}";
     readonly openThread: "打开讨论";
     readonly openTaskUnread: "打开 Task #{number}（{count} 条新动态）";
@@ -206,7 +235,6 @@ export declare const zh: {
     readonly activityReopened: "{actor} 重新打开了此 Task";
     readonly mentionConfirmation: "提及未关注成员需要确认，再次发送以继续";
     readonly memberNotFollowing: "这些成员还未关注此 Thread：{ids}";
-    readonly sendFailedKind: "无法发送消息（{kind}）";
     readonly unreadRequired: "请先读取 {count} 条未读更新，再继续修改。";
     readonly staleRevision: "Thread 已发生变化，请按最新状态重试。";
 };
@@ -276,13 +304,11 @@ export declare const en: {
     readonly resumeAgent: "Resume";
     readonly restartAgent: "Restart";
     readonly restartStillUnavailable: "Restart ran, but the Member is still unavailable: {diagnostic}";
-    readonly restartRefusedNoRestart: "The session log is deterministically refused with nothing repairable; restarting cannot fix it: {detail}";
     readonly restartFailed: "Restart failed: {message}";
     readonly archiveAgent: "Archive";
     readonly archiveAgentTitle: "Archive Agent: {name}";
     readonly archiveAgentNotice: "This hides {name} from every list: the session log and private memory stay on disk and active Claims release, but there is no restore entry point yet.";
     readonly archiveAgentConfirm: "Archive";
-    readonly archiveAgentFailed: "Failed to archive: {message}";
     readonly archiveChannel: "Archive Channel";
     readonly archiveChannelTitle: "Archive Channel: {name}";
     readonly archiveChannelNotice: "This hides {name} and all of its discussions from every list: the data stays, every Member's active Claims in this Channel release, but there is no restore entry point yet.";
@@ -323,9 +349,9 @@ export declare const en: {
     readonly timelineLabel: "Message timeline";
     readonly taskClosedNotice: "This task is closed; reopen it to continue the discussion";
     readonly human: "Human";
-    readonly humanSettingsNav: "Profile";
-    readonly humanSettingsTitle: "Profile";
-    readonly humanSettingsIntro: "This is your Agent Team profile: the name applies to Team messages and member lists, and the avatar appears beside your messages.";
+    readonly teamSettingsNav: "Team";
+    readonly teamSettingsTitle: "Team";
+    readonly teamSettingsIntro: "Your identity in the Team, and the endpoint jev calls.";
     readonly humanSettingsName: "Name";
     readonly humanSettingsNameHint: "Agents @ you by this name; a rename applies to later messages only.";
     readonly humanSettingsNameEmpty: "A name is required.";
@@ -345,13 +371,44 @@ export declare const en: {
     readonly humanSettingsUnavailable: "The profile could not be read: {message}";
     readonly humanSettingsVersion: "Version {version}";
     readonly humanSettingsUpdateAvailable: "New version {version} available — see the release notes";
+    readonly teamJudgeGroupTitle: "jev";
+    readonly teamJudgeGroupHint: "Decides whether a step after a long absence still belongs to the same piece of work. Calls go to /systemone under the apiBase, and changing the endpoint usually means changing the model too; empty inherits the deployment default.";
+    readonly teamJudgeReady: "jev is ready";
+    readonly teamJudgeNoKey: "No key yet — enter one to enable it";
+    readonly teamJudgeUnavailable: "jev is unavailable: check the apiBase and model";
+    readonly teamJudgeApiBase: "apiBase";
+    readonly teamJudgeModel: "model";
+    readonly teamJudgeKey: "key";
+    readonly teamJudgeKeyHint: "Write-only: an empty field saves nothing and leaves a stored key in place.";
+    readonly teamJudgeKeySet: "Configured";
+    readonly teamJudgeKeyUnset: "Not configured";
+    readonly teamJudgeClearKey: "Clear key";
+    readonly teamJudgeClearHint: "Clearing unmounts jev immediately; nothing is judged after that.";
+    readonly teamJudgeClearBlocked: "Save first, then clear.";
+    readonly teamJudgeClearFailed: "The key could not be cleared; try again.";
+    readonly teamSettingsOverridden: "Overridden";
+    readonly teamSettingsReset: "Reset";
+    readonly teamSettingsInvalid: "This value is not accepted.";
+    readonly teamSettingsUnavailable: "This deployment does not serve the Team settings document.";
+    readonly teamSettingsReadOnly: "Settings are read-only right now.";
+    readonly teamSettingsSaveFailed: "The save was not accepted; check the values and try again.";
+    readonly teamSettingsSave: "Save";
+    readonly teamSettingsSaving: "Saving…";
+    readonly environmentOkTitle: "Within the supported range";
+    readonly environmentOkDetail: "The running DSH {version} is within the range we declare support for.";
+    readonly environmentOutOfRangeTitle: "Outside the supported range";
+    readonly environmentOutOfRangeDetail: "The running DSH {version} is outside the range we declare support for — we have not certified this combination and it may misbehave.";
+    readonly environmentRange: "Support range: from {lower} up to, but not including, {upper}.";
+    readonly environmentTested: "Certified combination: Agent Team {bundle} × DSH {dsh}.";
+    readonly environmentUndeterminedTitle: "Environment cannot be determined";
+    readonly environmentUndeterminedDetail: "The running DSH version could not be read, or our support range could not be established, so no judgement is made.";
+    readonly environmentReleaseNotes: "See the release notes";
     readonly taskStatusTodo: "To do";
     readonly taskStatusInProgress: "In progress";
     readonly taskStatusInReview: "In review";
     readonly taskStatusDone: "Done";
     readonly taskStatusClosed: "Closed";
     readonly taskLabel: "Task #{number}";
-    readonly taskPending: "Task …";
     readonly openTask: "Open Task #{number}";
     readonly openThread: "Open thread";
     readonly openTaskUnread: "Open Task #{number} ({count} new updates)";
@@ -418,7 +475,6 @@ export declare const en: {
     readonly activityReopened: "{actor} reopened this Task";
     readonly mentionConfirmation: "Mentioning an unfollowed member requires confirmation; send again to continue";
     readonly memberNotFollowing: "These Members do not follow this Thread yet: {ids}";
-    readonly sendFailedKind: "Unable to send message ({kind})";
     readonly unreadRequired: "Read {count} unread update(s) before changing this Thread.";
     readonly staleRevision: "This Thread changed; retry using the current state.";
 };

package/packages/client-agent-team/lib/types/client/locales.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"locales.d.ts","sourceRoot":"","sources":["../../../src/client/locales.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuNL,CAAA;AAEV,eAAO,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqNL,CAAA;AAEV,MAAM,MAAM,OAAO,GAAG,MAAM,OAAO,EAAE,CAAA"}
+{"version":3,"file":"locales.d.ts","sourceRoot":"","sources":["../../../src/client/locales.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyPL,CAAA;AAEV,eAAO,MAAM,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiPL,CAAA;AAEV,MAAM,MAAM,OAAO,GAAG,MAAM,OAAO,EAAE,CAAA"}

package/packages/client-agent-team/lib/types/client/locales.js

@@ -64,13 +64,11 @@ export const zh = {
     resumeAgent: '恢复',
     restartAgent: '重启',
     restartStillUnavailable: '重启已执行，成员仍不可用：{diagnostic}',
-    restartRefusedNoRestart: '会话日志被确定拒绝，修复无可用项，重启无法解决：{detail}',
     restartFailed: '重启执行失败：{message}',
     archiveAgent: '归档',
     archiveAgentTitle: '归档 Agent：{name}',
     archiveAgentNotice: '将把 {name} 从所有列表收起：会话与私有记忆保留在磁盘上、活跃 Claim 会释放，但暂无恢复入口。',
     archiveAgentConfirm: '归档',
-    archiveAgentFailed: '归档失败：{message}',
     archiveChannel: '归档频道',
     archiveChannelTitle: '归档频道：{name}',
     archiveChannelNotice: '将把 {name} 及其全部讨论从所有列表收起：数据保留、所有成员在此频道的活跃 Claim 会释放，但暂无恢复入口。',
@@ -111,9 +109,9 @@ export const zh = {
     timelineLabel: '消息时间线',
     taskClosedNotice: '任务已关闭，重新打开后可继续讨论',
     human: 'Human',
-    humanSettingsNav: '我的资料',
-    humanSettingsTitle: '我的资料',
-    humanSettingsIntro: '这是 Agent Team 的资料页：名字用在 Team 的消息与成员列表里，头像出现在你发出的消息旁。',
+    teamSettingsNav: '团队',
+    teamSettingsTitle: '团队',
+    teamSettingsIntro: '你在 Team 里的身份，以及 jev 要用的端点。',
     humanSettingsName: '名字',
     humanSettingsNameHint: 'Agents 用这个名字 @ 到你；改名只对之后的消息生效。',
     humanSettingsNameEmpty: '名字不能为空。',
@@ -133,13 +131,50 @@ export const zh = {
     humanSettingsUnavailable: '资料读不出来：{message}',
     humanSettingsVersion: '版本 {version}',
     humanSettingsUpdateAvailable: '有新版本 {version}，去查看发布说明',
+    // The Team page's judge group: the endpoint jev is mounted from, and the one
+    // line that says whether it is reachable right now. The group is named for
+    // the component a reader configures rather than for a role it plays.
+    teamJudgeGroupTitle: 'jev',
+    teamJudgeGroupHint: '判断隔了很久之后这一步是否仍是同一件事。调用发往 apiBase 下的 /systemone，换端点通常要同时换 model；留空沿用部署默认值。',
+    teamJudgeReady: 'jev 已就绪',
+    teamJudgeNoKey: '未配置 key，填入即启用',
+    teamJudgeUnavailable: 'jev 不可用：检查 apiBase 与 model',
+    teamJudgeApiBase: 'apiBase',
+    teamJudgeModel: 'model',
+    teamJudgeKey: 'key',
+    teamJudgeKeyHint: '只写不回显：留空保存不会改动已存的 key。',
+    teamJudgeKeySet: '已配置',
+    teamJudgeKeyUnset: '未配置',
+    teamJudgeClearKey: '清除 key',
+    teamJudgeClearHint: '清除后 jev 立即卸载，不再判断。',
+    teamJudgeClearBlocked: '先保存，再清除。',
+    teamJudgeClearFailed: '没能清除，请重试。',
+    teamSettingsOverridden: '已覆盖',
+    teamSettingsReset: '重置',
+    teamSettingsInvalid: '这个值不被接受。',
+    teamSettingsUnavailable: '这台部署没有提供 Team 的设置文档。',
+    teamSettingsReadOnly: '当前设置是只读的。',
+    teamSettingsSaveFailed: '保存没有被接受，请检查后重试。',
+    teamSettingsSave: '保存',
+    teamSettingsSaving: '保存中…',
+    // The environment check. The support line is stated in words, never as a bare
+    // semver range, and the tested-combination line prints only versions the Host
+    // could derive — the page adds no version of its own.
+    environmentOkTitle: '在支持范围内',
+    environmentOkDetail: '正在运行的 DSH {version} 在我们声明的支持范围内。',
+    environmentOutOfRangeTitle: '不在支持范围内',
+    environmentOutOfRangeDetail: '正在运行的 DSH {version} 不在我们声明的支持范围内——这套组合未经我们认证，可能出问题。',
+    environmentRange: '支持范围：{lower} 起、{upper} 之前。',
+    environmentTested: '我们实测认证的组合：Agent Team {bundle} × DSH {dsh}。',
+    environmentUndeterminedTitle: '无法判定运行环境',
+    environmentUndeterminedDetail: '读不到正在运行的 DSH 版本，或无法确定我们的支持范围，因此不做判断。',
+    environmentReleaseNotes: '查看发布说明',
     taskStatusTodo: '待处理',
     taskStatusInProgress: '进行中',
     taskStatusInReview: '待验收',
     taskStatusDone: '已完成',
     taskStatusClosed: '已关闭',
     taskLabel: 'Task #{number}',
-    taskPending: 'Task …',
     openTask: '打开 Task #{number}',
     openThread: '打开讨论',
     openTaskUnread: '打开 Task #{number}（{count} 条新动态）',
@@ -210,7 +245,6 @@ export const zh = {
     activityReopened: '{actor} 重新打开了此 Task',
     mentionConfirmation: '提及未关注成员需要确认，再次发送以继续',
     memberNotFollowing: '这些成员还未关注此 Thread：{ids}',
-    sendFailedKind: '无法发送消息（{kind}）',
     unreadRequired: '请先读取 {count} 条未读更新，再继续修改。',
     staleRevision: 'Thread 已发生变化，请按最新状态重试。',
 };
@@ -280,13 +314,11 @@ export const en = {
     resumeAgent: 'Resume',
     restartAgent: 'Restart',
     restartStillUnavailable: 'Restart ran, but the Member is still unavailable: {diagnostic}',
-    restartRefusedNoRestart: 'The session log is deterministically refused with nothing repairable; restarting cannot fix it: {detail}',
     restartFailed: 'Restart failed: {message}',
     archiveAgent: 'Archive',
     archiveAgentTitle: 'Archive Agent: {name}',
     archiveAgentNotice: 'This hides {name} from every list: the session log and private memory stay on disk and active Claims release, but there is no restore entry point yet.',
     archiveAgentConfirm: 'Archive',
-    archiveAgentFailed: 'Failed to archive: {message}',
     archiveChannel: 'Archive Channel',
     archiveChannelTitle: 'Archive Channel: {name}',
     archiveChannelNotice: 'This hides {name} and all of its discussions from every list: the data stays, every Member\'s active Claims in this Channel release, but there is no restore entry point yet.',
@@ -327,9 +359,9 @@ export const en = {
     timelineLabel: 'Message timeline',
     taskClosedNotice: 'This task is closed; reopen it to continue the discussion',
     human: 'Human',
-    humanSettingsNav: 'Profile',
-    humanSettingsTitle: 'Profile',
-    humanSettingsIntro: 'This is your Agent Team profile: the name applies to Team messages and member lists, and the avatar appears beside your messages.',
+    teamSettingsNav: 'Team',
+    teamSettingsTitle: 'Team',
+    teamSettingsIntro: 'Your identity in the Team, and the endpoint jev calls.',
     humanSettingsName: 'Name',
     humanSettingsNameHint: 'Agents @ you by this name; a rename applies to later messages only.',
     humanSettingsNameEmpty: 'A name is required.',
@@ -349,13 +381,44 @@ export const en = {
     humanSettingsUnavailable: 'The profile could not be read: {message}',
     humanSettingsVersion: 'Version {version}',
     humanSettingsUpdateAvailable: 'New version {version} available — see the release notes',
+    teamJudgeGroupTitle: 'jev',
+    teamJudgeGroupHint: 'Decides whether a step after a long absence still belongs to the same piece of work. Calls go to /systemone under the apiBase, and changing the endpoint usually means changing the model too; empty inherits the deployment default.',
+    teamJudgeReady: 'jev is ready',
+    teamJudgeNoKey: 'No key yet — enter one to enable it',
+    teamJudgeUnavailable: 'jev is unavailable: check the apiBase and model',
+    teamJudgeApiBase: 'apiBase',
+    teamJudgeModel: 'model',
+    teamJudgeKey: 'key',
+    teamJudgeKeyHint: 'Write-only: an empty field saves nothing and leaves a stored key in place.',
+    teamJudgeKeySet: 'Configured',
+    teamJudgeKeyUnset: 'Not configured',
+    teamJudgeClearKey: 'Clear key',
+    teamJudgeClearHint: 'Clearing unmounts jev immediately; nothing is judged after that.',
+    teamJudgeClearBlocked: 'Save first, then clear.',
+    teamJudgeClearFailed: 'The key could not be cleared; try again.',
+    teamSettingsOverridden: 'Overridden',
+    teamSettingsReset: 'Reset',
+    teamSettingsInvalid: 'This value is not accepted.',
+    teamSettingsUnavailable: 'This deployment does not serve the Team settings document.',
+    teamSettingsReadOnly: 'Settings are read-only right now.',
+    teamSettingsSaveFailed: 'The save was not accepted; check the values and try again.',
+    teamSettingsSave: 'Save',
+    teamSettingsSaving: 'Saving…',
+    environmentOkTitle: 'Within the supported range',
+    environmentOkDetail: 'The running DSH {version} is within the range we declare support for.',
+    environmentOutOfRangeTitle: 'Outside the supported range',
+    environmentOutOfRangeDetail: 'The running DSH {version} is outside the range we declare support for — we have not certified this combination and it may misbehave.',
+    environmentRange: 'Support range: from {lower} up to, but not including, {upper}.',
+    environmentTested: 'Certified combination: Agent Team {bundle} × DSH {dsh}.',
+    environmentUndeterminedTitle: 'Environment cannot be determined',
+    environmentUndeterminedDetail: 'The running DSH version could not be read, or our support range could not be established, so no judgement is made.',
+    environmentReleaseNotes: 'See the release notes',
     taskStatusTodo: 'To do',
     taskStatusInProgress: 'In progress',
     taskStatusInReview: 'In review',
     taskStatusDone: 'Done',
     taskStatusClosed: 'Closed',
     taskLabel: 'Task #{number}',
-    taskPending: 'Task …',
     openTask: 'Open Task #{number}',
     openThread: 'Open thread',
     openTaskUnread: 'Open Task #{number} ({count} new updates)',
@@ -424,7 +487,6 @@ export const en = {
     activityReopened: '{actor} reopened this Task',
     mentionConfirmation: 'Mentioning an unfollowed member requires confirmation; send again to continue',
     memberNotFollowing: 'These Members do not follow this Thread yet: {ids}',
-    sendFailedKind: 'Unable to send message ({kind})',
     unreadRequired: 'Read {count} unread update(s) before changing this Thread.',
     staleRevision: 'This Thread changed; retry using the current state.',
 };

package/packages/tool-agent-team/README.md

@@ -7,13 +7,16 @@ Model-facing tools for Agent Team Members. The package registers tools in the ca
 ## Tools
 
 - `team_inbox` lists bounded unread Thread summaries for the calling Member, ordered by direct work and then recency; Task standing appears only where the Thread has a real Task overlay. The header states total unread/direct counts and the number of Threads shown (with a truncation conclusion when unread work lies beyond the bounded list); each item shows its exact unread/direct counts, Channel ref, and Task standing. The footer routes reading to `team_thread read`; the render carries no revision and no write token.
-- `team_thread` reads a Thread, pages history, follows, or unfollows. `threadRef` is primary; a `taskRef` is a Host alias only for released task-only Clients. The five actions render separately: `status`/`follow`/`unfollow` answer only the Attention question in one line; `read` renders outcome, Thread identity, orientation (full anchor when Host-supplied background is present, bounded anchor subject otherwise — and no background at all for a Member re-entering a Thread it has already read, so its orientation there is that subject plus this batch — never a duplicate of an in-facts anchor), active Claims only, the chronological facts with inline unread/direct markers, and a read-through/remaining-unread footer that also states how many Thread facts precede the watermark whenever the read left any behind; `history` renders a historical page with the full anchor on a first page and the bounded subject on continuation pages, never current Claims or advice. `read` advances the durable watermark and is the only read-side source of a next-write token — rendered only when no unread remains; your own committed public mutations hand off a fresh token as well. A read with nothing unread for the caller advances nothing, writes no operation, and renders `Read — no unread updates …` instead of claiming a commit, still answering from the current projection. Activity facts render structured — actor, Task ref, and the Claim refs each activity claimed, completed, accepted, or released. A read that acknowledges an unread acceptance of a still-done Task carries one `contextAdvice` block (usage, route budgets, the `min(128_000, handoffAt)` Task-boundary threshold, and one keep/rollover/handoff-now action); it is advisory only and degrades to an explicit `unavailable` line when measurement fails.
+- `team_thread` reads a Thread, pages history, follows, or unfollows. `threadRef` is primary; a `taskRef` is a Host alias only for released task-only Clients. The five actions render separately: `status`/`follow`/`unfollow` answer only the Attention question in one line; `read` renders outcome, Thread identity, orientation (full anchor when Host-supplied background is present, bounded anchor subject otherwise — and no background at all for a Member re-entering a Thread it has already read, so its orientation there is that subject plus this batch — never a duplicate of an in-facts anchor), active Claims only, the chronological facts with inline unread/direct markers, and a read-through/remaining-unread footer that also states how many Thread facts precede the watermark whenever the read left any behind; `history` renders a historical page with the full anchor on a first page and the bounded subject on continuation pages, never current Claims or advice. `read` advances the durable watermark and is the only read-side source of a next-write token — rendered only when no unread remains; your own committed public mutations hand off a fresh token as well. A read with nothing unread for the caller advances nothing, writes no operation, and renders `Read — no unread updates …` instead of claiming a commit, still answering from the current projection. Activity facts render structured — actor, Task ref, and the Claim refs each activity claimed, completed, accepted, or released. A read that acknowledges an unread acceptance of a still-done Task carries one `contextAdvice` block (usage, route budgets, the `min(128_000, handoffAt)` Task-boundary threshold, and one keep/rollover/compact-now action); it is advisory only and degrades to an explicit `unavailable` line when measurement fails.
 - `team_message` starts a top-level Thread, replies to an existing Thread, or sends a DM. It defaults to a taskless Thread; pass `asTask: true` for atomic Task creation. A committed start/reply renders one committed-verb outcome (Thread created / reply added) with the Message, Thread, and optional Task refs, and exactly one next-write token hand-off. Replies reject unread work before checking token freshness. Typed rejections begin `Not committed`, keep the structured refs and counts needed to reread and retry, and render no numeric revision or write token — recovery is read-and-reconsider. DMs distinguish `Delivered` from `Recorded, not delivered` (with the delivery note and a no-blind-duplicate warning).
 - `team_claim` lists or mutates the calling Member's Direction Claims through `list`, `claim`, `done`, and `release`; it applies only to real Tasks. `list` renders the Task/Thread identity with active Claims only (the collision surface) and no write token. A committed mutation names its action (Claim created/completed/released), renders the authoritative affected Claim first, and hands off one next-write token. Rejections share the message rejection form. Direction exclusion uses Unicode NFKC normalization, trim, whitespace compression, and deterministic case folding.
 - `team_view` is the address book: bounded, membership-authorized Channel, top-level Thread, and Member summaries — current addresses, not a work queue. Threads are the sole paginated catalog: newest-first rows carrying threadRef, Channel ref, a bounded anchor subject, and Task standing inline (never a second Task index, never revision or message count). The cursor pages Thread rows only; continuation pages render Threads alone, and paging reaches every authorized top-level Thread, including taskless and off-page taskful ones.
-- `context_rollover` schedules one rollover of the calling Member into a fresh context. The tool validates the bounded private `handoff` (plus optional `relatedFiles`, or a `checkpointRef` to return to a recorded checkpoint instead) against the Host, concludes the turn, and returns `status: 'scheduled'`; the Host performs the actual swap only after the successful tool result is durably appended. The `checkpointRef` copy is hardened on both the tool and parameter descriptions: omit it for ordinary generation changes and pressure-driven handoffs, and supply it only when citing the exact ref a `context_timeline` result listed as restorable — never a synthesized or guessed one. A `checkpointRef` that cannot succeed now — fabricated, unresolved, unattributable, nonshrinking, unmeasurable, over-budget, or blocked by multiple active Claims — rejects as a model-visible error result instead of a fake `scheduled`; the mutable guards (jobs, route limits) are revalidated at the swap seam, and a seam failure leaves the Member recoverable through a later-turn fresh rollover. `context_rollover` and `context_checkpoint` both conclude the Agent turn.
+- `context_rollover` schedules one rollover of the calling Member into a fresh context. The tool validates the bounded private `handoff` (plus optional `relatedFiles`, or a `checkpointRef` to return to a recorded checkpoint instead) against the Host, concludes the turn, and returns `status: 'scheduled'`; the Host performs the actual swap only after the successful tool result is durably appended. The `checkpointRef` copy is hardened on both the tool and parameter descriptions: omit it for ordinary generation changes and pressure-driven handoffs, and supply it only when citing the exact ref a `context_status` result listed as restorable — never a synthesized or guessed one. A `checkpointRef` that cannot succeed now — fabricated, unresolved, unattributable, nonshrinking, unmeasurable, over-budget, or blocked by multiple active Claims — rejects as a model-visible error result instead of a fake `scheduled`; the mutable guards (jobs, route limits) are revalidated at the swap seam, and a seam failure leaves the Member recoverable through a later-turn fresh rollover. `context_rollover` and `context_checkpoint` both conclude the Agent turn.
 - `context_checkpoint` records one named checkpoint of the calling Member's current context. The durable checkpoint is the successful `tool/call`+`tool/result` pair the Session projection folds; the returned ref is deterministic from the Member Session identity plus the tool call id. It performs no lifecycle side effect in the tool body and concludes the turn: a checkpoint resolves at its containing turn's end, so the model records it as its final action of a completed unit of work.
-- `context_timeline` returns one bounded structural view of the Member's context generations across the current Session and its archived ancestor lineage: recorded checkpoints and handoff/Team/compaction boundaries, with restorability reasons where a return cannot be proven safe. A Team boundary is offered exactly when the retained prefix through it stays inside one Thread and the return would shrink the working set below the handoff budget. Each row carries a short stable `anchor` id, a digest of that row's own ref, so rows that share a name and a price stay distinguishable — it is not a ref, and only the `checkpointRef` printed on a restorable row is citable. Structural only — no transcript content. A fresh `context_rollover` never requires consulting the timeline first.
+- `context_status` returns one bounded structural view of the Member's context generations across the current Session and its archived ancestor lineage: recorded checkpoints and handoff/Team/compaction boundaries, with restorability reasons where a return cannot be proven safe, plus the Member's usage against the handoff budget and, where the scope can price one, what a compaction started now would replace. A Team boundary is offered exactly when the retained prefix through it stays inside one Thread and the return would shrink the working set below the handoff budget. On a row that is not restorable the Team answers with a short stable `anchor` digest of that row's own ref, so rows sharing a name and a price stay distinguishable and no non-selectable row carries a citable string; only the `ref` printed on a restorable row can be cited. Structural only — no transcript content. A fresh `context_rollover` never requires reading the status first.
+- `context_compact` shortens the calling Member's current generation in place: one stretch of older history is replaced by a summary while the newest work stays verbatim. It never switches generation and never returns to an anchor. A Member whose preset mounts no compaction engine is told the capability is unavailable in this scope, and a context with nothing safe to replace reports itself unchanged.
+
+All four context tools are the engine's own definitions, built by `createContinuityTools`: the engine owns their argument contract, the anti-forgery gate on a cited ref, the turn-conclusion timing, and the render shapes, while the Team supplies its vocabulary and the adapter behind them.
 
 Mentions are authored in the Message body, as `@Handle` (the `@` is required, matching ignores case, and `@all` reaches the Channel); there is no recipient parameter. An Agent cannot silently enroll an uninvited Member: naming one this Thread has never carried commits the Message, delivers nothing to that Member, and reports them as undelivered. Human confirmation is a separate Host/Client flow. Closed Tasks reject replies, Claims, and new Attention until a Human reopens them; taskless Threads have no Claim or Task-resolution mutation path.
 

package/packages/tool-agent-team/README.zh.md

@@ -7,13 +7,16 @@
 ## 工具
 
 - `team_inbox` 列出调用方 Member 的有界未读 Thread 摘要，先按 direct work、再按最近活动排序；只有 Thread 存在真实 Task overlay 时才出现 Task standing。header 给出 unread/direct 总数与展示的 Threads 数（有界列表之外仍有未读时给出截断结论）；每个条目显示精确的 unread/direct 计数、Channel ref 与 Task standing。页脚把阅读指向 `team_thread read`；渲染不携带 revision 与写令牌。
-- `team_thread` 读取 Thread、分页历史、follow 或 unfollow。`threadRef` 是主身份；`taskRef` 只对 released task-only Client 是 Host alias。五个 action 分开渲染：`status`/`follow`/`unfollow` 一行只回答 Attention 问题；`read` 渲染结果、Thread 身份、导向（有 Host 提供的 background 时给 full anchor，否则给 bounded anchor subject——重新进入自己读过的 Thread 的 Member 完全没有 background，它在那里的定位就是该 subject 加本次 batch——anchor 已在 facts 中时绝不重复）、只含 active Claims、带行内 unread/direct 标记的按时间 facts、read-through/剩余未读页脚（只要这次 read 身后留有 Thread facts，页脚同时给出那些 facts 的数量）；`history` 渲染历史页（首页 full anchor、continuation 页 bounded subject，绝无当前 Claims 或 advice）。`read` 推进持久 watermark，是 next-write token 的读侧唯一来源——仅在未读清零时渲染；你自己的已提交 public mutation 也会回传一份新 token。一次对调用者没有未读的 read 什么都不推进、不写任何 operation，渲染也不再声称提交（`Read — no unread updates …`），画面仍来自当前 projection。Activity facts 结构化渲染——actor、Task ref，以及每条 activity claim、完成、接受或 release 的 Claim refs。确认仍为 done 状态 Task 的未读验收的那次 read 附带一段 `contextAdvice`（用量、路由预算、`min(128_000, handoffAt)` 任务边界阈值、keep/rollover/handoff-now 唯一动作）；它只是建议，测量失败时降级为显式 `unavailable` 文案。
+- `team_thread` 读取 Thread、分页历史、follow 或 unfollow。`threadRef` 是主身份；`taskRef` 只对 released task-only Client 是 Host alias。五个 action 分开渲染：`status`/`follow`/`unfollow` 一行只回答 Attention 问题；`read` 渲染结果、Thread 身份、导向（有 Host 提供的 background 时给 full anchor，否则给 bounded anchor subject——重新进入自己读过的 Thread 的 Member 完全没有 background，它在那里的定位就是该 subject 加本次 batch——anchor 已在 facts 中时绝不重复）、只含 active Claims、带行内 unread/direct 标记的按时间 facts、read-through/剩余未读页脚（只要这次 read 身后留有 Thread facts，页脚同时给出那些 facts 的数量）；`history` 渲染历史页（首页 full anchor、continuation 页 bounded subject，绝无当前 Claims 或 advice）。`read` 推进持久 watermark，是 next-write token 的读侧唯一来源——仅在未读清零时渲染；你自己的已提交 public mutation 也会回传一份新 token。一次对调用者没有未读的 read 什么都不推进、不写任何 operation，渲染也不再声称提交（`Read — no unread updates …`），画面仍来自当前 projection。Activity facts 结构化渲染——actor、Task ref，以及每条 activity claim、完成、接受或 release 的 Claim refs。确认仍为 done 状态 Task 的未读验收的那次 read 附带一段 `contextAdvice`（用量、路由预算、`min(128_000, handoffAt)` 任务边界阈值、keep/rollover/compact-now 唯一动作）；它只是建议，测量失败时降级为显式 `unavailable` 文案。
 - `team_message` 创建顶层 Thread、回复既有 Thread 或发送 DM。默认创建 taskless Thread；传入 `asTask: true` 才原子创建 Task。commit 的 start/reply 渲染一个 committed-verb 结果（Thread created / reply added），携带 Message、Thread 与可选 Task refs，以及恰好一个 next-write token hand-off。Reply 在检查令牌新鲜度前先拒绝未读工作。类型化拒绝以 `Not committed` 开头，保留重读与审慎重试所需的结构化 refs 与计数，不渲染数字 revision 或写令牌——恢复路径是 read-and-reconsider。DM 区分 `Delivered` 与 `Recorded, not delivered`（携带 delivery note 与禁止盲目重发的警告）。
 - `team_claim` 通过 `list`、`claim`、`done`、`release` 读取或修改调用方 Member 的 Direction Claim；它只适用于真实 Task。`list` 渲染 Task/Thread 身份与只有 active Claims 的 collision surface，且无写令牌。commit 的 mutation 点名动作（Claim created/completed/released），先渲染权威的受影响 Claim，再 hand-off 一个 next-write token。拒绝与 message 拒绝共享同一形式。Direction 互斥键执行 Unicode NFKC normalization、trim、空白压缩和确定性大小写折叠。
 - `team_view` 是 address book：有界、按 membership 授权的 Channel、顶层 Thread 与 Member 摘要——是当前的地址簿，不是工作队列。Threads 是唯一分页目录：newest-first 行携带 threadRef、Channel ref、bounded anchor subject 与行内 Task standing（绝无第二个 Task 索引，也不渲染 revision 或消息数）。cursor 只延续 Thread 行；continuation 页只渲染 Threads，翻页可达全部获授权的顶层 Threads，包括 taskless 与不在首页的 taskful。
-- `context_rollover` 为调用方 Member 安排一次进入全新上下文的 rollover。工具向 Host 校验有界的私有 `handoff`（及可选 `relatedFiles`；传入 `checkpointRef` 则改为回返到已记录的 checkpoint），结束当前 turn 并返回 `status: 'scheduled'`；Host 只在成功的 tool result 持久落盘后才执行真正的换窗。`checkpointRef` 在工具与参数两级 description 上做了 copy hardening：普通续代与压力换窗必须省略，只有引用 `context_timeline` 结果中列为 restorable 的精确 ref 时才提供——绝不合成或猜测。当下不可能成功的 `checkpointRef`——伪造、未 resolve、无法归属、不缩减、不可测量、超预算或被多个 active Claim 阻塞——以 model-visible 的 error result 拒绝，而不是返回假 `scheduled`；可变 guards（jobs、route limits）在换窗 seam 复查，seam 失败后 Member 仍可通过后续 turn 的显式 fresh rollover 恢复。`context_rollover` 与 `context_checkpoint` 都会结束 Agent turn（换窗后不得再接旧代工作；checkpoint 在其所属 turn 结束时 resolve）。
+- `context_rollover` 为调用方 Member 安排一次进入全新上下文的 rollover。工具向 Host 校验有界的私有 `handoff`（及可选 `relatedFiles`；传入 `checkpointRef` 则改为回返到已记录的 checkpoint），结束当前 turn 并返回 `status: 'scheduled'`；Host 只在成功的 tool result 持久落盘后才执行真正的换窗。`checkpointRef` 在工具与参数两级 description 上做了 copy hardening：普通续代与压力换窗必须省略，只有引用 `context_status` 结果中列为 restorable 的精确 ref 时才提供——绝不合成或猜测。当下不可能成功的 `checkpointRef`——伪造、未 resolve、无法归属、不缩减、不可测量、超预算或被多个 active Claim 阻塞——以 model-visible 的 error result 拒绝，而不是返回假 `scheduled`；可变 guards（jobs、route limits）在换窗 seam 复查，seam 失败后 Member 仍可通过后续 turn 的显式 fresh rollover 恢复。`context_rollover` 与 `context_checkpoint` 都会结束 Agent turn（换窗后不得再接旧代工作；checkpoint 在其所属 turn 结束时 resolve）。
 - `context_checkpoint` 为调用的 Member 记录一个命名的当前上下文 checkpoint。durable checkpoint 就是 Session projection 折叠的成功 `tool/call`+`tool/result` 对；返回的 ref 由 Member Session 身份加 tool call id 确定性派生。工具体不做 lifecycle 副作用，但会结束 turn：checkpoint 在其所属 turn 结束时 resolve，因此模型把它作为一个完整工作单元的最后动作来记录。
-- `context_timeline` 返回该 Member 跨当前 Session 与已归档祖先 lineage 的上下文代际有界结构视图：已记录的 checkpoints 与 handoff/Team/compaction 边界，无法证明可安全回返的条目携带拒绝原因。Team 边界只有在「经它保留的前缀仍停留在单一 Thread 内」且回返能把工作集缩到 handoff 预算之下时才会被提供。每一行附一个短的稳定 `anchor` id（该行自身 ref 的摘要），使名称与价格相同的行仍可区分——它不是 ref，只有 restorable 行上打印的 `checkpointRef` 可被引用。仅结构信息——不含任何 transcript 正文。fresh 的 `context_rollover` 从不需要先查 timeline。
+- `context_status` 返回该 Member 跨当前 Session 与已归档祖先 lineage 的上下文代际有界结构视图：已记录的 checkpoints 与 handoff/Team/compaction 边界，无法证明可安全回返的条目携带拒绝原因；同时给出该 Member 相对 handoff 预算的用量，以及作用域能定价时此刻发起 compaction 会替换的内容。Team 边界只有在「经它保留的前缀仍停留在单一 Thread 内」且回返能把工作集缩到 handoff 预算之下时才会被提供。对不可返回的行，Team 以该行自身 ref 的短稳定 `anchor` 摘要作答，使名称与价格相同的行仍可区分，且任何不可选择的行都不携带可引用的字符串；只有 restorable 行上打印的 `ref` 可被引用。仅结构信息——不含任何 transcript 正文。fresh 的 `context_rollover` 从不需要先读 status。
+- `context_compact` 就地缩短调用方 Member 的当前代：较早历史中的一段被替换为摘要，最新工作保持原文。它绝不切换代际，也绝不回返到锚点。preset 未挂载 compaction 引擎的 Member 会被告知该能力在此作用域不可用；没有可安全替换内容的上下文会报告自身未改变。
+
+四个 context 工具全部用引擎自己的定义（`createContinuityTools`）：参数契约、对引用 ref 的 anti-forgery 门、结束 turn 的时机与渲染形状都由引擎负责，Team 只提供自己的词汇与它们背后的 adapter。
 
 mention 在 Message 正文里撰写，形如 `@Handle`（`@` 必需、大小写不敏感，`@all` 触达整个 Channel）；不存在收件人参数。Agent 无法静默加入未被邀请的 Member：mention 一个该 Thread 从未承载过的 Member 时 Message 照常提交，但不向其送达，并在结果里报告为未送达。Human confirmation 属于单独的 Host/Client 流程。Closed Task 在 Human reopen 前拒绝 reply、Claim 和新的 Attention；taskless Thread 没有 Claim 或 Task resolution mutation path。