scene-capability-engine 3.6.18 → 3.6.20

package/CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.6.20] - 2026-03-06
+
+### Added
+- Capability catalog entries now expose pre-publish readiness UI fields for badge rendering and sorting.
+- Magicball capability library guide now documents list-level publish readiness fields.
+
+## [3.6.19] - 2026-03-06
+
+### Added
+- Capability map/register payloads now expose `release_readiness` with structured blocking reasons for publish UI.
+- Capability catalog payloads now expose `release_readiness_ui` for pre-publish status badges and sorting.
+- Magicball capability docs now define release blocker rendering for capability publish pages.
+
 ## [3.6.18] - 2026-03-06
 
 ### Added

package/README.md

@@ -218,5 +218,5 @@ MIT. See [LICENSE](LICENSE).
 
 ---
 
-**Version**: 3.6.18  
+**Version**: 3.6.20  
 **Last Updated**: 2026-03-05

package/README.zh.md

@@ -218,5 +218,5 @@ MIT，见 [LICENSE](LICENSE)。
 
 ---
 
-**版本**：3.6.18  
+**版本**：3.6.20  
 **最后更新**：2026-03-05

package/docs/command-reference.md

@@ -1897,6 +1897,8 @@ Schema references:
 ### Capability Library Reuse (query -> match -> use)
 
 `catalog/list/search/show/match/use` responses now include `ontology_core` and `ontology_core_ui` so UI can render triad readiness directly.
+`capability map/register` responses now include `release_readiness` so UI can render blocking reasons before publish.
+Catalog payloads also expose `release_readiness_ui` for pre-publish sorting and status badges.
 
 ```bash
 # List capability templates

package/docs/magicball-capability-iteration-api.md

@@ -87,7 +87,7 @@ sce capability map --input <candidate_file> --mapping <ontology_file> \
 ```
 
 响应：
-- 返回 `capability-map` payload，重点消费 `template.ontology_core`
+- 返回 `capability-map` payload，重点消费 `template.ontology_core` 与 `release_readiness`
 
 ---
 
@@ -112,7 +112,7 @@ sce capability register --input <template_file> --risk-level <level> --difficult
 ```
 
 响应：
-- 返回 `capability-register` payload，重点消费 `ontology_core`（入库 triad 审核结果）
+- 返回 `capability-register` payload，重点消费 `ontology_core` 与 `release_readiness`（入库 triad 审核结果）
 
 ---
 

package/docs/magicball-capability-iteration-ui.md

@@ -180,3 +180,9 @@ sce capability register --input <template.json> --json
 - `ontology_core_ui.missing`
 - `summary.ontology_triads_ready`
 - `summary.ontology_missing_triads`
+
+## 9. 发布阻断提示
+
+- 发布页直接消费 `release_readiness.ready`
+- 若为 `false`，展示 `blockers[].reason`、`blockers[].missing`、`blockers[].remediation`
+- 默认阻断文案：`能力模板未达到发布条件`

package/docs/magicball-capability-library.md

@@ -145,3 +145,35 @@ sce capability use --template <template-id> --spec <spec-id> --apply --json
 ---
 
 若需要“自动落地写入 spec 任务”的强制执行模式，可以在后续版本加 `--apply` 开关。
+
+### release_readiness_ui（列表状态）
+```json
+{
+  "publish_ready": false,
+  "blocking_count": 1,
+  "blocking_ids": ["ontology-core-triads"],
+  "blocking_reasons": ["missing required ontology triads"],
+  "blocking_missing": ["decision_strategy"]
+}
+```
+
+### release_readiness（发布阻断原因）
+```json
+{
+  "ready": false,
+  "blockers": [
+    {
+      "id": "ontology-core-triads",
+      "severity": "blocking",
+      "reason": "missing required ontology triads",
+      "missing": ["decision_strategy"],
+      "missing_labels": ["decision_strategy"],
+      "remediation": [
+        "补齐实体关系（entities + relations）",
+        "补齐业务规则（business_rules）",
+        "补齐决策策略（decisions)"
+      ]
+    }
+  ]
+}
+```

package/lib/commands/capability.js

@@ -432,10 +432,66 @@ function enrichCapabilityTemplateForUi(template) {
   const ontologyCore = template && template.ontology_core
     ? template.ontology_core
     : buildCoreOntologySummary(template && template.ontology_scope ? template.ontology_scope : createEmptyOntologyScope());
+  const releaseReadiness = template && template.release_readiness
+    ? template.release_readiness
+    : {
+        ready: ontologyCore.ready === true,
+        blockers: ontologyCore.ready === true
+          ? []
+          : [{
+              id: 'ontology-core-triads',
+              severity: 'blocking',
+              reason: 'missing required ontology triads',
+              missing: Array.isArray(ontologyCore.missing) ? ontologyCore.missing : []
+            }],
+        ontology_core: ontologyCore,
+        ontology_core_ui: buildOntologyCoreUiState(ontologyCore)
+      };
   return {
     ...template,
     ontology_core: ontologyCore,
-    ontology_core_ui: buildOntologyCoreUiState(ontologyCore)
+    ontology_core_ui: buildOntologyCoreUiState(ontologyCore),
+    release_readiness: releaseReadiness,
+    release_readiness_ui: buildCapabilityReleaseReadinessUi(releaseReadiness)
+  };
+}
+
+function buildCapabilityReleaseReadiness(templateCandidate) {
+  const enriched = enrichCapabilityTemplateForUi(templateCandidate || {});
+  const blockers = [];
+  if (!enriched.ontology_core.ready) {
+    blockers.push({
+      id: 'ontology-core-triads',
+      severity: 'blocking',
+      reason: 'missing required ontology triads',
+      missing: enriched.ontology_core.missing,
+      missing_labels: enriched.ontology_core_ui.missing_labels,
+      remediation: [
+        '补齐实体关系（entities + relations）',
+        '补齐业务规则（business_rules）',
+        '补齐决策策略（decisions）'
+      ]
+    });
+  }
+  return {
+    ready: blockers.length === 0,
+    blockers,
+    ontology_core: enriched.ontology_core,
+    ontology_core_ui: enriched.ontology_core_ui
+  };
+}
+
+function buildCapabilityReleaseReadinessUi(readiness) {
+  const details = readiness && typeof readiness === 'object'
+    ? readiness
+    : { ready: true, blockers: [] };
+  const blockers = Array.isArray(details.blockers) ? details.blockers : [];
+  return {
+    publish_ready: details.ready === true,
+    blocking_count: blockers.length,
+    blocking_ids: blockers.map((item) => item && item.id).filter(Boolean),
+    blocking_reasons: blockers.map((item) => item && item.reason).filter(Boolean),
+    blocking_missing: blockers.flatMap((item) => Array.isArray(item && item.missing) ? item.missing : [])
   };
 }
 
@@ -861,7 +917,8 @@ async function runCapabilityMapCommand(options = {}, dependencies = {}) {
     generated_at: new Date().toISOString(),
     input: inputPath,
     mapping: mappingPath || null,
-    template: templateCandidate
+    template: templateCandidate,
+    release_readiness: buildCapabilityReleaseReadiness(templateCandidate)
   };
 
   const outputPath = normalizeText(options.out) || buildDefaultTemplatePath(sceneId);
@@ -895,6 +952,15 @@ async function runCapabilityRegisterCommand(options = {}, dependencies = {}) {
   if (!templateCandidate || !templateCandidate.template_id) {
     throw new Error('template_id missing in capability template candidate');
   }
+  const releaseReadiness = buildCapabilityReleaseReadiness(templateCandidate);
+  if (!releaseReadiness.ready) {
+    const error = new Error(`capability register blocked: ${releaseReadiness.blockers.map((item) => item.reason).join('; ')}`);
+    error.code = 'CAPABILITY_REGISTER_BLOCKED';
+    error.details = {
+      release_readiness: releaseReadiness
+    };
+    throw error;
+  }
   const ontologySummary = assertCoreOntologySummary(
     buildCoreOntologySummary(templateCandidate.ontology_scope),
     'capability template'
@@ -919,6 +985,7 @@ async function runCapabilityRegisterCommand(options = {}, dependencies = {}) {
     template_id: templateCandidate.template_id,
     output_dir: exportDir,
     ontology_core: ontologySummary,
+    release_readiness: releaseReadiness,
     files: [
       path.join(exportDir, 'capability-template.json'),
       path.join(exportDir, 'template-registry.json')
@@ -1426,5 +1493,12 @@ module.exports = {
   runCapabilityExtractCommand,
   runCapabilityScoreCommand,
   runCapabilityMapCommand,
-  runCapabilityRegisterCommand
+  runCapabilityRegisterCommand,
+  listCapabilityCatalog,
+  searchCapabilityCatalog,
+  showCapabilityTemplate,
+  matchCapabilityTemplates,
+  useCapabilityTemplate,
+  enrichCapabilityTemplateForUi,
+  buildCapabilityReleaseReadinessUi
 };

package/package.json

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