scene-capability-engine 3.3.4 → 3.3.10

package/docs/interactive-customization/README.md

@@ -66,8 +66,8 @@ node scripts/interactive-context-bridge.js \
 
 Bridge output defaults:
 
-- Normalized page-context: `.kiro/reports/interactive-page-context.normalized.json`
-- Bridge report: `.kiro/reports/interactive-context-bridge.json`
+- Normalized page-context: `.sce/reports/interactive-page-context.normalized.json`
+- Bridge report: `.sce/reports/interactive-context-bridge.json`
 
 Run one-command full flow (bridge -> loop):
 
@@ -107,20 +107,20 @@ Common matrix flags:
 
 Flow output defaults:
 
-- Flow summary: `.kiro/reports/interactive-flow/<session-id>/interactive-flow.summary.json`
-- Bridge context: `.kiro/reports/interactive-flow/<session-id>/interactive-page-context.normalized.json`
-- Loop summary: `.kiro/reports/interactive-flow/<session-id>/interactive-customization-loop.summary.json`
-- Dialogue governance report: `.kiro/reports/interactive-flow/<session-id>/interactive-dialogue-governance.json`
+- Flow summary: `.sce/reports/interactive-flow/<session-id>/interactive-flow.summary.json`
+- Bridge context: `.sce/reports/interactive-flow/<session-id>/interactive-page-context.normalized.json`
+- Loop summary: `.sce/reports/interactive-flow/<session-id>/interactive-customization-loop.summary.json`
+- Dialogue governance report: `.sce/reports/interactive-flow/<session-id>/interactive-dialogue-governance.json`
 - Dialogue authorization signal stream:
-  - Session: `.kiro/reports/interactive-flow/<session-id>/interactive-dialogue-authorization-signals.jsonl`
-  - Global: `.kiro/reports/interactive-dialogue-authorization-signals.jsonl`
-- Authorization tier report: `.kiro/reports/interactive-flow/<session-id>/interactive-authorization-tier.json`
+  - Session: `.sce/reports/interactive-flow/<session-id>/interactive-dialogue-authorization-signals.jsonl`
+  - Global: `.sce/reports/interactive-dialogue-authorization-signals.jsonl`
+- Authorization tier report: `.sce/reports/interactive-flow/<session-id>/interactive-authorization-tier.json`
 - Authorization tier signal stream:
-  - Session: `.kiro/reports/interactive-flow/<session-id>/interactive-authorization-tier-signals.jsonl`
-  - Global: `.kiro/reports/interactive-authorization-tier-signals.jsonl`
-- Matrix summary JSON: `.kiro/reports/interactive-flow/<session-id>/moqui-template-baseline.json`
-- Matrix summary Markdown: `.kiro/reports/interactive-flow/<session-id>/moqui-template-baseline.md`
-- Matrix signal stream: `.kiro/reports/interactive-matrix-signals.jsonl`
+  - Session: `.sce/reports/interactive-flow/<session-id>/interactive-authorization-tier-signals.jsonl`
+  - Global: `.sce/reports/interactive-authorization-tier-signals.jsonl`
+- Matrix summary JSON: `.sce/reports/interactive-flow/<session-id>/moqui-template-baseline.json`
+- Matrix summary Markdown: `.sce/reports/interactive-flow/<session-id>/moqui-template-baseline.md`
+- Matrix signal stream: `.sce/reports/interactive-matrix-signals.jsonl`
 - Loop/flow summaries now include execution block diagnostics:
   - `summary.dialogue_authorization_decision` (`allow|review-required|deny`)
   - `summary.execution_block_reason_category` (`password-authorization|role-policy|authorization-tier|runtime-policy|approval-policy|unknown`)
@@ -142,7 +142,7 @@ Generate a change plan from intent (suggestion stage):
 
 ```bash
 node scripts/interactive-plan-build.js \
-  --intent .kiro/reports/interactive-change-intent.json \
+  --intent .sce/reports/interactive-change-intent.json \
   --context docs/interactive-customization/page-context.sample.json \
   --json
 ```
@@ -212,8 +212,8 @@ sce scene interactive-loop \
 ```
 
 `--feedback-score` writes feedback into both:
-- Session artifact: `.kiro/reports/interactive-loop/<session-id>/interactive-user-feedback.jsonl`
-- Governance global stream: `.kiro/reports/interactive-user-feedback.jsonl`
+- Session artifact: `.sce/reports/interactive-loop/<session-id>/interactive-user-feedback.jsonl`
+- Governance global stream: `.sce/reports/interactive-user-feedback.jsonl`
 - `--dialogue-profile` defaults to `business-user`; use `system-maintainer` for operations/maintenance sessions that must surface ticket + rollback requirements before execution.
 - `--ui-mode user-app|ops-console` binds interaction surface semantics (user app vs management console) and participates in authorization dialogue decisioning.
 - In default authorization tier, `business-user` only allows `suggestion` mode; apply path requires `system-maintainer` profile plus environment-specific step-up requirements.
@@ -226,7 +226,7 @@ Run runtime mode/environment policy evaluation directly:
 
 ```bash
 node scripts/interactive-runtime-policy-evaluate.js \
-  --plan .kiro/reports/interactive-change-plan.generated.json \
+  --plan .sce/reports/interactive-change-plan.generated.json \
   --ui-mode ops-console \
   --runtime-mode ops-fix \
   --runtime-environment staging \
@@ -250,12 +250,12 @@ Build interactive work-order artifacts directly:
 
 ```bash
 node scripts/interactive-work-order-build.js \
-  --plan .kiro/reports/interactive-change-plan.generated.json \
-  --dialogue .kiro/reports/interactive-dialogue-governance.json \
-  --gate .kiro/reports/interactive-change-plan-gate.json \
-  --runtime .kiro/reports/interactive-runtime-policy.json \
-  --authorization-tier .kiro/reports/interactive-authorization-tier.json \
-  --approval-state .kiro/reports/interactive-approval-state.json \
+  --plan .sce/reports/interactive-change-plan.generated.json \
+  --dialogue .sce/reports/interactive-dialogue-governance.json \
+  --gate .sce/reports/interactive-change-plan-gate.json \
+  --runtime .sce/reports/interactive-runtime-policy.json \
+  --authorization-tier .sce/reports/interactive-authorization-tier.json \
+  --approval-state .sce/reports/interactive-approval-state.json \
   --execution-attempted \
   --execution-result success \
   --execution-id exec-xxxx \
@@ -268,7 +268,7 @@ Run approval workflow state machine:
 # init from generated plan
 node scripts/interactive-approval-workflow.js \
   --action init \
-  --plan .kiro/reports/interactive-change-plan.generated.json \
+  --plan .sce/reports/interactive-change-plan.generated.json \
   --actor product-owner \
   --json
 
@@ -294,24 +294,24 @@ node scripts/interactive-moqui-adapter.js \
 # build plan from intent through adapter contract
 node scripts/interactive-moqui-adapter.js \
   --action plan \
-  --intent .kiro/reports/interactive-change-intent.json \
+  --intent .sce/reports/interactive-change-intent.json \
   --execution-mode suggestion \
   --json
 
 # validate/apply with policy gate and execution record output
 node scripts/interactive-moqui-adapter.js \
   --action validate \
-  --plan .kiro/reports/interactive-change-plan.adapter.json \
+  --plan .sce/reports/interactive-change-plan.adapter.json \
   --json
 node scripts/interactive-moqui-adapter.js \
   --action apply \
-  --plan .kiro/reports/interactive-change-plan.adapter.json \
+  --plan .sce/reports/interactive-change-plan.adapter.json \
   --json
 
 # one-click path: only accepts low-risk + allow decision
 node scripts/interactive-moqui-adapter.js \
   --action low-risk-apply \
-  --plan .kiro/reports/interactive-change-plan.adapter.json \
+  --plan .sce/reports/interactive-change-plan.adapter.json \
   --json
 
 # rollback by execution id from execution ledger
@@ -323,8 +323,8 @@ node scripts/interactive-moqui-adapter.js \
 
 Execution artifacts:
 
-- Latest execution record: `.kiro/reports/interactive-execution-record.latest.json`
-- Append-only execution ledger: `.kiro/reports/interactive-execution-ledger.jsonl`
+- Latest execution record: `.sce/reports/interactive-execution-record.latest.json`
+- Append-only execution ledger: `.sce/reports/interactive-execution-ledger.jsonl`
 - Execution records include diff summary, gate decision, validation snapshot, and rollback reference.
 
 Append business-user feedback for governance scoring:
@@ -354,29 +354,29 @@ node scripts/interactive-governance-report.js \
   --json
 ```
 
-The governance report consumes feedback events from `.kiro/reports/interactive-user-feedback.jsonl` by default.
-The governance report also consumes matrix signals from `.kiro/reports/interactive-matrix-signals.jsonl` by default.
-The governance report consumes dialogue-authorization signals from `.kiro/reports/interactive-dialogue-authorization-signals.jsonl` by default.
-The governance report consumes runtime policy signals from `.kiro/reports/interactive-runtime-signals.jsonl` by default.
-The governance report consumes authorization-tier signals from `.kiro/reports/interactive-authorization-tier-signals.jsonl` by default.
+The governance report consumes feedback events from `.sce/reports/interactive-user-feedback.jsonl` by default.
+The governance report also consumes matrix signals from `.sce/reports/interactive-matrix-signals.jsonl` by default.
+The governance report consumes dialogue-authorization signals from `.sce/reports/interactive-dialogue-authorization-signals.jsonl` by default.
+The governance report consumes runtime policy signals from `.sce/reports/interactive-runtime-signals.jsonl` by default.
+The governance report consumes authorization-tier signals from `.sce/reports/interactive-authorization-tier-signals.jsonl` by default.
 When `intent_total` is below `min_intent_samples` (default `5`), adoption emits a low-severity sample warning instead of a breach.
 
 Export matrix regression remediation queue lines (for close-loop-batch):
 
 ```bash
 node scripts/moqui-matrix-remediation-queue.js \
-  --baseline .kiro/reports/release-evidence/moqui-template-baseline.json \
+  --baseline .sce/reports/release-evidence/moqui-template-baseline.json \
   --top-templates 5 \
-  --lines-out .kiro/auto/matrix-remediation.lines \
-  --batch-json-out .kiro/auto/matrix-remediation.goals.json \
-  --commands-out .kiro/reports/release-evidence/matrix-remediation-commands.md \
+  --lines-out .sce/auto/matrix-remediation.lines \
+  --batch-json-out .sce/auto/matrix-remediation.goals.json \
+  --commands-out .sce/reports/release-evidence/matrix-remediation-commands.md \
   --json
 ```
 
 Recommended anti-429 phased execution (default outputs):
 
 ```bash
-sce auto close-loop-batch .kiro/auto/matrix-remediation.goals.high.json \
+sce auto close-loop-batch .sce/auto/matrix-remediation.goals.high.json \
   --format json \
   --batch-parallel 1 \
   --batch-agent-budget 2 \
@@ -386,7 +386,7 @@ sce auto close-loop-batch .kiro/auto/matrix-remediation.goals.high.json \
 
 sleep 30
 
-sce auto close-loop-batch .kiro/auto/matrix-remediation.goals.medium.json \
+sce auto close-loop-batch .sce/auto/matrix-remediation.goals.medium.json \
   --format json \
   --batch-parallel 1 \
   --batch-agent-budget 2 \
@@ -405,7 +405,7 @@ Zero-prep one-shot (prepare from baseline + run phased):
 
 ```bash
 node scripts/moqui-matrix-remediation-phased-runner.js \
-  --baseline .kiro/reports/release-evidence/moqui-template-baseline.json \
+  --baseline .sce/reports/release-evidence/moqui-template-baseline.json \
   --json
 
 npm run run:matrix-remediation-from-baseline -- --json

package/docs/interactive-customization/business-mode-policy-baseline.json

@@ -0,0 +1,33 @@
+{
+  "version": "1.0.0",
+  "defaults": {
+    "mode": null,
+    "enforce_alignment": true
+  },
+  "modes": {
+    "user-mode": {
+      "execution_mode": "suggestion",
+      "dialogue_profile": "business-user",
+      "ui_mode": "user-app",
+      "runtime_mode": "user-assist",
+      "runtime_environment": "staging",
+      "auto_execute_low_risk": false
+    },
+    "ops-mode": {
+      "execution_mode": "apply",
+      "dialogue_profile": "system-maintainer",
+      "ui_mode": "ops-console",
+      "runtime_mode": "ops-fix",
+      "runtime_environment": "staging",
+      "auto_execute_low_risk": false
+    },
+    "dev-mode": {
+      "execution_mode": "apply",
+      "dialogue_profile": "system-maintainer",
+      "ui_mode": "ops-console",
+      "runtime_mode": "feature-dev",
+      "runtime_environment": "dev",
+      "auto_execute_low_risk": false
+    }
+  }
+}

package/docs/interactive-customization/dual-ui-mode-integration-guide.md

@@ -75,7 +75,7 @@ When evaluating runtime policy directly, pass `--ui-mode`:
 
 ```bash
 node scripts/interactive-runtime-policy-evaluate.js \
-  --plan .kiro/reports/interactive-change-plan.generated.json \
+  --plan .sce/reports/interactive-change-plan.generated.json \
   --ui-mode user-app \
   --runtime-mode ops-fix \
   --runtime-environment staging \

package/docs/interactive-customization/moqui-adapter-interface.md

@@ -36,5 +36,5 @@ This document defines the minimal adapter contract used by interactive customiza
 
 ## Artifacts
 
-- Latest execution record: `.kiro/reports/interactive-execution-record.latest.json`
-- Execution ledger (JSONL): `.kiro/reports/interactive-execution-ledger.jsonl`
+- Latest execution record: `.sce/reports/interactive-execution-record.latest.json`
+- Execution ledger (JSONL): `.sce/reports/interactive-execution-ledger.jsonl`

package/docs/interactive-customization/moqui-copilot-integration-guide.md

@@ -97,4 +97,4 @@ node scripts/interactive-intent-build.js \
 2. Context contract gate passes (required fields + payload size + forbidden keys).
 3. Sensitive keys are masked or removed.
 4. Copilot outputs contain `readonly=true`.
-5. Audit event is appended to `.kiro/reports/interactive-copilot-audit.jsonl`.
+5. Audit event is appended to `.sce/reports/interactive-copilot-audit.jsonl`.

package/docs/interactive-customization/moqui-interactive-template-playbook.md

@@ -20,10 +20,10 @@ This playbook defines how to turn validated Moqui interactive customization flow
 
 Primary package for the interactive loop:
 
-- `.kiro/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
-- `.kiro/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
-- `.kiro/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/custom/scene.yaml`
-- `.kiro/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/template.manifest.json`
+- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
+- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
+- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/custom/scene.yaml`
+- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/template.manifest.json`
 
 ## Capability Matrix Mapping
 

package/docs/interactive-customization/phase-acceptance-evidence.md

@@ -90,8 +90,8 @@ Scope:
 
 Evidence:
 
-- `.kiro/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
-- `.kiro/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
+- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene-package.json`
+- `.sce/templates/scene-packages/kse.scene--moqui-interactive-customization-loop--0.1.0/scene.template.yaml`
 - `docs/interactive-customization/moqui-interactive-template-playbook.md`
 - `docs/interactive-customization/adapter-extension-contract.schema.json`
 - `docs/interactive-customization/domain-pack-extension-flow.md`

package/docs/knowledge-management-guide.md

@@ -12,7 +12,7 @@ The Knowledge Management system allows you to build and maintain a personal know
 sce knowledge init
 ```
 
-This creates `.kiro/knowledge/` directory with:
+This creates `.sce/knowledge/` directory with:
 - `patterns/` - Design patterns and solutions
 - `lessons/` - Lessons learned
 - `workflows/` - Custom workflows
@@ -168,7 +168,7 @@ Use consistent, descriptive tags:
 
 ### Custom Templates
 
-Create custom templates in `.kiro/knowledge/.templates/`:
+Create custom templates in `.sce/knowledge/.templates/`:
 
 ```markdown
 ---
@@ -233,7 +233,7 @@ Error: Failed to load index
 **Solution**: Rebuild index:
 ```bash
 # Delete index.json
-rm .kiro/knowledge/index.json
+rm .sce/knowledge/index.json
 
 # Reinitialize
 sce knowledge init
@@ -242,16 +242,16 @@ sce knowledge init
 ## FAQ
 
 **Q: Where is knowledge stored?**  
-A: In `.kiro/knowledge/` directory, organized by type.
+A: In `.sce/knowledge/` directory, organized by type.
 
 **Q: Can I edit entries manually?**  
 A: Yes, they're just Markdown files with YAML frontmatter.
 
 **Q: How do I share knowledge with team?**  
-A: Commit `.kiro/knowledge/` to git (except `.backups/`).
+A: Commit `.sce/knowledge/` to git (except `.backups/`).
 
 **Q: Can I use custom entry types?**  
-A: Yes, create custom templates in `.kiro/knowledge/.templates/`.
+A: Yes, create custom templates in `.sce/knowledge/.templates/`.
 
 **Q: How do I backup my knowledge?**  
 A: Use `sce knowledge export` or commit to git.

package/docs/manual-workflows-guide.md

@@ -37,7 +37,7 @@ Keep your workspace synchronized with task progress across multiple users or too
 ### Prerequisites
 - Project adopted with scene-capability-engine
 - Active spec with tasks.md file
-- Write access to .kiro/specs/ directory
+- Write access to .sce/specs/ directory
 
 ### Step-by-Step Instructions
 
@@ -169,7 +169,7 @@ sce context export my-feature --include-steering --steering-files CORE_PRINCIPLE
 #### 3. Locate Export File
 The export is saved to:
 ```
-.kiro/specs/<spec-name>/context-export.md
+.sce/specs/<spec-name>/context-export.md
 ```
 
 **Time:** ~5 seconds
@@ -227,7 +227,7 @@ Generate AI prompts for specific tasks with relevant context.
 #### 1. Identify Task
 Review tasks.md and note the task ID:
 ```bash
-cat .kiro/specs/<spec-name>/tasks.md
+cat .sce/specs/<spec-name>/tasks.md
 ```
 
 **Example task ID:** `1.2` or `3.1.1`
@@ -257,7 +257,7 @@ sce prompt generate my-feature 1.2 --target vscode
 #### 3. Locate Generated Prompt
 The prompt is saved to:
 ```
-.kiro/specs/<spec-name>/prompts/task-<task-id>.md
+.sce/specs/<spec-name>/prompts/task-<task-id>.md
 ```
 
 **Time:** ~5 seconds

package/docs/moqui-capability-matrix.md

@@ -70,17 +70,17 @@ Use this command during template iteration before full handoff execution:
 sce auto handoff capability-matrix \
   --manifest docs/handoffs/handoff-manifest.json \
   --format markdown \
-  --out .kiro/reports/handoff-capability-matrix.md \
+  --out .sce/reports/handoff-capability-matrix.md \
   --fail-on-gap \
   --json
 ```
 
 `capability-matrix` now checks both capability coverage and semantic completeness (ontology entities/relations + governance business rules/decision logic) by default.
 
-When gaps exist, sce writes remediation queue lines (default `.kiro/auto/moqui-remediation.lines`) that can be fed directly into:
+When gaps exist, sce writes remediation queue lines (default `.sce/auto/moqui-remediation.lines`) that can be fed directly into:
 
 ```bash
-sce auto close-loop-batch .kiro/auto/moqui-remediation.lines --format lines --json
+sce auto close-loop-batch .sce/auto/moqui-remediation.lines --format lines --json
 ```
 
 ## Definition Of Done

package/docs/moqui-standard-rebuild-guide.md

@@ -41,20 +41,20 @@ node scripts/moqui-metadata-extract.js \
 
 `moqui-metadata-extract` now performs multi-source catalog extraction by default:
 - Moqui XML (`entity/service/screen/form/rule/decision`)
-- `scene-package.json` contracts in `.kiro/specs/**/docs/`
+- `scene-package.json` contracts in `.sce/specs/**/docs/`
 - `docs/handoffs/handoff-manifest.json`
 - `docs/handoffs/capability-matrix.md`
 - `docs/handoffs/evidence/**/*.json`
-- `.kiro/recovery/salvage/**/*.json` (if present)
+- `.sce/recovery/salvage/**/*.json` (if present)
 
 ## Step 2: Build Rebuild Bundle
 
 ```bash
 node scripts/moqui-standard-rebuild.js \
   --metadata docs/moqui/metadata-catalog.json \
-  --out .kiro/reports/recovery/moqui-standard-rebuild.json \
-  --markdown-out .kiro/reports/recovery/moqui-standard-rebuild.md \
-  --bundle-out .kiro/reports/recovery/moqui-standard-bundle \
+  --out .sce/reports/recovery/moqui-standard-rebuild.json \
+  --markdown-out .sce/reports/recovery/moqui-standard-rebuild.md \
+  --bundle-out .sce/reports/recovery/moqui-standard-bundle \
   --json
 ```
 
@@ -63,9 +63,9 @@ node scripts/moqui-standard-rebuild.js \
 ```bash
 node scripts/moqui-rebuild-gate.js \
   --metadata docs/moqui/metadata-catalog.json \
-  --out .kiro/reports/recovery/moqui-standard-rebuild.json \
-  --markdown-out .kiro/reports/recovery/moqui-standard-rebuild.md \
-  --bundle-out .kiro/reports/recovery/moqui-standard-bundle
+  --out .sce/reports/recovery/moqui-standard-rebuild.json \
+  --markdown-out .sce/reports/recovery/moqui-standard-rebuild.md \
+  --bundle-out .sce/reports/recovery/moqui-standard-bundle
 ```
 
 Defaults: `ready>=6`, `partial<=0`, `gap<=0`.

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

@@ -46,7 +46,7 @@ Default onboarding and safety baselines:
 
 ## Template Capability Matrix Contract
 
-Use the baseline report as the canonical matrix contract (`.kiro/reports/moqui-template-baseline.json`):
+Use the baseline report as the canonical matrix contract (`.sce/reports/moqui-template-baseline.json`):
 
 | Matrix Dimension | Meaning | Default Gate Target |
 | --- | --- | --- |
@@ -88,7 +88,7 @@ sce scene moqui-baseline --json
 
 # 0.1) CI/release mode: compare against previous baseline and enforce portfolio gate
 sce scene moqui-baseline \
-  --compare-with .kiro/reports/release-evidence/moqui-template-baseline-prev.json \
+  --compare-with .sce/reports/release-evidence/moqui-template-baseline-prev.json \
   --fail-on-portfolio-fail \
   --json
 
@@ -96,14 +96,14 @@ sce scene moqui-baseline \
 sce auto handoff capability-matrix \
   --manifest docs/handoffs/handoff-manifest.json \
   --format markdown \
-  --out .kiro/reports/handoff-capability-matrix.md \
+  --out .sce/reports/handoff-capability-matrix.md \
   --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 \
+  --template-dir .sce/templates/scene-packages \
   --fail-on-gap \
   --json
 
@@ -133,36 +133,36 @@ sce scene package-publish-batch \
 sce scene package-publish-batch \
   --manifest docs/handoffs/handoff-manifest.json \
   --dry-run \
-  --ontology-report-out .kiro/reports/scene-package-ontology-batch.json \
+  --ontology-report-out .sce/reports/scene-package-ontology-batch.json \
   --json
 
 # 4) Validate registry + package gate
-sce scene package-registry --template-dir .kiro/templates/scene-packages --strict --json
-sce scene package-gate-template --out .kiro/templates/scene-package-gate-policy.json --profile three-layer --force --json
-sce scene package-gate --registry .kiro/templates/scene-packages/registry.json --policy .kiro/templates/scene-package-gate-policy.json --strict --json
+sce scene package-registry --template-dir .sce/templates/scene-packages --strict --json
+sce scene package-gate-template --out .sce/templates/scene-package-gate-policy.json --profile three-layer --force --json
+sce scene package-gate --registry .sce/templates/scene-packages/registry.json --policy .sce/templates/scene-package-gate-policy.json --strict --json
 ```
 
 ## Evidence Contract
 
 Required artifacts for each intake batch:
 
-- `.kiro/reports/moqui-template-baseline.json`
-- `.kiro/reports/moqui-template-baseline.md`
-- `.kiro/reports/release-evidence/moqui-template-baseline.json`
-- `.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/release-evidence/moqui-release-summary.json`
-- `.kiro/reports/release-evidence/moqui-release-summary.md`
-- `.kiro/reports/release-evidence/weekly-ops-summary.json`
-- `.kiro/reports/release-evidence/weekly-ops-summary.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`
-- `.kiro/auto/moqui-remediation.lines` (when baseline/coverage gaps exist)
-- `.kiro/templates/scene-packages/registry.json`
+- `.sce/reports/moqui-template-baseline.json`
+- `.sce/reports/moqui-template-baseline.md`
+- `.sce/reports/release-evidence/moqui-template-baseline.json`
+- `.sce/reports/release-evidence/moqui-template-baseline.md`
+- `.sce/reports/release-evidence/moqui-capability-coverage.json`
+- `.sce/reports/release-evidence/moqui-capability-coverage.md`
+- `.sce/reports/release-evidence/moqui-lexicon-audit.json`
+- `.sce/reports/release-evidence/moqui-lexicon-audit.md`
+- `.sce/reports/release-evidence/moqui-release-summary.json`
+- `.sce/reports/release-evidence/moqui-release-summary.md`
+- `.sce/reports/release-evidence/weekly-ops-summary.json`
+- `.sce/reports/release-evidence/weekly-ops-summary.md`
+- `.sce/reports/handoff-capability-matrix.md` (or JSON equivalent from `sce auto handoff capability-matrix`)
+- `.sce/reports/handoff-runs/<session>.json`
+- `.sce/reports/scene-package-ontology-batch.json`
+- `.sce/auto/moqui-remediation.lines` (when baseline/coverage gaps exist)
+- `.sce/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:
@@ -191,10 +191,10 @@ If any area is weak, export remediation queue lines and feed back to close-loop:
 sce scene package-publish-batch \
   --manifest docs/handoffs/handoff-manifest.json \
   --dry-run \
-  --ontology-task-queue-out .kiro/auto/ontology-remediation.lines \
+  --ontology-task-queue-out .sce/auto/ontology-remediation.lines \
   --json
 
-sce auto close-loop-batch .kiro/auto/ontology-remediation.lines --format lines --json
+sce auto close-loop-batch .sce/auto/ontology-remediation.lines --format lines --json
 ```
 
 ## Interactive Customization Template Baseline

package/docs/multi-agent-coordination-guide.md

@@ -33,7 +33,7 @@ All components are **zero overhead in single-agent mode** — they become no-ops
 
 ### 1. Enable Multi-Agent Mode
 
-Create the configuration file `.kiro/config/multi-agent.json`:
+Create the configuration file `.sce/config/multi-agent.json`:
 
 ```json
 {
@@ -104,7 +104,7 @@ await registry.deregister(agentId);
 │          │  Manager │  Store   │            │        │
 ├──────────┴──────────┴──────────┴────────────┴────────┤
 │              MultiAgentConfig                        │
-│         .kiro/config/multi-agent.json                │
+│         .sce/config/multi-agent.json                │
 ├──────────────────────────────────────────────────────┤
 │  v1.44.0: Spec-Level Steering & Context Sync        │
 │  SpecSteering │ SteeringLoader │ ContextSyncManager  │
@@ -121,7 +121,7 @@ await registry.deregister(agentId);
 Manages agent lifecycle with heartbeat-based health monitoring.
 
 **File**: `lib/collab/agent-registry.js`  
-**Storage**: `.kiro/config/agent-registry.json`
+**Storage**: `.sce/config/agent-registry.json`
 
 ```javascript
 const { AgentRegistry } = require('scene-capability-engine/lib/collab');
@@ -154,7 +154,7 @@ await registry.deregister(agentId);
 File-based mutual exclusion for task ownership.
 
 **File**: `lib/lock/task-lock-manager.js`  
-**Lock files**: `.kiro/specs/{specName}/locks/{taskId}.lock`
+**Lock files**: `.sce/specs/{specName}/locks/{taskId}.lock`
 
 ```javascript
 const { TaskLockManager } = require('scene-capability-engine/lib/lock');
@@ -218,7 +218,7 @@ await store.unclaimTask(specName, taskId, agentId, username);
 
 ### Steering File Lock
 
-Write serialization for steering files (`.kiro/steering/*.md`).
+Write serialization for steering files (`.sce/steering/*.md`).
 
 **File**: `lib/lock/steering-file-lock.js`
 
@@ -239,7 +239,7 @@ await steeringLock.releaseLock('CURRENT_CONTEXT.md', lockId);
 
 // Degraded write (when lock cannot be acquired)
 await steeringLock.writePending('CURRENT_CONTEXT.md', content, agentId);
-// Creates: .kiro/steering/CURRENT_CONTEXT.md.pending.{agentId}
+// Creates: .sce/steering/CURRENT_CONTEXT.md.pending.{agentId}
 ```
 
 ### Merge Coordinator
@@ -274,7 +274,7 @@ await merger.cleanupBranch(branchName);
 When `coordinator: true` in config, provides intelligent task assignment based on dependency analysis.
 
 **File**: `lib/collab/coordinator.js`  
-**Log**: `.kiro/config/coordination-log.json`
+**Log**: `.sce/config/coordination-log.json`
 
 ```javascript
 const { Coordinator } = require('scene-capability-engine/lib/collab');
@@ -300,7 +300,7 @@ const { specs, agents } = await coordinator.getProgress();
 Per-Spec `steering.md` providing independent constraints, notes, and decisions for each Spec. Eliminates cross-agent write conflicts on global steering files.
 
 **File**: `lib/steering/spec-steering.js`  
-**Storage**: `.kiro/specs/{spec-name}/steering.md`
+**Storage**: `.sce/specs/{spec-name}/steering.md`
 
 ```javascript
 const { SpecSteering } = require('scene-capability-engine/lib/steering');
@@ -377,7 +377,7 @@ await syncManager.writeContext(newContext);
 State machine managing Spec lifecycle transitions with auto-completion detection.
 
 **File**: `lib/collab/spec-lifecycle-manager.js`  
-**Storage**: `.kiro/specs/{spec-name}/lifecycle.json`
+**Storage**: `.sce/specs/{spec-name}/lifecycle.json`
 
 Valid transitions: `planned → assigned → in-progress → completed → released`
 
@@ -499,7 +499,7 @@ All components check `MultiAgentConfig.isEnabled()` before doing anything:
 
 ## Configuration Reference
 
-### `.kiro/config/multi-agent.json`
+### `.sce/config/multi-agent.json`
 
 ```json
 {
@@ -514,15 +514,15 @@ All components check `MultiAgentConfig.isEnabled()` before doing anything:
 
 | File | Purpose |
 |------|---------|
-| `.kiro/config/multi-agent.json` | Multi-agent configuration |
-| `.kiro/config/agent-registry.json` | Active agent registry |
-| `.kiro/config/coordination-log.json` | Coordinator assignment log |
-| `.kiro/specs/{spec}/locks/{taskId}.lock` | Task lock files |
-| `.kiro/specs/{spec}/tasks.md.lock` | tasks.md file lock |
-| `.kiro/specs/{spec}/steering.md` | Spec-level steering (L4) |
-| `.kiro/specs/{spec}/lifecycle.json` | Spec lifecycle state |
-| `.kiro/steering/{file}.lock` | Steering file locks |
-| `.kiro/steering/{file}.pending.{agentId}` | Pending steering writes |
+| `.sce/config/multi-agent.json` | Multi-agent configuration |
+| `.sce/config/agent-registry.json` | Active agent registry |
+| `.sce/config/coordination-log.json` | Coordinator assignment log |
+| `.sce/specs/{spec}/locks/{taskId}.lock` | Task lock files |
+| `.sce/specs/{spec}/tasks.md.lock` | tasks.md file lock |
+| `.sce/specs/{spec}/steering.md` | Spec-level steering (L4) |
+| `.sce/specs/{spec}/lifecycle.json` | Spec lifecycle state |
+| `.sce/steering/{file}.lock` | Steering file locks |
+| `.sce/steering/{file}.pending.{agentId}` | Pending steering writes |
 
 ---