@fitlab-ai/agent-infra 0.9.14 → 0.10.0

package/templates/.agents/skills/run-manual-validation/SKILL.en.md

@@ -14,6 +14,8 @@ Lifecycle events require explicit trigger data: use `{trigger-initiator}=orchest
 
 The entry point may omit the task ref; explicit task scope accepts only `--task <ref>` or `-t <ref>`, and positional task refs are not interpreted. Parse `--scope`, `--timeout`, and `--format` before `--`, preserve the user command after `--` verbatim, then call `agent-infra-internal task-context resolve {task-scope}`. Pass through resolution failures without scanning tasks locally. The internal `task-validate` protocol continues to use a positional task ref.
 
+For cross-environment validation (the task workspace lives on another host), pass `--branch <ref>` explicitly to enter the branch-only fallback: skip `task-context resolve` and use that branch ref directly as the positional argument of `task-validate`, which returns branch-only evidence with `taskId: null`. Without `--branch`, a resolution failure is still passed through; never degrade silently. `--task` and `--branch` are mutually exclusive.
+
 ## Boundary
 
 ### Persisted Report Evidence
@@ -23,8 +25,9 @@ Before generating a validation report, read `.agents/rules/evidence-reporting.md
 - Select the validation mode, call the sole mechanical entry point, and record evidence; do not mark PR manual validation complete.
 - `complete-manual-validation` remains the maintainer's final registration after coverage is judged sufficient.
 - Never manipulate temporary worktrees, leases, or containers directly; only call `agent-infra-internal task-validate`.
-- Never record tokens, environment variables, full argv, absolute user paths, or raw transcripts in the artifact.
+- Never record tokens, environment variables, full argv, absolute user paths, or raw transcripts in the artifact; the core must write one current-only evidence envelope for each validation target.
 - Before generating a validation artifact Markdown file that will be synced to an Issue, read `.agents/rules/sync-content-generation.md` and follow its generator-side constraints; Issue sync remains transparent and does not parse or rewrite the body.
+- The branch-only fallback writes to `.agents/workspace/validations/{branch-slug}/` and is marked `recoverable: false`: no task.md write-back, no lifecycle events, no Issue sync, no `task-verify`; the artifact must be carried back to the host that owns the task workspace for registration.
 
 ## Step 0: State Check (pre-execution hard gate)
 
@@ -34,20 +37,34 @@ Resolve the task reference, then run this command and record the task/artifact s
 agent-infra-internal task-snapshot {task-id} --format text
 ```
 
+Branch-only has no `{task-id}`: skip this step and record `not-applicable (branch-only)` in the artifact's `## State Check` section.
+
 ## Steps
 
 1. Read `reference/discovery-and-execution.md` and parse the input mode. Stop before started without an artifact for invalid or partial input.
 2. Run `agent-infra-internal task-artifact {task-id} inspect --family validation-run` and read the latest review-code manual-validation items. Then run `agent-infra-internal platform-pr inspect {task-id}` and use the reference status matrix to discover, merge, and number items. Only automatic mode stops before started when reliable sources are empty or the sole possible source is unreadable; valid explicit mode always continues with the user command as effective work.
 3. Take the round and artifact name from the core result. After confirming valid explicit work or a non-empty discovered list, run `agent-infra-internal task-event {task-id} validation-run.started --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code}` and classify each item as `executable|unavailable|unknown|unsafe|unresolved`.
-4. Invoke every executable item separately with `agent-infra-internal task-validate {task-ref} --scope snapshot --format json -- {command...}`. Only make a second explicit inplace invocation for that item when evidence proves it is required. If no item is executable, run no fabricated command but still produce coverage-gap evidence.
+4. Allocate an `{evidence-file}` for each validation target and invoke every executable item separately with `agent-infra-internal task-validate {task-ref} --scope snapshot --format json --evidence-file {evidence-file} -- {command...}`. Only make a second explicit inplace invocation for that item when evidence proves it is required, using its evidence file. If no item is executable, run no fabricated command but still produce coverage-gap evidence.
 5. Read `reference/report-template.md`, create `validation-run.md|validation-run-r{N}.md`, and record the input mode, discovered list, per-item results, CLI JSON allowlist, and sanitized summaries.
 6. Run `agent-infra-internal task-event {task-id} validation-run.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {artifact}`. When an Issue exists, run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}` and then `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {artifact} --agent {standard-agent-token}`.
 7. Run `agent-infra-internal task-verify {task-id} validation-run.completed --artifact {artifact} --format text`; fix failures and rerun it.
 8. Report the evidence path, coverage gaps, and verification result; explicitly leave the decision to run `complete-manual-validation` to the maintainer. Read `.agents/rules/next-step-output.md` and end with `Completed at`.
 
+## Scenario B: Branch-Only Fallback
+
+With `--branch <ref>`, only the following differ from the steps above; every other constraint (classification, per-item execution, sanitization, never changing PR manual validation state) still applies.
+
+- **Explicit mode only**: `task-artifact` and `platform-pr inspect` both require a task ref, so branch-only cannot discover items. Stop before writing any artifact when the user command after `--` is missing.
+- **Skip Step 0 and the Step 2 discovery**: record both sources as `unavailable` and list this round's items under the `explicit` source in the artifact's `## Discovered Items` section.
+- **Step 3 skips only the event call**: emit no `validation-run.started`, but still classify every item as `executable|unavailable|unknown|unsafe|unresolved`.
+- **Step 4 runs unchanged**: write evidence files in the same branch-only validation directory and invoke `agent-infra-internal task-validate {branch-ref} --scope snapshot --format json --evidence-file {evidence-file} -- {command...}`.
+- **Step 5 relocates the artifact**: write `.agents/workspace/validations/{branch-slug}/validation-run.md|validation-run-r{N}.md` using the same `reference/report-template.md`. Derive `{branch-slug}` from the `--branch` ref character by character: keep `[A-Za-z0-9._-]` and replace everything else (including `/`) with `-`, so the result is a single path segment; if the result is empty or consists only of `.`, treat it as invalid input and stop before writing any artifact.
+- **Skip Steps 6 and 7**: emit no `validation-run.completed`, run no `platform-comment sync`, and run no `task-verify`.
+- **Step 8 adds a notice**: state that the artifact is unrecoverable and unregistered, and must be carried back to the host owning the task workspace before a maintainer runs `complete-manual-validation`.
+
 ## Completion Checklist
 
 - [ ] Used `agent-infra-internal task-validate` for every executable item, or recorded that none were executable
 - [ ] Recorded sanitized validation-run evidence
 - [ ] Did not change PR manual validation completion state
-- [ ] Updated task.md and passed completion verification
+- [ ] Updated task.md and passed completion verification (branch-only instead: recorded `recoverable: false` and left the task ledger untouched)

package/templates/.agents/skills/run-manual-validation/SKILL.zh-CN.md

@@ -14,6 +14,8 @@ description: >
 
 入口可省略 task ref；显式 task scope 仅接受 `--task <ref>` 或 `-t <ref>`，不再解释位置 task ref。先解析 `--scope`、`--timeout`、`--format`，在 `--` 后原样保留用户命令，再调用 `agent-infra-internal task-context resolve {task-scope}`。解析失败时透传非零退出码，不自行扫描任务。内部 `task-validate` 协议仍使用位置 task ref。
 
+跨环境校验（任务工作区在另一台宿主）显式传 `--branch <ref>` 进入 branch-only 降级路径：不调用 `task-context resolve`，直接以该分支 ref 作为 `task-validate` 的位置参数，核心据此返回 `taskId: null` 的 branch-only 证据。未传 `--branch` 时解析失败仍透传非零退出码，不得静默降级。`--task` 与 `--branch` 互斥。
+
 ## 行为边界
 
 ### 持久化报告证据
@@ -23,8 +25,9 @@ description: >
 - 本技能负责选择校验模式、调用唯一机械入口并记录证据；不把 PR 人工校验标为完成。
 - `complete-manual-validation` 仍是维护者确认覆盖充分后的最终登记入口。
 - 禁止直接操作临时 worktree、lease 或 container；只调用 `agent-infra-internal task-validate`。
-- 产物不得记录 token、环境变量、完整 argv、绝对用户路径或原始 transcript。
+- 产物不得记录 token、环境变量、完整 argv、绝对用户路径或原始 transcript；每个验证目标必须由核心写入同一 current-only evidence envelope。
 - 生成会同步到 Issue 的验证 artifact Markdown 前，先读取 `.agents/rules/sync-content-generation.md` 并遵循其中的生成端约束；Issue 同步保持透明，不解析或改写正文。
+- branch-only 降级路径走 `.agents/workspace/validations/{branch-slug}/`，标记 `recoverable: false`：不写 task.md、不发 lifecycle 事件、不同步 Issue、不跑 `task-verify`；产物须带回宿主机，由维护者登记。
 
 ## 第 0 步：状态核对（执行前硬约束）
 
@@ -34,20 +37,34 @@ description: >
 agent-infra-internal task-snapshot {task-id} --format text
 ```
 
+branch-only 无 `{task-id}`，跳过本步，并在产物 `## 状态核对` 记录 `not-applicable (branch-only)`。
+
 ## 执行步骤
 
 1. 读取 `reference/discovery-and-execution.md`，解析输入模式；非法或半截输入在 started 前停止，不写产物。
 2. 运行 `agent-infra-internal task-artifact {task-id} inspect --family validation-run`，读取最新 review-code 人工校验项；再运行 `agent-infra-internal platform-pr inspect {task-id}`，按 reference 的状态矩阵发现、归并并编号。仅在自动模式下，可靠来源无项或唯一可能来源不可读时才在 started 前停止；合法显式模式始终以用户命令作为有效工作继续。
 3. 从核心结果取得轮次和产物名；确认存在有效显式工作或非空发现清单后，运行 `agent-infra-internal task-event {task-id} validation-run.started --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code}`，并逐项分类为 `executable|unavailable|unknown|unsafe|unresolved`。
-4. 每个可执行项分别调用 `agent-infra-internal task-validate {task-ref} --scope snapshot --format json -- {command...}`；只有证据表明必须原位时才对该项进行第二次显式 inplace 调用。零项可执行时不运行伪造命令，但仍继续产出覆盖缺口证据。
+4. 为每个验证目标分配 `{evidence-file}`，分别调用 `agent-infra-internal task-validate {task-ref} --scope snapshot --format json --evidence-file {evidence-file} -- {command...}`；只有证据表明必须原位时才对该项进行第二次显式 inplace 调用并写入对应 evidence 文件。零项可执行时不运行伪造命令，但仍继续产出覆盖缺口证据。
 5. 读取 `reference/report-template.md`，创建 `validation-run.md|validation-run-r{N}.md`；记录输入模式、发现清单、逐项结果、CLI JSON allowlist 与去敏摘要。
 6. 运行 `agent-infra-internal task-event {task-id} validation-run.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {artifact}`。存在 Issue 时依次运行 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}` 和 `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {artifact} --agent {standard-agent-token}`。
 7. 运行 `agent-infra-internal task-verify {task-id} validation-run.completed --artifact {artifact} --format text`；未通过则修复后重跑。
 8. 告知用户证据路径、覆盖缺口和验证结果；明确仍需维护者判断是否执行 `complete-manual-validation`。读取 `.agents/rules/next-step-output.md`，最后一行输出 `Completed at`。
 
+## 场景 B：branch-only 降级
+
+传入 `--branch <ref>` 时，相对上述步骤只有以下差异；其余约束（分类、逐项执行、去敏、不改 PR 人工验证完成状态）不变。
+
+- **仅接受显式模式**：`task-artifact` 和 `platform-pr inspect` 都要求 task ref，branch-only 无法自动发现。缺少 `--` 后的用户命令时，在写入任何产物前停止。
+- **跳过第 0 步与第 2 步的发现**：把两个来源记为 `unavailable`，并在产物 `## 发现清单` 用 `explicit` 来源登记本轮项。
+- **第 3 步只跳过事件调用**：不发 `validation-run.started`，但逐项分类为 `executable|unavailable|unknown|unsafe|unresolved` 照常执行。
+- **第 4 步照常执行**：将 evidence 文件写入同一 branch-only validation 目录，调用 `agent-infra-internal task-validate {branch-ref} --scope snapshot --format json --evidence-file {evidence-file} -- {command...}`。
+- **第 5 步改写产物位置**：写入 `.agents/workspace/validations/{branch-slug}/validation-run.md|validation-run-r{N}.md`，沿用同一份 `reference/report-template.md`。`{branch-slug}` 由 `--branch` 的 ref 逐字符转换：保留 `[A-Za-z0-9._-]`，其余（含 `/`）一律换成 `-`，结果必须是单层目录名；若结果为空或仅由 `.` 组成，判为非法输入并在写入任何产物前停止。
+- **跳过第 6、7 步**：不发 `validation-run.completed`，不做 `platform-comment sync`，不跑 `task-verify`。
+- **第 8 步追加提示**：明确告知产物不可恢复、未登记账本，需带回持有任务工作区的宿主机后再由维护者执行 `complete-manual-validation`。
+
 ## 完成检查清单
 
 - [ ] 每个可执行项均已使用 `agent-infra-internal task-validate`，或已记录零项可执行
 - [ ] 已记录去敏 validation-run 证据
 - [ ] 未修改 PR 人工验证完成状态
-- [ ] 已更新 task.md 并通过完成校验
+- [ ] 已更新 task.md 并通过完成校验（branch-only 改为：已记录 `recoverable: false` 且未触碰任务账本）

package/templates/.agents/skills/run-manual-validation/config/verify.en.json

@@ -12,7 +12,7 @@
     "activity-log": { "expected_action_pattern": "Run Manual Validation \\(Round \\d+\\)" },
     "review-ledger": { "stage_scope": ["analysis", "plan", "code"] },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "when": "platform_issue_identity_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,

package/templates/.agents/skills/run-manual-validation/config/verify.zh-CN.json

@@ -12,7 +12,7 @@
     "activity-log": { "expected_action_pattern": "Run Manual Validation \\(Round \\d+\\)" },
     "review-ledger": { "stage_scope": ["analysis", "plan", "code"] },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "when": "platform_issue_identity_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,

package/templates/.agents/skills/run-manual-validation/reference/discovery-and-execution.en.md

@@ -10,9 +10,12 @@ Read this file before parsing input, discovering manual-validation items, or con
 | A literal `--` is present but the target or command is empty | Invalid input; stop before `validation-run.started` |
 | No `--` and only a task ref | Automatic mode |
 | No `--` and additional positional arguments | Invalid or partial input; do not ignore arguments or guess a command |
+| `--branch <ref>` is passed | Branch-only fallback; must also be explicit mode, so a missing command after `--` is invalid input |
 
 Explicit mode still reads available sources to map coverage, but it must not synthesize another command for the same target. Only automatic mode constructs actions for discovered items.
 
+Branch-only has no task ref, so both discovery sources are unreadable and are recorded as `unavailable`; this round's items are listed under the `explicit` source and must not trigger the automatic-mode source stop conditions.
+
 ## Work Gate Matrix
 
 | mode | source state | gate |
@@ -58,7 +61,7 @@ Only `executable` items may run. Commands must not expose credentials, environme
 1. Invoke each executable item separately:
 
    ```bash
-   agent-infra-internal task-validate {task-ref} --scope snapshot --format json -- {command...}
+   agent-infra-internal task-validate {task-ref|branch-ref} --scope snapshot --format json -- {command...}
    ```
 
 2. Only when the item or first-run evidence proves a dependency on uncommitted content, original mounts, or in-place permissions, explicitly invoke that item a second time with `--scope inplace` and record the reason.

package/templates/.agents/skills/run-manual-validation/reference/discovery-and-execution.zh-CN.md

@@ -10,9 +10,12 @@
 | 存在 literal `--`，但目标或命令为空 | 非法输入；在 `validation-run.started` 前停止 |
 | 不存在 `--`，且只有 task ref | 自动模式 |
 | 不存在 `--`，但还有位置参数 | 非法/半截输入；不得忽略参数或猜测命令 |
+| 传入 `--branch <ref>` | branch-only 降级；必须同时是显式模式，缺少 `--` 后命令即非法输入 |
 
 显式模式也要读取可用来源以映射覆盖范围，但不得为同一目标另行合成命令。自动模式才为发现项构造动作。
 
+branch-only 没有 task ref，两个发现来源都不可读，一律记为 `unavailable`；本轮项以 `explicit` 来源登记，不得据此触发自动模式的来源停止条件。
+
 ## 工作门禁矩阵
 
 | mode | source state | gate |
@@ -58,7 +61,7 @@
 1. 每个可执行项分别调用：
 
    ```bash
-   agent-infra-internal task-validate {task-ref} --scope snapshot --format json -- {command...}
+   agent-infra-internal task-validate {task-ref|branch-ref} --scope snapshot --format json -- {command...}
    ```
 
 2. 仅当项目要求或首次证据证明依赖未提交内容、原挂载或原位权限时，再为该项显式调用一次 `--scope inplace`，并记录升级理由。

package/templates/.agents/skills/run-manual-validation/reference/report-template.en.md

@@ -3,6 +3,7 @@
 ## Input Mode
 
 - Mode: `{explicit|automatic}`
+- Context: `{task-bound|branch-only}` (branch-only also records `recoverable: false`)
 - Input decision: {sanitized-input-decision}
 - PR source status: `{success|no-op|failed|blocked}` / `{stable-code-or-none}`
 
@@ -13,6 +14,7 @@ $ agent-infra-internal task-snapshot {task-id} --format text
 {command-summary-and-key-result}
 ```
 > Follow `.agents/rules/evidence-reporting.md`: record command name, target scope, exit status, sanitized result, and coverage gap; do not paste complete argv or sensitive transcripts.
+> Branch-only has no `{task-id}`: record `not-applicable (branch-only)` in this section.
 
 ## Validation Target
 

package/templates/.agents/skills/run-manual-validation/reference/report-template.zh-CN.md

@@ -3,6 +3,7 @@
 ## 输入模式
 
 - 模式：`{explicit|automatic}`
+- 上下文：`{task-bound|branch-only}`（branch-only 另记 `recoverable: false`）
 - 输入判定：{sanitized-input-decision}
 - PR 来源状态：`{success|no-op|failed|blocked}` / `{stable-code-or-none}`
 
@@ -13,6 +14,7 @@ $ agent-infra-internal task-snapshot {task-id} --format text
 {command-summary-and-key-result}
 ```
 > 按 `.agents/rules/evidence-reporting.md` 记录命令名称、目标范围、退出状态、sanitized result 和覆盖缺口；不得粘贴完整 argv 或敏感 transcript。
+> branch-only 无 `{task-id}`，本段记 `not-applicable (branch-only)`。
 
 ## 验证目标
 

package/templates/.agents/skills/run-task/SKILL.en.md

@@ -17,7 +17,7 @@ The orchestrator delegates only and never executes a stage skill itself. First r
 2. Before `begin-or-resume`, Codex selects a host. Without `AGENT_INFRA_CONTROL_TOKEN`, use direct-host. With task-bound control authority but no `AGENT_INFRA_CODEX_CONTROLLER_CONTEXT`, only run `codex-sandbox-controller run` with the complete policy and wait; the outer loop must not create a run, baseline, or receipt. With a context, run `verify-context` first. Stop on protocol, task/controller/process, lease, or source/profile discovery failures. Package/build/contract or hook/profile content drift is delivered as a structured warning and tells the user to rebuild the sandbox.
 3. Run `task-orchestration {task-id} begin-or-resume --client {client}` with the complete explicit policy. With no explicit policy, core reads that client's configured policy; existing runs use persisted policy. Disk state outside the complete current structure fails closed without rewriting; finish or clear active runs before upgrading. Stop on paused/completed results.
 4. Run `route`. On `completed`, run `agent-infra-internal task-verify {task-id} run-task.completed --format text` and stop. Only a `running` result with non-null `next` supplies action, role, round, artifact, requested model, and requested effort.
-5. Codex runs `codex-lifecycle capability-arm --task-id {task-id}` once. The current loop's real PostToolUse must attest that ordinary tool response. Pass its marker token, the exact routed model, and the exact routed reasoning effort to `prepare --client {client} --requested-model {requestedModel} --requested-reasoning-effort {requestedReasoningEffort} --capability-token {token}`. Core first validates the exact routed model/effort, capability provenance, and controller binding, then captures a read-only snapshot, builds an in-memory prepared receipt, atomically consumes the token, and saves the prepared state with the capability session, turn, and tool-use origin. Activation then verifies that spawn belongs to the same session and turn and uses a distinct tool-use. Other clients use the same prepare without a token. Failure creates no baseline, receipt, or child.
+5. Codex runs `codex-lifecycle capability-arm --task-id {task-id}` once. The current loop's real PostToolUse must attest that ordinary tool response. Pass its `capabilityRef` marker, the exact routed model, and the exact routed reasoning effort to `prepare --client {client} --requested-model {requestedModel} --requested-reasoning-effort {requestedReasoningEffort} --capability-ref {capabilityRef}`. Core accepts only the phase attestation issued by the current controller issuer: `orchestration.prepare` reserves the capability, then `artifact.finalize-local` and `task-event.completed` validate and consume their own phases; the underlying capability is terminally consumed only after the completed commit is confirmed. Without current controller proof, direct-host returns `LOCAL_EXECUTION_AUTHORITY_UNAVAILABLE` and creates no recovery intent, baseline, receipt, or child. Activation then verifies that spawn belongs to the same session and turn and uses a distinct tool-use. Other clients use the same prepare without authority. Failure creates no baseline, receipt, or child.
 6. After prepare, run `task-orchestration <task-ref> dispatch` immediately before calling the fresh native child, then use route's exact model/effort and only the short task ref, skill, `--orchestrated`, and stage identity. The trusted hook-spawn first-observation time must fall between dispatch and the deadline. Its first provenance-sensitive command must be `await-activation --stage ... --round ... --artifact ... --role ...`; before `running`, it must not snapshot, emit stage-started, or write business files. The code stage may create a local checkpoint only through code-task's durable intent core; it must not delegate a separate commit stage or push. Only explicit `recover-prepared` may clear an expired orphan when the task fingerprint is exact and no matching unconsumed active lifecycle evidence remains.
 7. Codex uses SubagentStart/Stop and App Server actual evidence to activate, consume, and seal one receipt; trusted parent fallback must produce the same complete provenance. Timed-out waits do nothing. Advance only a sealed receipt and repeat step 4 only while running.
 8. Create a fresh child each round and never follow up with an old reviewer. Each requested/actual mismatch needs its own host fallback reason. Protocol, capability, receipt hook/evidence binding, source, controller, identity, ledger, or fingerprint failure pauses and fails closed; cross-root package/build/contract or hook/profile content drift is delivered as a warning instead of blocking natural evolution.

package/templates/.agents/skills/run-task/SKILL.zh-CN.md

@@ -17,7 +17,7 @@ description: >
 2. Codex 在 `begin-or-resume` 前选择宿主：没有 `AGENT_INFRA_CONTROL_TOKEN` 时使用 direct-host；有 task-bound control authority 但没有 `AGENT_INFRA_CODEX_CONTROLLER_CONTEXT` 时，只调用 `agent-infra-internal codex-sandbox-controller run`（转发完整显式策略）并等待其终态，外层不得创建 run、baseline 或 receipt；已有 context 时先调用 `verify-context`。protocol、task/controller/process、lease 或 source/profile discovery 校验失败即停止；package/build/contract 或 hook/profile 内容漂移只输出结构化 warning，并提示用户重建 sandbox。
 3. 调用 `agent-infra-internal task-orchestration {task-id} begin-or-resume --client {client}` 并转发完整显式策略。完全没有显式策略时由核心读取当前 client 的 `agentClients[].orchestration`；existing run 使用持久化策略。磁盘状态不符合当前完整结构时核心失败关闭且不改写；升级前必须完成或清空 active run。仅当核心返回 `ORCHESTRATION_MODEL_POLICY_REQUIRED` 时，先用 `agent-client model-selection` 展示 complete/partial/interactive-only 来源，再一次收集完整策略；未回答则不创建 run。若为 paused/completed，按结构化结果停止。
 4. 调用 `route` 并读取结构化结果。若返回 `completed`，立即运行 `agent-infra-internal task-verify {task-id} run-task.completed --format text` 并停止；仅当返回 `running` 且 `next` 非空时读取唯一 action、role、round、artifact、`requestedModel` 和 `requestedReasoningEffort`，不得自行推断。
-5. Codex 先调用一次 `agent-infra-internal codex-lifecycle capability-arm --task-id {task-id}`。该普通工具调用必须由当前 loop 的真实 PostToolUse 回写 attestation；把 route 返回的精确 model、effort 和 marker 中 token 一并传给 `prepare --client {client} --requested-model {requestedModel} --requested-reasoning-effort {requestedReasoningEffort} --capability-token {token}`。核心先校验精确的 model/effort、capability provenance 与 controller binding，再只读捕获快照、构造内存中的 prepared receipt，最后原子消费 token 并保存 prepared 状态，同时持久化 capability 的 session、turn、tool-use 来源。activation 再校验 spawn 与该来源属于同一 session/turn，且 spawn 使用独立的 tool-use。其他客户端直接调用同一 prepare（无 token）。任一失败不得创建 baseline、receipt 或 child。
+5. Codex 先调用一次 `agent-infra-internal codex-lifecycle capability-arm --task-id {task-id}`。该普通工具调用必须由当前 loop 的真实 PostToolUse 回写 attestation；把 route 返回的精确 model、effort 和 marker 中的 `capabilityRef` 一并传给 `prepare --client {client} --requested-model {requestedModel} --requested-reasoning-effort {requestedReasoningEffort} --capability-ref {capabilityRef}`。核心只接受当前 controller issuer 根据 typed lifecycle authority request 签发的 phase attestation：`orchestration.prepare` 只 reserve capability，随后由 `artifact.finalize-local` 和 `task-event.completed` 各自独立校验并消费 phase；底层 capability 仅在 completed commit 已确认后 terminal consume。没有 current controller proof 时 direct-host 返回 `LOCAL_EXECUTION_AUTHORITY_UNAVAILABLE`，不得创建 recovery intent、baseline、receipt 或 child。activation 再校验 spawn 与该来源属于同一 session/turn，且 spawn 使用独立的 tool-use。其他客户端直接调用同一 prepare（无 authority）。任一失败不得创建 baseline、receipt 或 child。
 6. prepare 成功后，在调用 fresh 原生子 Agent 的紧邻前一步执行 `task-orchestration <task-ref> dispatch`，再显式覆盖 route 返回的 model/effort；只传短任务引用、skill 名、`--orchestrated` 与 stage/round/artifact/role。可信 hook-spawn 首次观察时间必须位于 dispatch 与 deadline 之间。child 的第一条 provenance-sensitive 命令必须是 `await-activation --stage ... --round ... --artifact ... --role ...`；返回 running 前禁止 snapshot、阶段 started 或业务写入；代码阶段的本地 checkpoint 只能通过 code-task 的持久化 intent 核心完成，禁止单独委派 commit 阶段或推送。超时由核心暂停；崩溃遗留 prepared receipt 只能在 exact workspace fingerprint、无匹配的未消费 active lifecycle evidence 且 deadline 已过时显式 `recover-prepared`。
 7. Codex 用 SubagentStart/Stop 与 App Server actual evidence 激活、消费并封存唯一 receipt；受信 parent fallback 仍必须形成相同的完整 provenance。timed-out wait 无动作；只有 empty turns 或协议 `inProgress` 可等待，malformed、身份/传输错误或异常 terminal 均暂停。子 Agent 返回后只对 sealed receipt 调用 `advance`；只有 `running` 才重复步骤 4。
 8. 每轮创建新 child；禁止 follow-up 复用 reviewer。actual model/effort 与 requested 不同时必须有各自的宿主降级理由。protocol、capability、receipt 内 hook/evidence binding、source、controller、身份、账本或 fingerprint 异常都调用 `pause` 并失败关闭；跨根 package/build/contract 或 hook/profile 内容漂移按 warning 交付，不把自然演进差异当成硬失败。

package/templates/.agents/skills/test/SKILL.en.md

@@ -23,11 +23,11 @@ Execute the project's full test workflow including compilation checks and unit t
 
 Confirm no compilation errors.
 
-## 2. Run Unit Tests by Layer
+## 2. Run Tests by Layer
 
-This project uses three test layers as an optional optimization; if the test suite is small, all layers may map to the same full test command.
+This project uses test layers as an optional optimization; if the test suite is small, all layers may map to the same full test command.
 
-### fast smoke (target <5s)
+### fast smoke (reference target <10s)
 
 ```bash
 # TODO: Replace with this project's fast smoke subset command
@@ -38,7 +38,16 @@ This project uses three test layers as an optional optimization; if the test sui
 
 Use for code-task inner loops when the project provides a build-free fast path. It should cover the same tests as smoke while skipping redundant compilation or generation.
 
-### smoke (target <5s)
+### platform-smoke (cross-platform boundary)
+
+```bash
+# TODO: Replace with this project's cross-platform integration subset command
+# npm run test:platform-smoke:fast (Node.js)
+```
+
+Use for real CLI, git, shell, or subprocess tests moved out of the unit tier while preserving their original Windows/macOS execution boundary.
+
+### smoke (reference target <10s)
 
 ```bash
 # TODO: Replace with this project's smoke subset command
@@ -52,7 +61,7 @@ Use for:
 - save-and-run / frequent feedback when no fast path exists
 - project structure, configuration, and template contract checks
 
-### core (target <15s)
+### core (reference target <95s)
 
 ```bash
 # TODO: Replace with this project's core subset command
@@ -66,7 +75,7 @@ Use for:
 - final verification before writing code.md / code-r{N}.md
 - local gate before pushing a PR
 
-### full (complete test suite)
+### full (reference target <100s)
 
 ```bash
 # TODO: Replace with this project's full test command
@@ -83,6 +92,8 @@ Use for:
 
 If the project is not layered yet, smoke / core / full may all map to the same full test command; layering is a feedback-speed optimization, not a prerequisite for using the collaboration workflow.
 
+Reference targets are feedback budgets, not merge gates. If coverage is collected, document whether it runs only on the main branch and whether it blocks acceptance.
+
 ## 3. Output Results
 
 Report test result summary:

package/templates/.agents/skills/test/SKILL.zh-CN.md

@@ -21,11 +21,11 @@ description: >
 
 确认没有编译错误。
 
-## 2. 运行单元测试（按层级选择）
+## 2. 运行测试（按层级选择）
 
-三层测试是可选的反馈速度优化；如果测试套件较小，所有层级都可以映射到同一个完整测试命令。
+测试层级是可选的反馈速度优化；如果测试套件较小，所有层级都可以映射到同一个完整测试命令。
 
-### fast smoke（目标 <5s）
+### fast smoke（参考目标 <10s）
 
 ```bash
 # TODO：替换为项目的 fast smoke 子集命令
@@ -36,7 +36,16 @@ description: >
 
 当项目提供不重复构建的快速路径时，用于 code-task 内循环。它应覆盖与 smoke 相同的测试，同时跳过重复的编译或生成步骤。
 
-### smoke（目标 <5s）
+### platform-smoke（跨平台边界）
+
+```bash
+# TODO：替换为项目的跨平台 integration 子集命令
+# npm run test:platform-smoke:fast (Node.js)
+```
+
+用于承接从 unit 层迁出的真实 CLI、git、shell 或子进程测试，同时保留其原有 Windows/macOS 执行边界。
+
+### smoke（参考目标 <10s）
 
 ```bash
 # TODO：替换为项目的 smoke 子集命令
@@ -50,7 +59,7 @@ description: >
 - 项目没有 fast 路径时的保存即跑 / 频繁反馈
 - 仅断言项目结构、配置、模板契约
 
-### core（目标 <15s）
+### core（参考目标 <95s）
 
 ```bash
 # TODO：替换为项目的 core 子集命令
@@ -64,7 +73,7 @@ description: >
 - 写 code.md / code-r{N}.md 报告前的最终验证
 - 推送 PR 前的本地把关
 
-### full（完整测试套件）
+### full（参考目标 <100s）
 
 ```bash
 # TODO：替换为项目的完整测试命令
@@ -81,6 +90,8 @@ description: >
 
 如果项目尚未分层，smoke / core / full 可以全部使用完整测试命令；分层不是使用协作工作流的前置条件。
 
+参考目标是反馈预算，不是合并门禁。如果采集覆盖率，应说明是否仅在 main 分支运行，以及是否阻塞验收。
+
 ## 3. 输出结果
 
 报告测试结果摘要：

package/templates/.agents/templates/task.en.md

@@ -13,7 +13,7 @@ start_date:                     # Optional Issue field for Feature: YYYY-MM-DD
 target_date:                    # Optional Issue field for Feature: YYYY-MM-DD
 current_step: requirement-analysis # requirement-analysis | requirement-analysis-review | technical-design | technical-design-review | code | code-review | completed
 assigned_to:                   # claude | codex | antigravity | opencode | human
-pr_delivery_fact: '{"version":1,"state":"unbound","reason":"initial"}'
+pr_delivery_fact: '{"version":2,"state":"unbound","reason":"initial"}'
 delivery_remote: origin        # Git remote used to deliver the task branch
 delivery_base_ref: main        # Target branch for the task PR
 checkpoint_commit:             # Most recent local checkpoint commit

package/templates/.agents/templates/task.zh-CN.md

@@ -13,7 +13,7 @@ start_date:                     # Feature 可选 Issue 字段：YYYY-MM-DD
 target_date:                    # Feature 可选 Issue 字段：YYYY-MM-DD
 current_step: requirement-analysis # requirement-analysis | requirement-analysis-review | technical-design | technical-design-review | code | code-review | completed
 assigned_to:                   # claude | codex | antigravity | opencode | human
-pr_delivery_fact: '{"version":1,"state":"unbound","reason":"initial"}'
+pr_delivery_fact: '{"version":2,"state":"unbound","reason":"initial"}'
 delivery_remote: origin        # 任务分支交付使用的 Git remote
 delivery_base_ref: main        # 任务 PR 的目标分支
 checkpoint_commit:             # 最近一次本地 checkpoint commit

package/templates/.claude/commands/import-issue.en.md

@@ -1,6 +1,6 @@
 ---
 description: "Import an Issue and create a task"
-usage: "/import-issue <issue-number>"
+usage: "/import-issue <issue-token>"
 ---
 
 Read and execute the import-issue skill from `.agents/skills/import-issue/SKILL.md`.

package/templates/.claude/commands/import-issue.zh-CN.md

@@ -1,6 +1,6 @@
 ---
 description: "从 Issue 导入并创建任务"
-usage: "/import-issue <issue-number>"
+usage: "/import-issue <issue-token>"
 ---
 
 读取并执行 `.agents/skills/import-issue/SKILL.md` 中的 import-issue 技能。

package/templates/.claude/commands/restore-task.en.md

@@ -1,6 +1,6 @@
 ---
 description: "Restore local task files from Issue comments"
-usage: "/restore-task <issue-number> [task-id]"
+usage: "/restore-task <issue-token> [task-id]"
 disable-model-invocation: true
 ---
 

package/templates/.claude/commands/restore-task.zh-CN.md

@@ -1,6 +1,6 @@
 ---
 description: "从 Issue 评论还原本地任务文件"
-usage: "/restore-task <issue-number> [task-id]"
+usage: "/restore-task <issue-token> [task-id]"
 disable-model-invocation: true
 ---
 

package/templates/.claude/commands/run-manual-validation.en.md

@@ -1,6 +1,6 @@
 ---
 description: "Run host-side task validation and record sanitized evidence"
-usage: "/run-manual-validation [--task <ref> | -t <ref>] [--scope snapshot|inplace] [--timeout <ms>] [--format text|json] -- <command...>"
+usage: "/run-manual-validation [--task <ref> | -t <ref> | --branch <ref>] [--scope snapshot|inplace] [--timeout <ms>] [--format text|json] -- <command...>"
 disable-model-invocation: true
 ---
 

package/templates/.claude/commands/run-manual-validation.zh-CN.md

@@ -1,6 +1,6 @@
 ---
 description: "运行宿主侧任务校验并记录去敏证据"
-usage: "/run-manual-validation [--task <ref> | -t <ref>] [--scope snapshot|inplace] [--timeout <ms>] [--format text|json] -- <command...>"
+usage: "/run-manual-validation [--task <ref> | -t <ref> | --branch <ref>] [--scope snapshot|inplace] [--timeout <ms>] [--format text|json] -- <command...>"
 disable-model-invocation: true
 ---
 

package/dist/lib/platform/adapters.js

@@ -1,56 +0,0 @@
-const adapters = new Map();
-function registerPlatformAdapter(adapter) {
-    if (!adapter.type.trim())
-        throw new Error('Platform adapter type is required');
-    adapters.set(adapter.type, adapter);
-}
-function getPlatformAdapter(type) {
-    return type ? adapters.get(type) ?? null : null;
-}
-function registerPlatformCapabilities(type, capabilities) {
-    const adapter = adapters.get(type) ?? { type };
-    adapters.set(type, { ...adapter, ...capabilities });
-}
-function hasPlatformCapability(type, capability) {
-    const adapter = getPlatformAdapter(type);
-    if (capability === 'change-request')
-        return typeof adapter?.inspectChangeRequest === 'function';
-    if (capability === 'issue-closing-change-requests')
-        return typeof adapter?.inspectIssueClosingChangeRequests === 'function';
-    if (capability === 'required-checks')
-        return typeof adapter?.inspectRequiredChecks === 'function';
-    return typeof adapter?.resolveChangeRequestGitEvidence === 'function';
-}
-function inspectPlatformIssueClosingChangeRequests(type, context) {
-    const adapter = getPlatformAdapter(type);
-    return adapter?.inspectIssueClosingChangeRequests?.(context) ??
-        unsupported(type, 'issue closing change-request inspection');
-}
-function unsupported(type, capability) {
-    return {
-        ok: false,
-        error: {
-            code: 'PLATFORM_CAPABILITY_UNSUPPORTED',
-            message: `Platform '${type || 'none'}' does not provide ${capability}`,
-            retryable: false
-        }
-    };
-}
-function inspectPlatformChangeRequest(type, context) {
-    const adapter = getPlatformAdapter(type);
-    return adapter?.inspectChangeRequest?.(context) ?? unsupported(type, 'change-request inspection');
-}
-function inspectPlatformRequiredChecks(type, context) {
-    const adapter = getPlatformAdapter(type);
-    return adapter?.inspectRequiredChecks?.(context) ?? unsupported(type, 'required-checks inspection');
-}
-function resolvePlatformChangeRequestGitEvidence(type, context) {
-    const adapter = getPlatformAdapter(type);
-    return adapter?.resolveChangeRequestGitEvidence?.(context) ??
-        unsupported(type, 'change-request Git evidence');
-}
-function listPlatformAdapters() {
-    return [...adapters.keys()].sort();
-}
-export { getPlatformAdapter, hasPlatformCapability, inspectPlatformChangeRequest, inspectPlatformIssueClosingChangeRequests, inspectPlatformRequiredChecks, listPlatformAdapters, registerPlatformAdapter, registerPlatformCapabilities, resolvePlatformChangeRequestGitEvidence };
-//# sourceMappingURL=adapters.js.map