feat(v0.12): DKF120-T03 Execution Capsules validation

.development-kit/workspace.json

@@ -0,0 +1,24 @@
+{
+  "schemaVersion": 1,
+  "targets": {
+    "dkf-framework": {
+      "path": ".",
+      "kind": "development-framework",
+      "dependencies": [],
+      "commands": {
+        "test": "npm run release:validate",
+        "test:orchestration": "npm run orchestration-core:validate"
+      },
+      "capabilities": [
+        "dkf-control-plane",
+        "node-runtime",
+        "release-validation"
+      ],
+      "verification": [
+        "test",
+        "test:orchestration"
+      ],
+      "adapter": null
+    }
+  }
+}

.github/workflows/ci.yml

@@ -83,6 +83,21 @@ jobs:
           npm run token-efficiency:test
           npm run token:audit:check
 
+      - name: Run Scale/Context Phase 0-1 baseline
+        run: node scripts/phase01-scale-context-baseline.mjs
+
+      - name: Validate Scale/Context v0.12 Phase 2 PLAN
+        run: node scripts/phase02-scale-context-plan-validate.mjs
+
+      - name: Validate v0.12 Cost Observatory increment
+        run: npm run cost-observatory:test
+
+      - name: Validate v0.12 Workspace Target Engine increment
+        run: npm run workspace-targets:test
+
+      - name: Validate v0.12 Execution Capsules & Context Cache increment
+        run: npm run execution-capsule:test
+
       - name: Validate Design Authority governance
         run: npm run design-authority:validate
 

.gitignore

@@ -30,5 +30,6 @@ desktop.ini
 .development-kit/runs/
 .development-kit/decisions/
 .development-kit/secrets/
+.development-kit/telemetry/
 freebuff-chat-*.md
 

docs/03-reference/scripts/phase01-scale-context-baseline.md

@@ -0,0 +1,51 @@
+# phase01-scale-context-baseline.mjs
+
+## Purpose
+
+`scripts/phase01-scale-context-baseline.mjs` is an analysis-only baseline runner for the Development Kit Scale, Context & Iteration initiative.
+
+It measures the current framework before implementation changes are made. The script does not modify DKF production runtime behaviour, change package versions, publish releases, or mutate repository state outside temporary test fixtures.
+
+## What it measures
+
+The runner records:
+
+- repository, test, and canonical instruction-file inventory;
+- the existing deterministic token/context audit;
+- representative single-package context packaging;
+- representative multi-package context packaging;
+- representative calculation-heavy context packaging;
+- Autopilot state-file growth across 26 immutable revisions;
+- current observability gaps for provider token usage, repository reads/scans, agent invocations, and host tool calls.
+
+## Representative fixtures
+
+The fixtures are synthetic and deterministic. They exercise the existing DKF runtime APIs rather than claiming to reproduce provider billing or a specific production repository exactly.
+
+The multi-package fixture contains web, mobile, shared, calculation, and database-style paths. The calculation-heavy fixture establishes a baseline before domain/numerical gate profiles exist.
+
+## Usage
+
+Print JSON to standard output:
+
+```bash
+node scripts/phase01-scale-context-baseline.mjs
+```
+
+Optionally persist the JSON output:
+
+```bash
+node scripts/phase01-scale-context-baseline.mjs --out=path/to/baseline.json
+```
+
+## Measurement rules
+
+The runner reuses `scripts/token-audit.mjs` and the existing `runtime/orchestration/token-efficiency.mjs` estimator.
+
+Estimated token values therefore remain deterministic `ceil(characters / 4)` approximations and must not be represented as provider billing-token counts.
+
+Metrics that the current runtime cannot observe are emitted as unavailable with a reason instead of being estimated or fabricated.
+
+## Scope
+
+This script belongs to Phase 0/1 evidence gathering only. Later Cost Observatory work may extend or replace parts of this runner after the baseline has been preserved.

docs/03-reference/scripts/phase02-scale-context-plan-validate.md

@@ -0,0 +1,42 @@
+# phase02-scale-context-plan-validate.mjs
+
+## Purpose
+
+`scripts/phase02-scale-context-plan-validate.mjs` validates the machine-readable Development Kit v0.12.0 Scale, Context & Iteration PLAN using the existing deterministic `runtime/orchestration/plan-validator.mjs`.
+
+It is a Phase 2 planning validator. It does not implement v0.12 runtime functionality.
+
+## Authoritative PLAN model
+
+```text
+docs/04-architecture/dkf-scale-context-iteration-v0.12-plan-model.json
+```
+
+## Validation performed
+
+The script checks:
+
+- declared task count;
+- dependency references;
+- dependency cycles;
+- declared dependency graph versus computed graph;
+- required logical resource ownership;
+- duplicate resource ownership;
+- acceptance-criterion coverage;
+- configuration dependency validity.
+
+The acceptance-criterion authority comes from the reconciled v0.12 specification.
+
+## Usage
+
+```bash
+node scripts/phase02-scale-context-plan-validate.mjs
+```
+
+The command prints the complete deterministic validation report as JSON and exits non-zero when the PLAN is invalid.
+
+## Scope
+
+This validator intentionally reuses the existing DKF PLAN validation engine instead of creating a second planning model.
+
+A green result proves structural PLAN consistency. It does not replace specification review, architecture review, implementation verification, or Product Owner release approval.

docs/03-reference/scripts/phase03-cost-observatory-contract.md

@@ -0,0 +1,47 @@
+# phase03-cost-observatory-contract.mjs
+
+## Purpose
+
+`scripts/phase03-cost-observatory-contract.mjs` creates or reuses the Development Contract for **DKF120-T01 — Cost Observatory**.
+
+The contract is normal DKF runtime state and is persisted under:
+
+```text
+.development-kit/contracts/INC-DKF120-T01/
+```
+
+That directory remains git-ignored. The script itself is committed so contract construction is reproducible from the authoritative v0.12 sources.
+
+## Authoritative sources
+
+The contract binds:
+
+- the v0.12 Scale, Context & Iteration specification;
+- the v0.12 technical design;
+- the validated v0.12 implementation PLAN;
+- the Phase 0/1 baseline evidence.
+
+Whole-file fingerprints remain authoritative even when the contract requests selected sections for context delivery.
+
+## Acceptance criteria
+
+The T01 contract owns:
+
+- `DKF-120-AC-001`
+- `DKF-120-AC-002`
+- `DKF-120-AC-003`
+- `DKF-120-AC-033`
+
+## Usage
+
+```bash
+node scripts/phase03-cost-observatory-contract.mjs
+```
+
+The script validates the resulting contract and immediately verifies that it is not stale.
+
+If an existing contract has become stale, normal DKF stale-contract handling applies; the script does not silently overwrite it.
+
+## Boundary
+
+This script authorises only T01 Cost Observatory work. It does not authorise T02 or later v0.12 increments.

docs/03-reference/scripts/phase04-workspace-target-engine-contract.md

@@ -0,0 +1,60 @@
+# phase04-workspace-target-engine-contract.mjs
+
+## Purpose
+
+`scripts/phase04-workspace-target-engine-contract.mjs` creates or reuses the Development Contract for **DKF120-T02 — Workspace Target Engine**.
+
+The contract is persisted through the normal DKF runtime contract store under:
+
+```text
+.development-kit/contracts/INC-DKF120-T02/
+```
+
+That runtime directory remains git-ignored.
+
+## Bootstrap note
+
+T02 introduces Workspace Target Engine support itself.
+
+Therefore the T02 Development Contract is created **without** a workspace target binding. This is intentional bootstrap behaviour: target binding cannot be mandatory for the increment that first creates the target engine.
+
+After T02 acceptance, target-aware Development Contracts may bind:
+
+- primary target;
+- affected targets;
+- verification targets;
+- the exact workspace-registry fingerprint.
+
+A later change to that registry then makes the target-aware contract stale.
+
+## Authoritative sources
+
+The contract binds:
+
+- the v0.12 Scale, Context & Iteration specification;
+- the v0.12 technical design;
+- the validated v0.12 implementation PLAN;
+- accepted T01 evidence;
+- the Phase 0/1 multi-package baseline.
+
+## Acceptance criteria
+
+The T02 contract owns:
+
+- `DKF-120-AC-004`
+- `DKF-120-AC-005`
+- `DKF-120-AC-006`
+- `DKF-120-AC-007`
+- `DKF-120-AC-039`
+
+## Usage
+
+```bash
+node scripts/phase04-workspace-target-engine-contract.mjs
+```
+
+The script validates the contract, confirms its derived gates, and verifies that it is not stale.
+
+## Boundary
+
+This script authorises only T02 Workspace Target Engine work. It does not authorise T03 or later v0.12 increments.

docs/03-reference/scripts/phase05-execution-capsule-contract.md

@@ -0,0 +1,77 @@
+# phase05-execution-capsule-contract.mjs
+
+## Purpose
+
+`scripts/phase05-execution-capsule-contract.mjs` creates or reuses the Development Contract for **DKF120-T03 — Execution Capsules & Context Cache**.
+
+The contract is persisted through the normal DKF contract store under:
+
+```text
+.development-kit/contracts/INC-DKF120-T03/
+```
+
+The runtime contract directory remains git-ignored.
+
+## Target binding
+
+T03 is the first Scale, Context & Iteration increment that is created after the Workspace Target Engine is available.
+
+Its Development Contract therefore binds:
+
+```text
+primary:      dkf-framework
+affected:     dkf-framework
+verification: dkf-framework
+```
+
+and stores the exact fingerprint of:
+
+```text
+.development-kit/workspace.json
+```
+
+If that registry changes after contract creation, the T03 contract becomes stale.
+
+## Risk and derived gates
+
+The validated PLAN classifies T03 as **High risk** because an incorrect cache hit could feed stale repository context into implementation or independent verification.
+
+Under the current DKF gate selector, risk level 3 derives:
+
+- specification verification;
+- tests;
+- code review;
+- architecture review;
+- security review;
+- security control-domain review.
+
+No human consequential-action approval is derived at risk level 3.
+
+## Acceptance criteria
+
+The T03 contract owns:
+
+- `DKF-120-AC-008`
+- `DKF-120-AC-009`
+- `DKF-120-AC-010`
+- `DKF-120-AC-011`
+- `DKF-120-AC-035`
+
+## Usage
+
+```bash
+node scripts/phase05-execution-capsule-contract.mjs
+```
+
+The script validates:
+
+- the Development Contract;
+- target binding;
+- derived gates;
+- contract staleness.
+
+## Boundary
+
+This script authorises only T03.
+
+It does not authorise State Engine V2, Lifecycle Instances, discovery/re-entry, Gate Profiles, the Verification Extension SDK, Complexity Delta Guard, Control Center v0.12 integration, release publication, or a package-version change.