Frontend: Team Automations scoped AgentKey API 接入（blocked on backend contract）

[potter-sun]

当前治理 ownership 边界

#2743 保留最终 member-scoped frontend writer 角色；#2676 仅作 umbrella 与 acceptance tracking，二者不认领同一 writer surface。

本项保持 crnd:phase:blocked dependency wait；不丢弃任何 product work。

背景

Parent / umbrella: #2676

本 issue 承接 #2676 中真实后端 API 接入的部分。当前必须保持 blocked，直到后端完成 Team Automation dedicated AgentKey contract。不能用 generic /api/schedules、Account raw-key 管理页、一次性 full_key 展示或 senderNyxId schedule auth 替代。

Blocked by

• 定时调用凭证：补齐 agent key 双轨撤销、失败补偿与 allowlist fail-closed #2728：现有 catalog scheduled-agent 单一 provisioning / 双轨补偿前置。
• 定时调用凭证：修复 workflow Agent Key 的 DurableCallerCredentialRef 不变量 #2736：tag-7 workflow dispatch 必须映射为 DurableCallerCredentialRef，raw key 不进入 LlmControl / Envelope / state / event / readmodel。
• 定时调用凭证：统一强类型授权计划与 exact NyxID service/node grants #2737：统一 typed authorization plan，分离 Aevatar invocation target 与 exact NyxID service/node grants，返回 permissionDigest / policyVersion / disclosure facts。
• Team Automation：将 scheduled credential lifecycle 扩展到 schedule actor #2738：schedule actor 持有 Team automation provisioning / rotation / revocation Saga，含 operation id、owner descriptor、expiry committed status。
• Team Automation：提供 canonical command API 与 credential health current-state read model #2739：canonical Team/member API 与 credential-health current-state read model。

等待的后端 contract

前端以 #2739 最终 contract 为准，预期至少需要 scoped endpoints：

GET /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations
POST /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations:preflight
POST /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations
GET /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations/{scheduleId}
PATCH /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations/{scheduleId}
DELETE /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations/{scheduleId}
POST /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations/{scheduleId}:reauthorize
POST /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations/{scheduleId}:pause
POST /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations/{scheduleId}:resume
POST /api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations/{scheduleId}:run-now

Read model / DTO 至少需要：

• typed owner (scopeId, memberId)，teamId 仅作为当前 containment 验证路径；
• authorizationStatus；
• credentialSourceKind；
• keyExpiresAt；
• lastAuthorizationErrorCode；
• permissionDigest；
• policyVersion；
• typed invocationTarget；
• typed nyxIdServiceGrants 与 nyxIdNodeGrants；
• typed disclosure facts/codes。

前端接入范围

• 将 TeamAutomationsTab 从 generic scheduledDispatchApi.listAll/create/update/delete/enable/disable/runNow 迁移到 scoped teamAutomationApi。
• Team UI 不再全局 list schedules 后按 serviceKey / publishedServiceId 过滤。
• preflight 后展示后端 typed authorization plan，不在前端推导 service/node grants。
• create/update/reauthorize 只提交 schedule config、typed authorization intent、permissionDigest、policyVersion、idempotency/operation key；不提交 secret 或 credential IDs。
• 根据 readmodel 显示 Authorizing / Active / Needs authorization / Revocation pending / Failed 等状态。
• pause/resume/run-now/delete 全部走 scoped API，并验证错误状态不会泄漏跨 scope/team/member 资源存在性。

明确不做

• 不调用 generic /api/schedules 访问 Team-owned automation；后端 generic route 会排除/拒绝 Team records。
• 不调用 NyxID create-key。
• 不展示、缓存、提交或测试快照保存 fullKey、OAuth token、SecretReference、apiKeyId。
• 不把 accepted ACK 当 provisioning committed；UI 必须等待 readmodel/operation 状态。

验收

• Team automation list/detail/create/update/delete/pause/resume/run-now 全部使用 scoped Team/member API。
• 前端创建只发一个 Team/member scoped application command。
• authorization_plan_changed 会刷新 plan 并要求重新 consent。
• Needs authorization 可原地 reauthorize 且表单内容不丢失。
• Revocation pending 不被显示成凭证已删除。
• 所有测试 fixture 使用不同身份：m-alpha / wf-alpha / svc-alpha / sch-alpha / ak-alpha。
• 测试断言不会调用 /api/schedules 访问 Team-owned records。
• 测试断言 payload/cache/snapshot 无 fullKey、OAuth token、SecretReference、apiKeyId。

⟦AI:AUTO-LOOP⟧

[potter-sun]

github-devloop intake decision: enable
Service class: standard

Reason:
Least-privilege scoped-API and secret-boundary practice supports TeamAutomationsTab -> teamAutomationApi; this is a concrete frontend integration blocked on #2739, not an umbrella or recurring instance.

[potter-sun]

github-devloop thinking: consensus started

[potter-sun]

github-devloop decision: approve
Three-angle verdicts: teleology=approve parsimony=approve fidelity=approve

teleology:
Approve: #2743 is sound, bounded, and verifiable; it waits for the backend contract, rejects unsafe substitutes like generic /api/schedules, Account raw-key flows, full_key, and senderNyxId, and gives concrete frontend acceptance checks aligned with least-privilege credential handling and server-authored authorization.

parsimony:
approve: the proposal follows established least-privilege, server-authoritative credential and scoped API practice, and its parsimony is sound because it removes generic schedule access, client-side filtering, raw-key handling, and frontend-derived grants instead of adding compensating branches; advisory only, the future PR should treat #2739 as the sole contract authority and avoid hardcoding the provisional endpoint shape until that backend contract lands.

fidelity:
This proposal is sound, bounded, and worth advancing while blocked: it measures the real security and product behavior rather than a UI proxy, defers authority to the backend contract, forbids known unsafe substitutes such as generic /api/schedules, raw key creation/display, and accepted-ACK-as-committed, and gives concrete acceptance tests that future code can verify. Advisory: future PR review should check the actual generated/request DTOs against #2739 rather than trusting the endpoint sketch in this issue.

⟦AI:FKST⟧