peaks-loop 4.0.0-beta.33 → 4.0.0-beta.36

package/CHANGELOG.md

@@ -4,17 +4,6 @@
 
 ### Patch Changes
 
-- Updated dependencies
-  - peaks-loop-shared@0.0.27
-  - peaks-loop-audit-independent@0.0.13
-  - peaks-loop-crystallization@0.0.14
-  - peaks-loop-doctor@0.0.13
-  - peaks-loop-final-review@0.0.13
-
-## 4.0.0
-
-### Patch Changes
-
 - Updated dependencies
   - peaks-loop-shared@0.0.18
   - peaks-loop-audit-independent@0.0.12

package/README-en.md

@@ -125,7 +125,7 @@ Every lane opens with **one slash command**.
 
 | | |
 | --- | --- |
-| **Latest** | [`4.0.0-beta.33`](https://github.com/SquabbyZ/peaks-loop/releases) — 4.x GA is in the works |
+| **Latest** | [`4.0.0-beta.36`](https://github.com/SquabbyZ/peaks-loop/releases) — 4.x GA is in the works |
 | **Domains** | Code (`peaks-code`) · Content (`peaks-content`) · Project health (`peaks-doctor`) · Issue sweep (`peaks-issue-fix-orchestrator`) · Custom SOP (`peaks-sop`) · Cross-domain primitives (`peaks-solo` dispatcher · `peaks-resume` · `peaks-status` · `peaks-test`) |
 | **Sediment pool** | `~/.peaks/` local pool · twice-clean runs auto-promote to a bee · broken runs come back for you to redefine · the bee grows with your taste |
 | **Test suite** | 5,439 passed · 19 skipped · 0 failed |

package/README.md

@@ -125,7 +125,7 @@ npm i -g peaks-loop
 
 | | |
 | --- | --- |
-| **最新版本** | [`4.0.0-beta.33`](https://github.com/SquabbyZ/peaks-loop/releases) — 4.x 正式版筹备中 |
+| **最新版本** | [`4.0.0-beta.36`](https://github.com/SquabbyZ/peaks-loop/releases) — 4.x 正式版筹备中 |
 | **覆盖域** | 代码(`peaks-code`) · 内容(`peaks-content`) · 项目健康(`peaks-doctor`) · 批量修 issue(`peaks-issue-fix-orchestrator`) · 自定义 SOP(`peaks-sop`) · 通用原语(`peaks-solo` 分诊 / `peaks-resume` 续 / `peaks-status` 看 / `peaks-test` 测) |
 | **沉淀池** | `~/.peaks/` 本地池 · 跑两次自动晋升成 bee · 跑翻车让你重定义 · bee 跟着你的口味长 |
 | **测试套件** | 5,439 passed · 19 skipped · 0 failed |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "peaks-loop",
-  "version": "4.0.0-beta.33",
+  "version": "4.0.0-beta.36",
   "description": "Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration",
   "author": "SquabbyZ",
   "license": "MIT",
@@ -54,14 +54,14 @@
     "headroom-ai": "0.22.4",
     "yaml": "^2.9.0",
     "zod": "^3.25.76",
-    "peaks-loop-doctor": "0.0.12",
-    "peaks-loop-crystallization": "0.0.13",
     "peaks-loop-audit-independent": "0.0.12",
-    "peaks-loop-final-review": "0.0.12",
+    "peaks-loop-crystallization": "0.0.13",
     "peaks-loop-mut": "0.1.1",
+    "peaks-loop-final-review": "0.0.12",
     "peaks-loop-job-snapshot": "0.0.6",
-    "peaks-loop-shared": "0.0.26",
-    "peaks-loop-shared-channel": "0.0.6"
+    "peaks-loop-doctor": "0.0.12",
+    "peaks-loop-shared-channel": "0.0.6",
+    "peaks-loop-shared": "0.0.27"
   },
   "peerDependencies": {
     "@alibaba-group/open-code-review": "1.3.1"

package/scripts/sync-version.mjs

@@ -18,46 +18,20 @@ writeFileSync(
   `export const CLI_VERSION = ${JSON.stringify(version)};\n`,
 );
 
-// 2026-07-22 follow-up (post-monorepo recurrence): automatically bump
-// `peaks-loop-shared`'s own package.json version so the npm pack always
-// ships a fresh tarball. Pre-monorepo this never recurred because the
-// root was the only published artifact; in monorepo mode the shared
-// subpackage's tarball gets cached on the registry with stale CLI_VERSION
-// when only the root version changes, and `npm install` re-uses that
-// cached tarball because peaks-loop<ver>'s package.json still pins
-// `peaks-loop-shared@<old>`. Bumping the shared version forces a fresh
-// tarball upload. Read-modify-write on the shared package's package.json
-// only — the shared package is private, so its version field doesn't
-// appear in any consumer's package.json (the peaks-loop dependency
-// rewrite is still handled by the publish pack step).
+// 2026-07-23 follow-up (peaks-publish-stale fix, AC6): the shared
+// bump used to live here, gated on `PEAKS_AUTO_BUMP_SHARED === '1'`.
+// That gate was the Layer 2 root cause: publish.yml set the env on
+// the CI Build step, but local dev runs (and any path that didn't
+// re-export the env) produced stale shared tarballs. The bump now
+// lives in `scripts/bump-version.mjs` (which always runs when root
+// version changes) and `bump-version.mjs` is the single owner of
+// the shared/package.json#version bump.
 //
-// SAFETY: this auto-bump only runs when invoked from the publish
-// `build` step (i.e. on the CI runner producing a release). It does NOT
-// run for `pretest` / `predev` / `prepublish` / `pretest:coverage` —
-// otherwise a local dev loop would ratchet the shared version upward
-// by 0.0.1 every test run and the working tree would diverge from the
-// last git tag. The gate is `process.env.PEAKS_AUTO_BUMP_SHARED === '1'`.
-//
-// Skip the bump when the existing shared version is NOT a clean
-// x.y.z SemVer (some test fixtures use markers like `9.9.9-oldsub`).
-// In that case, leave the version alone and let the test that set
-// the marker continue to work.
-if (process.env.PEAKS_AUTO_BUMP_SHARED === '1') {
-  const sharedPkgPath = resolve('packages/peaks-loop-shared/package.json');
-  const sharedPkg = JSON.parse(readFileSync(sharedPkgPath, 'utf8'));
-  const sharedVersion = sharedPkg.version;
-  const sharedVersionMatch = /^(\d+)\.(\d+)\.(\d+)$/.exec(sharedVersion);
-  if (sharedVersionMatch) {
-    const nextSharedVersion = `${sharedVersionMatch[1]}.${sharedVersionMatch[2]}.${Number(sharedVersionMatch[3]) + 1}`;
-    sharedPkg.version = nextSharedVersion;
-    writeFileSync(sharedPkgPath, JSON.stringify(sharedPkg, null, 2) + '\n');
-    console.log(`[sync-version] bumped peaks-loop-shared ${sharedVersion} -> ${nextSharedVersion} (root ${version})`);
-  } else {
-    console.log(`[sync-version] peaks-loop-shared version "${sharedVersion}" is not x.y.z; skipping auto-bump`);
-  }
-} else {
-  console.log(`[sync-version] peaks-loop-shared auto-bump skipped (PEAKS_AUTO_BUMP_SHARED not set)`);
-}
+// This script keeps a fallback shared bump when explicitly invoked
+// from another path with `PEAKS_AUTO_BUMP_SHARED === '1'` — that
+// preserves the contract for any out-of-band build invocation that
+// still sets the env var. The bump-version.mjs path is primary and
+// always-on; the gate here is just a back-stop.
 
 // 2026-07-22 follow-up (Bug-04 root-cause fix): the previous version of
 // this script wrote `version.ts` only, then handed off to `tsc`. Tsc's