@elvis1513/auto-coding-skill 3.0.1 → 3.0.3
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 +25 -2
- package/cli/assets/agents/fixer.toml +3 -3
- package/cli/assets/skill/SKILL.md +35 -22
- package/cli/assets/skill/data/contracts/orchestration-v1.schema.json +18 -2
- package/cli/assets/skill/data/policies/workflow-migrations-v1.json +371 -0
- package/cli/assets/skill/data/templates/ENGINEERING.md +27 -13
- package/cli/assets/skill/data/templates/bridges/AGENTS.md +5 -1
- package/cli/assets/skill/scripts/ap.py +403 -19
- package/cli/src/index.js +390 -39
- package/cli/tests/ap_concurrency_test.py +73 -7
- package/cli/tests/ap_profiles_test.py +100 -2
- package/cli/tests/index.test.js +102 -12
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,6 +4,29 @@ A generic `.agents` engineering workflow with isolated parallel worktrees, fast
|
|
|
4
4
|
local validation, push-based completion, required access configuration, and safe
|
|
5
5
|
branch cleanup.
|
|
6
6
|
|
|
7
|
+
## What changed in v3.0.3
|
|
8
|
+
|
|
9
|
+
- Made workspace isolation adaptive: one serial task uses a clean current branch;
|
|
10
|
+
dirty checkouts or concurrent writers use isolated task branches/worktrees.
|
|
11
|
+
- Kept one changed-scope fast gate as the complete local validation step and
|
|
12
|
+
avoided temporary branches when they provide no isolation benefit.
|
|
13
|
+
- Fixed quoted and inline legacy gate YAML detection in CLI status.
|
|
14
|
+
|
|
15
|
+
## What changed in v3.0.2
|
|
16
|
+
|
|
17
|
+
- Added controlled synchronization for the root `AGENTS.md` workflow bridge as
|
|
18
|
+
well as the managed `ENGINEERING.md` workflow block.
|
|
19
|
+
- Migrated known legacy rules that required full local gates, verify mode, or
|
|
20
|
+
Jenkins polling during normal development while preserving project facts and
|
|
21
|
+
unrelated custom instructions.
|
|
22
|
+
- Made project status, sync, doctor, and task lifecycle commands fail closed on
|
|
23
|
+
unknown workflow instructions that conflict with the changed-scope fast gate.
|
|
24
|
+
- Removed legacy YAML escalation fields during upgrade while keeping explicit
|
|
25
|
+
full-gate commands available for user-requested diagnostics.
|
|
26
|
+
- Clarified that locked dependencies may be restored only when the configured
|
|
27
|
+
changed-scope gate actually needs them, after which only that same fast gate is
|
|
28
|
+
rerun.
|
|
29
|
+
|
|
7
30
|
## What changed in v3.0.1
|
|
8
31
|
|
|
9
32
|
- Fixed normal development to analysis → decomposition → design → development →
|
|
@@ -74,7 +97,7 @@ branch cleanup.
|
|
|
74
97
|
advisory structure checks, minimal scaffold budgets, on-demand docs, and Agent
|
|
75
98
|
model inheritance.
|
|
76
99
|
|
|
77
|
-
This section records historical v2 behavior. The v3.0.
|
|
100
|
+
This section records historical v2 behavior. The v3.0.3 workflow above supersedes
|
|
78
101
|
its full-gate and verify-mode rules for normal development.
|
|
79
102
|
|
|
80
103
|
## Install
|
|
@@ -146,7 +169,7 @@ worktree.
|
|
|
146
169
|
|
|
147
170
|
```yaml
|
|
148
171
|
concurrency:
|
|
149
|
-
isolation:
|
|
172
|
+
isolation: adaptive
|
|
150
173
|
base_ref: origin/dev
|
|
151
174
|
target_branch: dev
|
|
152
175
|
branch_prefix: codex/
|
|
@@ -7,9 +7,9 @@ developer_instructions = """
|
|
|
7
7
|
你负责小而准的实现修改。
|
|
8
8
|
|
|
9
9
|
工作要求:
|
|
10
|
-
1. 只在问题已经相对明确,并收到 task_id、
|
|
11
|
-
2.
|
|
12
|
-
3. 一个 worktree 只能有一个写入者。只修改 owned_paths,不进入或修改其他任务工作树;发现未知改动立即停止,不 restore/reset/stash/clean。
|
|
10
|
+
1. 只在问题已经相对明确,并收到 task_id、execution_mode、owned_paths、depends_on 和 acceptance 后再动手;isolated 模式还必须收到 task_branch 和绝对 worktree_path。
|
|
11
|
+
2. direct 模式只用于单写入者且主代理确认当前 checkout 干净的当前分支;isolated 模式必须确认当前目录和 task_branch 与分配的注册 worktree 一致。不满足时停止并上报。
|
|
12
|
+
3. 一个 worktree 只能有一个写入者。只修改 owned_paths,不进入或修改其他任务工作树;发现未知改动立即停止,不 restore/reset/stash/clean。direct 模式期间主代理不得并发编辑同一 checkout。
|
|
13
13
|
4. 坚持“最小可辩护修改”原则。
|
|
14
14
|
5. 除非明确要求,否则不要重构、不做大面积改名、不改无关文件。
|
|
15
15
|
6. 先跟随项目现有模式、helper、组件、脚本和文档约束,不新造不必要抽象。
|
|
@@ -12,9 +12,10 @@ gate → push workflow. The project keeps one manual configuration source:
|
|
|
12
12
|
At task start, inventory installed skills, MCP servers, connectors, browser
|
|
13
13
|
tools, and repository scripts. Prefer the most direct authoritative capability.
|
|
14
14
|
The main agent decomposes the task before dispatch. Run independent read-only
|
|
15
|
-
discovery roles in parallel when the runtime supports them.
|
|
16
|
-
|
|
17
|
-
never share a write
|
|
15
|
+
discovery roles in parallel when the runtime supports them. A single serial
|
|
16
|
+
writer uses the current branch when its checkout is clean. Dirty checkouts and
|
|
17
|
+
parallel writers use one registered worktree per fixer; never share a write
|
|
18
|
+
worktree between agents.
|
|
18
19
|
|
|
19
20
|
## Install and upgrade
|
|
20
21
|
|
|
@@ -65,15 +66,18 @@ python3 docs/tools/autopipeline/ap.py classify --scope auto
|
|
|
65
66
|
# or --intent-file when the working tree does not yet describe the task.
|
|
66
67
|
```
|
|
67
68
|
|
|
68
|
-
`light-gate` remains available for an explicit gate-diagnostic task. Do not
|
|
69
|
-
it before normal
|
|
69
|
+
`light-gate` remains available for an explicit gate-diagnostic task. Do not add
|
|
70
|
+
it before normal closure. The main agent runs exactly one configured changed
|
|
71
|
+
gate directly on a clean serial branch or through `commit-push` for isolated work.
|
|
70
72
|
|
|
71
|
-
##
|
|
73
|
+
## Adaptive write isolation
|
|
72
74
|
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
75
|
+
For one serial writer, inspect the current checkout before creating anything. If
|
|
76
|
+
it is clean, use its current branch directly. If it already has changes, or two
|
|
77
|
+
or more writers will run concurrently, preserve the checkout and use one
|
|
78
|
+
registered task branch/worktree per writer. Read-only discovery may stay in the
|
|
79
|
+
primary worktree. A worktree has exactly one writer; no other agent may edit it
|
|
80
|
+
while that writer is active. The lifecycle commands below are for isolated mode.
|
|
77
81
|
|
|
78
82
|
```bash
|
|
79
83
|
python3 docs/tools/autopipeline/ap.py task-start <TASK_ID> \
|
|
@@ -151,19 +155,27 @@ explicitly recovered.
|
|
|
151
155
|
in parallel, then let the main agent merge their evidence into one design.
|
|
152
156
|
3. Create DD/ADR only for cross-module, API, DB, deployment/CI, security, key UI
|
|
153
157
|
flow, or lasting structural decisions.
|
|
154
|
-
4.
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
+
4. For one serial writer, inspect the current checkout first and work directly on
|
|
159
|
+
its current branch when it is clean. Create registered task branches/worktrees
|
|
160
|
+
only when the checkout already has changes or multiple writers run in parallel.
|
|
161
|
+
Never share one worktree between writers; parallelize only dependency-free
|
|
162
|
+
units with non-overlapping paths.
|
|
158
163
|
5. Review each stable diff with a read-only reviewer. Route blocking findings to
|
|
159
164
|
the owning fixer and re-review after any change. The main agent records the
|
|
160
165
|
current verdict with `task-review`, then hands the writer lease back before Git
|
|
161
166
|
closure when required.
|
|
162
|
-
6. After all agents have returned, the main agent
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
+
6. After all agents have returned, the main agent executes the changed-scope fast
|
|
168
|
+
gate once, records `DEV-CLOSED`, commits, and pushes. Use `commit-push` for
|
|
169
|
+
registered isolated tasks; on a clean serial current branch, commit and push
|
|
170
|
+
that branch directly without creating a temporary branch.
|
|
171
|
+
If that configured fast gate fails only because a dependency already present
|
|
172
|
+
in the lockfile is not installed locally, restore the locked dependencies and
|
|
173
|
+
rerun that same fast gate once. Missing dependencies in an accidentally or
|
|
174
|
+
explicitly invoked standard/full diagnostic do not justify dependency
|
|
175
|
+
installation or a full-gate rerun.
|
|
176
|
+
7. For isolated tasks, the main agent runs `task-integrate` in dependency order
|
|
177
|
+
and cleans every task worktree and merged task branch. Direct serial work has
|
|
178
|
+
no temporary branch to clean.
|
|
167
179
|
8. Stop. Jenkins owns later build/deploy work and the project owner owns actual
|
|
168
180
|
acceptance. Ignore later external failures unless the user opens a diagnostic task.
|
|
169
181
|
|
|
@@ -200,9 +212,10 @@ For standard and high-risk write tasks, use the following fan-out/fan-in contrac
|
|
|
200
212
|
role, scope, dependencies, acceptance criteria, and expected output.
|
|
201
213
|
2. Discovery roles are read-only and may run in parallel. Browser work is limited
|
|
202
214
|
to requested reproduction/evidence; it does not replace owner acceptance.
|
|
203
|
-
3. Each fixer receives
|
|
204
|
-
|
|
205
|
-
|
|
215
|
+
3. Each fixer receives `execution_mode` and owned paths. Direct mode also names
|
|
216
|
+
the clean current checkout; isolated mode supplies a task branch and absolute
|
|
217
|
+
worktree path. It may edit only its assigned checkout and must not commit,
|
|
218
|
+
push, integrate, clean, or run the project gate.
|
|
206
219
|
4. Each reviewer receives a stable diff and binds approved or changes-requested
|
|
207
220
|
to its fingerprint. Changes go back to the same fixer and invalidate approval.
|
|
208
221
|
5. Every subagent returns exactly one JSON object conforming to
|
|
@@ -82,6 +82,10 @@
|
|
|
82
82
|
"acceptance": {
|
|
83
83
|
"$ref": "#/$defs/stringArray"
|
|
84
84
|
},
|
|
85
|
+
"execution_mode": {
|
|
86
|
+
"type": "string",
|
|
87
|
+
"enum": ["direct", "isolated"]
|
|
88
|
+
},
|
|
85
89
|
"task_branch": {
|
|
86
90
|
"type": "string",
|
|
87
91
|
"minLength": 1
|
|
@@ -123,9 +127,21 @@
|
|
|
123
127
|
},
|
|
124
128
|
"then": {
|
|
125
129
|
"required": [
|
|
126
|
-
"
|
|
127
|
-
"worktree_path",
|
|
130
|
+
"execution_mode",
|
|
128
131
|
"owned_paths"
|
|
132
|
+
],
|
|
133
|
+
"allOf": [
|
|
134
|
+
{
|
|
135
|
+
"if": {
|
|
136
|
+
"properties": {
|
|
137
|
+
"execution_mode": { "const": "isolated" }
|
|
138
|
+
},
|
|
139
|
+
"required": ["execution_mode"]
|
|
140
|
+
},
|
|
141
|
+
"then": {
|
|
142
|
+
"required": ["task_branch", "worktree_path"]
|
|
143
|
+
}
|
|
144
|
+
}
|
|
129
145
|
]
|
|
130
146
|
}
|
|
131
147
|
},
|
|
@@ -0,0 +1,371 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schema_version": 1,
|
|
3
|
+
"managed_versions": {
|
|
4
|
+
"agents": "3.0.3",
|
|
5
|
+
"engineering": "3.0.3"
|
|
6
|
+
},
|
|
7
|
+
"known_official_agents_sha256": [
|
|
8
|
+
"ebaaadab60327b3a4852948443d7191a4d48cb00bf4910038ab78c9149089373"
|
|
9
|
+
],
|
|
10
|
+
"known_official_engineering_body_sha256": [
|
|
11
|
+
"d1306cc626e8baf8c83c953b760fd771066de2bf125168eca3a7b7d6ff2b87a2",
|
|
12
|
+
"305931c6edef770033a4f1970b00e5fb1c1728351856a173dbfa497daf563021",
|
|
13
|
+
"198d675361337bc272880154266b3eb1f50e3f82f3c6ab04b2e559cd18d8c7b4"
|
|
14
|
+
],
|
|
15
|
+
"known_official_fragments": [
|
|
16
|
+
{
|
|
17
|
+
"id": "agents-v22-autovpn-high-risk",
|
|
18
|
+
"paths": ["AGENTS.md"],
|
|
19
|
+
"match": "exact-line",
|
|
20
|
+
"text": "- `high-risk` is mandatory for migrations, auth/access, billing/orders, Jenkins, container or production deployment work. It cannot be downgraded and must run the real `gate_full`, then use `verify` for Jenkins and target-environment evidence.",
|
|
21
|
+
"replacement": "- Migrations, auth/access, billing/orders, Jenkins, container, and production deployment work are high-risk for analysis, design, and review depth; the automatic local gate remains changed-scope and push ends coding."
|
|
22
|
+
},
|
|
23
|
+
{
|
|
24
|
+
"id": "agents-v22-autovpn-resolved-gate",
|
|
25
|
+
"paths": ["AGENTS.md"],
|
|
26
|
+
"match": "exact-line",
|
|
27
|
+
"text": "7. Run the resolved changed/standard/full gate. High-risk work must use the configured real full command and then verify Jenkins/target surfaces before `PASS`.",
|
|
28
|
+
"replacement": "7. Run the configured changed-scope fast gate once, commit and push, then stop; Jenkins and target acceptance are owner-managed unless a separate diagnostic task is requested."
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"id": "agents-v22-autovpn-version",
|
|
32
|
+
"paths": ["AGENTS.md"],
|
|
33
|
+
"match": "exact-line",
|
|
34
|
+
"text": "- Version 2.2 resolves `auto` to micro/standard/high-risk, enforces a strict real full gate for high-risk work, and selects roles dynamically."
|
|
35
|
+
},
|
|
36
|
+
{
|
|
37
|
+
"id": "agents-v22-geemanage-profile",
|
|
38
|
+
"paths": ["AGENTS.md"],
|
|
39
|
+
"match": "exact-line",
|
|
40
|
+
"text": "- The repo-local auto-coding-skill 2.2 workflow resolves `auto` into `micro`, `standard`, or `high-risk`; high-risk always uses a real full gate and verify-style closure."
|
|
41
|
+
},
|
|
42
|
+
{
|
|
43
|
+
"id": "agents-v22-geemanage-gate",
|
|
44
|
+
"paths": ["AGENTS.md"],
|
|
45
|
+
"match": "exact-line",
|
|
46
|
+
"text": "- `high-risk`: configured full gate; changed/standard fallback is invalid.",
|
|
47
|
+
"replacement": "- `high-risk` increases analysis, design, and review depth; it still uses the configured changed-scope fast gate for normal development."
|
|
48
|
+
},
|
|
49
|
+
{
|
|
50
|
+
"id": "agents-v22-geemill-profile",
|
|
51
|
+
"paths": ["AGENTS.md"],
|
|
52
|
+
"match": "exact-line",
|
|
53
|
+
"text": "- `docs/ENGINEERING.md` uses auto-coding-skill 2.2 profiles: `micro`, `standard`, and `high-risk`. `auto` selects one profile; high-risk always requires a real full gate and verify closure."
|
|
54
|
+
},
|
|
55
|
+
{
|
|
56
|
+
"id": "agents-v22-geemill-gate",
|
|
57
|
+
"paths": ["AGENTS.md"],
|
|
58
|
+
"match": "exact-line",
|
|
59
|
+
"text": "- `high-risk`: the real `gate_full`; changed/standard fallback is forbidden",
|
|
60
|
+
"replacement": "- `high-risk`: deeper analysis, design, and review with the same changed-scope fast development gate"
|
|
61
|
+
},
|
|
62
|
+
{
|
|
63
|
+
"id": "agents-v22-geemill-verify",
|
|
64
|
+
"paths": ["AGENTS.md"],
|
|
65
|
+
"match": "exact-line",
|
|
66
|
+
"text": "7. For high-risk, pass full locally, commit/push, verify configured Jenkins and target surfaces, then record `PASS`, `FAIL`, or `PARTIAL` from actual evidence.",
|
|
67
|
+
"replacement": "7. Run the changed-scope fast gate once, commit/push, and record `DEV-CLOSED`; Jenkins and target acceptance are owner-managed unless requested as a separate diagnostic task."
|
|
68
|
+
},
|
|
69
|
+
{
|
|
70
|
+
"id": "agents-v22-geestack-profile",
|
|
71
|
+
"paths": ["AGENTS.md"],
|
|
72
|
+
"match": "exact-line",
|
|
73
|
+
"text": "- Let `workflow.profile: auto` resolve the effective `micro`, `standard`, or `high-risk` path. High-risk signals force a real full gate and verified closure even when the configured baseline mode is `dev`."
|
|
74
|
+
},
|
|
75
|
+
{
|
|
76
|
+
"id": "agents-v22-geestack-gate",
|
|
77
|
+
"paths": ["AGENTS.md"],
|
|
78
|
+
"match": "exact-line",
|
|
79
|
+
"text": "- `micro` uses the changed gate, `standard` uses the standard gate, and `high-risk` must execute `commands.gate_full`; a light or standard fallback never counts as full verification."
|
|
80
|
+
},
|
|
81
|
+
{
|
|
82
|
+
"id": "agents-v22-geestack-verify",
|
|
83
|
+
"paths": ["AGENTS.md"],
|
|
84
|
+
"match": "exact-line",
|
|
85
|
+
"text": "- After push, verify Jenkins build and production target health when the effective profile is high-risk, the configured mode is `verify`, or the user explicitly requests it. Use `--allow-no-deploy` only for docs-only sync verification."
|
|
86
|
+
},
|
|
87
|
+
{
|
|
88
|
+
"id": "agents-v22-geestack-path",
|
|
89
|
+
"paths": ["AGENTS.md"],
|
|
90
|
+
"match": "exact-line",
|
|
91
|
+
"text": "- Dockerfiles, compose, Jenkins, workflow tooling, auth/payment, and database changes automatically enter the high-risk/full path.",
|
|
92
|
+
"replacement": "- Dockerfiles, Compose, Jenkins, workflow tooling, auth/payment, and database changes are high-risk for analysis, design, and review; they do not expand the automatic local gate beyond changed-scope."
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"id": "agents-v22-geestock-full",
|
|
96
|
+
"paths": ["AGENTS.md"],
|
|
97
|
+
"match": "exact-line",
|
|
98
|
+
"text": "- Runtime/config/schema changes require the full gate declared in `docs/ENGINEERING.md`.",
|
|
99
|
+
"replacement": "- Runtime/config/schema changes are high-risk for analysis, design, and review; normal development still runs only the changed-scope fast gate."
|
|
100
|
+
},
|
|
101
|
+
{
|
|
102
|
+
"id": "agents-v22-govchain-full",
|
|
103
|
+
"paths": ["AGENTS.md"],
|
|
104
|
+
"match": "exact-line",
|
|
105
|
+
"text": "- `high-risk` cannot be downgraded and must execute `commands.gate_full`; changed or standard fallbacks do not count. Use `PASS / FAIL / PARTIAL` only from the required executed evidence."
|
|
106
|
+
},
|
|
107
|
+
{
|
|
108
|
+
"id": "agents-v22-geesight-flow",
|
|
109
|
+
"paths": ["AGENTS.md"],
|
|
110
|
+
"match": "exact-block",
|
|
111
|
+
"text": "- Micro work uses the changed gate and dev closure; ordinary product work uses the\n standard three-stack gate and dev closure; DB, auth, dependency, deployment,\n Jenkins, Docker, Compose, or MediaMTX changes use the real full gate and verify closure.\n- High-risk signals cannot be downgraded. Jenkins and target verification run only\n after commit/push when the effective profile is high-risk or verification is explicit.",
|
|
112
|
+
"replacement": "- DB, auth, dependency, deployment, Jenkins, Docker, Compose, and MediaMTX changes are high-risk for analysis, design, and review; every normal task still uses one changed-scope fast gate and push closure.\n- Jenkins and target verification are owner-managed after push and run only in a separately requested diagnostic task."
|
|
113
|
+
},
|
|
114
|
+
{
|
|
115
|
+
"id": "agents-v22-xjmate-version",
|
|
116
|
+
"paths": ["AGENTS.md"],
|
|
117
|
+
"match": "exact-line",
|
|
118
|
+
"text": "- For any non-trivial code, config, deployment, database, UI, or docs change, follow the repo-local auto-coding-skill 2.2 workflow."
|
|
119
|
+
},
|
|
120
|
+
{
|
|
121
|
+
"id": "agents-v22-xjmate-high-risk",
|
|
122
|
+
"paths": ["AGENTS.md"],
|
|
123
|
+
"match": "exact-line",
|
|
124
|
+
"text": "- `high-risk`: DB, auth/access/account, content security, files/object storage, client contracts, gateway/deployment/build/tooling, or explicit verify work; run the real `gate_full`, commit/push, verify Jenkins and target surfaces, then record `PASS`, `FAIL`, or `PARTIAL`.",
|
|
125
|
+
"replacement": "- DB, auth/access/account, content security, files/object storage, client contracts, and gateway/deployment/build/tooling changes are high-risk for analysis, design, and review; normal development still uses the changed-scope fast gate and push completion."
|
|
126
|
+
},
|
|
127
|
+
{
|
|
128
|
+
"id": "agents-v22-xjmate-fallback",
|
|
129
|
+
"paths": ["AGENTS.md"],
|
|
130
|
+
"match": "exact-line",
|
|
131
|
+
"text": "- High-risk signals cannot be downgraded. A changed/standard gate cannot substitute for full."
|
|
132
|
+
},
|
|
133
|
+
{
|
|
134
|
+
"id": "agents-v22-xjmate-local-full",
|
|
135
|
+
"paths": ["AGENTS.md"],
|
|
136
|
+
"match": "exact-line",
|
|
137
|
+
"text": "- Local Docker startup/runtime checks remain opt-in by task scope; high-risk local full still requires all configured non-runtime build/test/static checks.",
|
|
138
|
+
"replacement": "- Local Docker startup/runtime checks remain opt-in and run only for a separately requested diagnostic task, not as part of the automatic development gate."
|
|
139
|
+
},
|
|
140
|
+
{
|
|
141
|
+
"id": "engineering-v22-table-high-risk-en",
|
|
142
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
143
|
+
"match": "exact-line",
|
|
144
|
+
"text": "| `high-risk` | DB/auth/payment/deploy/build config or declared high risk | full | verify |",
|
|
145
|
+
"replacement": "| `high-risk` | DB/auth/payment/deploy/build config or declared high risk | changed/quick | push / `DEV-CLOSED` |"
|
|
146
|
+
},
|
|
147
|
+
{
|
|
148
|
+
"id": "engineering-v22-autovpn-table-high-risk",
|
|
149
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
150
|
+
"match": "exact-line",
|
|
151
|
+
"text": "| `high-risk` | migration、auth/access、billing/order、Jenkins、容器与生产部署 | real full | verify |",
|
|
152
|
+
"replacement": "| `high-risk` | migration、auth/access、billing/order、Jenkins、容器与生产部署 | changed/quick | push / `DEV-CLOSED` |"
|
|
153
|
+
},
|
|
154
|
+
{
|
|
155
|
+
"id": "engineering-v22-geemanage-high-risk",
|
|
156
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
157
|
+
"match": "exact-line",
|
|
158
|
+
"text": "- `high-risk` 用于数据库迁移、认证权限、安全、依赖/构建、Jenkins、Compose、运行时配置或显式 verify 工作;必须执行真正的 `commands.gate_full`,不得降级为 changed/standard。",
|
|
159
|
+
"replacement": "- 数据库迁移、认证权限、安全、依赖/构建、Jenkins、Compose 和运行时配置属于 high-risk,提升分析、设计和评审深度;正常开发仍只执行 changed/quick 门禁。"
|
|
160
|
+
},
|
|
161
|
+
{
|
|
162
|
+
"id": "engineering-v22-geemanage-flow",
|
|
163
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
164
|
+
"match": "exact-block",
|
|
165
|
+
"text": "5. 执行解析后的 gate;high-risk 必须 full。\n6. micro/standard 记录 `DEV-CLOSED`;high-risk/verify 在真实验证后记录 `PASS`、`FAIL` 或 `PARTIAL`。",
|
|
166
|
+
"replacement": "5. 仅执行一次配置的 changed/quick 门禁;风险档位只影响分析、设计和评审深度。\n6. 门禁通过后记录 `DEV-CLOSED`、提交并推送;Jenkins、部署和实际验收由项目所有者负责。"
|
|
167
|
+
},
|
|
168
|
+
{
|
|
169
|
+
"id": "engineering-v22-geemill-high-risk",
|
|
170
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
171
|
+
"match": "exact-line",
|
|
172
|
+
"text": "- `high-risk`:数据库迁移、认证/RBAC、MOM/ICS envelope 与 inbox/outbox/replay、排产与仓储锁、生产状态流转、Jenkins/Compose/部署、依赖及工作流工具变更;必须执行真实 `commands.gate_full`,并进入 `verify`。",
|
|
173
|
+
"replacement": "- 数据库迁移、认证/RBAC、MOM/ICS envelope 与 inbox/outbox/replay、排产与仓储锁、生产状态流转、Jenkins/Compose/部署、依赖及工作流工具变更属于 high-risk,提升分析、设计和评审深度;正常开发门禁仍为 changed/quick。"
|
|
174
|
+
},
|
|
175
|
+
{
|
|
176
|
+
"id": "engineering-v22-xjmate-high-risk",
|
|
177
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
178
|
+
"match": "exact-line",
|
|
179
|
+
"text": "- `high-risk`:数据库迁移、认证/访问控制/账号、管理员写操作与审计、内容安全、文件与对象存储、客户端契约、网关/部署/依赖/构建或工作流工具变更;必须执行真实 `commands.gate_full`,并进入 `verify`。",
|
|
180
|
+
"replacement": "- 数据库迁移、认证/访问控制/账号、管理员写操作与审计、内容安全、文件与对象存储、客户端契约、网关/部署/依赖/构建及工作流工具变更属于 high-risk,提升分析、设计和评审深度;正常开发门禁仍为 changed/quick。"
|
|
181
|
+
},
|
|
182
|
+
{
|
|
183
|
+
"id": "engineering-v22-full-fallback-zh",
|
|
184
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
185
|
+
"match": "exact-line",
|
|
186
|
+
"text": "高风险信号不可由 CLI、规则或手工 scope 降级。full 只能由 `gate_full`(或兼容的 `full_gate`)满足,不能回退到 changed/standard。"
|
|
187
|
+
},
|
|
188
|
+
{
|
|
189
|
+
"id": "engineering-v22-geesight-table",
|
|
190
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
191
|
+
"match": "exact-line",
|
|
192
|
+
"text": "| `high-risk` | DB migration、OpenAPI/依赖锁、身份权限、Docker/Compose、MediaMTX、Jenkins | 真实 `gate_full` | `verify` |",
|
|
193
|
+
"replacement": "| `high-risk` | DB migration、OpenAPI/依赖锁、身份权限、Docker/Compose、MediaMTX、Jenkins | changed/quick | push / `DEV-CLOSED` |"
|
|
194
|
+
},
|
|
195
|
+
{
|
|
196
|
+
"id": "engineering-v22-verify-zh",
|
|
197
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
198
|
+
"match": "exact-line",
|
|
199
|
+
"text": "本项目要求 Jenkins 和目标环境验证。high-risk 本地 full 通过后提交推送,再以真实 Jenkins、健康检查、API、页面或业务路径证据记录 `PASS`、`FAIL` 或 `PARTIAL`。未执行的验证不得写成通过。"
|
|
200
|
+
},
|
|
201
|
+
{
|
|
202
|
+
"id": "engineering-v22-xjmate-verify-zh",
|
|
203
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
204
|
+
"match": "exact-line",
|
|
205
|
+
"text": "本项目要求 Jenkins 和目标环境验证。high-risk 本地 full 通过后提交推送,再以真实 Jenkins、目标健康、API、小程序/管理端或业务路径证据记录 `PASS`、`FAIL` 或 `PARTIAL`。未执行的验证不得写成通过。"
|
|
206
|
+
},
|
|
207
|
+
{
|
|
208
|
+
"id": "engineering-v22-autovpn-full-contract",
|
|
209
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
210
|
+
"match": "exact-block",
|
|
211
|
+
"text": "`workflow.profile: auto` 只负责选择最终档位。高风险路径、声明为\n`profile: high-risk` 的规则、显式 full 或 verify 都不可被命令行降级。\n高风险任务必须执行 `commands.gate_full`;changed、standard、light gate\n或单项测试不能冒充 full gate。"
|
|
212
|
+
},
|
|
213
|
+
{
|
|
214
|
+
"id": "engineering-v22-autovpn-closure",
|
|
215
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
216
|
+
"match": "exact-block",
|
|
217
|
+
"text": "6. micro/standard 写 `DEV-CLOSED` 后 commit + push;high-risk 先完成 real\n full,再 commit + push,并继续 Jenkins/目标环境验证后记录\n `PASS`、`FAIL` 或 `PARTIAL`。",
|
|
218
|
+
"replacement": "6. 所有档位只执行 changed/quick 门禁,写 `DEV-CLOSED` 后 commit + push;Jenkins、目标环境和实际验收由项目所有者负责。"
|
|
219
|
+
},
|
|
220
|
+
{
|
|
221
|
+
"id": "engineering-v22-geemanage-external-gate",
|
|
222
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
223
|
+
"match": "exact-line",
|
|
224
|
+
"text": "- `verification.jenkins_required` 和 `verification.target_env_required` 分别要求外部 Jenkins 和目标环境证据。T0012 已修复 GeeManage SCM,Jenkins #16 从 `dev` 精确提交构建、发布并部署成功,因此两项均为强制门禁;不能用本地结果替代外部证据。",
|
|
225
|
+
"replacement": "- T0012 已修复 GeeManage SCM,Jenkins #16 从 `dev` 精确提交构建、发布并部署成功;这是历史环境事实,不是正常编码门禁,后续 Jenkins、目标环境和实际验收由项目所有者负责。"
|
|
226
|
+
},
|
|
227
|
+
{
|
|
228
|
+
"id": "engineering-v22-geemanage-auto-full",
|
|
229
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
230
|
+
"match": "exact-line",
|
|
231
|
+
"text": "- PostgreSQL schema 只通过 `backend/migrations` 变更;迁移、认证和运行时配置自动进入 high-risk/full。",
|
|
232
|
+
"replacement": "- PostgreSQL schema 只通过 `backend/migrations` 变更;迁移、认证和运行时配置提升 high-risk 分析、设计和评审深度,但自动门禁保持 changed/quick。"
|
|
233
|
+
},
|
|
234
|
+
{
|
|
235
|
+
"id": "engineering-v22-geemill-version",
|
|
236
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
237
|
+
"match": "exact-line",
|
|
238
|
+
"text": "本仓库使用 auto-coding-skill 2.2 的自适应开发工作流。Frontmatter 是唯一的手工工作流配置源;项目事实、任务、接口和历史证据继续保存在对应文档中。",
|
|
239
|
+
"replacement": "Frontmatter 是唯一的手工工作流配置源;项目事实、任务、接口和历史证据继续保存在对应文档中。"
|
|
240
|
+
},
|
|
241
|
+
{
|
|
242
|
+
"id": "engineering-v22-xjmate-version",
|
|
243
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
244
|
+
"match": "exact-line",
|
|
245
|
+
"text": "本仓库使用 auto-coding-skill 2.2 的自适应开发工作流。Frontmatter 是唯一的手工工作流配置源;产品决策、任务、接口和历史证据继续保存在项目文档中。",
|
|
246
|
+
"replacement": "Frontmatter 是唯一的手工工作流配置源;产品决策、任务、接口和历史证据继续保存在项目文档中。"
|
|
247
|
+
},
|
|
248
|
+
{
|
|
249
|
+
"id": "engineering-v22-geestack-heading",
|
|
250
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
251
|
+
"match": "exact-line",
|
|
252
|
+
"text": "# GeeStack Engineering Workflow (auto-coding-skill 2.2)",
|
|
253
|
+
"replacement": "# GeeStack Engineering Workflow"
|
|
254
|
+
},
|
|
255
|
+
{
|
|
256
|
+
"id": "engineering-v22-geestack-full-contract",
|
|
257
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
258
|
+
"match": "exact-block",
|
|
259
|
+
"text": "- `high-risk`: authentication, payment, database, gateway, deployment, build\n configuration, or workflow tooling. Run the real `gate_full` and use verified\n closure.\n\nA high-risk signal cannot be downgraded by a CLI flag. The full path must execute\n`commands.gate_full`; a light or standard fallback is not equivalent.",
|
|
260
|
+
"replacement": "- Authentication, payment, database, gateway, deployment, build configuration, and workflow-tooling changes are high-risk for analysis, design, and review; normal development still uses the changed-scope fast gate."
|
|
261
|
+
},
|
|
262
|
+
{
|
|
263
|
+
"id": "engineering-v22-geestack-verification",
|
|
264
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
265
|
+
"match": "exact-block",
|
|
266
|
+
"text": "Jenkins and target verification are enabled for this repository. High-risk work\ntherefore requires the full local gate, push-triggered Jenkins evidence, and the\nconfigured target health/business checks before a PASS closure. Do not claim a\nmatrix or deployment result from a command that did not run.",
|
|
267
|
+
"replacement": "Jenkins and target surfaces exist for this repository, but they are owner-managed after push and are not part of normal coding completion. Do not claim a matrix or deployment result from a command that did not run."
|
|
268
|
+
},
|
|
269
|
+
{
|
|
270
|
+
"id": "engineering-v22-geestock-selector",
|
|
271
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
272
|
+
"match": "exact-block",
|
|
273
|
+
"text": "`auto` is only a selector. The effective profile is always `micro`, `standard`,\nor `high-risk`. A high-risk signal cannot be downgraded with a CLI flag or a\nproject rule. An explicit non-auto profile replaces auto's low/normal baseline.\n`workflow.mode: verify` also requires the full gate.\n\nProject `gate.rules` may declare `paths`, `commands`, `scope`, and an optional\n`profile`. Configure `commands.gate_full` (or legacy `commands.full_gate`) for\nhigh-risk work; a light or standard command does not count as a full gate."
|
|
274
|
+
},
|
|
275
|
+
{
|
|
276
|
+
"id": "engineering-v22-geestock-verified-flow",
|
|
277
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
278
|
+
"match": "exact-block",
|
|
279
|
+
"text": "High-risk or explicit verification:\n\n1. Run the real full gate.\n2. Commit and push.\n3. Verify enabled CI/Jenkins and target-environment surfaces.\n4. Record `PASS`, `FAIL`, or `PARTIAL` from actual evidence."
|
|
280
|
+
},
|
|
281
|
+
{
|
|
282
|
+
"id": "engineering-v22-govchain-heading",
|
|
283
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
284
|
+
"match": "exact-line",
|
|
285
|
+
"text": "# GovChain Engineering Workflow (auto-coding-skill 2.2)",
|
|
286
|
+
"replacement": "# GovChain Engineering Workflow"
|
|
287
|
+
},
|
|
288
|
+
{
|
|
289
|
+
"id": "engineering-v22-govchain-full-contract",
|
|
290
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
291
|
+
"match": "exact-block",
|
|
292
|
+
"text": "- `high-risk`: database, authentication, file transfer, gateway, deployment,\n build configuration, or workflow tooling; run the real full gate and use\n verified closure.\n\nHigh-risk signals cannot be downgraded. A full result is valid only when\n`commands.gate_full` executes; changed/standard fallbacks do not count.",
|
|
293
|
+
"replacement": "- Database, authentication, file-transfer, gateway, deployment, build-configuration, and workflow-tooling changes are high-risk for analysis, design, and review; normal development still uses the changed-scope fast gate."
|
|
294
|
+
},
|
|
295
|
+
{
|
|
296
|
+
"id": "engineering-v22-govchain-full-closure",
|
|
297
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
298
|
+
"match": "exact-line",
|
|
299
|
+
"text": "high-risk work uses `PASS`, `FAIL`, or `PARTIAL` after its full gate."
|
|
300
|
+
},
|
|
301
|
+
{
|
|
302
|
+
"id": "engineering-v22-govchain-disabled-external",
|
|
303
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
304
|
+
"match": "exact-block",
|
|
305
|
+
"text": "- Jenkins and target verification are currently disabled in configuration.\n High-risk work still requires the real local full gate; disabled external\n surfaces must be reported as skipped, never as passed.",
|
|
306
|
+
"replacement": "- Jenkins and target verification are currently disabled in configuration; disabled external surfaces remain owner-managed and must never be reported as passed."
|
|
307
|
+
},
|
|
308
|
+
{
|
|
309
|
+
"id": "engineering-v22-geesight-profile",
|
|
310
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
311
|
+
"match": "exact-block",
|
|
312
|
+
"text": "高风险信号不能被命令行或项目规则降级。只有 high-risk 才自动进入 verify;普通开发不因\n项目具备 Jenkins 和目标环境而被迫执行完整部署闭环。"
|
|
313
|
+
},
|
|
314
|
+
{
|
|
315
|
+
"id": "engineering-v22-geesight-full-command",
|
|
316
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
317
|
+
"match": "exact-line",
|
|
318
|
+
"text": "python3 docs/tools/autopipeline/ap.py light-gate --scope full --profile high-risk --mode verify --explain"
|
|
319
|
+
},
|
|
320
|
+
{
|
|
321
|
+
"id": "engineering-v22-geesight-verified-closure",
|
|
322
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
323
|
+
"match": "exact-block",
|
|
324
|
+
"text": "high-risk 工作必须先通过本地 full gate,再提交推送,随后验证启用的 Jenkins 与目标环境,\n最后依据真实证据记录 PASS、FAIL 或 PARTIAL。Jenkins/目标配置、账号和明文密码直接维护在\nfrontmatter 的 `access.*`;兼容凭据环境变量可继续保留。本地审计或升级不得自行触发构建、部署或目标探测。",
|
|
325
|
+
"replacement": "Jenkins/目标配置、账号和明文密码直接维护在 frontmatter 的 `access.*`,兼容凭据环境变量可继续保留。正常开发在 changed/quick 门禁和推送后结束;本地审计或升级不得自行触发构建、部署或目标探测。"
|
|
326
|
+
}
|
|
327
|
+
],
|
|
328
|
+
"conflict_rules": [
|
|
329
|
+
{
|
|
330
|
+
"id": "stale-workflow-version",
|
|
331
|
+
"paths": ["AGENTS.md", "docs/ENGINEERING.md"],
|
|
332
|
+
"pattern": "auto-coding-skill\\s+2\\.2",
|
|
333
|
+
"flags": "i",
|
|
334
|
+
"message": "stale 2.2 workflow authority remains outside the managed block"
|
|
335
|
+
},
|
|
336
|
+
{
|
|
337
|
+
"id": "expanded-full-gate-en",
|
|
338
|
+
"paths": ["AGENTS.md", "docs/ENGINEERING.md"],
|
|
339
|
+
"pattern": "(?:(?:high[- ]risk|normal development)|(?:(?:runtime|config|schema)(?:/config/schema)?)(?:\\s+(?:changes?|work))?)[^\\n]*(?:must|always|requires?|force|cannot|forbidden|invalid|still requires)[^\\n]*(?:gate_full|full gate|real full|full path|full verification)|(?:gate_full|full gate|real full|full path)[^\\n]*(?:must|requires?|cannot|forbidden|invalid)",
|
|
340
|
+
"flags": "i",
|
|
341
|
+
"message": "normal development is required to run an expanded full gate"
|
|
342
|
+
},
|
|
343
|
+
{
|
|
344
|
+
"id": "expanded-profile-table",
|
|
345
|
+
"paths": ["docs/ENGINEERING.md"],
|
|
346
|
+
"pattern": "^\\s*\\|\\s*`?high[- ]risk`?\\s*\\|[^\\n]*\\|\\s*(?:real\\s+)?`?(?:gate_)?full`?\\s*\\|",
|
|
347
|
+
"flags": "i",
|
|
348
|
+
"message": "profile table still maps high-risk work to a full gate"
|
|
349
|
+
},
|
|
350
|
+
{
|
|
351
|
+
"id": "expanded-full-gate-zh",
|
|
352
|
+
"paths": ["AGENTS.md", "docs/ENGINEERING.md"],
|
|
353
|
+
"pattern": "(?:high-risk|高风险)[^\\n]*(?:必须|不得|不能|不可|要求)[^\\n]*(?:gate_full|full|完整门禁|verify|Jenkins|目标环境)|(?:必须|要求)[^\\n]*(?:gate_full|full)[^\\n]*(?:high-risk|高风险)",
|
|
354
|
+
"flags": "i",
|
|
355
|
+
"message": "正常开发被要求执行 full/verify 外部门禁"
|
|
356
|
+
},
|
|
357
|
+
{
|
|
358
|
+
"id": "post-push-external-verification",
|
|
359
|
+
"paths": ["AGENTS.md", "docs/ENGINEERING.md"],
|
|
360
|
+
"pattern": "(?:after (?:commit/)?push|push-triggered|提交推送后|推送后)[^\\n]*(?:verify|verification|验证)[^\\n]*(?:Jenkins|target|目标)|(?:Jenkins|target|目标)[^\\n]*(?:verify|verification|验证)[^\\n]*(?:after (?:commit/)?push|提交推送后|推送后)",
|
|
361
|
+
"flags": "i",
|
|
362
|
+
"message": "coding closure still requires post-push Jenkins or target verification"
|
|
363
|
+
}
|
|
364
|
+
],
|
|
365
|
+
"dependency_recovery": {
|
|
366
|
+
"allowed_gate": "gate_changed",
|
|
367
|
+
"requires_locked_dependency": true,
|
|
368
|
+
"retry_same_gate_only": true,
|
|
369
|
+
"forbid_full_gate_recovery": true
|
|
370
|
+
}
|
|
371
|
+
}
|