flower-trellis 0.6.5 → 0.6.6

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.
@@ -137,9 +137,9 @@
137
137
  "<!-- BEGIN skill-garden patch brainstorm-planning-handoff v0.6 -->\n## Quality Bar",
138
138
  "## Planning Handoff",
139
139
  "<!-- BEGIN skill-garden patch brainstorm-planning-readiness v0.6 -->\n8. Load `trellis-task-brief`",
140
- "The latest full Brief has been presented to the user.",
140
+ "Only valid explicit preauthorization for the current final Brief, as defined by `trellis-task-brief`, permits same-turn start within unchanged scope.",
141
141
  "The final Brief must cover Goal, Scope, Non-Goals, Key Decisions, Key Context, Acceptance, one-hop Next Step",
142
- "Implementation intent expressed before the final artifacts and full Brief are shown authorizes planning only",
142
+ "Ordinary implementation intent expressed before the final artifacts and full Brief are shown authorizes planning only",
143
143
  "unresolved items are `- [ ]`",
144
144
  "Do not write bare placeholders"
145
145
  ]
@@ -161,9 +161,9 @@
161
161
  "<!-- BEGIN skill-garden patch brainstorm-planning-handoff v0.6 -->\n## Quality Bar",
162
162
  "## Planning Handoff",
163
163
  "<!-- BEGIN skill-garden patch brainstorm-planning-readiness v0.6 -->\n8. Load `trellis-task-brief`",
164
- "The latest full Brief has been presented to the user.",
164
+ "Only valid explicit preauthorization for the current final Brief, as defined by `trellis-task-brief`, permits same-turn start within unchanged scope.",
165
165
  "The final Brief must cover Goal, Scope, Non-Goals, Key Decisions, Key Context, Acceptance, one-hop Next Step",
166
- "Implementation intent expressed before the final artifacts and full Brief are shown authorizes planning only",
166
+ "Ordinary implementation intent expressed before the final artifacts and full Brief are shown authorizes planning only",
167
167
  "unresolved items are `- [ ]`",
168
168
  "Do not write bare placeholders"
169
169
  ]
@@ -9,15 +9,13 @@ Before declaring planning ready:
9
9
  - Complex tasks have `design.md` and `implement.md`.
10
10
  - Sub-agent-dispatch tasks have real curated entries in both `implement.jsonl` and `check.jsonl`; seed-only manifests are not ready.
11
11
  - Planning artifacts are ready for the final Brief handoff.
12
- - The latest full Brief has been presented to the user.
13
- - In a subsequent message, the user explicitly approved that Brief for implementation.
14
12
 
15
13
  Do not start implementation merely because the user originally asked for implementation.
16
14
 
17
15
  ## Planning Handoff
18
16
 
19
- Once the Quality Bar is satisfied, load `trellis-task-brief`, refresh `brief.md` from the final planning artifacts, display the full Brief in chat, and end the current turn. Wait for the user's planning review confirmation before running `task.py start` or beginning implementation.
17
+ Once the Quality Bar is satisfied, load `trellis-task-brief`, refresh `brief.md` from the final planning artifacts, and display the full Brief in chat. By default, end the current turn and wait for the user's planning review confirmation. Only valid explicit preauthorization for the current final Brief, as defined by `trellis-task-brief`, permits same-turn start within unchanged scope.
20
18
 
21
- Implementation intent expressed before the final artifacts and full Brief are shown authorizes planning only; it cannot be reused as the final review confirmation.
19
+ Ordinary implementation intent expressed before the final artifacts and full Brief are shown authorizes planning only; it cannot be reused as the final review confirmation.
22
20
 
23
21
  For `## Open Questions`, use Markdown checkbox state rather than placeholder prose: unresolved items are `- [ ]`; resolved items move into requirements/decisions or are removed; when no open questions remain, remove the section or leave it empty. Do not write bare placeholders such as `- None`, `- TBD`, or `- 已确认` because historical bare list items require an explicit auto-loop semantic review.
@@ -1 +1 @@
1
- For every non-trivial task, the user must respond at least once after the initial request before implementation begins. If no clarification is needed, that response must approve the final Brief described below.
1
+ For every non-trivial task, follow `trellis-task-brief` for the final Brief review and its explicit preauthorization exception before implementation begins. Ordinary implementation or task-creation intent is not Brief approval.
@@ -1,2 +1,2 @@
1
- 8. Load `trellis-task-brief`, refresh `brief.md` from the converged artifacts, display the full Brief, and stop. Do not run `task.py start` or edit product code in the same turn.
2
- 9. Only a subsequent user message that explicitly approves the latest full Brief authorizes `task.py start` and implementation. If the artifacts change materially after approval, refresh and repeat the Brief review.
1
+ 8. Load `trellis-task-brief`, refresh `brief.md` from the converged artifacts, and display the full Brief. Follow its review gate and explicit preauthorization exception.
2
+ 9. Run `task.py start` and begin implementation only after that review gate is satisfied. If the artifacts change materially after approval, refresh and repeat the Brief review.
@@ -1,3 +1,3 @@
1
- Do not manufacture clarification questions when the request and repository evidence already resolve every decision. In that case, proceed directly to the final Brief handoff, which still requires a subsequent explicit approval.
1
+ Do not manufacture clarification questions when the request and repository evidence already resolve every decision. In that case, proceed directly to the final Brief handoff through `trellis-task-brief`.
2
2
 
3
- The final Brief review is a required phase-transition gate, not a prohibited process question. Task-creation consent, the initial implementation request, and approval given before the latest full Brief do not satisfy this gate.
3
+ The final Brief review is a required phase-transition gate, not a prohibited process question. Task-creation consent and ordinary implementation intent do not satisfy this gate; explicit preauthorization is evaluated only by `trellis-task-brief`.
@@ -1,7 +1,7 @@
1
1
  {
2
- "syncedAt": "2026-09-05T18:24:52.904Z",
2
+ "syncedAt": "2026-09-07T02:30:42.961Z",
3
3
  "syncedFrom": "vendor/skill-garden",
4
- "sourceCommit": "6199ab8b2e0259ff695d70797943ea1ae97e099c",
4
+ "sourceCommit": "ad64c8ab30cb14184895aa31d672cf1b846e5726",
5
5
  "common": {
6
6
  "codexSkills": [
7
7
  "aliyun-ops",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "flower-trellis",
3
- "version": "0.6.5",
3
+ "version": "0.6.6",
4
4
  "description": "一键安装/升级 Trellis 并自动融合 skill-garden 强化包(默认 Claude + agents)",
5
5
  "type": "module",
6
6
  "bin": {
@@ -70,9 +70,9 @@
70
70
  "commit-and-tag-version": "^12.7.3"
71
71
  },
72
72
  "flowerReleaseNotes": {
73
- "version": "0.6.5",
73
+ "version": "0.6.6",
74
74
  "source": "CHANGELOG.md",
75
- "body": "### ✨ 新功能 Features\n\n* **cli:** 优化调用契约与帮助体验 ([b7a39db](https://github.com/SilentFlower/flower-trellis/commit/b7a39dbda2042643c3e15dd47caebe7c83242548))\n* **codex:** 为 Astra 添加 SessionStart 工作流提示 ([1d79835](https://github.com/SilentFlower/flower-trellis/commit/1d79835f4bea1782f5774ff8c14a6263742b1677))\n* **telemetry:** 采集平台活跃与核心操作质量 ([08598bf](https://github.com/SilentFlower/flower-trellis/commit/08598bf26638567b9183150d7c258e2f801046a4))\n\n\n### 🐛 修复 Bug Fixes\n\n* **hooks:** 分段注入启动上下文并保留额度 ([5eaf6af](https://github.com/SilentFlower/flower-trellis/commit/5eaf6afd7c7b088e8421f3b176d0d79ccb9cdba2))\n* **plugin:** 兼容旧 RD Guide 离线升级 ([fcec390](https://github.com/SilentFlower/flower-trellis/commit/fcec3905629dd31bc3f113ac28bf64139311324e))",
75
+ "body": "### 🐛 修复 Bug Fixes\n\n* **codex:** 明确 Astra 规划授权边界 ([07428f8](https://github.com/SilentFlower/flower-trellis/commit/07428f8c4406449656edfe2e6dd6463d4540370a))",
76
76
  "truncated": false
77
77
  },
78
78
  "optionalDependencies": {
@@ -27,7 +27,7 @@ When executing the current task:
27
27
  - Treat required steps, required references, phase boundaries, and output templates in applicable SKILL and WORKFLOW instructions as execution and delivery checks.
28
28
  - Before a step, review its rules and required references. Reuse material already read in full and unchanged; search matches are not full reads.
29
29
  - Preserve required heading levels, section order, and conditional sections in specified templates. General brevity or no-heading preferences apply to ordinary prose and do not justify flattening, shortening, or reshaping a specified template.
30
- - Resolve conflicts by instruction hierarchy and respect the user's current explicit authorization. Do not invent additional confirmation steps or claim that this hint or a SKILL overrides all host rules.
30
+ - Resolve conflicts by instruction hierarchy. Follow the owning workflow's phase-transition and review requirements, checking the scope of prior authorization; do not infer approval of the final plan from permission to begin planning.
31
31
  - Before claiming "read", "checked", or "complete", verify actual tool records and artifacts. Successful reading and compliant execution are separate facts.
32
32
  - When corrected, review the applicable rules, execution records, and actual result before repairing it. If evidence is missing, state uncertainty. Do not invent causes such as "not read", "forgot", or "file missing", or consult unrelated rules in place of the relevant ones.
33
33
  </trellis-astra-workflow-hint>"""