chore: 发布 DevFlow 0.2.14

Author: TrueNine

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
 	"name": "devflow-skills",
-	"version": "0.2.13",
+	"version": "0.2.14",
 	"description": "DevFlow engineering workflow skills for Codex: routing, DDD, TDD, planning, execution, debugging, review, verification, and branch finishing.",
 	"composerIcon": "./assets/app-icon-small.svg",
 	"logo": "./assets/app-icon.png",

README.md

@@ -131,26 +131,26 @@ bunfig.toml
 
 DevFlow can use project-owned style packs after the business design is clear. A style pack is not a shared DevFlow template; it is repository-owned material that helps agents preserve local implementation style through rules, golden examples, anti-patterns, and review checklists.
 
-Recommended project locations:
+Project-owned style packs have one default discovery location:
 
 ```text
-devflow-style-packs/
-.devflow/style-packs/
-.ai/style-packs/
-docs/devflow/style-packs/
+.devflow/style-pack/
 ```
 
 Recommended shape:
 
 ```text
-<style-pack-name>/
-  style-pack.yaml
-  rules.md
-  examples/
-  anti-patterns.md
-  review-checklist.md
+.devflow/style-pack/
+  <style-pack-name>/
+    .pack.toml
+    rules.md
+    examples/
+    anti-patterns.md
+    review-checklist.md
 ```
 
+`.pack.toml` describes metadata such as scope, applicable task types, primary examples, verification commands, review checks, and known exclusions.
+
 Use style packs with `df-glue-coding` after DDD, CQRS, API, security, validation, and persistence constraints are already respected. Keep project-specific examples in the project repository, not in this public DevFlow repository.
 
 ## 开发

agents/df-publisher.toml

@@ -1,4 +1,4 @@
-# devflow-version = "0.2.13"
+# devflow-version = "0.2.14"
 name = "df-publisher"
 description = "唯一被授权执行 git 和 gh 命令的 Codex worker session。负责提交、推送、PR、合并、发布等全部 git/github 操作。遵守保护分支规则。"
 nickname_candidates = ["df-publisher", "publisher"]

package.json

@@ -1,6 +1,6 @@
 {
 	"name": "devflow-skills",
-	"version": "0.2.13",
+	"version": "0.2.14",
 	"type": "module",
 	"private": true,
 	"scripts": {

skills/df-codex-assets/assets/hash.txt

@@ -1 +1 @@
-f96f43e7bffa428d6f2e87deaa18b43dd794764e9ee4f647b2e01cb79e7fea98
+58a5fee02adc8e8a28248c6103cd7698691f3ce4b68ed05aed669dba06cfb694

skills/df-glue-coding/SKILL.md

@@ -26,7 +26,7 @@ Use Glue Coding after:
 Look for project-owned material in this order:
 
 1. Rules: `AGENTS.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, local docs, package scripts, framework config.
-2. Style packs and reference patterns: explicit user-provided style pack paths, `devflow-style-packs/`, `.devflow/style-packs/`, `.ai/style-packs/`, `docs/devflow/style-packs/`, `reference/`, `references/`, `examples/`, `docs/patterns/`, `.ai/patterns/`, templates, scaffolds.
+2. Style packs and reference patterns: explicit user-provided style pack paths, `.devflow/style-pack/`, `reference/`, `references/`, `examples/`, `docs/patterns/`, `.ai/patterns/`, templates, scaffolds.
 3. Nearby production code: similar pages, endpoints, handlers, adapters, projections, tests, fixtures, migrations, exports, imports, jobs, or config. For refactors, classify whether each candidate is a target pattern, legacy pattern, anti-pattern, or behavior evidence.
 4. Historical context: `.ai/tracks/`, prior specs, plans, ADRs, issue notes, PR descriptions, or implementation notes.
 
@@ -119,7 +119,7 @@ Keep this concise. Do not paste long source files into the response; cite file p
 Before handoff or completion, ask whether the task revealed reusable material:
 
 - a new or improved code pattern worth adding to `reference/`, `examples/`, `docs/patterns/`, or `.ai/patterns/`
-- a style pack rule, golden example, anti-pattern, or review checklist entry worth adding to `devflow-style-packs/`, `.devflow/style-packs/`, `.ai/style-packs/`, or `docs/devflow/style-packs/`
+- a style pack rule, golden example, anti-pattern, or review checklist entry worth adding to `.devflow/style-pack/`
 - a rule that belongs in `AGENTS.md` or project docs
 - domain knowledge or a pitfall that belongs in local knowledge notes
 - a persistent spec or decision that belongs in `.ai/tracks/`

skills/df-glue-coding/references/style-packs.md

@@ -21,28 +21,25 @@ Search project-owned material in this order:
 
 1. Explicit user-provided paths or names.
 2. `AGENTS.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, and local workflow docs that name style packs.
-3. `devflow-style-packs/`
-4. `.devflow/style-packs/`
-5. `.ai/style-packs/`
-6. `docs/devflow/style-packs/`
-7. `docs/patterns/`, `examples/`, `reference/`, and `references/`
+3. `.devflow/style-pack/`
+4. `docs/patterns/`, `examples/`, `reference/`, and `references/`
 
 If a style pack conflicts with current production code, prefer current production code unless the task is explicitly to migrate toward the style pack.
 
 ## Recommended Shape
 
 ```text
-devflow-style-packs/
+.devflow/style-pack/
   <style-pack-name>/
-    style-pack.yaml
+    .pack.toml
     rules.md
     examples/
       <golden-example files>
     anti-patterns.md
     review-checklist.md
 ```
 
-`style-pack.yaml` should describe the scope, applicable task types, primary examples, verification commands, and known exclusions.
+`.pack.toml` should describe metadata such as scope, applicable task types, primary examples, verification commands, review checks, and known exclusions.
 
 `rules.md` should contain concise rules that affect implementation choices, naming, layering, error handling, transaction boundaries, tests, or projection behavior.