@elvis1513/auto-coding-skill 3.0.0 → 3.0.1
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 +111 -54
- package/cli/assets/agents/browser-debugger.toml +5 -7
- package/cli/assets/agents/docs-researcher.toml +3 -5
- package/cli/assets/agents/explorer.toml +5 -10
- package/cli/assets/agents/fixer.toml +19 -17
- package/cli/assets/agents/reviewer.toml +14 -10
- package/cli/assets/skill/SKILL.md +111 -49
- package/cli/assets/skill/data/contracts/orchestration-v1.schema.json +475 -0
- package/cli/assets/skill/data/templates/ENGINEERING.md +164 -82
- package/cli/assets/skill/data/templates/bridges/AGENTS.md +4 -4
- package/cli/assets/skill/data/templates/docs/tasks/closure-log.md +7 -6
- package/cli/assets/skill/data/templates/docs/tasks/taskbook.md +11 -4
- package/cli/assets/skill/scripts/ap.py +1000 -563
- package/cli/src/index.js +399 -51
- package/cli/tests/ap_concurrency_test.py +396 -75
- package/cli/tests/ap_profiles_test.py +242 -99
- package/cli/tests/index.test.js +409 -15
- package/package.json +3 -3
|
@@ -2,12 +2,42 @@
|
|
|
2
2
|
workflow:
|
|
3
3
|
mode: "dev"
|
|
4
4
|
profile: "auto"
|
|
5
|
+
completion: "push"
|
|
5
6
|
|
|
6
7
|
project:
|
|
7
8
|
name: ""
|
|
8
9
|
repo_root: "."
|
|
9
10
|
stack: "generic"
|
|
10
11
|
|
|
12
|
+
access:
|
|
13
|
+
project:
|
|
14
|
+
frontend:
|
|
15
|
+
url: ""
|
|
16
|
+
username: ""
|
|
17
|
+
password: ""
|
|
18
|
+
backend:
|
|
19
|
+
url: ""
|
|
20
|
+
username: ""
|
|
21
|
+
password: ""
|
|
22
|
+
jenkins:
|
|
23
|
+
frontend:
|
|
24
|
+
url: ""
|
|
25
|
+
username: ""
|
|
26
|
+
password: ""
|
|
27
|
+
backend:
|
|
28
|
+
url: ""
|
|
29
|
+
username: ""
|
|
30
|
+
password: ""
|
|
31
|
+
gitlab:
|
|
32
|
+
url: ""
|
|
33
|
+
username: ""
|
|
34
|
+
password: ""
|
|
35
|
+
nexus:
|
|
36
|
+
frontend:
|
|
37
|
+
url: ""
|
|
38
|
+
username: ""
|
|
39
|
+
password: ""
|
|
40
|
+
|
|
11
41
|
concurrency:
|
|
12
42
|
isolation: "worktree"
|
|
13
43
|
base_ref: ""
|
|
@@ -19,38 +49,14 @@ concurrency:
|
|
|
19
49
|
disposable_ignored: []
|
|
20
50
|
|
|
21
51
|
commands:
|
|
22
|
-
gate_changed: ""
|
|
23
|
-
gate_standard: ""
|
|
24
|
-
gate_full: ""
|
|
52
|
+
gate_changed: "git diff --check"
|
|
25
53
|
|
|
26
54
|
gate:
|
|
27
|
-
default_scope: "
|
|
28
|
-
fallback_scope: "
|
|
29
|
-
full_on_unknown:
|
|
30
|
-
no_change_scope: "
|
|
55
|
+
default_scope: "changed"
|
|
56
|
+
fallback_scope: "changed"
|
|
57
|
+
full_on_unknown: false
|
|
58
|
+
no_change_scope: "changed"
|
|
31
59
|
profile_log: ".local/auto-coding-skill/gate-profile.jsonl"
|
|
32
|
-
full_on:
|
|
33
|
-
paths:
|
|
34
|
-
- "Jenkinsfile"
|
|
35
|
-
- "Jenkinsfile.*"
|
|
36
|
-
- ".github/workflows/**"
|
|
37
|
-
- "Dockerfile"
|
|
38
|
-
- "**/Dockerfile"
|
|
39
|
-
- "docker-compose*.yml"
|
|
40
|
-
- "docker-compose*.yaml"
|
|
41
|
-
- "compose*.yml"
|
|
42
|
-
- "compose*.yaml"
|
|
43
|
-
- "docs/ENGINEERING.md"
|
|
44
|
-
- "docs/tools/autopipeline/**"
|
|
45
|
-
- "package-lock.json"
|
|
46
|
-
- "pnpm-lock.yaml"
|
|
47
|
-
- "yarn.lock"
|
|
48
|
-
- "go.mod"
|
|
49
|
-
- "go.sum"
|
|
50
|
-
- "Cargo.lock"
|
|
51
|
-
- "pom.xml"
|
|
52
|
-
- "build.gradle*"
|
|
53
|
-
- "settings.gradle*"
|
|
54
60
|
rules: []
|
|
55
61
|
|
|
56
62
|
structure:
|
|
@@ -86,10 +92,6 @@ optimization:
|
|
|
86
92
|
require_baseline_for_global_review: false
|
|
87
93
|
report_accepted_debt_as_findings: false
|
|
88
94
|
|
|
89
|
-
verification:
|
|
90
|
-
target_env_required: false
|
|
91
|
-
jenkins_required: false
|
|
92
|
-
|
|
93
95
|
docs:
|
|
94
96
|
taskbook: "docs/tasks/taskbook.md"
|
|
95
97
|
closure_log: "docs/tasks/closure-log.md"
|
|
@@ -119,57 +121,63 @@ docs:
|
|
|
119
121
|
|
|
120
122
|
# Engineering Workflow
|
|
121
123
|
|
|
122
|
-
|
|
123
|
-
|
|
124
|
+
<!-- auto-coding-skill:managed-workflow:start version=3.0.1 -->
|
|
125
|
+
|
|
126
|
+
This file is the single project workflow configuration. Keep it in Git. Its YAML
|
|
127
|
+
frontmatter and content outside these versioned markers are manually maintained;
|
|
128
|
+
`autocoding sync` updates only this managed workflow block. Fill every access URL,
|
|
129
|
+
username, and password during project initialization.
|
|
124
130
|
|
|
125
131
|
## Execution profiles
|
|
126
132
|
|
|
127
133
|
`workflow.profile: auto` selects one of three effective profiles:
|
|
128
134
|
|
|
129
|
-
| Profile | Typical work |
|
|
135
|
+
| Profile | Typical work | Local gate | Completion |
|
|
130
136
|
| --- | --- | --- | --- |
|
|
131
|
-
| `micro` | docs/tests-only, very small isolated work | changed |
|
|
132
|
-
| `standard` | ordinary feature and defect work |
|
|
133
|
-
| `high-risk` | DB/auth/payment/deploy/build config or declared high risk |
|
|
137
|
+
| `micro` | docs/tests-only, very small isolated work | changed/quick | pushed |
|
|
138
|
+
| `standard` | ordinary feature and defect work | changed/quick | pushed |
|
|
139
|
+
| `high-risk` | DB/auth/payment/deploy/build config or declared high risk | changed/quick | pushed |
|
|
134
140
|
|
|
135
|
-
`auto` is only a selector. The effective profile
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
141
|
+
`auto` is only a selector. The effective profile remains useful for analysis,
|
|
142
|
+
design depth, and reviewer recommendations, but it never expands the local gate.
|
|
143
|
+
All profiles run the fast changed-scope gate and complete when the configured
|
|
144
|
+
target branch is pushed. Jenkins owns later build/deploy work; its result and
|
|
145
|
+
manual acceptance are outside the coding task.
|
|
139
146
|
|
|
140
|
-
Project `gate.rules` may
|
|
141
|
-
|
|
142
|
-
|
|
147
|
+
Project `gate.rules` may raise the planning profile or request design/reviewer
|
|
148
|
+
attention. Their legacy `scope` and `commands` values never execute in the
|
|
149
|
+
automatic development flow. Standard/full commands remain callable on demand
|
|
150
|
+
with `ap.py run <name>` but are not part of normal development.
|
|
143
151
|
|
|
144
152
|
## Minimal configuration
|
|
145
153
|
|
|
146
154
|
Required for normal development:
|
|
147
155
|
|
|
148
|
-
- `workflow.mode`: `dev`
|
|
156
|
+
- `workflow.mode`: `dev`
|
|
149
157
|
- `workflow.profile`: `auto`, `micro`, `standard`, or `high-risk`
|
|
158
|
+
- `workflow.completion`: `push`
|
|
150
159
|
- `project.name`
|
|
151
|
-
-
|
|
160
|
+
- all URL, username, and direct password fields under `access.project`,
|
|
161
|
+
`access.jenkins`, `access.gitlab`, and `access.nexus`; blank/TODO values make
|
|
162
|
+
initialization incomplete and block `doctor`; keep each value as an inline
|
|
163
|
+
YAML string, quoting values that resemble numbers, dates, booleans, or YAML
|
|
164
|
+
collections
|
|
165
|
+
- `concurrency.isolation`: the only supported value is `worktree`; shared-checkout
|
|
166
|
+
and legacy write modes are rejected
|
|
152
167
|
- `concurrency.base_ref` and `target_branch`: leave blank to derive the current
|
|
153
168
|
upstream, or set them explicitly for a fixed integration branch
|
|
154
169
|
- `concurrency.branch_prefix` and `worktree_root`
|
|
155
170
|
- `concurrency.cleanup_merged` and `delete_remote_branch`: keep both enabled to
|
|
156
171
|
remove integrated temporary worktrees and branches
|
|
157
172
|
- `concurrency.disposable_ignored`: add only project-specific ignored cache/build
|
|
158
|
-
paths that may be discarded with a task worktree; ignored
|
|
173
|
+
paths that may be discarded with a task worktree; ignored data and unknown
|
|
159
174
|
paths block cleanup, including inside initialized submodules
|
|
160
|
-
-
|
|
161
|
-
project can exercise changed, standard, and full scopes
|
|
162
|
-
- `verification.target_env_required` and `verification.jenkins_required`
|
|
175
|
+
- one fast `commands.gate_changed`; the default is `git diff --check`
|
|
163
176
|
|
|
164
|
-
Legacy command keys such as `commands.light_gate`, `
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
`health_path`. Add frontend/backend URLs only for requested endpoint checks, and
|
|
169
|
-
login/secret references only when basic auth is requested. When Jenkins is
|
|
170
|
-
enabled, add `jenkins` with its base/job URLs, branch, artifact/deploy metadata,
|
|
171
|
-
timeout, UI/API users, and password values or environment references. Unused
|
|
172
|
-
sections should remain absent rather than filled with placeholders.
|
|
177
|
+
Legacy command keys such as `commands.light_gate`, `test`, and `build` remain
|
|
178
|
+
callable explicitly with `ap.py run <name>` but never replace the automatic
|
|
179
|
+
changed gate. `quick_test` remains the only fallback when `gate_changed` is
|
|
180
|
+
absent. Run `doctor` for exact missing-field diagnostics.
|
|
173
181
|
|
|
174
182
|
## Concurrent write tasks
|
|
175
183
|
|
|
@@ -177,18 +185,43 @@ Run every write task in a registered Git worktree and task branch. Do not share
|
|
|
177
185
|
the primary worktree between writers.
|
|
178
186
|
|
|
179
187
|
```bash
|
|
180
|
-
python3 docs/tools/autopipeline/ap.py task-start <TASK_ID>
|
|
188
|
+
python3 docs/tools/autopipeline/ap.py task-start <TASK_ID> \
|
|
189
|
+
--owned-path <PATH> [--owned-path <PATH> ...] \
|
|
190
|
+
[--depends-on <TASK_ID>=<SHA> ...] [--writer <WRITER>]
|
|
181
191
|
# Enter the worktree path printed by task-start.
|
|
182
192
|
python3 docs/tools/autopipeline/ap.py task-status <TASK_ID>
|
|
183
193
|
python3 docs/tools/autopipeline/ap.py task-submodule-sync <TASK_ID>
|
|
184
|
-
python3 docs/tools/autopipeline/ap.py
|
|
194
|
+
python3 docs/tools/autopipeline/ap.py task-review <TASK_ID> \
|
|
195
|
+
--verdict approved --diff-fingerprint <SHA256> [--reviewer <REVIEWER>]
|
|
196
|
+
python3 docs/tools/autopipeline/ap.py task-handoff <TASK_ID> \
|
|
197
|
+
--from <WRITER> --to <WRITER> [--generation <N>]
|
|
198
|
+
python3 docs/tools/autopipeline/ap.py commit-push <TASK_ID> \
|
|
199
|
+
--msg "<TASK_ID>: <summary>" [--writer <WRITER>]
|
|
185
200
|
python3 docs/tools/autopipeline/ap.py task-integrate <TASK_ID>
|
|
201
|
+
python3 docs/tools/autopipeline/ap.py task-resume <TASK_ID>
|
|
186
202
|
```
|
|
187
203
|
|
|
188
204
|
`task-start` fixes the task's base revision and records its task branch and
|
|
189
|
-
worktree
|
|
190
|
-
|
|
191
|
-
|
|
205
|
+
worktree, repeated `owned_paths`, dependency task/SHA pairs, and the active writer
|
|
206
|
+
lease in the repository manifest. Run `commit-push` only from that registered
|
|
207
|
+
worktree. Changed and staged paths must be a subset of `owned_paths`; an unknown
|
|
208
|
+
change blocks the push and must never be restored, reset, stashed, cleaned, or
|
|
209
|
+
otherwise altered.
|
|
210
|
+
|
|
211
|
+
The lifecycle fields are runtime gates, not advisory notes. `task-review` records
|
|
212
|
+
the reviewer verdict against the current diff fingerprint; any edit, rebase, or
|
|
213
|
+
conflict resolution invalidates that approval. `task-handoff` is the only way to
|
|
214
|
+
transfer the writer lease, and its generation check prevents stale owners from
|
|
215
|
+
resuming writes. `commit-push` validates the active writer (explicit `--writer`
|
|
216
|
+
or `CODEX_THREAD_ID`), path ownership, exact dependency SHAs, and an approved
|
|
217
|
+
current fingerprint before it runs the single fast gate. `task-integrate` repeats
|
|
218
|
+
the dependency and review checks. If integration stops on a conflict, resolve it
|
|
219
|
+
inside the task worktree, run `task-resume`, obtain a fresh review, and then retry
|
|
220
|
+
integration. A target rebase likewise requires a fresh review.
|
|
221
|
+
|
|
222
|
+
The task commit runs project commit hooks once. The internal backup task-branch
|
|
223
|
+
push skips the pre-push hook; the final target-branch push runs it once.
|
|
224
|
+
`task-integrate` creates no second evidence commit.
|
|
192
225
|
|
|
193
226
|
Successful integration removes the clean worktree and merged local branch, and
|
|
194
227
|
deletes the merged remote task branch by default. Use `task-finish <TASK_ID>` to
|
|
@@ -211,29 +244,70 @@ reinitialized or recovered.
|
|
|
211
244
|
Integration must not update the primary checkout; pull it explicitly only when
|
|
212
245
|
its user-owned state is ready.
|
|
213
246
|
|
|
247
|
+
Before running `autocoding sync`, finish, integrate, and clean every registered
|
|
248
|
+
v3.0 task with the currently installed 3.0.0 runtime. Sync atomically rejects the
|
|
249
|
+
whole project batch while any schema-v1 task remains, including
|
|
250
|
+
`--components skill`; it never guesses or auto-claims owned paths during upgrade.
|
|
251
|
+
|
|
252
|
+
## Subagent orchestration
|
|
253
|
+
|
|
254
|
+
The main agent owns the task graph and Git lifecycle. Before dispatch, decompose
|
|
255
|
+
the request into bounded units and record for each unit its task ID, role, scope,
|
|
256
|
+
dependencies, acceptance criteria, and expected result. Run only independent
|
|
257
|
+
work concurrently.
|
|
258
|
+
|
|
259
|
+
1. Run justified `explorer`, `docs_researcher`, and `browser_debugger` roles in
|
|
260
|
+
parallel for read-only discovery. Browser work collects reproduction evidence;
|
|
261
|
+
it is not post-push acceptance.
|
|
262
|
+
2. The main agent merges discovery evidence and decides the design, dependency
|
|
263
|
+
graph, and non-overlapping path ownership.
|
|
264
|
+
3. Assign each independent write unit to exactly one `fixer`, one registered task
|
|
265
|
+
branch, and one worktree. Never run two writers in one worktree, and do not let
|
|
266
|
+
the main agent edit a fixer-owned worktree concurrently.
|
|
267
|
+
4. Parallelize fixer units only when they are dependency-free and their owned
|
|
268
|
+
paths do not overlap. Complete implementation → review → gate/integration for
|
|
269
|
+
the current dependency wave, then start the next wave only after its
|
|
270
|
+
prerequisites are integrated into the target branch.
|
|
271
|
+
5. A read-only `reviewer` checks a stable diff after implementation and binds its
|
|
272
|
+
verdict to the diff fingerprint. Blocking findings return to the owning fixer;
|
|
273
|
+
any edit invalidates approval and requires re-review. Record the final verdict
|
|
274
|
+
with `task-review` before handing the writer lease back to the main agent.
|
|
275
|
+
6. Subagents never commit, push, integrate, clean branches, or run the project
|
|
276
|
+
gate. Their versioned result contains node/task/role, base SHA, status,
|
|
277
|
+
dependencies, owned and changed paths, diff fingerprint, evidence, findings,
|
|
278
|
+
verdict, risks, and next owner. Read-only roles return no changed paths.
|
|
279
|
+
7. After all required results return, use `task-handoff` to transfer the lease to
|
|
280
|
+
the main agent. The main agent alone runs `commit-push` for each write task,
|
|
281
|
+
which validates the current review and runs the single fast gate, then
|
|
282
|
+
integrates in dependency order, pushes, and cleans all temporary branches and
|
|
283
|
+
worktrees.
|
|
284
|
+
|
|
285
|
+
`classify` emits a machine-readable `agent_plan` with this stage and ownership
|
|
286
|
+
contract. Micro tasks remain main-agent-only unless useful independent work
|
|
287
|
+
clearly exceeds delegation overhead. If the client cannot run subagents, execute
|
|
288
|
+
the same stages sequentially without weakening worktree isolation.
|
|
289
|
+
|
|
214
290
|
## Default workflow
|
|
215
291
|
|
|
216
292
|
Development:
|
|
217
293
|
|
|
218
294
|
1. Read this file and the active task entry.
|
|
219
|
-
2.
|
|
220
|
-
3.
|
|
295
|
+
2. Analyze and decompose the request; run or reason through `classify --scope auto`.
|
|
296
|
+
3. Fan out independent discovery roles, then fan their results back into one main-agent design.
|
|
221
297
|
4. Record the smallest useful design note; create DD/ADR only when indicated.
|
|
222
|
-
5.
|
|
223
|
-
6.
|
|
224
|
-
7.
|
|
225
|
-
|
|
226
|
-
|
|
298
|
+
5. Start one registered worktree per independent write unit with explicit owned paths, dependency SHAs, and writer lease.
|
|
299
|
+
6. Review stable diffs, record their fingerprints with `task-review`, and return findings to their owning fixers until approved.
|
|
300
|
+
7. Hand the writer lease to the main agent. The main agent runs `commit-push` for each write task; it enforces ownership,
|
|
301
|
+
dependency, lease, and current-review gates, executes the one changed-scope fast gate, records
|
|
302
|
+
`DEV-CLOSED`, commits, and pushes the task branch.
|
|
303
|
+
8. The main agent runs `task-integrate` in dependency order to push the target branch and clean the task worktree and
|
|
304
|
+
merged task branches. This completes the push stage and ends the coding task.
|
|
227
305
|
|
|
228
|
-
|
|
229
|
-
|
|
230
|
-
3. Verify enabled CI/Jenkins and target-environment surfaces.
|
|
231
|
-
4. Record `PASS`, `FAIL`, or `PARTIAL` from actual evidence.
|
|
232
|
-
5. Integrate successful work and clean its temporary worktree and branches.
|
|
306
|
+
Do not wait for, poll, diagnose, or record Jenkins/build/deploy results after the
|
|
307
|
+
push. The project owner performs real acceptance separately.
|
|
233
308
|
|
|
234
|
-
The authoritative order
|
|
235
|
-
|
|
236
|
-
then implementation. Do not mark unexecuted checks as PASS.
|
|
309
|
+
The authoritative order is analysis, decomposition, design, development, fast
|
|
310
|
+
local gate, then push. Do not mark unexecuted external checks as PASS.
|
|
237
311
|
|
|
238
312
|
## Structure policy
|
|
239
313
|
|
|
@@ -274,16 +348,24 @@ python3 docs/tools/autopipeline/ap.py doctor
|
|
|
274
348
|
python3 docs/tools/autopipeline/ap.py classify --scope auto
|
|
275
349
|
python3 docs/tools/autopipeline/ap.py light-gate --scope auto --explain
|
|
276
350
|
python3 docs/tools/autopipeline/ap.py structure-check --scope auto
|
|
277
|
-
python3 docs/tools/autopipeline/ap.py task-start <TASK_ID>
|
|
351
|
+
python3 docs/tools/autopipeline/ap.py task-start <TASK_ID> --owned-path <PATH>
|
|
278
352
|
python3 docs/tools/autopipeline/ap.py task-status <TASK_ID>
|
|
279
353
|
python3 docs/tools/autopipeline/ap.py task-submodule-sync <TASK_ID>
|
|
354
|
+
python3 docs/tools/autopipeline/ap.py task-review <TASK_ID> --verdict approved --diff-fingerprint <SHA256>
|
|
355
|
+
python3 docs/tools/autopipeline/ap.py task-handoff <TASK_ID> --from <WRITER> --to <WRITER>
|
|
280
356
|
python3 docs/tools/autopipeline/ap.py commit-push <TASK_ID> --msg "<TASK_ID>: <summary>"
|
|
281
357
|
python3 docs/tools/autopipeline/ap.py task-integrate <TASK_ID>
|
|
358
|
+
python3 docs/tools/autopipeline/ap.py task-resume <TASK_ID>
|
|
282
359
|
python3 docs/tools/autopipeline/ap.py task-finish <TASK_ID>
|
|
283
360
|
python3 docs/tools/autopipeline/ap.py task-prune
|
|
284
361
|
python3 docs/tools/autopipeline/ap.py docs-ledger-check
|
|
285
362
|
python3 docs/tools/autopipeline/ap.py gate-profile
|
|
286
363
|
```
|
|
287
364
|
|
|
365
|
+
`light-gate` is available for an explicit gate-diagnostic task. Do not run it
|
|
366
|
+
before normal `commit-push`; `commit-push` owns the single automatic gate.
|
|
367
|
+
|
|
288
368
|
The launcher under `docs/tools/autopipeline` delegates to the single runtime in
|
|
289
369
|
`.agents/skills/auto-coding-skill/scripts`; do not duplicate that runtime.
|
|
370
|
+
|
|
371
|
+
<!-- auto-coding-skill:managed-workflow:end -->
|
|
@@ -4,9 +4,9 @@ Before code changes, read the configured structure standard and place new code i
|
|
|
4
4
|
Obey `structure.layer_rules` import boundaries unless a DD/ADR explicitly records the exception.
|
|
5
5
|
Before optimization reviews, read the project health baseline and optimization backlog, and report only new, worsened, unrecorded P0/P1, or upgraded-priority items.
|
|
6
6
|
Route work through already available MCP servers, installed skills, plugins, and app connectors when they provide current docs, design context, browser evidence, GitHub/CI state, security review, or artifact rendering.
|
|
7
|
-
Use the `.agents/agents` role model when available
|
|
8
|
-
|
|
7
|
+
Use the `.agents/agents` role model when available. The main agent decomposes and fans out independent explorer/docs_researcher/browser_debugger work, fans evidence into one design, assigns each independent fixer exactly one registered branch/worktree with explicit non-overlapping paths, routes stable diffs through reviewer and back to the owning fixer, then alone runs the fast gate, commits, integrates in dependency order, pushes, and cleans. Never run two writers in one worktree; start dependent write work only after its prerequisite is integrated. If the client cannot run subagents, execute the same stages sequentially without weakening isolation.
|
|
8
|
+
Use exactly one fast changed-scope local gate before pushing. Keep advisory structure, docs-ledger, full regression, Docker, API, Jenkins, and target checks outside the default development gate.
|
|
9
9
|
Keep active docs ledgers small: `taskbook.md`, `closure-log.md`, and top-level `docs/design/T*.md` must be physically archived when over budget. Use `docs-ledger-archive --plan` before `--write`; `archive-index.md` is only navigation.
|
|
10
10
|
Keep `docs/tasks/evidence.jsonl` and closure Markdown aligned with actual executed checks.
|
|
11
|
-
|
|
12
|
-
|
|
11
|
+
Treat target-branch push as coding completion. Do not wait for, poll, diagnose, or fix Jenkins/build/deploy results unless the user starts a separate diagnostic task; the project owner performs acceptance.
|
|
12
|
+
Use the direct URL, username, and password values configured under `access.*` in `docs/ENGINEERING.md`; do not invent credentials.
|
|
@@ -1,16 +1,17 @@
|
|
|
1
1
|
# Closure Log
|
|
2
2
|
|
|
3
|
-
Record one
|
|
4
|
-
|
|
3
|
+
Record one development closure per task. `DEV-CLOSED` means the fast local gate
|
|
4
|
+
passed and the code was pushed. Jenkins, deployment, and owner acceptance happen
|
|
5
|
+
later and do not change the coding closure.
|
|
5
6
|
|
|
6
7
|
## <TASK_ID> — <Title> — YYYY-MM-DD HH:MM
|
|
7
8
|
|
|
8
9
|
- Commit:
|
|
9
10
|
- Effective profile: micro | standard | high-risk
|
|
10
|
-
-
|
|
11
|
-
-
|
|
12
|
-
-
|
|
13
|
-
- Result: DEV-CLOSED
|
|
11
|
+
- Fast local gate:
|
|
12
|
+
- Target push:
|
|
13
|
+
- External build/deploy/acceptance: owner-managed
|
|
14
|
+
- Result: DEV-CLOSED
|
|
14
15
|
- Follow-up:
|
|
15
16
|
|
|
16
17
|
---
|
|
@@ -6,16 +6,23 @@ they are useful.
|
|
|
6
6
|
|
|
7
7
|
## Task T0001 — <Title>
|
|
8
8
|
|
|
9
|
-
- Status: Planned | Designing | Implementing | Checking |
|
|
9
|
+
- Status: Planned | Designing | Implementing | Checking | Pushed | Blocked
|
|
10
10
|
- Scope:
|
|
11
|
+
- Orchestrator:
|
|
12
|
+
- Owning fixer:
|
|
13
|
+
- Registered worktree / branch:
|
|
14
|
+
- Owned paths:
|
|
15
|
+
- Depends on integrated tasks:
|
|
16
|
+
- Reviewer / stable diff:
|
|
17
|
+
- Review verdict: pending | approved | changes-requested
|
|
11
18
|
- Non-goals:
|
|
12
19
|
- Effective profile: micro | standard | high-risk
|
|
13
20
|
- Classification reasons:
|
|
14
21
|
- Existing owner / reuse points:
|
|
15
22
|
- Minimal design:
|
|
16
|
-
-
|
|
17
|
-
-
|
|
18
|
-
- Commit /
|
|
23
|
+
- Development acceptance criteria:
|
|
24
|
+
- Fast local gate evidence:
|
|
25
|
+
- Commit / target push:
|
|
19
26
|
- Follow-up:
|
|
20
27
|
|
|
21
28
|
---
|