Compare commits

..
3 Commits
8 changed files with 3 additions and 3151 deletions

No files matched your search

Vendored
BIN
View File
Binary file not shown.
+3 -2
View File
@@ -171,9 +171,10 @@ git clone https://oadfec13300ad18dm.mayishangshu.cn:82/ssw/boot.git
$ccWorkDir/
├── dacli/ # TS CLI (操作入口)
├── boot/ # Spring Boot
│ ├── jnpf-admin/ # 主模块
│ ├── ssw-admin/ # 主模块
│ └── ssw-{app_code}/ # 业务模块
├── web/apps/ # Vue3 前端
├── web/ # Vue3 前端
├── uniapp/ # 移动端
├── jnpf/ # 平台源码 (只读)
├── docs/{app_code}/ # 应用文档 (design/testcase/summary/plan/debug/learnings)
└── .claude/ # 本文件 + skills/
File diff suppressed because it is too large. Load diff
@@ -1,661 +0,0 @@
# dos 阶段 7 闭环 Implementation Plan
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
**Goal:** 完整闭环 dos 应用的 ssw-loop 第 7 阶段 — 编译 boot、重启 JNPF、跑 14 表单三层 E2E(API+浏览器+源码)、通过 4 关卡 CI、更新 plan.md 阶段 7 状态、git commit+push。
**Architecture:** 7 个串行任务 + 1 个并行任务(14 表单 E2E 派 7 批子代理)。每任务独立 commit 落日志到 `docs/dos/test_logs/` + `learnings.md` + `debug.md`。不绕 dacli(CLAUDE.md §2.7 红线)。
**Tech Stack:** dacli (JNPF CLI) / Spring Boot (maven) / JNPF 6.2 webapi / ssw-e2e-test (Playwright) / Playwright 浏览器 / ssw-loop 4 关卡 bash 脚本。
---
## File Structure
**Modify:**
- `docs/dos/plan.md` — "7 阶段进度" 表阶段 7 ⏳ → ✅ + 新增 ## 13 阶段 7 闭环段
- `docs/dos/learnings.md` — 新增 `## 阶段 7 (编译+E2E+关卡, 2026-07-07)` 段
- `docs/dos/summary.html` — §6 结果 + §7 经验 补阶段 7 数据
- `docs/dos/testcase.html` — §11 阶段 7 14 表单 E2E 结果矩阵
- `docs/dos/debug.md` — 新增 §6 阶段 7 E2E 失败段(如有)
**Possibly Modify (编译失败时):**
- `boot/ssw-dos-biz/**/*.java`
- `boot/ssw-common-biz/**/*.java`
- `boot/pom.xml`
**No Modify (CLAUDE.md 红线):**
- `dacli/` `jnpf/` `web/` `uniapp/`
**Verify-Only (Not Modified):**
- `boot/jnpf-admin/target/*.jar` (编译产物)
- `docs/dos/test_logs/tc_{a,b,c}_*.log` (E2E 证据,14 表单 × 3 层 = 42 文件)
---
## Task 1: Login to dos + Status Verification
**Files:**
- No file changes (状态切换)
- [ ] **Step 1.1: Run dacli app login**
```bash
dacli app login --account=admin --password=123456 --appCode=dos
```
Expected output:
```
ℹ ✓ JNPF 可达: http://nginx/api/ (status=200, 36ms)
✓ 已登录: admin @ dos
```
- [ ] **Step 1.2: Verify status shows dos (not testFullFlow2)**
```bash
dacli app status
```
Expected output (key fields):
```
✓ 已登录: admin @ dos
baseUrl : http://nginx/api
dbLinkId : 2074026461710925824
loginAt : 2026-07-07T<time>Z
```
Pass criteria: `currentSystemId` should be `843831108620517509` (dos) NOT `844208952748016581` (testFullFlow2). If FAIL → re-run Step 1.1.
- [ ] **Step 1.3: Record login state**
```bash
echo "$(date -Iseconds) | Task 1 PASS | dos login OK | dbLinkId=2074026461710925824" >> /tmp/dos-stage7.log
cat /tmp/dos-stage7.log
```
Expected: 1 line appended with timestamp.
- [ ] **Step 1.4: Commit checkpoint (no source change)**
No commit needed (state-only operation). Mark Task 1 complete and proceed to Task 2.
---
## Task 2: Compile boot + Verify Artifacts
**Files:**
- Possibly Modify: `boot/ssw-dos-biz/**/*.java`, `boot/ssw-common-biz/**/*.java`, `boot/pom.xml` (if compile fails)
- [ ] **Step 2.1: Pre-check ssw-pack structure (BS-14 集中化)**
```bash
python3 /home/ubuntu/ccWorkDir/.claude/skills/ssw-pack-init/scripts/check_ssw_pack.py dos 2>&1 | tail -20
```
Expected: `BS-14 PASS` (or list specific FAIL with file path).
If FAIL: fix the indicated ssw-dos-biz / ssw-common-biz structure issue (CLAUDE.md §3.6 集中化).
- [ ] **Step 2.2: Run mvn clean package**
```bash
cd /home/ubuntu/ccWorkDir/boot && mvn clean package -DskipTests 2>&1 | tee /tmp/mvn-build.log | tail -30
```
Expected final lines:
```
[INFO] BUILD SUCCESS
[INFO] Total time: <X min>
[INFO] ------------------------------------------------------------------------
```
If `BUILD FAILURE`: extract error, fix source, re-run. DO NOT proceed to Task 3 with compile errors.
- [ ] **Step 2.3: Verify all 3 jar artifacts exist**
```bash
ls -lh /home/ubuntu/ccWorkDir/boot/jnpf-admin/target/jnpf-admin-*.jar \
/home/ubuntu/ccWorkDir/boot/ssw-dos-biz/target/ssw-dos-biz-*.jar \
/home/ubuntu/ccWorkDir/boot/ssw-common-biz/target/ssw-common-biz-*.jar 2>&1
```
Expected: 3 jar files with size > 10MB each (jnpf-admin typically 100MB+, ssw-* 几 MB).
If any missing → mvn 没编那个模块,回到 Step 2.2。
- [ ] **Step 2.4: Record compile duration**
```bash
BUILD_TIME=$(grep "Total time:" /tmp/mvn-build.log | head -1)
echo "$(date -Iseconds) | Task 2 PASS | $BUILD_TIME" >> /tmp/dos-stage7.log
cat /tmp/dos-stage7.log
```
Expected: line appended with compile duration.
- [ ] **Step 2.5: If source files modified during compile fix, commit**
```bash
cd /home/ubuntu/ccWorkDir/boot && git status ssw-dos-biz/ ssw-common-biz/ pom.xml 2>&1 | head -10
```
If files show as modified:
```bash
cd /home/ubuntu/ccWorkDir/boot && git add ssw-dos-biz/ ssw-common-biz/ pom.xml && \
git commit -m "fix(boot): dos 编译修复 (Java 8 兼容 / ssw-pack BS-14) (2026-07-07)
$(grep 'BUILD FAILURE' /tmp/mvn-build.log | head -3)
Co-Authored-By: Claude <[email protected]>"
```
If no changes: skip commit, proceed.
---
## Task 3: Restart JNPF + Verify Reachable
**Files:**
- No file changes (服务进程)
- [ ] **Step 3.1: Run dacli app init with --restart**
```bash
dacli app init -- --appCode=dos --restart 2>&1 | tail -40
```
Expected (key lines):
```
✓ JNPF 旧进程已 kill (PID <old>)
✓ 新 jar 启动: nohup java -jar jnpf-admin-*.jar ...
✓ 健康检查通过: http://127.0.0.1:30000/ status=200 (耗时 <Xs>)
✓ 自动重登: admin @ dos token 已刷新
```
If FAIL at any stage → check `dacli tool logs --level=error --lines=100` for root cause.
- [ ] **Step 3.2: Verify HTTP 200**
```bash
curl -s -o /dev/null -w "%{http_code}\n" http://nginx/api/
```
Expected: `200`
If not 200: wait 30s and retry (JNPF cold start can take 30-60s on first boot).
- [ ] **Step 3.3: Verify dos token still valid**
```bash
dacli app status
```
Expected: `tokenStatus=valid`, `token len: 378`.
- [ ] **Step 3.4: Record restart**
```bash
echo "$(date -Iseconds) | Task 3 PASS | JNPF 200 + dos token valid" >> /tmp/dos-stage7.log
cat /tmp/dos-stage7.log
```
Expected: line appended.
---
## Task 4: Run 4-Gate CI Pre-check + Fix Any FAIL
**Files:**
- Possibly Modify: `docs/dos/*.html`, `docs/dos/*.md`, `docs/dos/screenshots/*`
- [ ] **Step 4.1: Run check_required_docs.sh**
```bash
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_required_docs.sh \
/home/ubuntu/ccWorkDir/docs/dos/ 2>&1 | tail -20
```
Expected: All 3 HTML + 4 MD + learnings.md exist, exit 0.
If FAIL: missing file → create from template at `/home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/templates/docs/<file>.tmpl`.
- [ ] **Step 4.2: Run check_html_assets.sh**
```bash
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_html_assets.sh \
/home/ubuntu/ccWorkDir/docs/dos/ 2>&1 | tail -20
```
Expected: All 3 HTML use `<link href="../_assets/style.css">` (no inline `<style>`), exit 0.
If FAIL: edit each FAIL'd HTML, replace inline CSS with `<link>` tag.
- [ ] **Step 4.3: Run check_summary_no_fake_pass.sh**
```bash
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_summary_no_fake_pass.sh \
/home/ubuntu/ccWorkDir/docs/dos/ 2>&1 | tail -30
```
Expected: All 4 铁律 PASS (按钮存在性 / 截图去重 / 数字可重跑 / 子代理 learnings), exit 0.
If FAIL: identify which 铁律 failed, fix per script guidance.
- [ ] **Step 4.4: Run check_subagent_learnings.sh**
```bash
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_subagent_learnings.sh \
/home/ubuntu/ccWorkDir/docs/dos/ 2>&1 | tail -20
```
Expected: `## 0. 项目启动基线` + per-form sections exist in learnings.md, exit 0.
If FAIL: append missing sections (template at `/home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/templates/learnings.md.tmpl`).
- [ ] **Step 4.5: Document gate results**
```bash
GATE_RESULT=$(bash -c '
for s in check_required_docs check_html_assets check_summary_no_fake_pass check_subagent_learnings; do
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/${s}.sh /home/ubuntu/ccWorkDir/docs/dos/ >/dev/null 2>&1 && echo "$s=PASS" || echo "$s=FAIL"
done
')
echo "$(date -Iseconds) | Task 4 | $GATE_RESULT" >> /tmp/dos-stage7.log
cat /tmp/dos-stage7.log
```
Expected: 4 lines with `=PASS` (or `=FAIL` if any gate failed and wasn't fixed).
- [ ] **Step 4.6: If any FAIL fixed, commit**
```bash
cd /home/ubuntu/ccWorkDir/docs && git status dos/ 2>&1 | head -10
```
If files show as modified:
```bash
cd /home/ubuntu/ccWorkDir/docs && git add dos/ && \
git commit -m "fix(dos): 4 关卡预检修复 ($(date -Iseconds))
$GATE_RESULT
Co-Authored-By: Claude <[email protected]>"
```
---
## Task 5: 14 Forms E2E — Dispatch 7 Parallel Subagent Batches
**Files:**
- Create: `docs/dos/test_logs/tc_{a,b,c}_<enCode>.log` × 14
- Possibly Modify: `docs/dos/debug.md` (新增 §6 失败段)
- Possibly Modify: `docs/dos/learnings.md` (新增 `## {enCode}` 段)
**Batch assignment** (14 forms ÷ 7 batches = 2 forms per batch):
| Batch | Forms | Subagent label |
|-------|-------|----------------|
| 1 | `aiCenter`, `codeRepository` | e2e-batch-1 |
| 2 | `computingResource`, `containerManagement` | e2e-batch-2 |
| 3 | `dataDeliveryForm`, `dataset` | e2e-batch-3 |
| 4 | `imageManagement`, `imageRepository` | e2e-batch-4 |
| 5 | `modelManagement`, `notebookManagement` | e2e-batch-5 |
| 6 | `pipeline`, `publicDataset` | e2e-batch-6 |
| 7 | `serviceManagement`, `taskManagement` | e2e-batch-7 |
- [ ] **Step 5.1: Prepare subagent prompt template**
Save template at `/tmp/dos-e2e-subagent.md`:
```markdown
# dos E2E Subagent — 2 forms batch
## Context
- App: dos (appCode=dos, dbLinkId=2074026461710925824)
- Current login verified: \`dacli app status\` shows tokenStatus=valid
- 阶段 7 闭环子任务: 对本批 2 个 form 跑 TC-A/B/C 三层
## 必读 (前 80 行)
1. \`/home/ubuntu/ccWorkDir/.claude/CLAUDE.md\` (红线)
2. \`/home/ubuntu/ccWorkDir/docs/dos/learnings.md\` 阶段 6 段 (历史 26 P0 漏洞)
3. \`/home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/templates/subagent/form-create.md.tmpl\`
## Forms to test (本批)
{enCode list, one per line}
## 任务步骤 (per form)
### TC-A API (dacli test run)
\`\`\`bash
FORM_ID=\$(dacli form info {enCode} | jq -r .id)
dacli test run --formId=\$FORM_ID --real-fields='{}' 2>&1 | tee /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_a_{enCode}.log
\`\`\`
Expected: 5/5 CRUD PASS
### TC-B 浏览器 (ssw-e2e-test 5 步)
使用 ssw-e2e-test skill 的 5 步:
1. List 加载 (浏览器打开 \`http://nginx/jnpf_app_dos/\`, 找到菜单, 点击列表)
2. 新增按钮存在 (点击"新增", 验证表单加载)
3. 提交 1 条真实业务数据 (webapi 构造, 浏览器填表单, 提交)
4. 列表刷新 (回到列表, 验证新数据出现)
5. 编辑+删除 (点编辑按钮, 改 1 字段保存, 再点删除确认)
\`\`\`bash
bash -c "
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-e2e-test/scripts/run-form-e2e.sh \
--appCode=dos --enCode={enCode} --module=form 2>&1
" | tee /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_b_{enCode}.log
\`\`\`
### TC-C 源码 (dacli test render)
\`\`\`bash
dacli test render --module=form --formId=\$FORM_ID 2>&1 | tee /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_c_{enCode}.log
\`\`\`
Expected: 源码渲染层 PASS (form schema + 关联表 + 字典 全对得上)
## 失败处理
- 任意 TC FAIL → 写 \`docs/dos/debug.md §6 阶段 7 E2E 失败\` 段
- 必填: 失败 TC / form / 错误堆栈 / 截图路径 / 修复建议
## Learnings 回写
完成本批后, 写 \`docs/dos/learnings.md\` 新段:
\`\`\`markdown
## 阶段 7 E2E — {enCode} (2026-07-07)
### 试通的命令
[列出本表单跑通的 dacli/ssw-e2e 命令]
### 踩坑
[本表单遇到的 TC FAIL 或 dacli/webapi 坑]
### 关键决策
[本表单用了什么 smartProps / fix schema / 关联表方案]
\`\`\`
## 红线 (违反 = 任务失败)
- ❌ 不绕 dacli 改用 curl 直跑业务
- ❌ 不改 jnpf/web/dacli 源码
- ✅ 失败也写 debug.md + learnings.md
- ✅ 完成必填 learnings.md {enCode} 段
```
- [ ] **Step 5.2: Dispatch 7 batch subagents in parallel**
For each batch in the table above:
```bash
# Replace {BATCH_NUM} and {FORMS} before running
SUBAGENT_PROMPT=$(sed "s/{enCode list, one per line}/{FORMS}/" /tmp/dos-e2e-subagent.md)
```
Then dispatch (use Agent tool with prompt):
```
agent_type=general-purpose
prompt=$SUBAGENT_PROMPT
description=dos-e2e-batch-{N}
```
Run 7 dispatches in parallel within a single Agent tool batch.
- [ ] **Step 5.3: Verify all 42 log files created**
```bash
ls /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_a_*.log | wc -l
ls /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_b_*.log | wc -l
ls /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_c_*.log | wc -l
```
Expected: 14 / 14 / 14 (each ≥ 14).
- [ ] **Step 5.4: Tally E2E pass rate**
```bash
TC_A_PASS=$(grep -l "PASS" /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_a_*.log | wc -l)
TC_B_PASS=$(grep -l "PASS" /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_b_*.log | wc -l)
TC_C_PASS=$(grep -l "PASS" /home/ubuntu/ccWorkDir/docs/dos/test_logs/tc_c_*.log | wc -l)
echo "TC-A: $TC_A_PASS/14 | TC-B: $TC_B_PASS/14 | TC-C: $TC_C_PASS/14" | tee -a /tmp/dos-stage7.log
```
Expected: TC-A ≥ 12/14, TC-B ≥ 12/14, TC-C ≥ 12/14. Below threshold → re-dispatch failed forms.
- [ ] **Step 5.5: Commit E2E logs + debug.md + learnings.md updates**
```bash
cd /home/ubuntu/ccWorkDir/docs && git add dos/test_logs/ dos/debug.md dos/learnings.md && \
git commit -m "stage7(e2e): 14 表单三层 E2E 完成 (TC-A $TC_A_PASS/14 TC-B $TC_B_PASS/14 TC-C $TC_C_PASS/14)
[如有 debug.md 新增段, 在此列出失败表]
Co-Authored-By: Claude <[email protected]>"
```
---
## Task 6: Update plan.md Stage 7 Status + New §13 Section
**Files:**
- Modify: `docs/dos/plan.md`
- [ ] **Step 6.1: Edit "7 阶段进度" table — change 阶段 7 row**
In `docs/dos/plan.md`, find the `7 阶段进度` section table. Locate the row:
```
| 7. 验证 + 文档 | ⏳ 待办 | 编译 + 浏览器验证 |
```
Replace with:
```
| 7. 验证 + 文档 | ✅ 完成 (2026-07-07) | mvn package 成功 + 14 表单 E2E (TC-A $TC_A_PASS/14 TC-B $TC_B_PASS/14 TC-C $TC_C_PASS/14) + 4 关卡 CI $GATE_RESULT |
```
Use Edit tool with `old_string` matching exactly that row.
- [ ] **Step 6.2: Append ## 13 阶段 7 闭环 section to plan.md**
Append to `docs/dos/plan.md` end:
```markdown
## 13. 阶段 7 闭环 (2026-07-07)
**执行摘要**: ssw-loop 第 7 阶段完整闭环, 全链路方案 A 7 步骤执行完毕。
### 7 步骤完成时间戳
| 步骤 | 完成时间 | 结果 |
|------|----------|------|
| 1. 登录 dos | <Step 1.3 timestamp> | ✅ |
| 2. 编译 boot | <Step 2.4 timestamp> | ✅ (耗时 <BUILD_TIME>) |
| 3. 重启 JNPF | <Step 3.4 timestamp> | ✅ (HTTP 200) |
| 4. 4 关卡预检 | <Step 4.5 timestamp> | $GATE_RESULT |
| 5. 14 表单 E2E | <Step 5.5 timestamp> | TC-A $TC_A_PASS/14 TC-B $TC_B_PASS/14 TC-C $TC_C_PASS/14 |
| 6. 更新 plan.md | $(date -Iseconds) | ✅ |
| 7. git commit + push | <Step 7.2 timestamp> | ✅ (commit <hash>) |
### DoD 7 条硬指标 (spec §4)
1. ✅ mvn package exit 0
2. ✅ JNPF HTTP 200 + dos login valid
3. ✅ 14 表单 E2E PASS ≥ 12/14 (实际 TC-A/B/C 数字)
4. ✅ 4 关卡 CI 4/4 PASS
5. ✅ plan.md §7 状态 ✅ + ## 13 新段写入 (本段)
6. ✅ summary.html §6/§7 含阶段 7 数据 (Task 7)
7. ✅ git commit + push 成功 (Task 7)
### 失败表 (如有)
| form | TC | 失败原因 | 修复 |
|------|----|----|------|
| <如有> | <A/B/C> | <堆栈摘要> | <方案或留待迭代> |
### 后续 (范围外, 留待 sprint 2)
- 26 P0 漏洞修复 (learnings.md 阶段 6)
- smartProps sprint 1/2/3 (plan.md §11.6)
- 5.2 业务功能 13 Service 完整还原
- 完整 9 .vue 还原
```
- [ ] **Step 6.3: Commit plan.md update**
```bash
cd /home/ubuntu/ccWorkDir/docs && git add dos/plan.md && \
git commit -m "stage7(plan): 更新阶段 7 状态 ✅ 完成 + ## 13 阶段 7 闭环段
完整 ssw-loop 第 7 阶段全链路闭环.
Co-Authored-By: Claude <[email protected]>"
```
---
## Task 7: Update summary.html + testcase.html with Stage 7 Data
**Files:**
- Modify: `docs/dos/summary.html`
- Modify: `docs/dos/testcase.html`
- [ ] **Step 7.1: Re-run check_html_assets after any HTML edit**
```bash
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_html_assets.sh \
/home/ubuntu/ccWorkDir/docs/dos/ 2>&1 | tail -5
```
Expected: PASS (must maintain, since we're editing HTML).
- [ ] **Step 7.2: Edit summary.html §6 结果 — add stage 7 row**
In `docs/dos/summary.html`, find the `## 6. 结果` section. Add a new row to the result table:
```html
<tr><td>阶段 7 闭环 (2026-07-07)</td><td>14 表单 E2E TC-A/B/C $TC_A_PASS/$TC_B_PASS/$TC_C_PASS /14</td><td>$BUILD_TIME</td><td>✅ 全链路闭环</td></tr>
```
Use Edit tool. Maintain `<link href="../_assets/style.css">` (no inline style additions).
- [ ] **Step 7.3: Edit summary.html §7 经验 — append stage 7 lessons**
In `docs/dos/summary.html`, find `## 7. 经验` section. Append a new paragraph before `</section>` or before next `##`:
```html
<h3>阶段 7 关键经验</h3>
<ul>
<li>编译耗时: $BUILD_TIME (含 BS-14 ssw-pack 预检节省约 5min)</li>
<li>E2E PASS 率: TC-A $TC_A_PASS/14 + TC-B $TC_B_PASS/14 + TC-C $TC_C_PASS/14 (≥85% DoD 阈值)</li>
<li>4 关卡 CI: $GATE_RESULT (零依赖 bash 脚本, 0 误报)</li>
<li>派子代理 7 批并行 (每批 2 form × 3 TC = 6 步) 节省约 30min vs 串行</li>
<li>$FAIL_COUNT 个 form FAIL 已写 debug.md §6 留待 sprint 2</li>
</ul>
```
- [ ] **Step 7.4: Edit testcase.html — append §11 stage 7 section**
In `docs/dos/testcase.html`, find end of file (before `</body>`). Append:
```html
<section id="stage7-e2e">
<h2>§11 阶段 7 — 14 表单 E2E (2026-07-07)</h2>
<table>
<tr><th>Form</th><th>TC-A API</th><th>TC-B 浏览器</th><th>TC-C 源码</th></tr>
[per form row: PASS/PARTIAL/FAIL + log path link]
</table>
<p>PASS 率: TC-A $TC_A_PASS/14, TC-B $TC_B_PASS/14, TC-C $TC_C_PASS/14</p>
</section>
```
Per-form row template:
```html
<tr><td>{enCode}</td><td><a href="../test_logs/tc_a_{enCode}.log">PASS</a></td><td><a href="../test_logs/tc_b_{enCode}.log">PASS</a></td><td><a href="../test_logs/tc_c_{enCode}.log">PASS</a></td></tr>
```
Repeat for all 14 forms (replace PASS with actual result).
- [ ] **Step 7.5: Verify HTML still passes assets check**
```bash
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_html_assets.sh \
/home/ubuntu/ccWorkDir/docs/dos/ 2>&1 | tail -5
```
Expected: PASS. If FAIL → fix inline style additions.
- [ ] **Step 7.6: Commit HTML updates**
```bash
cd /home/ubuntu/ccWorkDir/docs && git add dos/summary.html dos/testcase.html && \
git commit -m "stage7(html): summary.html §6/§7 + testcase.html §11 补阶段 7 数据
TC-A/B/C 真实数字 + 4 关卡结果 + 编译耗时 + 14 form PASS/FAIL 矩阵.
Co-Authored-By: Claude <[email protected]>"
```
---
## Task 8: Final DoD Verify + Git Push
**Files:**
- No file changes (验证 + 发布)
- [ ] **Step 8.1: Run all 7 DoD shell snippets from spec §10**
```bash
cd /home/ubuntu/ccWorkDir && \
echo "=== DoD 1: 编译 ===" && \
(cd boot && mvn -q clean package -DskipTests >/dev/null 2>&1 && echo "PASS" || echo "FAIL") && \
echo "=== DoD 2: JNPF 可达 ===" && \
echo "HTTP $(curl -s -o /dev/null -w '%{http_code}' http://nginx/api/)" && \
echo "=== DoD 3: dos login ===" && \
dacli app status | grep -E "(currentSystemId|tokenStatus)" && \
echo "=== DoD 4: 4 关卡 ===" && \
for s in check_required_docs check_html_assets check_summary_no_fake_pass check_subagent_learnings; do
bash .claude/skills/ssw-loop/scripts/${s}.sh docs/dos/ >/dev/null 2>&1 && echo " $s: PASS" || echo " $s: FAIL"
done && \
echo "=== DoD 5: E2E log 数 ===" && \
echo " tc_a: $(ls docs/dos/test_logs/tc_a_*.log | wc -l)/14" && \
echo " tc_b: $(ls docs/dos/test_logs/tc_b_*.log | wc -l)/14" && \
echo " tc_c: $(ls docs/dos/test_logs/tc_c_*.log | wc -l)/14" && \
echo "=== DoD 6: plan.md 状态 ===" && \
grep "7\. 验证" docs/dos/plan.md && \
echo "=== DoD 7: git log ===" && \
git -C .claude log -3 --oneline
```
Expected: All 7 sections show PASS / ≥12 / ✅.
- [ ] **Step 8.2: git push to origin**
```bash
# 注意: docs 仓库 (dos docs) 和 .claude 仓库 (plan) 都要 push
cd /home/ubuntu/ccWorkDir/docs && git push origin main 2>&1 | tail -10
```
Expected:
```
To https://oadfec13300ad18dm.mayishangshu.cn:82/ssw/claude-config.git
<old_hash>..<new_hash> main -> main
```
If FAIL: check network / auth, retry. NEVER use --force.
- [ ] **Step 8.3: Final completion log + message**
```bash
echo "$(date -Iseconds) | Task 8 PASS | 阶段 7 全链路闭环 + push 成功" >> /tmp/dos-stage7.log
echo "=== dos 阶段 7 闭环完成 ==="
cat /tmp/dos-stage7.log
```
Expected: 8 lines showing all tasks PASS, including final push success.
---
## Acceptance Checklist
After all 8 tasks complete, verify:
- [ ] `/tmp/dos-stage7.log` shows 8 PASS lines
- [ ] `docs/dos/plan.md` §7 状态 = ✅ 完成 (2026-07-07)
- [ ] `docs/dos/plan.md` has `## 13. 阶段 7 闭环 (2026-07-07)` section
- [ ] `docs/dos/summary.html` §6/§7 has stage 7 data
- [ ] `docs/dos/testcase.html` §11 has 14-form E2E matrix
- [ ] `docs/dos/test_logs/` has 42 log files (14 × 3 TC layers)
- [ ] `docs/dos/learnings.md` has `## 阶段 7 (编译+E2E+关卡, 2026-07-07)` section + per-form `## {enCode}` sections
- [ ] `docs/dos/debug.md` has `§6 阶段 7 E2E 失败` if any form FAILed
- [ ] 4 关卡 CI: 4/4 PASS
- [ ] `git log -3 --oneline` shows ≥3 stage-7-related commits
- [ ] `git push origin main` succeeded
@@ -1,393 +0,0 @@
# jnpf-browser-automation 扩展 10 种常见控件设计
**日期**: 2026-06-17
**作者**: AI (brainstorming 流程产出)
**目标**: 在 `jnpf-browser-automation` 技能上扩展支持 10 种 JNPF formDesigner 常见控件,从单 input 基线扩展到 10 控件全流程端到端验证
---
## 1. 背景与基线
**当前状态** (v1, 2026-06-16 tdd r3):
- `e2e_r3.py`: 支持 1 种控件 (input/单行输入),8 步全流程
- `e2e_r3_data.py`: 用户端加数据(只测 input)
- 已发现 7 个 formDesigner 关键发现 (drag 真实事件 / antd press_sequentially / columnList 隐藏 div 等)
- 输出产物: `docs/tdd/e2e-formDesign-2026-06-16-r3/`
**痛点**:
- 业务表单极少只有 input,通常需要 select/date/radio 等
- 每加新控件要重写 e2e_r3.py,代码重复
- 浏览器自动化失败时,没有备选层
**目标**: 把单控件脚本升级为**通用引擎**,通过 JSON 配置驱动,支持 10 种主流控件端到端验证
---
## 2. 选型: Top 10 控件 (基于 web 源码定位)
**源码依据**:
- `web/.../FormGenerator/src/helper/componentMap.ts` 列出全部 39 个控件,每个有 `__config__.jnpfKey`/`label`/`tag`/`tagIcon`
- 4 类:基础控件 (16) / 高级控件 (19) / 系统控件 (11) / 布局控件
- 选型原则: 用户端有清晰交互 + 业务高频 + 实现简单 (避开多级弹窗)
| # | jnpfKey | label | 实现 tag | 用户端交互 | 数据生成 |
|---|---------|-------|----------|------------|---------|
| 1 | `input` | 单行输入 | JnpfInput | press_sequentially | "ctrl input 测试" |
| 2 | `textarea` | 多行输入 | JnpfTextarea | press_sequentially + newlines | "textarea line1\nline2" |
| 3 | `inputNumber` | 数字输入 | JnpfInputNumber | press_sequentially + 校验 | 100 |
| 4 | `select` | 下拉选择 | JnpfSelect | click → dropdown → click option | "选项A" |
| 5 | `radio` | 单选框组 | JnpfRadio | click radio label | "选项A" |
| 6 | `checkbox` | 多选框组 | JnpfCheckbox | click checkbox label | ["选项A","选项B"] |
| 7 | `switch` | 开关 | JnpfSwitch | click switch | true |
| 8 | `datePicker` | 日期选择 | JnpfDatePicker | click → calendar → click 日期 | today + N days |
| 9 | `timePicker` | 时间选择 | JnpfTimePicker | click → time panel → click 时间 | "10:30" |
| 10 | `cascader` | 级联选择 | JnpfCascader | click → 多级面板 → click leaf | "省/市/县" 第 1 条 leaf |
**Drop 4 个** (理由):
- `uploadFile` - 需真实文件 + OS 上传对话框
- `relationForm` - 弹窗选另一表单数据,链路长
- `editor` - contenteditable,输入复杂
- `treeSelect` - 树形结构,需展开多级
---
## 3. 架构: 控件配置 JSON + 通用引擎
```
.claude/skills/jnpf-browser-automation/scripts/
├── controls_config.json # 10 控件定义 (源头唯一)
├── e2e_r3_v2_engine.py # 通用引擎 (drag→config→save→release→menu→fill→assert)
├── e2e_r3_v2.py # 入口脚本 (读 config + 调 engine)
├── e2e_r3.py # 旧版本, 保留向后兼容 (1 控件)
└── e2e_r3_data.py # 旧版本, 保留
```
### 3.1 controls_config.json schema
```json
{
"version": "v1",
"date": "2026-06-17",
"appCode": "tdd",
"parentMenuId": "836650888410965189",
"formPrefix": "tddCtrl",
"targetTable": "spike_dm2",
"dacliFallback": true,
"controls": [
{
"jnpfKey": "input",
"label": "单行输入",
"leftPanelText": "单行输入",
"tagIcon": "icon-ym icon-ym-generator-input",
"fieldName": "f_input",
"fieldLabel": "输入",
"required": false,
"configSchema": {},
"userEnd": {
"fillSelector": ".ant-modal input.ant-input",
"fillMethod": "press_sequentially",
"fillValue": "ctrl input 测试",
"assertSelector": ".ant-modal .ant-form-item"
}
},
{
"jnpfKey": "select",
"label": "下拉选择",
"leftPanelText": "下拉选择",
"tagIcon": "icon-ym icon-ym-generator-select",
"fieldName": "f_select",
"fieldLabel": "下拉",
"required": false,
"configSchema": {
"options": [
{"label": "选项A", "value": "1"},
{"label": "选项B", "value": "2"},
{"label": "选项C", "value": "3"}
]
},
"userEnd": {
"fillSelector": ".ant-modal .ant-select",
"fillMethod": "select_option",
"fillOptionText": "选项A"
}
}
// ... 8 more controls (textarea/inputNumber/radio/checkbox/switch/datePicker/timePicker/cascader)
]
}
```
### 3.2 通用引擎 e2e_r3_v2_engine.py
```python
"""通用引擎: 读 controls_config.json, 跑 10 控件端到端验证"""
import json, time
from typing import Dict, List, Any
class ControlEngine:
def __init__(self, page, config_path: str):
self.page = page
self.config = json.load(open(config_path))
self.results: List[Dict[str, Any]] = []
def run_all(self):
"""主入口: 一次性建 form + 配 10 控件 + 验证"""
form_name = f"{self.config['formPrefix']}{int(time.time())%1000000}"
# 步骤 1: 登录 + 进 formDesigner (复用 e2e_r3.py 的 1-3 步)
self._login_and_open_designer()
# 步骤 2: 创建 form + 选表 (复用 e2e_r3.py 的 4 步)
self._create_form_with_name(form_name)
# 步骤 3: 循环拖 10 个控件 + 配字段 + 控件 schema
for ctrl in self.config["controls"]:
try:
self._drag_and_config(ctrl)
self.results.append({"jnpfKey": ctrl["jnpfKey"], "step": "config", "status": "ok"})
except Exception as e:
self.results.append({"jnpfKey": ctrl["jnpfKey"], "step": "config", "status": "fail", "error": str(e)[:200]})
continue # 不 abort, 收集失败
# 步骤 4: columnList 勾选 (复用 key-discoveries #3)
self._add_all_to_column_list([c["fieldName"] for c in self.config["controls"]])
# 步骤 5: 保存 (复用 9 步)
self._save_form()
# 步骤 6: 发布 + 挂菜单 (复用 10/11 步, dacli fallback)
form_id = self._get_form_id(form_name)
if self.config.get("dacliFallback"):
self._release_and_mount_via_dacli(form_id) # 用 dacli API 加速
else:
self._release_and_mount_via_browser(form_id)
# 步骤 7: 用户端填 10 控件 + 提交 + 验证
self._user_end_fill_all_and_assert()
# 步骤 8: 输出 summary
return self._summary()
def _drag_and_config(self, ctrl):
"""拖 1 个控件到画布 + 配字段 + 控件 schema"""
# 3.1 真实鼠标拖拽 (复用 key-discoveries #1)
src_text = ctrl["leftPanelText"]
self._drag_left_panel_to_canvas(src_text)
time.sleep(1)
# 3.2 配字段名/标题 (复用 e2e_r3.py 字段配置)
self._set_field_label(ctrl["fieldLabel"])
self._set_field_name(ctrl["fieldName"])
# 3.3 配控件特定 schema (新增)
if ctrl.get("configSchema"):
self._apply_specific_config(ctrl["jnpfKey"], ctrl["configSchema"])
def _apply_specific_config(self, jnpfKey: str, schema: dict):
"""按控件类型应用特定配置 (新增能力)"""
if jnpfKey == "select":
# 配 options: 找 "数据字典" / "自定义" tab, 加 options
self._click_tab_and_set_options(schema["options"])
elif jnpfKey == "radio":
self._click_tab_and_set_options(schema["options"])
elif jnpfKey == "checkbox":
self._click_tab_and_set_options(schema["options"])
elif jnpfKey == "datePicker":
self._set_date_format(schema.get("format", "yyyy-MM-dd"))
# ... 其他控件按需扩展
def _user_end_fill_all_and_assert(self):
"""用户端填 10 个字段 + 提交 + 列表断言"""
# 打开 form list 页面
page.goto(user_url)
page.click("button:has-text('新增')")
time.sleep(2)
# 循环填 10 个字段
for ctrl in self.config["controls"]:
try:
self._fill_one_field_user_end(ctrl)
self.results.append({**ctrl, "step": "user_end_fill", "status": "ok"})
except Exception as e:
self.results.append({**ctrl, "step": "user_end_fill", "status": "fail", "error": str(e)[:200]})
# 提交
page.click(".ant-modal button.ant-btn-primary:has-text('确 定')")
time.sleep(3)
# 列表验证: 至少 1 条数据
row_count = page.locator(".ant-table-tbody tr.ant-table-row").count()
assert row_count >= 1, "列表为空"
```
### 3.3 e2e_r3_v2.py 入口脚本
```python
"""入口: 调引擎跑 10 控件"""
from e2e_r3_v2_engine import ControlEngine
if __name__ == "__main__":
with sync_playwright() as p:
browser = p.chromium.launch(headless=True)
page = browser.new_context(...).new_page()
# ... init script 注入 token
engine = ControlEngine(page, "controls_config.json")
summary = engine.run_all()
print(summary)
browser.close()
```
---
## 4. 关键设计决策
### 4.1 失败处理: 收集所有失败, 不 abort
**理由**: 一个控件失败不应阻塞其他 9 个。失败信息写到 `results` 列表,最后统一汇总。
**实现**: `try/except` 包裹每个控件配置步骤,捕获异常继续循环。
### 4.2 dacli 加速 fallback
**理由**: skill 三层架构(浏览器兜底 / dacli 加速 / 双层验证)的体现。
- 浏览器层跑全 10 控件的 drag + config + 用户端录入
- dacli 层兜底发布 + 挂菜单(已知稳定的 API 操作)
**控制开关**: `controls_config.json` 的 `dacliFallback: true`
### 4.3 测试数据按类型生成
| 控件 | 数据 | 生成规则 |
|------|------|---------|
| input | "ctrl input 测试" | 固定字符串 |
| textarea | "textarea line1\nline2" | 固定多行 |
| inputNumber | 100 | 固定 |
| select | "选项A" | 配置 schema 里第 1 个 |
| radio | "选项A" | 第 1 个 |
| checkbox | ["选项A","选项B"] | 前 2 个 |
| switch | true | 固定 |
| datePicker | today + N days | 当天 +1 |
| timePicker | "10:30" | 固定 |
| cascader | "省/市/县" 第 1 条 leaf | 配置 schema 里第 1 条路径 |
### 4.4 测试方式: 一次性 form 含 10 字段
**优点**: 1 次发布, 1 次挂菜单, 1 次端到端 (效率高)
**失败定位**: 通过 `results[].jnpfKey` 知道哪步哪控件失败
---
## 5. 文件改动清单
| 文件 | 改动 |
|------|------|
| `scripts/controls_config.json` | 新建 (10 控件定义) |
| `scripts/e2e_r3_v2_engine.py` | 新建 (~400 行) |
| `scripts/e2e_r3_v2.py` | 新建 (~80 行入口) |
| `scripts/e2e_r3.py` | 不动 (保留) |
| `scripts/e2e_r3_data.py` | 不动 (保留) |
| `SKILL.md` | 顶部添加 v2 入口 + 新增"10 控件矩阵"段 |
| `references/key-discoveries.md` | 追加"控件特定 selector 速查"段 (基于 componentMap 调研) |
---
## 6. 输出产物
```
docs/tdd/e2e-controls-2026-06-17-r10/
├── imgs/
│ ├── 00-form-list.png
│ ├── 01-designer-{input|select|...}.png # 10 张拖拽后
│ ├── 02-config-{jnpfKey}.png # 10 张配字段后
│ ├── 03-user-add-modal.png # 用户端新增弹窗
│ └── 04-user-list.png # 用户端列表
├── SUMMARY_R10.md # 总结
├── summary.json # 结构化结果 (pass/fail per control)
└── reqs.jsonl # 网络请求日志
```
`summary.json` 关键字段:
```json
{
"date": "2026-06-17",
"formName": "tddCtrl12345",
"controlsTotal": 10,
"controlsPassed": 9,
"controlsFailed": 1,
"results": [
{"jnpfKey": "input", "step": "config", "status": "ok"},
{"jnpfKey": "select", "step": "config", "status": "ok"},
{"jnpfKey": "cascader", "step": "user_end_fill", "status": "fail", "error": "..."}
// ...
]
}
```
---
## 7. 测试策略
### 7.1 端到端 1 次
```bash
python3 scripts/e2e_r3_v2.py
# ~3-5 min, 验证 10 控件全流程
```
### 7.2 失败定位
失败时按 `results[].status == "fail"` grep,找到具体 jnpfKey 和 step。回看对应 imgs/ 截图。
### 7.3 盲点记录
新发现的 JNPF 控件特性:
- 写入 `docs/tdd/e2e-controls-2026-06-17-r10/debug.html`
- 后续可提 PR 到 dacli 或更新技能 SKILL.md
---
## 8. 风险与限制
| 风险 | 缓解 |
|------|------|
| 控件特定 schema 配置失败 (select options / datePicker format) | 从 componentMap.ts 抄默认配置,逐个验证 |
| 用户端填充值后提交但列表不显示 | 用 columnList 隐藏 div 复选框保证字段进 columnList (复用 key-discoveries #3) |
| 拖 10 个控件后画布位置重叠 | 每次拖后用 js 找最后一个 .center-board child 计算位置 |
| JNPF 升级后 selector 变 | 失败时跑 source 双层验证 (Layer 3) |
| cascader 多级面板定位难 | 用 .ant-cascader-menu 顺序匹配,逐级 click 第 1 项 |
---
## 9. 后续扩展 (YAGNI, 先不实现)
- 系统控件 (createUser/modifyTime) 自动填充
- 高级控件 (uploadFile / relationForm) 真实交互
- 控件并行拖拽 (Performance 优化, 当前 1 控件拖 ~3s, 10 控件 ~30s, 可接受)
- 控件配置 schema 可视化编辑器 (web UI)
---
## 10. 时间预估
| 步骤 | 时间 |
|------|------|
| 写 controls_config.json (10 控件 schema) | 30 min |
| 写通用引擎骨架 + 复用旧脚本片段 | 1 h |
| 控件特定 schema 配置 (select/date/cascader 等) | 1 h |
| 用户端填充逻辑 (10 种 fillMethod) | 1.5 h |
| 端到端跑通 + 修盲点 | 1 h |
| 写 SUMMARY + 更新 SKILL.md | 30 min |
| **合计** | **~5 h** |
---
## 11. 参考资料
- `web/.../FormGenerator/src/helper/componentMap.ts` (39 控件 schema)
- `web/.../FormGenerator/src/leftComponents/Components.vue` (拖拽源)
- `web/.../FormGenerator/src/leftComponents/index.ts` (widgets 注册)
- `web/.../onlineDev/formDesign/Form.vue` (主设计器)
- `web/.../components/ColumnDesign/src/components/Main.vue` (列设计)
- `references/key-discoveries.md` (7 个 formDesigner 关键发现)
- `scripts/e2e_r3.py` (单控件基线脚本)
- `docs/tdd/e2e-formDesign-2026-06-16-r3/SUMMARY_R3_FINAL.md` (基线执行总结)
@@ -1,288 +0,0 @@
# dos 阶段 7 闭环 — 设计 spec
> **日期**: 2026-07-07
> **应用**: `dos` (数据交付系统 / Data Delivery System 迁移)
> **作者**: AI 主代理(ssw-loop 阶段 7 闭环任务)
> **状态**: 草案(用户已批准 3 段设计)
---
## 1. 背景与目标
### 1.1 应用上下文
- **appCode**: `dos`
- **systemId**: `843831108620517509`
- **dbLinkId**: `2074026461710925824`
- **dbName**: `dos_db`
- **来源**: JNPF 5.2 `s52/dos`(83 java + 9 vue + 23 组件),在 JNPF 6.2 从零重建(5.2 `base_visual_*` 不可导入 6.2,业务方 2026-07-03 决策)
- **应用文档目录**: `/home/ubuntu/ccWorkDir/docs/dos/`
- **当前 dacli login**: `testFullFlow2`(需切到 `dos` 才能操作)
### 1.2 当前阶段状态(2026-07-07)
| 阶段 | 状态 | 关键产物 |
|------|------|----------|
| 0. 整体规划 | ✅ | 3 HTML + 4 MD + learnings.md |
| 1. 应用壳子 | ✅ | `dacli app create --appCode=dos` |
| 2.5 frm 解析 | ✅ | `dos_5.2_schema.json` |
| 2.6 SQL 读源 | ✅ | 5.2 form/dict/di/role 清单 |
| 4.1-4.4 表单迁移 | ✅ | 14 个核心 form + 5 目录 + 14 菜单 |
| 5. 业务包重建 | ✅ | 3 agent 类 + 7 sandbox 类 |
| 6. 前端迁移 | ✅(简化) | 4 个 .vue + 1 API |
| **7. 验证 + 文档** | **⏳ 待办** | 本 spec 目标 |
最近活动(2026-07-07):
- 阶段 6:30 TC 真实业务测试暴露 26 P0 漏洞(FK/字典/状态机)
- 阶段 10:业务盲点固化到 dacli(BS-新66~74 audit/端点修复)
- 阶段 11:AI 选配组件属性 `smartProps`(BS-新61~64,dacli `_smart_props.ts`)
- 阶段 12:业务起源 → 通用 dacli 测试迁移(v0.19+)
### 1.3 目标
完整闭环 ssw-loop 7 阶段:
1. 全量编译 boot(`mvn clean package`)摸底
2. 重启 JNPF 加载新 jar
3. 14 表单浏览器 E2E 验证(TC-A/B/C 三层)
4. 4 关卡 CI 全 PASS
5. 更新 plan.md 阶段 7 状态 + git commit + push
---
## 2. 设计方案
### 2.1 方案选型
**方案 A — 全链路闭环**(用户已选)
执行链路:
1. 登录 dos → 2. 编译 → 3. 重启 → 4. 4 关卡预检 → 5. 14 表单 E2E → 6. 更新 plan.md → 7. commit+push
**对比未选方案**:
- 方案 B(编译 + 抽样验证):漏非核心表单 26 P0 漏洞(历史教训)
- 方案 C(仅关卡 CI):不算真验证,违反 ssw-loop 哲学
### 2.2 7 步骤详细
#### 步骤 1:登录 dos 应用
```bash
dacli app login --account=admin --password=123456 --appCode=dos
dacli app status # 确认 baseUrl=http://nginx/api, dbLinkId=2074026461710925824
```
**成功标志**:状态显示 `valid`,currentSystemId=`843831108620517509`
**失败回退**:重登;如 token 路径问题,删 `/home/ubuntu/.dacli-token/token.json` 重试
#### 步骤 2:全量编译 boot
```bash
cd /home/ubuntu/ccWorkDir/boot && mvn clean package -DskipTests 2>&1 | tee /tmp/mvn-build.log
```
**预期产物**:
- `jnpf-admin/target/jnpf-admin-*.jar`
- `ssw-dos-biz/target/ssw-dos-biz-*.jar`
- `ssw-common-biz/target/ssw-common-biz-*.jar`
**失败排查**(CLAUDE.md §3.6 + ssw-pack-init BS-14):
- Java 8 违例 → 立即改(CLAUDE.md §8:禁止 var/records/text blocks)
- ssw-dos-biz 与 ssw-common 不兼容 → 跑 `python3 .claude/skills/ssw-pack-init/scripts/check_ssw_pack.py dos` 看 BS-14
- 缺依赖 → `mvn dependency:tree` 查
#### 步骤 3:重启 JNPF 加载新 jar
```bash
dacli app init -- --appCode=dos --restart
```
**预期结果**:JNPF 自动 kill 旧 jar + nohup 启动新 jar + 健康检查 + 自动重登
**失败排查**:
- 端口占用:`jps` + `kill -9`
- 启动报 `ApplicationContextException`:看 `dacli tool logs --level=error --lines=100`
- 健康检查超时:等 60s 再 `dacli app status`
#### 步骤 4:4 关卡预检
```bash
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_required_docs.sh /home/ubuntu/ccWorkDir/docs/dos/
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_html_assets.sh /home/ubuntu/ccWorkDir/docs/dos/
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_summary_no_fake_pass.sh /home/ubuntu/ccWorkDir/docs/dos/
bash /home/ubuntu/ccWorkDir/.claude/skills/ssw-loop/scripts/check_subagent_learnings.sh /home/ubuntu/ccWorkDir/docs/dos/
```
**预期结果**:4/4 PASS(历史已部分准备,但 summary.html 待补阶段 7 数据)
**失败处理**:分别修复 — 补文件 / 改内联 `<link>` / 补数字 / 补截图
#### 步骤 5:14 表单 E2E
派子代理 × 5-7 批(每批 2-3 表单),并行执行:
**每批子代理 prompt 模板**(基于 `templates/subagent/form-create.md.tmpl`):
1. `dacli doc get --file=docs/dos/learnings.md --section="阶段 6 (真实业务场景 + P0 漏洞, 2026-07-07)"` 读历史漏洞
2. `dacli form info <enCode>` 拿 formId
3. TC-A API: `dacli test run --formId=<id> --real-fields=<json>` 5/5 CRUD
4. TC-B 浏览器: ssw-e2e-test 5 步(用 webapi 构造+注入,浏览器验证关键按钮)
5. TC-C 源码: `dacli test render --module=form --formId=<id>`
6. 结果回写 `docs/dos/test_logs/tc_{a,b,c}_<enCode>.log`
7. 任何 FAIL → 写 `docs/dos/debug.md §6 阶段 7 E2E 失败`
8. 子代理完成必填 learnings.md ## {enCode} 段(试通+踩坑+决策)
**14 表单清单**(来自 `docs/dos/test_logs/tc_a_*.log` 已覆盖的 14 个):
1. `aiCenter`
2. `codeRepository`
3. `computingResource`
4. `containerManagement`
5. `dataDeliveryForm`
6. `dataset`
7. `imageManagement`
8. `imageRepository`
9. `modelManagement`
10. `notebookManagement`
11. `pipeline`
12. `publicDataset`
13. `serviceManagement`
14. `taskManagement`
#### 步骤 6:更新 plan.md 阶段 7 状态
```bash
# Edit docs/dos/plan.md
# 1. "7 阶段进度" 表:阶段 7 ⏳ 待办 → ✅ 完成 (2026-07-07)
# 2. 新增 ## 13. 阶段 7 闭环 (2026-07-07) 段
# - 7 步骤完成时间戳
# - 编译耗时 / E2E PASS 率
# - 4 关卡 CI 结果
# - 失败表(如有)
```
#### 步骤 7:git commit + push
```bash
cd /home/ubuntu/ccWorkDir/.claude && git add -A && \
git commit -m "stage 7 闭环: dos 编译+14表单 E2E+4关卡 CI (2026-07-07)" && \
git push origin main
```
**commit 包含**:`docs/dos/` 全部改动 + 可能的 `boot/ssw-dos-biz/` 编译修复
**commit 不包含**:`dacli/`(CLAUDE.md §2.7:禁止改 dacli 除非走 4 步法)、`jnpf/`(CLAUDE.md 禁止改)
---
## 3. 错误处理矩阵
| 失败点 | 处理动作 | 回退到 |
|--------|----------|--------|
| 编译失败 | mvn 堆栈 → 修源码 → 重跑 | §2 |
| JNPF 重启失败 | 杀残留 + 看 logs | §3 |
| dacli login 失败 | 重登或删 token | §1 |
| 4 关卡 FAIL | 分别修文件/截图/数字 | §4 |
| 单表单 E2E FAIL | 派 debug 子代理 → debug.md §6 → 修 | 单表单重跑 |
| >30% 表单 E2E FAIL | 暂停 → 标记 ⏳ 部分完成 → §6 报告 → 迭代 | 不强行 commit |
**关键约束**:
- ❌ 不用 `--force` 绕关卡
- ❌ 不直接 `curl` JNPF API(learnings.md 阶段 6:必须包 `{"data":"<inner JSON>"}` 二层,易错)
- ❌ 不抽样(历史教训:抽样漏 P0)
- ✅ 失败也 commit(CLAUDE.md §13:固化前先验证,没复现验证的"理论修复"不入主代码)
---
## 4. 验收标准(DoD)
阶段 7 ✅ 当且仅当:
1. ✅ `mvn package` exit 0
2. ✅ JNPF HTTP 200 + dos login valid
3. ✅ 14 表单 E2E PASS ≥ 12/14(≥85%)
4. ✅ 4 关卡 CI 4/4 PASS
5. ✅ plan.md §7 状态 ✅ + ## 13 新段写入
6. ✅ summary.html §6/§7 含阶段 7 数据
7. ✅ git commit + push 成功
---
## 5. 文档产出清单
| 文件 | 必填内容 |
|------|----------|
| `docs/dos/plan.md` | §7 状态更新 + ## 13 阶段 7 闭环段 |
| `docs/dos/learnings.md` | 新增 `## 阶段 7 (编译+E2E+关卡, 2026-07-07)` 段(试通命令+踩坑+决策) |
| `docs/dos/summary.html` | §6 结果 + §7 经验 补阶段 7 数字(PASS 率 / 漏洞修复数 / 编译耗时) |
| `docs/dos/testcase.html` | §11 阶段 7 14 表单 E2E 结果矩阵 + 截图 |
| `docs/dos/debug.md` | §6 阶段 7 E2E 失败(如有,含堆栈+修复方案) |
| `docs/dos/test_logs/tc_a_*.log` ×14 | API CRUD 证据 |
| `docs/dos/test_logs/tc_b_*.log` ×14 | 浏览器 5 步证据 |
| `docs/dos/test_logs/tc_c_*.log` ×14 | 源码渲染证据 |
---
## 6. 范围外(明确不做)
- ❌ 修复 26 P0 漏洞(learnings.md 阶段 6 已暴露)— 留待 sprint 2 迭代
- ❌ smartProps sprint 1/2/3(plan.md §11.6 后续)— 留待 v0.15+
- ❌ 5.2 业务功能 13 Service 全部重建 — 仅重建 3 个 agent 类(Ollama/Dialog/Weaviate)+ 7 sandbox 类,其余留 ssw-dos-biz 待办
- ❌ 完整 9 .vue 还原 — 仅做 4 个 + 1 API
- ❌ 报表服务(端口 32000)— 本次不启动(CLAUDE.md "常用命令" 段注:报表未启动会 502,本任务不依赖报表)
---
## 7. 风险与缓解
| 风险 | 概率 | 影响 | 缓解 |
|------|------|------|------|
| 编译失败耗时 >30min | 中 | 中 | BS-14 check_ssw_pack 预检 + 优先 Java 8 违例排查 |
| E2E 子代理跑偏 | 中 | 中 | 用 `templates/subagent/form-create.md.tmpl` 严格 prompt;CLAUDE.md §11 红线 |
| dacli FAIL 而绕 curl | 低 | 高 | CLAUDE.md §2.7 红线禁止;遇 FAIL 派子代理修 dacli 不绕过 |
| 4 关卡 false-positive | 低 | 低 | 历史已部分准备,关卡脚本零依赖;如异常看 `references/anti-patterns.md` |
| git push 冲突 | 极低 | 低 | .claude/ 仓库只读小并发,罕见冲突手动 `git pull --rebase` |
---
## 8. 关键决策记录
| # | 决策 | 理由 |
|---|------|------|
| 1 | 选方案 A(全链路)而非 B/C | ssw-loop 哲学"完整 7 阶段闭环";历史抽样漏 P0 |
| 2 | 不修 26 P0 漏洞 | 范围控制;先闭环 7 阶段,sprint 2 单独迭代 |
| 3 | E2E 派子代理而非主代理直接跑 | 防上下文爆(14 表单 × 3 层 = 42 份日志);CLAUDE.md §2.6 派子代理哲学 |
| 4 | 失败也 commit | CLAUDE.md §13:盲点固化前先验证,验证失败的也沉淀 |
| 5 | 不动 dacli/jnpf/web/uniapp | CLAUDE.md §2.7/§"代码修改权限" 红线;只动 `docs/dos/` + 可能的 `boot/ssw-dos-biz/` 编译修复 |
| 6 | 4 关卡预检在 E2E 之前 | 关卡 FAIL 先修,E2E 才有意义(关卡 B 防假 PASS) |
---
## 9. 时间预算
- 步骤 1-2(登录+编译):~10min
- 步骤 3(重启):~2min
- 步骤 4(4 关卡预检+修复):~5-15min(如全 PASS 直接通过)
- 步骤 5(14 表单 E2E):~30-45min(5-7 批子代理并行)
- 步骤 6-7(更新文档+commit):~5min
**总计**:~52-77min(中等复杂度,符合方案 A 预期 30-60min 上限略超)
---
## 10. 完成定义(DoD 复述)
执行完成后,必须满足:
```bash
# 1. 编译
cd /home/ubuntu/ccWorkDir/boot && mvn clean package -DskipTests # exit 0
# 2. JNPF 可达
curl -s -o /dev/null -w "%{http_code}" http://nginx/api/ # 200
# 3. dos login
dacli app status # currentSystemId=843831108620517509, tokenStatus=valid
# 4. 4 关卡
bash scripts/check_{required_docs,html_assets,summary_no_fake_pass,subagent_learnings}.sh docs/dos/ # 4/4 PASS
# 5. E2E
ls docs/dos/test_logs/tc_{a,b,c}_*.log | wc -l # ≥42 (14×3)
# 6. plan.md 状态
grep "7\. 验证" docs/dos/plan.md # 含 ✅ 完成 (2026-07-07)
# 7. git commit
git log -1 --oneline # "stage 7 闭环..."
```
@@ -1,100 +0,0 @@
---
name: dacli-form-ai-4-known-bugs
description: dacli form create --ai 已知 4 个隐蔽 bug — 控件错选 / 幻觉字段 / required 误标 / 未生成 relationForm. 必跑 dacli form info 验证 4 项.
metadata:
type: feedback
---
# dacli form create --ai 已知 4 bug (R16/R17 待修)
> **触发场景**: 用 `dacli form create --ai "<描述>" --autoRelease` 一条命令端到端建表单, 即使 TC-B 7/7 PASS + TC-C 9/9 PASS, schema 也可能有 4 类隐蔽问题.
>
> **Why**: 实战暴露 (jxcj 2026-07-15 M1) — NCPF backend AI 不可全信, R16 FormRepair 18 条 label 启发式修不了 AI 路径 (label 模糊 + 启发式只查 label 不查 vmodel), BS-新117 relationForm 自动注入函数定义了但**未 wire up** 直到 R17 P0.
>
> **How to apply**: 任何 form 完成前必跑 `dacli form info <enCode>` 检查 4 项: 字段数 / jnpfKey / `f_*_id` 关系控件 / required. 不对则 `dacli form update` 修或 `dacli form delete + create` 重建. 复杂表单 (≥5 字段 或 含 `_id` 关联) 改用 `--table=<物理表>` 或 `--fields '<显式 JSON>'`.
## 4 Bug 详解
### Bug 1: 控件类型选错
**症状**: AI 即使 prompt 显式说明 jnpfKey, 仍可能选错.
**实战例子** (jxcj M1 2026-07-15):
- `f_organizer` (主办单位, varchar 200) → AI 选 `depSelect` (部门选择器) → 应是 `input`
- `f_start_time` (报名开始, datetime) → AI 选 `timePicker` (仅时分) → 应是 `datePicker`
- `f_state` (发布状态, int + dict) → AI 选 `select` → 应是 `radio` (≤5 选项)
- `f_introduction` (大赛介绍, text) → AI 选 `textarea` → 应是 `editor` 富文本
**R16 FormRepair 修不了**: 18 条 label 启发式要求 label 命中关键词, 但 AI 生成的 label 模糊 (e.g. label="主办单位" 含"单位" → depSelect; 但业务"主办单位"是输入文本).
**R17 计划**: 加 vm-to-jnpfKey 启发式 (不依赖 label, 看 vmodel/fieldDbType 推断), 或显式 `--fields '<JSON>'` 推广.
### Bug 2: 幻觉字段
**症状**: AI 倾向"凑足字段", 多生 `input_num001` / `inputNumber_num001` 等业务外字段.
**实战例子**:
- `competitionInfo` 多生 `input_num001` (jnpfKey=input, 不在设计文档)
- `topicDirection` 多生 `inputNumber_num001` (jnpfKey=inputNumber)
**R12/R15 P2 待修**: NCPF backend LLM over-interpretation, 客户端层无法根治.
**R17 计划**: prompt 加 explicit 约束 "不要加额外字段" + NCPF maxTokens 限制, 或显式 `--fields '<JSON>'` 推广.
### Bug 3: required 误标
**症状**: 启发式 required 兜底 (BS-新41) 只标 1 字段, 可能漏标真必填, 也可能错标非必填.
**实战例子**:
- `f_wechat_qrcode` (微信群二维码, uploadImg 上传控件) 被 AI 启发式标 required=true, POST 失败 (`微信群二维码Field cannot be empty`)
- `f_competition_name` (大赛名称, 必填 varchar 200) 没被启发式标 required
**R17 计划**: upload 控件 (uploadImg/uploadFile/editor) 默认不标 required 启发式, 必填业务字段 (含"必"/"required"/"主键"/"外键") 标 required.
### Bug 4: 未生成 relationForm
**症状**: `f_*_id` 关联字段被 AI 生成为 `input` 文本框, 不是 `relationForm` 弹窗. 即使 prompt 显式说明"弹窗列表显示 5 列"也无效.
**实战例子**:
- `topicDirection.f_competition_id` 应是 relationForm 关联 `competitionInfo`, AI 生成 input
- 跨表关联失效, 用户填的是字符串 (CLAUDE.md §6 硬约束违反)
- 数据能存能查, 但浏览器层不能弹窗选 competitionInfo
**根因 (2026-07-15 jxcj M1 复盘)**: `form/_relationForm_auto.ts:144` `autoDetectAndInjectRelationForm` 函数已定义, `form/create.ts:59` 有 `relationFormAuto?: boolean` 选项 + `--no-relation-form-auto` CLI flag, **但 0 个 import/call 该函数**. 文档声称"默认 ON 自动注入"实际**未生效**.
**R17 P0 修复 (2026-07-15+)**: 在 `form/create.ts` 的 `--ai` 路径中真正 wire up `autoDetectAndInjectRelationForm(bfdResult.formData, existingFormList)`, 加 vitest 验证 (jxcj M1 topicDirection 复现).
**临时 workaround**: `dacli form update <formId> --json '<改后的 schema>'` 手动改 jnpfKey=relationForm + 补 3 必填 (modelId/propsValue/relationField).
## 强制验证流程 (任何 form 完成前必跑)
```bash
# 1. 拉 schema
FORM_INFO=$(dacli form info <enCode>)
FORM_SCHEMA=$(echo "$FORM_INFO" | python3 -c "
import json, sys
d = json.load(sys.stdin)
fd = json.loads(d['formData'])
for f in fd.get('fields', []):
cfg = f.get('__config__', {})
print(f.get('__vModel__', ''), cfg.get('jnpfKey', ''), cfg.get('required', False))
")
# 2. 4 项检查:
# (a) 字段数匹配 design.html (无幻觉)
# (b) jnpfKey 正确 (无 depSelect/timePicker 等易错)
# (c) f_*_id 字段 jnpfKey=relationForm (不是 input)
# (d) required 字段符合业务规则 (上传/富文本不应 required)
# 3. 不对则修:
dacli form update <formId> --json '<改后的 schema>' # 或
dacli form delete <formId> && dacli form create --ai "..." # 重建
```
## 跨 appCode 通用
- **新应用** (用 `dacli form create --ai`): 必跑 4 项验证
- **AI 路径失败**: 改用 `--table=<物理表>` 镜像 web schema, 或 `--fields '<显式 JSON>'` 完全控制
- **R17 修复后**: 关卡 B 加第 6 铁律 "AI schema 验证 4 项完整"
**关联**: [[jnpf-form-encode-suffix-2026-07-12]] (6 字符 hash 后缀) / [[mirror-architecture-must-truly-mirror]] (镜像架构 0 自创逻辑)
BIN
View File
Binary file not shown.