flower-trellis 0.4.8 → 0.4.10

package/enhancements/0.6/overrides/workflow-states/in_progress-inline.md

@@ -3,11 +3,12 @@ HIGHEST PRIORITY SKILL-GARDEN STATE GUARD (in_progress-inline):
 Hub is source of truth for Task Brief, Routing, Post-Check, Commit, and Snapshot gates.
 Before first implement route, restate `<task>/brief.md`; if missing, read artifacts and suggest backfill.
 New work not plainly covered by active task title/brief: stop before route/edits; recommend new task; if declined, confirm untracked work; if it belongs here, update artifacts first.
-At project-local knowledge boundaries, run `spec_router.py`; skip trivial/read-only turns unless local conventions may affect the approach.
+At project-local knowledge boundaries, run `python3 ./.trellis/scripts/spec_router.py "<intended action>"`; read high-confidence matches before acting; read medium-confidence matches only when clearly relevant; skip trivial/read-only turns unless local conventions may affect the approach.
 Inline workflow-state is not an inline route decision. Phase 2.1/2.2 must reuse explicit target-matched `route_decision`; otherwise invoke `trellis-route`. If unavailable, read local `trellis-route/SKILL.md`, show numbered choices, and wait.
 Summaries, preferences, `codex-mode`, raw `.runtime`, and empty/stale prefs are not route evidence unless `trellis-route` validates them; user reselect/override wins.
 Ignore lower direct-edit/check shortcuts. Do not default inline just because this state is inline or helper is unavailable. Dispatch subagents only when route selected subagent.
-After check/check-all, stop and report; Phase 3.4 uses `trellis-push`, never bare git commit/push; finish-work is explicit-only after Phase 3.4.
-Overrides lower `Flow: ... -> /trellis:finish-work` lines.
+After `trellis-check` / `trellis-check-all`, stop and report; point the user to Phase 3.4 `trellis-push` (or commit-only when needed). Do not run `/trellis:finish-work` unless the user explicitly asks after Phase 3.4 is complete.
+This guard overrides any lower `Flow: ... -> /trellis:finish-work` line in this state block.
+At Phase 3.4, code commit/push goes through `trellis-push` (commit-only mode for commit-without-push); never bare `git commit`/`git push` on code (hub: Code Commit Confirmation Gate).
 Push snapshot recovery: follow the hub; use `push_snapshot.py status --json` only when needed.
 <!-- END skill-garden workflow-state in_progress_inline v0.6 -->

package/enhancements/0.6/overrides/workflow-states/in_progress.md

@@ -3,11 +3,12 @@ HIGHEST PRIORITY SKILL-GARDEN STATE GUARD (in_progress):
 Hub is source of truth for Task Brief, Routing, Post-Check, Commit, and Snapshot gates.
 Before first implement route, restate `<task>/brief.md`; if missing, read artifacts and suggest backfill.
 New work not plainly covered by active task title/brief: stop before route/edits; recommend new task; if declined, confirm untracked work; if it belongs here, update artifacts first.
-At project-local knowledge boundaries, run `spec_router.py`; skip trivial/read-only turns unless local conventions may affect the approach.
+At project-local knowledge boundaries, run `python3 ./.trellis/scripts/spec_router.py "<intended action>"`; read high-confidence matches before acting; read medium-confidence matches only when clearly relevant; skip trivial/read-only turns unless local conventions may affect the approach.
 Phase 2.1/2.2: reuse only explicit target-matched `route_decision`; otherwise invoke `trellis-route`. If skill invocation is unavailable, read local `trellis-route/SKILL.md`, show numbered choices, and wait.
 Summaries, preferences, `codex-mode`, raw `.runtime`, and empty/stale prefs are not route evidence unless `trellis-route` validates them; user reselect/override wins.
 Ignore lower direct-dispatch shortcuts. Do not spawn `trellis-implement` or `trellis-check*` unless route selected subagent. If route cannot be resolved, do not default inline.
-After check/check-all, stop and report; Phase 3.4 uses `trellis-push`, never bare git commit/push; finish-work is explicit-only after Phase 3.4.
-Overrides lower `Flow: ... -> /trellis:finish-work` lines.
+After `trellis-check` / `trellis-check-all`, stop and report; point the user to Phase 3.4 `trellis-push` (or commit-only when needed). Do not run `/trellis:finish-work` unless the user explicitly asks after Phase 3.4 is complete.
+This guard overrides any lower `Flow: ... -> /trellis:finish-work` line in this state block.
+At Phase 3.4, code commit/push goes through `trellis-push` (commit-only mode for commit-without-push); never bare `git commit`/`git push` on code (hub: Code Commit Confirmation Gate).
 Push snapshot recovery: follow the hub; use `push_snapshot.py status --json` only when needed.
 <!-- END skill-garden workflow-state in_progress v0.6 -->

package/enhancements/0.6/overrides/workflow-states/no_task.md

@@ -3,7 +3,7 @@ HIGHEST PRIORITY SKILL-GARDEN STATE GUARD (no_task):
 Creating or resuming a task is not implementation permission.
 After PRD is ready and the task is started, the next implementation action is Phase 2.1 `trellis-route(implement)` unless a valid current-task implement route decision already exists.
 If no active task exists, use `push_snapshot.py status --json` once per session; if it returns candidates, relay them and suggest rebinding before resuming.
-At project-local knowledge boundaries, run `spec_router.py`; skip trivial/read-only turns unless local conventions may affect the approach.
+At project-local knowledge boundaries, run `python3 ./.trellis/scripts/spec_router.py "<intended action>"`; read high-confidence matches before acting; read medium-confidence matches only when clearly relevant; skip trivial/read-only turns unless local conventions may affect the approach.
 Do NOT call the harness built-in plan mode (`EnterPlanMode` / `ExitPlanMode`) for Trellis planning. It is not a substitute for Trellis task-creation consent, Trellis planning, or the route gate. For new, complex, or unclear work, classify the turn, ask for task-creation consent, then use `trellis-brainstorm`; `task.py create` and the default `prd.md` are not sufficient planning.
 For lightweight Trellis meta edits, ask/confirm skipping Trellis tracking before edits.
 <!-- END skill-garden workflow-state no_task v0.6 -->

package/enhancements/0.6/overrides/workflow-states/planning-inline.md

@@ -6,6 +6,6 @@ A created task or existing `prd.md` is not enough to start implementation.
 Complete prd.md + required context first.
 If the active workflow later routes to sub-agent execution, required context includes real curated entries in both `implement.jsonl` and `check.jsonl`; the seed `_example` row alone is not ready.
 Before `task.py start`, use `trellis-task-brief` to refresh `brief.md` from the latest task artifacts and display it in chat for review.
-At project-local knowledge boundaries, run `spec_router.py`; skip trivial/read-only turns unless local conventions may affect the approach.
+At project-local knowledge boundaries, run `python3 ./.trellis/scripts/spec_router.py "<intended action>"`; read high-confidence matches before acting; read medium-confidence matches only when clearly relevant; skip trivial/read-only turns unless local conventions may affect the approach.
 After status becomes in_progress, next action = `trellis-route(implement)`, not direct edits.
 <!-- END skill-garden workflow-state planning_inline v0.6 -->

package/enhancements/0.6/overrides/workflow-states/planning.md

@@ -6,6 +6,6 @@ A created task or existing `prd.md` is not enough to start implementation.
 Complete prd.md + required context first.
 For sub-agent-dispatch platforms, required context includes real curated entries in both `implement.jsonl` and `check.jsonl`; the seed `_example` row alone is not ready.
 Before `task.py start`, use `trellis-task-brief` to refresh `brief.md` from the latest task artifacts and display it in chat for review.
-At project-local knowledge boundaries, run `spec_router.py`; skip trivial/read-only turns unless local conventions may affect the approach.
+At project-local knowledge boundaries, run `python3 ./.trellis/scripts/spec_router.py "<intended action>"`; read high-confidence matches before acting; read medium-confidence matches only when clearly relevant; skip trivial/read-only turns unless local conventions may affect the approach.
 After status becomes in_progress, next action = `trellis-route(implement)`, not direct edits.
 <!-- END skill-garden workflow-state planning v0.6 -->

package/enhancements/MANIFEST.json

@@ -1,7 +1,7 @@
 {
-  "syncedAt": "2026-07-08T00:31:59.624Z",
+  "syncedAt": "2026-07-08T03:53:14.101Z",
   "syncedFrom": "vendor/skill-garden",
-  "sourceCommit": "c52e2dd6a16dff1317379a804d69b189c9527c81",
+  "sourceCommit": "6ecfb1b46320d82aeb3e83442235f271d92aa398",
   "common": {
     "codexSkills": [
       "craft-rpa",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flower-trellis",
-  "version": "0.4.8",
+  "version": "0.4.10",
   "description": "一键安装/升级 Trellis 并自动融合 skill-garden 强化包(默认 Claude + agents)",
   "type": "module",
   "bin": {
@@ -58,9 +58,9 @@
     "commit-and-tag-version": "^12.7.3"
   },
   "flowerReleaseNotes": {
-    "version": "0.4.8",
+    "version": "0.4.10",
     "source": "CHANGELOG.md",
-    "body": "### ✨ 新功能 Features\n\n* **flower:** 支持从 skill-garden 分发 hook override,并在 Codex 已有 `SessionStart` 时去掉重复的 `trellis-start` 提示。\n\n\n### 🐛 修复 Bug Fixes\n\n* **flower:** 修复项目版本追平提示不展示 release notes 的问题。",
+    "body": "### 🐛 修复 Bug Fixes\n\n* **flower:** 项目侧待更新提示会显示对应版本更新摘要 ([cc98c02](https://github.com/SilentFlower/flower-trellis/commit/cc98c021eb0536f693f50651854093a4795d9e93))",
     "truncated": false
   }
 }

package/src/lib/self-check.js

@@ -119,6 +119,46 @@ function releaseNotesFromMetadata(metadata, range) {
   return buildReleaseNotesSummary(metadata?.releaseNotesByVersion, range);
 }
 
+/**
+ * 安全执行 npm metadata 拉取。
+ *
+ * 默认 fetcher 已经吞掉网络错误;这里再兜底测试注入的 fetcher,确保 release notes
+ * 补拉失败不会破坏 self-check 主流程。
+ *
+ * @param {() => Promise<object|null>} fetchMetadata npm metadata 拉取函数
+ * @returns {Promise<object|null>} registry metadata,失败时为 null
+ */
+async function safeFetchPackageUpdateMetadata(fetchMetadata) {
+  try {
+    return await fetchMetadata();
+  } catch {
+    return null;
+  }
+}
+
+/**
+ * 缓存命中但缺少摘要时,主动补拉 release notes。
+ *
+ * 这个补拉只服务当前 actionable 提示的摘要展示,不能把失败写成新的远程版本证据;
+ * 成功时也只写回 lastReleaseNotes,保持 lastRemote 仍只记录 dist-tags。
+ *
+ * @param {string} target 目标项目根
+ * @param {object|null} manifest 目标项目 manifest
+ * @param {boolean} writeCache 是否允许写缓存
+ * @param {object|null} range release notes 范围
+ * @param {() => Promise<object|null>} fetchMetadata npm metadata 拉取函数
+ * @returns {Promise<object|null>} release notes 摘要;范围有效但不可用时返回 unavailable 摘要
+ */
+async function fetchMissingReleaseNotes(target, manifest, writeCache, range, fetchMetadata) {
+  if (!range) return null;
+  const metadata = await safeFetchPackageUpdateMetadata(fetchMetadata);
+  const releaseNotes = releaseNotesFromMetadata(metadata, range);
+  if (releaseNotes && !releaseNotes.unavailable && writeCache && manifest) {
+    writeUpdateCheck(target, { lastReleaseNotes: releaseNotes });
+  }
+  return releaseNotes;
+}
+
 /** 检查目标目录 git 工作区是否 clean。 */
 function gitSafety(target) {
   const common = {
@@ -312,12 +352,15 @@ export function safetyState(target, status, command) {
  * 构建启动自更新检查结果。
  *
  * @param {string} target 目标项目根
- * @param {{writeCache?: boolean, forceRemote?: boolean}} options 检查选项
+ * @param {{writeCache?: boolean, forceRemote?: boolean, fetchMetadata?: () => Promise<object|null>}} options 检查选项
  * @returns {Promise<object>} 结构化检查结果
  */
 export async function buildSelfCheck(target, options = {}) {
   const writeCache = options.writeCache !== false;
   const forceRemote = options.forceRemote === true;
+  const fetchMetadata = typeof options.fetchMetadata === "function"
+    ? options.fetchMetadata
+    : fetchPackageUpdateMetadata;
   const now = new Date();
   const absoluteTarget = path.resolve(target);
   const trellisDir = path.join(absoluteTarget, ".trellis");
@@ -404,11 +447,19 @@ export async function buildSelfCheck(target, options = {}) {
     }
     if (projectOutOfSync) {
       const releaseNotesRange = projectReleaseNotesRange(projectFlower, currentFlower);
+      const releaseNotes = cachedReleaseNotes(updateCheck, releaseNotesRange) ||
+        await fetchMissingReleaseNotes(
+          absoluteTarget,
+          manifest,
+          writeCache,
+          releaseNotesRange,
+          fetchMetadata,
+        );
       return projectOutOfSyncResult(base, absoluteTarget, {
         tags,
         fromCache: true,
         skipped: true,
-      }, cachedReleaseNotes(updateCheck, releaseNotesRange));
+      }, releaseNotes);
     }
     return {
       ...base,
@@ -418,7 +469,7 @@ export async function buildSelfCheck(target, options = {}) {
     };
   }
 
-  const metadata = await fetchPackageUpdateMetadata();
+  const metadata = await safeFetchPackageUpdateMetadata(fetchMetadata);
   if (!metadata) {
     if (writeCache && manifest) {
       writeUpdateCheck(absoluteTarget, {