朱子纯 / erp-workflow-plugin

- delete lib/merge-gitignore.mjs + merge-gitignore.test.mjs: over-engineered for a once-run greenfield step (base .gitignore usually absent; duplicate ignore patterns are harmless)
- D now uses C.1-style Read+Write: Write template if no .gitignore, else append missing lines (consistent with render.mjs removal + scope-lock direct-write)
- removes the 'pre-Write empty .gitignore' fragility (Write self-creates); skeleton-gen drops Bash(node *) from allowed-tools

尾部 6/6 reset-test-db 与下次运行的 1/x setup-test-db 重复（都 DROP+CREATE），对正确性零贡献；删除后闸门为 detect→setup→build→lint→test→e2e，重编号 1/5..5/5。

- C.1: stop generating sql/migrations/.gitkeep (A4 db-init's Write V1 creates the dir); README A2 drops 'create empty migrations dir'
- precedence rule: on color conflict, tokens.css wins over prototype (prototype = structure/layout/interaction; tokens.css = color) — encoded in skeleton-gen note, coding.mjs frontend stage, code-reviewer § Design Tokens

- skeleton-gen B.1: remove stale line claiming 根包名/命名空间 placeholder is filled at docs/09 top (docs/09 has no such placeholder; base_package lives in config-vars.yaml since A1)
- docs-05-header: 端口 占位 -> pointer to config-vars.yaml backend.http_port (was a duplicate 【人工填写】 of the same port)

- README (A0 row + prerequisites): dep check now auto-installs missing tools (was: print guide + halt, no auto-install), matching project-init SKILL
- project-init SKILL: fix typo 失败失败 -> 失败
- CLAUDE template rule #5: inline cross-module 留痕 requirement (soft-rule S2 table was removed)

- A0 SKILL: drop inline cross-platform dep-check script + OS install guides; dep check now auto-installs missing tools (was detect-only); trim 用 Edit/用 Bash 等工具名提示
- CLAUDE template: remove B 阶段流程 / 占位符约定 / 🚩 中断机制 / 🟡 软规则(S1,S2) / 硬规则#6 / 禁止项#2 等小节
- docs-01 index: drop trailing 填写说明

…o-chain, docs/06+A6 removal

- delete frontend-scope-lock skill + docs/06 templates (static + module-pagelist)
- A5 downstream-gen gains prototype/ gate + FE-list derivation -> docs/08 § 三
- plan-start: drop A6 dispatch row, gate 5->4 items; coding-start A0~A6 -> A0~A5
- Design Tokens single source = src/styles/tokens.css (code-reviewer, coding.mjs)
- plugin.json skills 9->8; docs-09 tree drops 06-UI; docs-08 drops A6 section

- D-step: CC writes _module.md/REQ-*.md directly (no render.mjs/vars.json)
- req-card template restructured: input/output example tables copied verbatim, CC fills 6 {{}} scalars; E.1 validates {{}} residual only
- E.2: write all config (incl. secret placeholders) into config-vars.yaml
- E.4: no human-review stop — auto Skill(skeleton-gen) into A2

- config-vars.yaml now holds全部 config incl. secrets (database/admin_init.password/secrets), committed
- delete env-local-template; setup-test-db reads config-vars.yaml; gitignore no longer ignores .env.local
- docs-07 single-store rule; db-init/db-design-gen read config-vars.yaml database: section
- drop test_db_allowed_hosts whitelist + schema-looks-like-test guard (trust config-vars.yaml)

- remove render.mjs/render.test.mjs (scope-lock now writes REQ cards directly)
- add yaml-config.mjs: minimal 2-level YAML reader (+ tests)
- apply-ddl: parse config-vars.yaml database: section instead of .env.local dotenv; drop assertSafeDbTarget host-whitelist + schema guards (config-vars.yaml is trusted)
- merge-gitignore/validate-ddl: self-contained pathToFileURL comment (no longer 'see render.mjs')

docs-06-static-template.md actually defines § 二 Design Tokens with
subsections 2.1 / 2.2 / 2.3. The CSS template comments still cited the
pre-renumber § 四 / § 4.1 / § 4.2, so downstream-generated tokens.css
files pointed readers to non-existent sections of docs/06.

The TAG_REPORT_FRESHNESS_SCHEMA + checkTagReportFreshPromptM + the
post-`tag.exists` freshness branch in runMilestone existed to detect
"tag points at a commit whose § ⑫ is still {{milestone_tag}}". Per the
original comments, this only catches historical leftovers from the
pre-fix tag → § ⑫ ordering; the same fix reversed the order so the
runtime guard is no longer load-bearing. ~25 lines of branchy
defensive code that the source-level fix already prevents.

If a pre-fix repo has stale milestone tags, delete them with
`git tag -d milestone/<id>` and re-run coding-start.

…, single-source error-codes

…d parenthetical 参考 blocks

Visual clarity: the file tree now matches the README's phase model.
- skills/plan/   — 8 skills (plan-start entry + A0~A6)
- skills/coding/ — 1 skill (coding-start thin entry)

Slugs unchanged. /erp-workflow:<name> still resolves identically because
each SKILL.md declares its own `name:` frontmatter (verified for all 9).

Plugin loader treats the default `./skills/` scan as flat, so the nested
layout is opted into via an explicit path array in plugin.json — the only
mechanism Claude Code provides for nested skill discovery.

Changes:
- mv skills/{plan-start,project-init,scope-lock,skeleton-gen,
       db-design-gen,db-init,downstream-gen,frontend-scope-lock}
     → skills/plan/<same>/
- mv skills/coding-start → skills/coding/coding-start/
- .claude-plugin/plugin.json: skills[] now lists all 9 explicit paths
- README.md: directory tree + Skill 清单 heading updated to reflect grouping

No code touches any skill path (only README did, and only in the tree
diagram). lib tests still pass (62/62).

Independent Claude + Codex review of the working-tree diff surfaced
23 issues; all applied in-place across three domains.

workflows/coding.mjs (9):
- spec/plan/verify/review prompts now git-commit their artifacts
  (closes milestone-dirty-worktree halt risk)
- CHECKBOX_STATE_SCHEMA requires `state` + defensive guard in reviewWithFixLoop
- writeDocs08FieldPromptM scopes edits to module via line anchor
- assertSafeId guards Router output (module/REQ/FE ids)
- featureLoop captures reviewWithFixLoop's return value
- dateFromArtifactPath rejects impossible dates (9999-99-99 etc.)
- terminal HALT review-unresolved message disambiguated
- updated comment on top-level `return` (ESM vs node --check)

lib/validate-ddl.mjs + tests (10):
- extractType preserves unsigned/signed modifiers
- KEY/INDEX fallthrough no longer creates spurious 'KEY' columns
- FOREIGN KEY REFERENCES accepts schema-qualified `db.table`
- index keys normalized to name:kind:cols (UNIQUE-aware)
- FK keys include ON DELETE action (defaults to RESTRICT)
- CREATE TEMPORARY TABLE parsed
- parseForeignKeyBullet/parseIndexBullet reject prose bullets
- +10 regression tests (62 total, all pass)
- merge-gitignore.mjs docstring synced to implementation

skills/ (4):
- docs-06 template header: § 一~二 → § 一~三
- downstream-gen §A steps renumbered 1-7 (was 1,3,4,5,6,7,8)
- docs-08 initial template adds tokens.css checkbox
- coding-start drops "已在后台启动" wording (Workflow is synchronous)

- 新增 scope-lock/templates/config-vars-template.yaml：非敏感项目级配置
  （包名/端口/前端包名/初始账号）+ secrets_ref 键名引用 .env.local；
  A1 E.2 锁定。docs/07 改为只记规则/约定不记具体值。
- 连带更新 skeleton-gen / plan-start 闸门 2 / frontend-scope-lock /
  CLAUDE-template / README / docs-06·07 模板对齐新的配置分层与 docs/06 小节编号。
- lib 修复（含回归测试）：
  - apply-ddl: 抽出 resolveDbConfig，DB_SCHEMA 为契约 schema 键，缺库名 fail-closed (M1)
  - render: 用 Object.hasOwn 拒绝原型链继承键，guard process.argv[1]
  - validate-ddl: 解析 ### 索引/### 外键 bullet (C2)、剥 SQL 注释防幽灵表 (L4)、PRIMARY 归一化
- coding.mjs: Router 把全部前端 FE 聚合为单一末尾 frontend-phase 模块；
  新增 branchSetupPrompt 功能分支生命周期 (C1)；diff 区间改三点 diff；fix 后复跑 verify。

- Delete all 7 banners/flow*.txt and remove the banner step from each
  Plan skill (plan-start renumbered: gate=第1步, 放行/拦截=第2步 A/B).
- Drop now-unused Bash(cat *) from scope-lock/db-design-gen/downstream-gen/
  plan-start allowed-tools.
- downstream-gen: replace `cp` (not Windows-safe) with Read+Write, drop Bash(cp *).
- project-init: fix stale dispatcher name session-start -> plan-start.
- README: remove the Banners 清单 section.

The autonomous build changed it to `export default` to satisfy `node --check`,
but Workflow scripts run in an async wrapper where top-level `return` is the
result contract (alongside `export const meta`). `export default` would be a
dead module export and the per-module result summary would be lost.

…frontend scope-lock) + de-bash + ERP-confirmable