ISSUES CLOSED: #9449

@@ -0,0 +52,4 @@
+    And the apply JSON data validation should contain field "type_check"
+
+  Scenario: apply JSON data lifecycle field contains required sub-fields
+    When I invoke plan apply with --format json and a mocked service

@@ -0,0 +185,4 @@
+
+    # Verify validation sub-fields
+    validation = data.get("validation", {})
+    required_validation = {"test", "lint", "type_check"}

@@ -0,0 +52,4 @@
+    And the apply JSON data validation should contain field "type_check"
+
+  Scenario: apply JSON data lifecycle field contains required sub-fields
+    When I invoke plan apply with --format json and a mocked service

@@ -0,0 +92,4 @@
+    return mock_service
+
+
+def _invoke_apply_json(plan: LifecyclePlan | None = None) -> dict:  # type: ignore[type-arg]

@@ -0,0 +185,4 @@
+
+    # Verify validation sub-fields
+    validation = data.get("validation", {})
+    required_validation = {"test", "lint", "type_check"}

@@ -55,3 +55,4 @@
 )
+from cleveragents.domain.models.core.plan import Plan as LifecyclePlan
 from cleveragents.domain.models.core.plan import PlanPhase, ProcessingState
 from cleveragents.infrastructure.sandbox.git_worktree import (

@@ -0,0 +52,4 @@
+    And the apply JSON data validation should contain field "type_check"
+
+  Scenario: apply JSON data lifecycle field contains required sub-fields
+    When I invoke plan apply with --format json and a mocked service

@@ -0,0 +92,4 @@
+    return mock_service
+
+
+def _invoke_apply_json(plan: LifecyclePlan | None = None) -> dict:  # type: ignore[type-arg]

@@ -0,0 +185,4 @@
+
+    # Verify validation sub-fields
+    validation = data.get("validation", {})
+    required_validation = {"test", "lint", "type_check"}

@@ -480,0 +541,4 @@
+    # Derive from validation_summary when available; fall back to "passed".
+    validation_summary = plan.validation_summary or {}
+    validation: dict[str, object] = {
+        "test": (

@@ -480,0 +605,4 @@
+    }
+
+    # ── Timing ────────────────────────────────────────────────────────────────
+    timing: dict[str, object] = {"applied_at": applied_at}

@@ -480,0 +609,4 @@
+
+    # ── Data payload ──────────────────────────────────────────────────────────
+    data: dict[str, object] = {
+        "artifacts": artifacts,

@@ -0,0 +34,4 @@
+    Then the apply JSON envelope messages should be a non-empty list
+
+  # ── Data field structure ─────────────────────────────────────────────────
+

@@ -0,0 +159,4 @@
+        "lifecycle",
+    }
+    missing = required_data - set(data.keys())
+    if missing:

@@ -480,0 +525,4 @@
+            "messages": ["Changes applied"],
+        }
+
+    # ── Artifacts ─────────────────────────────────────────────────────────────

@@ -480,0 +568,4 @@
+            "warnings": lint_summary.get("warnings", 0),
+        },
+        "type_check": {
+            "status": "passed" if type_check_summary.get("type_check_passed", True) else "failed",

@@ -480,0 +572,4 @@
+            "errors": type_check_summary.get("errors", 0),
+        },
+        "duration_s": float(
+            validation_summary.get("duration_s") or validation_summary.get("duration", 0)

@@ -0,0 +4,4 @@
+  So that tooling and scripts can reliably parse the apply output
+
+  Background:
+    Given a plan CLI runner for the apply JSON envelope test

@@ -0,0 +70,4 @@
+        project_links=[ProjectLink(project_name="local/my-project")],
+        strategy_actor="openai/gpt-4",
+        execution_actor="openai/gpt-4",
+        created_by="test-user",