scene-capability-engine 3.6.58 → 3.6.60

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.6.60] - 2026-03-19
+
+### Changed
+- Stabilized tracked `project-shared-problems.json` aging output to whole-day precision so release and publish gates no longer dirty the worktree on minute-scale `age_days` drift.
+- Published the canonical follow-up package after `3.6.59` was already minted from the pre-fix candidate; use `3.6.60` when strict npm/tag/repository alignment matters.
+
+## [3.6.59] - 2026-03-19
+
+### Changed
+- Published a follow-up alignment patch so the npm package, Git tag, and repository release line all point at the final post-release state after shared project problem projection sync.
+- Kept runtime capability contracts unchanged from `3.6.58`; this patch is for release-state consistency rather than new engine behavior.
+
 ## [3.6.58] - 2026-03-19
 
 ### Added

package/README.md

@@ -230,5 +230,5 @@ MIT. See [LICENSE](LICENSE).
 
 ---
 
-**Version**: 3.6.58
+**Version**: 3.6.60
 **Last Updated**: 2026-03-19

package/README.zh.md

@@ -235,5 +235,5 @@ MIT，见 [LICENSE](LICENSE)。
 
 ---
 
-**版本**：3.6.58
+**版本**：3.6.60
 **最后更新**：2026-03-19

package/docs/releases/README.md

@@ -9,6 +9,8 @@ This directory stores release-facing documents:
 ## Archived Versions
 
 - [Release checklist](../release-checklist.md)
+- [v3.6.60 release notes](./v3.6.60.md)
+- [v3.6.59 release notes](./v3.6.59.md)
 - [v3.6.58 release notes](./v3.6.58.md)
 - [v3.6.57 release notes](./v3.6.57.md)
 - [v3.6.56 release notes](./v3.6.56.md)

package/docs/releases/v3.6.59.md

@@ -0,0 +1,18 @@
+# v3.6.59 Release Notes
+
+Release date: 2026-03-19
+
+## Highlights
+
+- Published an alignment-only follow-up patch so the npm package, repository tag, and release branch all reference the same final repository state.
+- Kept the MagicBall delivery, engineering, and multi-project contracts exactly the same as `v3.6.58`.
+
+## Validation
+
+- `npm run audit:release-docs`
+- `node scripts/git-managed-gate.js --fail-on-violation --json`
+- `npm publish --access public` via `prepublishOnly`
+
+## Release Notes
+
+- This patch does not introduce new runtime or adapter-facing behavior. It exists to remove release-state ambiguity after the post-release shared project problem projection snapshot was committed to the repository. Use `v3.6.59` as the canonical follow-up version when strict npm/tag/repository alignment matters.

package/docs/releases/v3.6.60.md

@@ -0,0 +1,19 @@
+# v3.6.60 Release Notes
+
+Release date: 2026-03-19
+
+## Highlights
+
+- Stabilized tracked `project-shared-problems.json` aging output to whole-day precision so release and publish gates no longer dirty the worktree on minute-scale `age_days` drift.
+- Published the canonical follow-up package after `v3.6.59` had already been published from the pre-fix candidate.
+
+## Validation
+
+- `npx jest tests/unit/problem/project-problem-projection.test.js --runInBand`
+- `npm run audit:release-docs`
+- `node scripts/git-managed-gate.js --fail-on-violation --json`
+- `npm publish --access public` via `prepublishOnly`
+
+## Release Notes
+
+- Use `v3.6.60` as the canonical aligned version for the shared-problem projection release line. It preserves the `v3.6.58/v3.6.59` MagicBall and multi-project contracts, and only closes the last publish-time worktree-drift gap in tracked project problem projection output.

package/docs/zh/releases/README.md

@@ -9,6 +9,8 @@
 ## 历史版本归档
 
 - [发布检查清单](../release-checklist.md)
+- [v3.6.60 发布说明](./v3.6.60.md)
+- [v3.6.59 发布说明](./v3.6.59.md)
 - [v3.6.58 发布说明](./v3.6.58.md)
 - [v3.6.57 发布说明](./v3.6.57.md)
 - [v3.6.56 发布说明](./v3.6.56.md)

package/docs/zh/releases/v3.6.59.md

@@ -0,0 +1,18 @@
+# v3.6.59 发布说明
+
+发布日期：2026-03-19
+
+## 重点变化
+
+- 发布了一个仅用于对齐的补丁版，使 npm 包、仓库 tag 与发布分支都指向同一份最终仓库状态。
+- MagicBall 的 delivery、engineering 与 multi-project 契约能力与 `v3.6.58` 保持完全一致，没有新增运行时能力变化。
+
+## 验证
+
+- `npm run audit:release-docs`
+- `node scripts/git-managed-gate.js --fail-on-violation --json`
+- 通过 `prepublishOnly` 执行 `npm publish --access public`
+
+## 发布说明
+
+- 这个补丁版不引入新的运行时行为，也不改变适配层合同。它的目的只是消除发版状态歧义：在共享项目问题投影快照于发版后写回仓库后，再给出一个严格对齐 npm/tag/仓库状态的正式版本。如果你要求 npm、tag、GitHub 发布线完全一致，应以后续的 `v3.6.59` 作为标准版本。

package/docs/zh/releases/v3.6.60.md

@@ -0,0 +1,19 @@
+# v3.6.60 发布说明
+
+发布日期：2026-03-19
+
+## 重点变化
+
+- 稳定了被 Git 跟踪的 `project-shared-problems.json` aging 输出；发布/发版时不再因为分钟级 `age_days` 漂移把工作区写脏。
+- 在 `v3.6.59` 已经以未修复候选包形式发布后，补发了真正对齐的正式版本。
+
+## 验证
+
+- `npx jest tests/unit/problem/project-problem-projection.test.js --runInBand`
+- `npm run audit:release-docs`
+- `node scripts/git-managed-gate.js --fail-on-violation --json`
+- 通过 `prepublishOnly` 执行 `npm publish --access public`
+
+## 发布说明
+
+- `v3.6.60` 才是这条 shared-problem projection 发布线的标准对齐版本。它保持 `v3.6.58/v3.6.59` 的 MagicBall 与多项目合同不变，只补上了项目共享问题投影在发版时的最后一个工作区漂移缺口。

package/lib/problem/project-problem-projection.js

@@ -107,6 +107,14 @@ function toComparableProjection(payload) {
   return sortKeysDeep(clone);
 }
 
+function normalizeProjectionAgeDays(value) {
+  const numeric = Number(value);
+  if (!Number.isFinite(numeric)) {
+    return null;
+  }
+  return Math.max(0, Math.floor(numeric));
+}
+
 async function buildProjectSharedProblemProjection(projectPath = process.cwd(), options = {}, dependencies = {}) {
   const fileSystem = dependencies.fileSystem || fs;
   const studioIntakePolicy = dependencies.studioIntakePolicy || await loadStudioIntakePolicy(projectPath, fileSystem);
@@ -156,7 +164,7 @@ async function buildProjectSharedProblemProjection(projectPath = process.cwd(),
       scene_id: record.scene_id || null,
       lifecycle_state: record.lifecycle_state || null,
       updated_at: record.updated_at || null,
-      age_days: Number.isFinite(Number(record.age_days)) ? Number(record.age_days) : null,
+      age_days: normalizeProjectionAgeDays(record.age_days),
       tasks_total: Number.isFinite(Number(record.tasks_total)) ? Number(record.tasks_total) : 0,
       tasks_done: Number.isFinite(Number(record.tasks_done)) ? Number(record.tasks_done) : 0,
       tasks_progress: Number.isFinite(Number(record.tasks_progress)) ? Number(record.tasks_progress) : 0,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scene-capability-engine",
-  "version": "3.6.58",
+  "version": "3.6.60",
   "description": "SCE (Scene Capability Engine) - A CLI tool and npm package for spec-driven development with AI coding assistants.",
   "main": "index.js",
   "bin": {

package/template/.sce/README.md

@@ -243,6 +243,6 @@ A Spec is a complete feature definition with three parts:
 ---
 
 **Project Type**: Spec-driven development  
-**sce Version**: 3.6.58  
+**sce Version**: 3.6.60  
 **Last Updated**: 2026-03-19  
 **Purpose**: Guide AI tools to work effectively with this project