dev-flow-codex 0.3.0 → 0.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +150 -197
- package/package.json +3 -1
- package/plugin/.codex-plugin/plugin.json +1 -1
- package/plugin/skills/dev-flow/SKILL.md +293 -150
- package/plugin/skills/dev-flow/references/method-profiles.md +153 -0
- package/plugin/skills/dev-flow/references/node-payloads.md +305 -0
- package/runtime/darwin-arm64/dev-flow +0 -0
package/README.md
CHANGED
|
@@ -1,243 +1,196 @@
|
|
|
1
1
|
# dev-flow-codex
|
|
2
2
|
|
|
3
|
-
`dev-flow-codex`
|
|
4
|
-
|
|
5
|
-
`darwin-arm64`
|
|
3
|
+
`dev-flow-codex` 是 Codex CLI 的 explicit-only Dev Flow Adapter。package 包含一个 Codex
|
|
4
|
+
Plugin、一个 `dev-flow` Skill、一份 local STDIO MCP 声明、method-profile reference 和一个
|
|
5
|
+
`darwin-arm64` Core executable。它不保存 Task、process cursor、transition table 或 recovery
|
|
6
|
+
classification。
|
|
6
7
|
|
|
7
|
-
|
|
8
|
-
|
|
8
|
+
## 安装与发布身份
|
|
9
|
+
|
|
10
|
+
当前 package、plugin 和 bundled Core 版本是 `0.4.0`。Feature 009 发布已完成的 Feature 008
|
|
11
|
+
graph runtime；历史 `0.3.0` 包、Tag、Release 与证据保持冻结。
|
|
12
|
+
|
|
13
|
+
标准安装和显式注册入口是：
|
|
9
14
|
|
|
10
15
|
```bash
|
|
11
|
-
npm install -g dev-flow-codex
|
|
16
|
+
npm install -g dev-flow-codex@0.4.0
|
|
12
17
|
dev-flow-codex setup
|
|
13
18
|
```
|
|
14
19
|
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
20
|
+
精确 npm tarball、standalone Core、manifest、checksums、实际 Codex 版本和最终 Journey 结果以
|
|
21
|
+
GitHub Release `v0.4.0` 与 registry 回读证据为准。
|
|
22
|
+
|
|
23
|
+
当前公开支持 native macOS arm64、Node.js `>=24` 和 Codex
|
|
24
|
+
`>=0.147.0 <0.148.0`。没有 Linux、Windows、Intel Mac、Rosetta 或 DeepSeek 产品支持声明。
|
|
19
25
|
|
|
20
|
-
|
|
21
|
-
explicit `remove` removes only proven product-owned registration. npm uninstall remains a separate
|
|
22
|
-
file-removal operation. Task data and unknown adjacent files are retained by default. The package
|
|
23
|
-
contains its Core and requires no Go toolchain, source checkout, first-run download, or separate
|
|
24
|
-
backend.
|
|
26
|
+
## Closed package
|
|
25
27
|
|
|
26
|
-
|
|
28
|
+
生产 package 内容由 `package.json.files` 和本地 builder 共同关闭：
|
|
27
29
|
|
|
28
30
|
```text
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
31
|
+
.agents/plugins/marketplace.json
|
|
32
|
+
LICENSE
|
|
33
|
+
README.md
|
|
34
|
+
bin/dev-flow-codex.mjs
|
|
35
|
+
lib/lifecycle.mjs
|
|
36
|
+
lib/paths.mjs
|
|
37
|
+
package.json
|
|
38
|
+
plugin/.codex-plugin/plugin.json
|
|
39
|
+
plugin/.mcp.json
|
|
40
|
+
plugin/skills/dev-flow/SKILL.md
|
|
41
|
+
plugin/skills/dev-flow/agents/openai.yaml
|
|
42
|
+
plugin/skills/dev-flow/references/method-profiles.md
|
|
43
|
+
plugin/skills/dev-flow/references/node-payloads.md
|
|
44
|
+
runtime/darwin-arm64/dev-flow
|
|
39
45
|
```
|
|
40
46
|
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
indefinite compatibility promise or public-registry evidence.
|
|
47
|
+
Artifact 不包含 tests、fixtures、specs、source tree、`.git`、`node_modules`、用户数据、构建日志
|
|
48
|
+
或绝对路径。package 没有 production npm dependency 和 install/update/uninstall lifecycle hook；
|
|
49
|
+
安装文件与显式 Codex 注册是两个操作。
|
|
45
50
|
|
|
46
|
-
|
|
47
|
-
package has no production npm dependency and no install, download, or host-mutation lifecycle hook.
|
|
48
|
-
Installation and explicit Codex registration are separate operations, and neither setup nor removal
|
|
49
|
-
may edit the current repository or delete Core-owned task data.
|
|
51
|
+
## Local package build
|
|
50
52
|
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
Create a temporary, non-final development artifact and install it with lifecycle scripts disabled:
|
|
53
|
+
在干净、已提交的 source commit 上，把最终验收制品构建到仓库外的空目录：
|
|
54
54
|
|
|
55
55
|
```bash
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
--
|
|
62
|
-
|
|
63
|
-
|
|
56
|
+
ARTIFACT_ROOT="${TMPDIR:-/tmp}/dev-flow-local-artifacts"
|
|
57
|
+
mkdir -p "$ARTIFACT_ROOT"
|
|
58
|
+
SOURCE_COMMIT="$(git rev-parse HEAD)"
|
|
59
|
+
|
|
60
|
+
pnpm --dir packages/codex run build:local \
|
|
61
|
+
--output "$ARTIFACT_ROOT" \
|
|
62
|
+
--final \
|
|
63
|
+
--source-commit "$SOURCE_COMMIT" \
|
|
64
|
+
--report "$ARTIFACT_ROOT/artifact-evidence.json"
|
|
64
65
|
```
|
|
65
66
|
|
|
66
|
-
|
|
67
|
-
|
|
67
|
+
`--final` 表示 builder 的 clean-source/identity verification 模式；公开 Release 由 standalone
|
|
68
|
+
一键发布命令产生。
|
|
69
|
+
Builder 要求输出目录已经存在、没有 `.tgz`，source tree 干净且 HEAD 等于 `--source-commit`；
|
|
70
|
+
它验证 package/Core/plugin version identity、platform、detached runtime executable 和 closed pack
|
|
71
|
+
contents，并输出 SHA-256 evidence。制品与 evidence JSON 均保留在仓库外。
|
|
68
72
|
|
|
69
|
-
|
|
70
|
-
dev-flow-codex --version
|
|
71
|
-
dev-flow-codex setup --json
|
|
72
|
-
codex plugin marketplace list --json
|
|
73
|
-
codex plugin list --json
|
|
74
|
-
```
|
|
75
|
-
|
|
76
|
-
Setup supports only macOS arm64 in this feature. It verifies the installed Codex version against
|
|
77
|
-
the selected bounded range, the package/plugin/Core version identity, the package-local executable,
|
|
78
|
-
the one Skill, its explicit-only `agents/openai.yaml` policy, the typed MCP resource, and
|
|
79
|
-
`dev-flow-codex` discovery on `PATH` before its first registry write. It registers
|
|
80
|
-
`dev-flow-local` and `dev-flow-codex@dev-flow-local` through Codex JSON commands, validates the
|
|
81
|
-
official camelCase mutation results, and requires exact `{marketplaces: [...]}` plus
|
|
82
|
-
`{installed: [...], available: [...]}` readback before writing the ownership receipt at
|
|
83
|
-
`~/Library/Application Support/dev-flow/registrations/codex.json`. Matching repeated setup is a
|
|
84
|
-
no-op; malformed, incomplete, or conflicting state fails closed. Restart or open a fresh Codex
|
|
85
|
-
session after setup so the host refreshes plugin, Skill, and MCP discovery.
|
|
86
|
-
|
|
87
|
-
Without `DEV_FLOW_DATA_DIR`, `dev-flow-codex mcp` creates only
|
|
88
|
-
`~/Library/Application Support/dev-flow/data` with restrictive permissions. A nonempty override
|
|
89
|
-
must already be an absolute, canonical, usable directory. Runtime selection is always relative to
|
|
90
|
-
the installed package; it never falls back to a Core binary in the current repository.
|
|
73
|
+
本地构建只生成和检查制品，不执行 setup/remove、不修改真实 Codex 配置、不启动 native Journey。
|
|
91
74
|
|
|
92
75
|
## Explicit invocation boundary
|
|
93
76
|
|
|
94
|
-
|
|
95
|
-
the installed Skill full name is `dev-flow-codex:dev-flow`. The only exact explicit selector is `$dev-flow-codex:dev-flow`.
|
|
96
|
-
Bare `$dev-flow` is not an alias and does not select this installed Skill. A wrong plugin namespace,
|
|
97
|
-
a wrong Skill base name, or a missing selector also does not select it.
|
|
98
|
-
Codex 0.147 registers plugin MCP tools independently from Skill injection, so this package does not
|
|
99
|
-
claim selector-bound MCP visibility or authorization. An ordinary prompt must make zero Dev Flow
|
|
100
|
-
calls. Other non-exact selectors must not complete a task-bearing operation or change task, event,
|
|
101
|
-
or claim state; host-exposed read-only and Core-rejected calls remain observable. Non-exact Skill
|
|
102
|
-
selection does not disable ordinary Codex repository tools or revoke work independently authorized
|
|
103
|
-
by the rest of the prompt. Final acceptance therefore uses a non-mutating bare-selector probe and
|
|
104
|
-
verifies that controlled probe leaves the repository unchanged.
|
|
105
|
-
`$dev-flow-codex:dev-flow` with no substantive requirement, a conversational request, a non-Git
|
|
106
|
-
directory, or work spanning more than one repository stops before Skill-owned task discovery.
|
|
107
|
-
For an admitted request, the Skill resolves one canonical current worktree and calls
|
|
108
|
-
`dev_flow_server_info({})` first; an incomplete or incompatible six-tool catalog stops the request.
|
|
109
|
-
|
|
110
|
-
## Core-governed create and resume
|
|
111
|
-
|
|
112
|
-
After the handshake, a new invocation opens one `host=codex` task using only the bounded user
|
|
113
|
-
request, repository instructions, acceptance criteria, exclusions, and verification authority. An
|
|
114
|
-
explicit resume omits `new_task`; Core must return the compatible active task. A restart/resume must
|
|
115
|
-
preserve the same task ID and continue its advancing revision lineage. An ownership or contract
|
|
116
|
-
conflict stops the invocation without choosing, merging, or replacing task records.
|
|
117
|
-
|
|
118
|
-
Every iteration consumes one complete fresh Core action. Its task/revision/action identity,
|
|
119
|
-
repository binding, allowed effects, required evidence, payload schema, blocker, and outcome stay
|
|
120
|
-
together. Codex performs only the allowed effect, constructs the returned closed payload, retains a
|
|
121
|
-
request ID, and submits exactly one mutation. A complete success continues only from the returned
|
|
122
|
-
next action or a fresh Core read; Codex does not infer transitions or completion.
|
|
123
|
-
|
|
124
|
-
If a mutation result is missing, cancelled, malformed, truncated, or otherwise uncertain, read
|
|
125
|
-
before retry: retain the exact original operation, call `dev_flow_get_task` and
|
|
126
|
-
`dev_flow_get_next_action`, and follow only Core's recovery assessment. Never reconstruct a missing
|
|
127
|
-
operation probe or repeat a mutation because its response was lost.
|
|
128
|
-
|
|
129
|
-
Every completed host command event is retained only as role-scoped status, exit code, and safe
|
|
130
|
-
command/output hashes. Ambient commands in the ordinary or invalid sessions and repository
|
|
131
|
-
inspection or implementation commands in active sessions are non-verification facts. Only the one
|
|
132
|
-
Core-submitted and retained logical proof, rendered by Codex 0.147 on macOS as the closed supported
|
|
133
|
-
command, counts against the verification budget. An unbound or duplicate proof and any known test
|
|
134
|
-
or full-suite command fail closed. Do not run a forbidden full suite; when automatic capacity is
|
|
135
|
-
exhausted, report an honest manual handoff.
|
|
136
|
-
Static, simulated, user-performed, and native evidence keep distinct labels. A Core blocker,
|
|
137
|
-
ownership/contract conflict, `CANCELLED`, or Core-owned `DONE` outcome stops repository work and is
|
|
138
|
-
reported without reinterpretation.
|
|
139
|
-
|
|
140
|
-
## Explicit removal and retained task data
|
|
141
|
-
|
|
142
|
-
Deregister before running npm uninstall:
|
|
77
|
+
Skill metadata 设置 `policy.allow_implicit_invocation: false`。唯一精确 selector 是：
|
|
143
78
|
|
|
144
|
-
```
|
|
145
|
-
dev-flow-codex
|
|
146
|
-
npm uninstall -g --ignore-scripts dev-flow-codex
|
|
79
|
+
```text
|
|
80
|
+
$dev-flow-codex:dev-flow
|
|
147
81
|
```
|
|
148
82
|
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
absence is an idempotent no-op.
|
|
155
|
-
|
|
156
|
-
The command does not delete the npm package, Core task data, repository, Codex config/cache, receipt
|
|
157
|
-
parents, or unknown adjacent resources. Stop Core before comparing task-data manifests; after
|
|
158
|
-
deregistration, directly reopen the recorded task with Core to prove retention. Perform npm
|
|
159
|
-
uninstall separately only after successful absence readback. A later artifact within the selected
|
|
160
|
-
compatible range may be installed and explicitly set up again against the retained data.
|
|
161
|
-
|
|
162
|
-
Setup, version reporting, and removal are package/user-state operations and behave the same from
|
|
163
|
-
any working directory. They do not add configuration, databases, instructions, or generated files
|
|
164
|
-
to the target repository and never mutate Git.
|
|
165
|
-
|
|
166
|
-
The `>=0.147.0 <0.148.0` line and exact `0.147.0` host were selected on 2026-08-15, not promised
|
|
167
|
-
indefinitely. The selected MCP file uses Agent Plugins v1 `$schema`, camelCase `mcpServers`, and one
|
|
168
|
-
`type: stdio` entry, a shape accepted by both 0.147 plugin parsers. A future changed official
|
|
169
|
-
contract requires every compatibility-bearing contract, test, and guide to be updated before a
|
|
170
|
-
final artifact is built.
|
|
83
|
+
Skill resource/base name 是 `dev-flow`，installed Skill full name 是 `dev-flow-codex:dev-flow`，
|
|
84
|
+
only exact explicit selector 是 `$dev-flow-codex:dev-flow`。bare `$dev-flow` is not an alias and
|
|
85
|
+
does not select this Skill；wrong plugin namespace、wrong Skill base name 或 missing selector 也不会
|
|
86
|
+
选择它。ordinary prompt 必须产生 zero Dev Flow calls。non-exact selectors must not complete a task-bearing operation；
|
|
87
|
+
This does not disable ordinary Codex repository tools. The package does not make or claim selector-bound MCP visibility or authorization。
|
|
171
88
|
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
Run the product-bearing package layers directly:
|
|
89
|
+
被接纳的请求必须只涉及一个现有 Git repository，并先调用 `dev_flow_server_info({})`。当前
|
|
90
|
+
source-local Contract 0.2 handshake 必须返回：
|
|
175
91
|
|
|
176
|
-
```
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
92
|
+
```text
|
|
93
|
+
schema_version = 2
|
|
94
|
+
core_limits_version = 0.2
|
|
95
|
+
process = standard-development@1
|
|
96
|
+
method_profiles = plain, spec-kit, openspec
|
|
97
|
+
exact six-tool catalog
|
|
182
98
|
```
|
|
183
99
|
|
|
184
|
-
|
|
185
|
-
Codex: completed success with text/structured parity, failed Core-domain result with the same parity,
|
|
186
|
-
and failed transport with no complete Core result. They contain no prompt, source, user path,
|
|
187
|
-
environment, token, or secret.
|
|
100
|
+
不完整、不同版本或不同顺序的 catalog 会停止请求。公开工具为：
|
|
188
101
|
|
|
189
|
-
```
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
102
|
+
```text
|
|
103
|
+
dev_flow_server_info
|
|
104
|
+
dev_flow_open_task
|
|
105
|
+
dev_flow_get_task
|
|
106
|
+
dev_flow_get_next_action
|
|
107
|
+
dev_flow_apply_action
|
|
108
|
+
dev_flow_cancel_task
|
|
193
109
|
```
|
|
194
110
|
|
|
195
|
-
##
|
|
111
|
+
## Graph task 与 method profiles
|
|
196
112
|
|
|
197
|
-
|
|
198
|
-
|
|
113
|
+
新任务从 `REQUIREMENTS` 开始，Core 返回完整 node contract、semantic method steps 和全部合法
|
|
114
|
+
transitions。Codex 只提交 Core 返回的 `transition_id` 和 closed node payload；destination、guard、
|
|
115
|
+
current node 和 completion 都由 Core 决定。
|
|
199
116
|
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
117
|
+
Task 创建时选择一个 immutable profile：
|
|
118
|
+
|
|
119
|
+
```text
|
|
120
|
+
plain
|
|
121
|
+
spec-kit
|
|
122
|
+
openspec
|
|
206
123
|
```
|
|
207
124
|
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
125
|
+
三种 profile 使用同一状态图。Adapter 按当前 Action 渲染实际存在的 capability 和预期 artifact。
|
|
126
|
+
capability unavailable 或 unknown 时，它明确报告缺失，并呈现合同定义的 plain-equivalent work；
|
|
127
|
+
只有等价工作实际完成时才提交 `plain_fallback` method evidence。command、checkbox、sync、archive
|
|
128
|
+
或 artifact 自身不会推进 Core。
|
|
212
129
|
|
|
213
|
-
|
|
130
|
+
`TEST` 成功后必须进入 `COMPREHENSION_REVIEW`。Codex 向开发者解释当前行为、复杂度和维护
|
|
131
|
+
风险，并取得明确 verdict；AI/static evidence 不能替代用户确认。复杂代码进入 `REFACTOR`，
|
|
132
|
+
repository-changing refactor 只能回到 `TEST`。
|
|
214
133
|
|
|
215
|
-
|
|
216
|
-
runs passed with distinct tasks. Those runs establish repeatability but do not replace acceptance.
|
|
217
|
-
Run one final real-host acceptance against the reviewed commit immediately before merge approval.
|
|
218
|
-
The real-host entry point records ephemeral session observations:
|
|
134
|
+
## Read-before-retry
|
|
219
135
|
|
|
220
|
-
|
|
221
|
-
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
136
|
+
每次 mutation 前，Adapter 保留完整 operation identity：request/operation ID、process、source
|
|
137
|
+
cursor、revision、action、issuance binding 和原始 closed payload。结果缺失、取消、损坏、截断或
|
|
138
|
+
transport failure 时不得盲目重试，也不得重建缺失的 probe。
|
|
139
|
+
|
|
140
|
+
Adapter 使用 `dev_flow_get_task` 或 `dev_flow_get_next_action` 提交原 operation probe，并只遵循
|
|
141
|
+
Core 返回的五分类 Assessment 和 advice。Probe 零写入；只有显式 recovery apply 可以完成一次
|
|
142
|
+
Core-derived transition 或创建一次 blocker。Adapter 不判断 classification、retry safety、resume
|
|
143
|
+
node 或 destination。
|
|
144
|
+
|
|
145
|
+
## Schema 1 unsupported guidance
|
|
146
|
+
|
|
147
|
+
Graph package 只支持 fresh Schema 2、snapshot-v2 和精确 `standard-development@1`。遇到 Schema
|
|
148
|
+
1/pre-graph data 时 Core 返回 `SCHEMA_UNSUPPORTED`，且不 decode、migrate、rename、truncate、
|
|
149
|
+
delete 或 reset 旧数据。不要重复启动或自动清理。
|
|
150
|
+
|
|
151
|
+
用户必须明确选择一个新的绝对、canonical、usable `DEV_FLOW_DATA_DIR`，或在 Core 外部手工
|
|
152
|
+
archive/rename/delete 旧目录，再启动 graph Core。错误信息不回显私有数据库路径。
|
|
153
|
+
|
|
154
|
+
## Setup、remove 与 retained data
|
|
155
|
+
|
|
156
|
+
`0.4.0` package 文件安装仍与 Codex 注册分离：只有 `dev-flow-codex setup` 可以创建经 ownership
|
|
157
|
+
和 read-back 验证的注册，只有 `dev-flow-codex remove` 可以删除该产品拥有的注册。
|
|
226
158
|
|
|
227
|
-
|
|
228
|
-
|
|
229
|
-
|
|
230
|
-
|
|
231
|
-
|
|
232
|
-
|
|
233
|
-
|
|
159
|
+
setup/update/remove/uninstall 均保留 Core task data 和未知相邻文件，不会修改目标 repository 或
|
|
160
|
+
Git。remove 应先证明 plugin/marketplace absence，再单独执行 package-manager uninstall。重新安装
|
|
161
|
+
兼容的 graph artifact 可以从同一 Schema 2 数据目录恢复任务；没有任何 Schema 1 reader 或
|
|
162
|
+
conversion path。
|
|
163
|
+
|
|
164
|
+
## Closed node payload construction
|
|
165
|
+
|
|
166
|
+
打包 Skill 在每次普通 apply 前同时读取 live Action、`dev_flow_apply_action` `inputSchema` 和
|
|
167
|
+
`plugin/skills/dev-flow/references/node-payloads.md` 的对应标记模板。该 reference 覆盖
|
|
168
|
+
REQUIREMENTS、DESIGN、TASKS、IMPLEMENT、TEST、COMPREHENSION_REVIEW 的复杂度/通过分支、
|
|
169
|
+
REFACTOR、DELIVERY 和 BLOCKED resolution，并由真实 MCP validator、workflow decoder 和 payload
|
|
170
|
+
validator 提取验证。它只提供构造指引，不保存游标、复制 transition authority 或替代 Core。
|
|
171
|
+
|
|
172
|
+
`required_evidence` 与 ArtifactReference role 不同；`repository_observation` 不得作为 artifact
|
|
173
|
+
role。无真实 process artifact 时使用空 `artifacts`，同时保留完整 branch wrapper、当前 baseline/
|
|
174
|
+
record/evidence identity 和精确 MethodEvidence。Core `INVALID_ARGUMENT` 会停止该 mutation，不会
|
|
175
|
+
触发候选 payload 试探或自动重试。
|
|
176
|
+
|
|
177
|
+
对于 apply/cancel，Result Envelope `request_id` 与 caller mutation `request_id` 相同，并与成功
|
|
178
|
+
提交后的 `LastOperation.operation_id`/TaskEvent identity 对齐。没有 caller request ID 的 read/open/
|
|
179
|
+
info 工具继续使用 Core 生成的本地 transport identity。
|
|
180
|
+
|
|
181
|
+
## Deterministic validation
|
|
182
|
+
|
|
183
|
+
完整 package-local 测试入口为：
|
|
234
184
|
|
|
235
185
|
```bash
|
|
236
|
-
|
|
237
|
-
acceptance-report \
|
|
238
|
-
--report "$CODEX_ACCEPTANCE_REPORT"
|
|
186
|
+
pnpm --dir packages/codex test
|
|
239
187
|
```
|
|
240
188
|
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
189
|
+
它覆盖 package contract、Skill contract、lifecycle、journey harness、parser/evidence 以及已有
|
|
190
|
+
launcher/runtime tests。fixture、simulated Harness 和 static contract 证据不属于 native Codex
|
|
191
|
+
evidence，也不证明 package 已公开发布。
|
|
192
|
+
|
|
193
|
+
Feature 008 的 source-local acceptance 已完成。Attempt 3 提供真实 native Codex graph-flow
|
|
194
|
+
evidence；独立的 no-Codex deterministic lifecycle 使用同一精确 artifact 证明 setup、remove、
|
|
195
|
+
npm uninstall、data retention、相同 artifact reinstall 和同一 lifecycle Task terminal reopen。
|
|
196
|
+
两类 evidence 保持不同标签，且都不构成 registry package 或公开发布证明。
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dev-flow-codex",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.5.0",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "Explicit-only Dev Flow integration for Codex CLI.",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -36,6 +36,8 @@
|
|
|
36
36
|
"plugin/.mcp.json",
|
|
37
37
|
"plugin/skills/dev-flow/SKILL.md",
|
|
38
38
|
"plugin/skills/dev-flow/agents/openai.yaml",
|
|
39
|
+
"plugin/skills/dev-flow/references/method-profiles.md",
|
|
40
|
+
"plugin/skills/dev-flow/references/node-payloads.md",
|
|
39
41
|
"runtime/darwin-arm64/dev-flow"
|
|
40
42
|
],
|
|
41
43
|
"scripts": {
|