@adlc/runner

中文文档
1.12.0发布于 2026/10/10MITES Module构建来源已验证近 30 天下载 8202

Artifact-asserting ADLC phase runner for deterministic gate completion checks.

原始使用文档
文档目录3 节
  1. Usage
  2. Exit codes
  3. ADLC phase

@adlc/runner

Artifact-asserting phase runner for ADLC.

Usage

adlc run p5 --ticket T1 --dir .adlc --json
adlc run p6 --ticket T1 --dir .adlc

The runner does not treat "a command ran" as a gate. It checks .adlc/manifest.jsonl for the evidence each phase requires. P0, P1, P3, P4, P5, and P6 evidence must be scoped to a ticket; adlc run p0, adlc run p1, adlc run p3, adlc run p4, adlc run p5, and adlc run p6 fail operationally without --ticket.

For normal git worktree use, omit --revision. P5 and P6 use the current content fingerprint and fail closed if reviewed content changes. Committing the exact content reviewed at P5 does not move the fingerprint; changing tracked content, ignored ADLC control files such as .adlc/tickets.json, or untracked non-artifact files after P5 makes P6 fail closed until P5 is re-run.

Explicit --revision is an offline selector for recorded manifest and artifact evidence. When supplied, the runner verifies the matching manifest entries, transcript hashes, review packet hashes, ticket hash when available, and P6 packet/snapshot hashes without comparing against the live git worktree.

Standard generated artifacts such as the active manifest/lock files, the exact packet path passed to adlc accept --packet ..., and any exact snapshot paths passed with --before/--after do not move the P6 fingerprint. In-worktree P6 packet and snapshot paths must live under .adlc/ or .omo/evidence/; source paths are rejected before they can become fingerprint exclusions. The runner records hashes for the packet and snapshots and re-verifies them at adlc run p6, so accepted behavior evidence is tamper-evident even though its paths are excluded from the worktree fingerprint.

Exit codes

  • 0: required phase artifacts are present
  • 1: operational error
  • 2: required phase artifacts are missing

ADLC phase

Cross-phase. This package gives CI and Codex skills one stable command for asserting phase completion.

版本与发布记录

@adlc/runner 共发布 16 个版本,首次发布于 2026/06/23;过去 12 个月发布了 16 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
1.12.0latest2026/10/1027 天前
1.11.12026/09/091 个月前
1.11.02026/08/252 个月前
1.10.02026/08/112 个月前
1.9.02026/08/092 个月前
1.8.02026/08/082 个月前

关于 @adlc/runner 的常见问题

@adlc/runner 是什么?

Artifact-asserting ADLC phase runner for deterministic gate completion checks.

如何安装 @adlc/runner?

在项目目录运行 npm install @adlc/runner,或使用 pnpm add / yarn add / bun add。它还提供命令行工具 adlc-runner,可以用 npx adlc-runner 直接运行。

@adlc/runner 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/adlc__runner 是否存在。

@adlc/runner 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@adlc/runner 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=18。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@adlc/runner 可以商用吗?

@adlc/runner 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@adlc/runner 的下载量有多少?

根据 npm 官方下载统计,@adlc/runner 在 2026/10/05 – 2026/11/03 这 30 天内被下载 8,202 次,日均约 273 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@adlc/runner 还在维护吗?

最新版本 1.12.0 发布于 2026/10/10(27 天前);至今共发布 16 个版本,其中过去 12 个月发布了 16 个;首次发布于 2026/06/23。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。