scene-capability-engine 3.0.2 → 3.0.3

package/CHANGELOG.md

@@ -8,7 +8,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 ### Added
+- **Capability lexicon hard gate end-to-end defaultization**: `sce auto handoff run` and `sce auto handoff capability-matrix` now enforce unknown Moqui capability alias blocking by default (expected/provided), emit lexicon gate telemetry into release evidence, and promote those signals into governance risk/concern/recommendation/close-loop block decisions.
 - **SCE naming consolidation + compatibility bridge**: Rebranded product naming to `Scene Capability Engine`, moved package to `scene-capability-engine`, promoted `sce` as the primary CLI command, and preserved `sco` / `sce` / `scene-capability-engine` aliases for migration continuity.
+- **Official template library v1.5.0 alignment**: Synced with `scene-capability-engine-templates` `v1.5.0`, adding scene orchestration template coverage for canvas visualization, interaction hardening, execution playbook, dependency drilldown, decision cockpit, runbook export, action queue orchestration, action pack export, and unified scene governance closure.
 - **Branding consistency release guard**: Added `test:brand-consistency` to block publish when legacy repository/package/product naming reappears in tracked source files.
 - **Rate-limit launch budget safety guard**: Hardened orchestration launch-budget bookkeeping to safely handle partially initialized engine instances in property/instrumentation scenarios.
 - **Property test CI stability (`orchestration-engine.property`)**: Disabled launch-budget waiting in parallel invariant property harness to avoid artificial 60s hold windows and intermittent Jest worker crashes under high-concurrency CI runs.

package/docs/command-reference.md

@@ -724,7 +724,13 @@ Close-loop controller session maintenance:
 
 Cross-archive autonomous governance maintenance:
 - `sce auto governance stats [--days <n>] [--status <csv>] [--json]`: aggregate a unified governance snapshot from session/batch-session/controller-session archives plus recovery memory state.
-  - JSON output includes `totals`, `throughput`, `health` (`risk_level`, `concerns`, `recommendations`, `release_gate`), `top_master_specs`, `recovery_memory`, and full per-archive stats under `archives`.
+  - JSON output includes `totals`, `throughput`, `health` (`risk_level`, `concerns`, `recommendations`, `release_gate`, `handoff_quality`), `top_master_specs`, `recovery_memory`, and full per-archive stats under `archives`.
+  - `health.handoff_quality` carries Moqui matrix regression governance signals:
+    - `latest_moqui_matrix_regression_count`
+    - `latest_moqui_matrix_regression_gate_max`
+    - `avg_moqui_matrix_regression_count`
+    - `max_moqui_matrix_regression_count`
+    - `moqui_matrix_regression_positive_rate_percent`
 - `sce auto governance maintain [--days <n>] [--status <csv>] [--session-keep <n>] [--batch-session-keep <n>] [--controller-session-keep <n>] [--recovery-memory-older-than-days <n>] [--apply] [--dry-run] [--json]`: run governance-maintenance planning and optional execution in one command.
   - Plan-only mode is default; add `--apply` to execute maintenance actions (`session prune`, `batch-session prune`, `controller-session prune`, `recovery-memory prune`).
   - When release gate is blocked, plan output prioritizes release remediation advisories (`release-gate-evidence-review`, `release-gate-scene-batch-remediate`) before routine cleanup actions.
@@ -736,6 +742,9 @@ Cross-archive autonomous governance maintenance:
   - `--governance-session-keep` (with optional `--governance-session-older-than-days`) enables post-run governance session retention pruning while protecting the current session snapshot.
   - `--execute-advisory` enables automatic advisory action execution (`recover-latest`, `controller-resume-latest`) when governance assessment detects failed sessions or controller pending goals; sce auto-selects the latest actionable advisory source and reports `skipped` (not `failed`) when no actionable source exists.
   - JSON output includes round-by-round risk/action telemetry (`rounds`, with `risk_before/risk_after` and `release_gate_before/release_gate_after`), advisory telemetry (`execute_advisory`, `advisory_policy`, `advisory_summary`, `rounds[*].advisory_actions`), `stop_detail` + `recommendations` for explicit blocking reasons, plus `initial_assessment`, `final_assessment`, and convergence metadata.
+  - Release-gate block reasons now include handoff matrix regression reasons when present:
+    - `handoff-moqui-matrix-regressions-positive:<n>`
+    - `handoff-moqui-matrix-regressions-over-gate:<n>/<max>`
 - `sce auto governance session list [--limit <n>] [--status <csv>] [--resume-only] [--json]`: list persisted governance close-loop sessions (`--resume-only` filters to resumed-chain sessions only).
 - `sce auto governance session stats [--days <n>] [--status <csv>] [--resume-only] [--json]`: aggregate governance close-loop session telemetry (completion/failure/convergence, rounds, risk/stop composition, resumed-chain ratios/source counts, and aggregated `release_gate` round telemetry trends).
 - `sce auto governance session prune [--keep <n>] [--older-than-days <n>] [--dry-run] [--json]`: prune governance close-loop session archive by retention policy.
@@ -770,19 +779,21 @@ Dual-track handoff integration:
 - `sce auto handoff queue --manifest <path> [--out <path>] [--append] [--no-include-known-gaps] [--dry-run] [--json]`: generate close-loop batch goal queue from handoff manifest and optionally persist line-based queue file (default `.kiro/auto/handoff-goals.lines`).
 - `sce auto handoff template-diff --manifest <path> [--json]`: compare manifest templates against local template exports/registry and report `missing_in_local` and `extra_in_local`.
 - `sce auto handoff capability-matrix --manifest <path> [--strict] [--strict-warnings] [--min-capability-coverage <n>] [--min-capability-semantic <n>] [--no-require-capability-semantic] [--format <json|markdown>] [--out <path>] [--remediation-queue-out <path>] [--fail-on-gap] [--json]`: generate a fast Moqui capability matrix (`template-diff + baseline + capability coverage + semantic completeness`) and optionally fail fast on gaps.
-- `sce auto handoff run --manifest <path> [--out <path>] [--queue-out <path>] [--append] [--no-include-known-gaps] [--continue-from <session|latest|file>] [--continue-strategy <auto|pending|failed-only>] [--dry-run] [--strict] [--strict-warnings] [--no-dependency-batching] [--min-spec-success-rate <n>] [--max-risk-level <level>] [--no-require-ontology-validation] [--no-require-moqui-baseline] [--min-capability-coverage <n>] [--no-require-capability-coverage] [--require-release-gate-preflight] [--release-evidence-window <n>] [--json]`: execute handoff end-to-end (`plan -> queue -> close-loop-batch -> observability`) with automatic report archive to `.kiro/reports/handoff-runs/<session>.json`.
+- `sce auto handoff run --manifest <path> [--out <path>] [--queue-out <path>] [--append] [--no-include-known-gaps] [--continue-from <session|latest|file>] [--continue-strategy <auto|pending|failed-only>] [--dry-run] [--strict] [--strict-warnings] [--no-dependency-batching] [--min-spec-success-rate <n>] [--max-risk-level <level>] [--max-moqui-matrix-regressions <n>] [--no-require-ontology-validation] [--no-require-moqui-baseline] [--min-capability-coverage <n>] [--no-require-capability-coverage] [--require-release-gate-preflight] [--release-evidence-window <n>] [--json]`: execute handoff end-to-end (`plan -> queue -> close-loop-batch -> observability`) with automatic report archive to `.kiro/reports/handoff-runs/<session>.json`.
   - Default mode is dependency-aware: spec integration goals are grouped into dependency batches and executed in topological order.
   - `--continue-from` resumes pending goals from an existing handoff run report (`latest`, session id, or JSON file path). For safety, sce enforces manifest-path consistency between the previous report and current run.
   - `--continue-strategy auto|pending|failed-only` controls resumed scope. `auto` (default) derives the best strategy from prior run state (`pending` when unprocessed/planned goals exist, otherwise `failed-only` for pure failure replay).
   - Non-dry runs auto-merge release evidence into `.kiro/reports/release-evidence/handoff-runs.json` with session-level gate/ontology/regression/moqui-baseline/capability-coverage snapshots. Merge failures are recorded as warnings without aborting the run.
   - `--release-evidence-window` controls trend snapshot window size (2-50, default `5`) used in merged release evidence (`latest_trend_window` and per-session `trend_window`).
   - Run output includes `moqui_baseline` snapshot by default, with artifacts at `.kiro/reports/release-evidence/moqui-template-baseline.json` and `.kiro/reports/release-evidence/moqui-template-baseline.md`.
+  - `moqui_baseline.summary` now includes `scope_breakdown`, `coverage_matrix`, and `gap_frequency` for ER/BR/decision closure tracking.
+  - `moqui_baseline.compare` now includes `coverage_matrix_deltas` and `coverage_matrix_regressions` for trend-level entity/relation/rule/decision closure movement and negative-delta alerts (used by matrix-regression hard gate).
   - Run output includes `moqui_capability_coverage` snapshot by default (when manifest `capabilities` is declared), with artifacts at `.kiro/reports/release-evidence/moqui-capability-coverage.json` and `.kiro/reports/release-evidence/moqui-capability-coverage.md`.
   - Run output includes `release_gate_preflight` (latest release gate history signal snapshot + blocked reasons) and carries this context into `warnings`.
   - `release_gate_preflight` is advisory by default; use `--require-release-gate-preflight` to hard-fail when preflight is unavailable/blocked.
   - When Moqui baseline/capability gates fail, sce auto-generates remediation queue lines at `.kiro/auto/moqui-remediation.lines`.
   - Run result includes `failure_summary` (failed phase/gate/release-gate preflight highlights) and `recommendations` with executable follow-up commands (for example, auto-generated `--continue-from <session>` on failed/incomplete batches).
-  - Gate defaults: `--min-spec-success-rate` defaults to `100`, `--max-risk-level` defaults to `high`, ontology validation requirement is enabled by default, Moqui baseline requirement is enabled by default, and capability coverage minimum defaults to `100` when manifest `capabilities` is declared.
+  - Gate defaults: `--min-spec-success-rate` defaults to `100`, `--max-risk-level` defaults to `high`, `--max-moqui-matrix-regressions` defaults to `0`, ontology validation requirement is enabled by default, Moqui baseline requirement is enabled by default, and capability coverage minimum defaults to `100` when manifest `capabilities` is declared.
   - Use `--no-require-ontology-validation`, `--no-require-moqui-baseline`, or `--no-require-capability-coverage` only for emergency bypass.
 - `sce auto handoff regression [--session-id <id|latest>] [--window <n>] [--format <json|markdown>] [--out <path>] [--json]`: compare one handoff run report with its previous run and output trend deltas (success-rate/risk/failed-goals/elapsed time).
   - `--window` (2-50, default `2`) returns multi-run `series`, `window_trend`, and `aggregates` for broader regression visibility.
@@ -806,6 +817,9 @@ Dual-track handoff integration:
   - Aggregates include scene package batch, drift, and release-preflight/hard-gate signals (`scene_package_batch_*`, `drift_alert_*`, `drift_block_*`, `release_gate_preflight_*`) when present in gate reports.
   - `--markdown-out <path>` writes a human-readable trend card markdown for PR/Issue handoff.
 
+Moqui template library lexicon audit (script-level governance helper):
+- `node scripts/moqui-lexicon-audit.js [--manifest <path>] [--template-dir <path>] [--lexicon <path>] [--out <path>] [--markdown-out <path>] [--fail-on-gap] [--json]`: audit manifest/template capability names against canonical Moqui lexicon; reports unknown aliases and uncovered expected capabilities.
+
 Recommended `.kiro/config/orchestrator.json`:
 
 ```json
@@ -904,13 +918,14 @@ sce scene package-ontology-backfill-batch --from-331 --dry-run --out-report .kir
 ### Moqui Template Baseline Scorecard
 
 ```bash
-# Preferred CLI entry: score Moqui/ERP templates in the local template library (default filter: moqui|erp)
+# Preferred CLI entry: score Moqui + scene orchestration templates in the local template library
+# (default filter: moqui|erp|suite|playbook|runbook|decision|action|governance)
 sce scene moqui-baseline --json
 
 # Script alias (same behavior)
 npm run report:moqui-baseline
 
-# Score all scene templates instead of Moqui/ERP subset
+# Score all scene templates instead of the default Moqui + orchestration subset
 sce scene moqui-baseline --include-all --json
 
 # Customize score thresholds and output paths

package/docs/moqui-capability-matrix.md

@@ -15,6 +15,27 @@ This document defines the execution boundary for converting Moqui capabilities i
 | P0 | Order read (`OrderHeader`, `OrderItem`, query services) | `query` | `sce.scene--erp-order-query-read--0.1.0` | `order_header`, `order_item`, `order_projection`, `customer_party` | low risk, idempotent query, lineage complete | template-ready |
 | P0 | Order fulfillment (reserve, payment, release) | `workflow` | `sce.scene--erp-order-fulfillment-workflow--0.1.0` | `order_header`, `order_item`, `inventory_reservation`, `payment_authorization`, `fulfillment_execution` | medium risk, approval required, compensation strategy | template-ready |
 | P0 | Inventory reserve + adjust | `workflow/crud hybrid` | `sce.scene--erp-inventory-reserve-adjust--0.1.0` | `inventory_item`, `inventory_reservation`, `inventory_adjustment`, `inventory_snapshot` | medium risk, approval required, non-negative stock rule | template-ready |
+| P1 | Party master (`Party`, `PartyRole`) | `crud` | `sce.scene--erp-party-management--0.1.0` | `party`, `party_role`, `party_relationship` | medium risk, merge/dedup strategy required | matrix-intake-ready |
+| P1 | Product master (`Product`, classification/pricing) | `crud` | `sce.scene--erp-product-management--0.1.0` | `product`, `product_category`, `price_rule` | medium risk, version consistency, rule closure | matrix-intake-ready |
+| P1 | Procurement + supplier flow | `workflow` | `sce.scene--erp-procurement-management--0.1.0` | `purchase_order`, `supplier_party`, `receipt_line` | medium risk, approval + receipt reconciliation | matrix-intake-ready |
+| P1 | Shipment execution + tracking | `workflow` | `sce.scene--erp-shipment-management--0.1.0` | `shipment`, `shipment_item`, `fulfillment_event` | medium risk, irreversible step guard | matrix-intake-ready |
+| P1 | Return/RMA handling | `workflow` | `sce.scene--erp-return-rma-management--0.1.0` | `return_header`, `return_item`, `refund_decision` | medium risk, policy decision completeness | matrix-intake-ready |
+| P1 | Production run + work order execution | `workflow` | `sce.scene--erp-production-run--0.1.0` | `production_run`, `work_effort`, `material_issue` | high risk, capacity/exception path required | matrix-intake-ready |
+| P1 | BOM + routing maintenance | `crud/workflow hybrid` | `sce.scene--erp-bom-routing-management--0.1.0` | `bom`, `routing`, `operation_step` | medium risk, effective-date governance | matrix-intake-ready |
+| P1 | Quality inspection + hold/release | `decision workflow` | `sce.scene--erp-quality-inspection--0.1.0` | `inspection_lot`, `quality_rule`, `release_decision` | high risk, decision closure mandatory | matrix-intake-ready |
+| P1 | Equipment lifecycle + maintenance | `workflow` | `sce.scene--erp-equipment-management--0.1.0` | `equipment_asset`, `maintenance_order`, `downtime_event` | medium risk, safety/approval policy | matrix-intake-ready |
+| P2 | Workflow approval engine | `platform service` | `sce.scene--platform-workflow-approval-engine--0.1.0` | `approval_flow`, `approval_node`, `approval_decision` | high risk, branch decision coverage | matrix-intake-ready |
+| P2 | Reporting + audit operations | `platform query` | `sce.scene--platform-reporting-audit-ops--0.1.0` | `audit_event`, `report_slice`, `trace_lineage` | low risk, lineage completeness | matrix-intake-ready |
+| P2 | Suite observability/parity audit | `platform query/dashboard` | `sce.scene--platform-suite-observability-parity--0.1.0` | `suite_capability`, `parity_audit`, `scene_coverage` | medium risk, regression signal quality | matrix-intake-ready |
+
+## 331-poc Intake Snapshot
+
+- Source baseline: `331-poc/docs/handoffs/handoff-manifest.json` (timestamp `2026-02-18T01:08:00+08:00`).
+- Newly aligned domain set in this round: party/product/order/procurement/inventory/production/quality/equipment/cost/engineering/hr/calendar + suite platform governance templates.
+- Core landing contract:
+  - capability aliases are normalized through `lib/data/moqui-capability-lexicon.json`
+  - handoff run default gate keeps `max_moqui_matrix_regressions=0`
+  - governance stats/close-loop consumes matrix regression signals as release-block conditions
 
 ## Ownership Boundary
 

package/docs/moqui-template-core-library-playbook.md

@@ -15,8 +15,10 @@ sce defaults already enforce the baseline below:
 - `sce auto handoff run`: ontology validation is required by default.
 - `sce auto handoff run`: generates Moqui baseline snapshot by default and appends it to release-evidence sessions.
 - `sce auto handoff run`: requires Moqui baseline portfolio pass by default.
+- `sce auto handoff run`: enforces Moqui matrix regression hard-gate by default (`max_moqui_matrix_regressions=0`).
 - `sce auto handoff run`: evaluates capability coverage matrix by default when manifest `capabilities` is declared (default minimum `100%`).
 - `sce auto handoff capability-matrix`: enforces both capability coverage and capability semantic completeness (default minimum `100%` for each).
+- `sce auto governance stats` / `sce auto governance close-loop`: treats Moqui matrix regressions as first-class risk/block signals (including over-gate stop reasons).
 - `sce scene package-publish-batch`:
   - ontology validation required by default
   - batch ontology gate defaults:
@@ -32,7 +34,7 @@ Emergency bypass exists but is not recommended:
 ## One-Shot Intake Flow
 
 ```bash
-# 0) Generate template baseline scoreboard (Moqui/ERP templates by default)
+# 0) Generate template baseline scoreboard (Moqui + scene orchestration templates by default)
 sce scene moqui-baseline --json
 
 # 0.1) CI/release mode: compare against previous baseline and enforce portfolio gate
@@ -49,9 +51,22 @@ sce auto handoff capability-matrix \
   --fail-on-gap \
   --json
 
+# 0.3) Capability lexicon audit (expected/provided canonical alignment)
+node scripts/moqui-lexicon-audit.js \
+  --manifest docs/handoffs/handoff-manifest.json \
+  --template-dir .kiro/templates/scene-packages \
+  --fail-on-gap \
+  --json
+
 # 1) Handoff close-loop
 sce auto handoff run --manifest docs/handoffs/handoff-manifest.json --json
 
+# 1.1) Explicitly keep strict matrix hard-gate (same as default, recommended in CI)
+sce auto handoff run \
+  --manifest docs/handoffs/handoff-manifest.json \
+  --max-moqui-matrix-regressions 0 \
+  --json
+
 # 2) Publish templates from scene packages (with default ontology gates)
 sce scene package-publish-batch \
   --manifest docs/handoffs/handoff-manifest.json \
@@ -80,6 +95,8 @@ Required artifacts for each intake batch:
 - `.kiro/reports/release-evidence/moqui-template-baseline.md`
 - `.kiro/reports/release-evidence/moqui-capability-coverage.json`
 - `.kiro/reports/release-evidence/moqui-capability-coverage.md`
+- `.kiro/reports/release-evidence/moqui-lexicon-audit.json`
+- `.kiro/reports/release-evidence/moqui-lexicon-audit.md`
 - `.kiro/reports/handoff-capability-matrix.md` (or JSON equivalent from `sce auto handoff capability-matrix`)
 - `.kiro/reports/handoff-runs/<session>.json`
 - `.kiro/reports/scene-package-ontology-batch.json`
@@ -87,6 +104,17 @@ Required artifacts for each intake batch:
 - `.kiro/templates/scene-packages/registry.json`
 - gate output/evidence linked from release notes or handoff summary
 
+`moqui-template-baseline.json` summary should be consumed as a matrix gate:
+- `scope_breakdown` (moqui_erp / scene_orchestration / other)
+- `coverage_matrix` (entity/relation/business-rule/decision coverage and closure rates)
+- `gap_frequency` (top recurring ontology gaps for remediation prioritization)
+- `compare.coverage_matrix_deltas` (trend deltas used to detect matrix regression/plateau between runs)
+- `compare.coverage_matrix_regressions` (negative-delta signals consumed by auto remediation/recommendation flows)
+- default handoff hard-gate enforces `max_moqui_matrix_regressions=0` unless explicitly relaxed
+- governance close-loop block reasons include:
+  - `handoff-moqui-matrix-regressions-positive:<n>`
+  - `handoff-moqui-matrix-regressions-over-gate:<n>/<max>`
+
 ## Minimum Semantic Coverage
 
 Each accepted template should include ontology semantics for: