From 6b72f954a78bfcb5993bf8c1c7e8ed5e8822146c Mon Sep 17 00:00:00 2001
From: Evan Alferez <eoalferez@gmail.com>
Date: Tue, 23 Jun 2026 08:43:55 +0900
Subject: [PATCH] fix(tests): carry render_runtime into e2e edit_decisions
 fixture (#69)

tests/qa/test_08_end_to_end.py runs at module import, so pytest fails
collection with CheckpointValidationError: the Stage 5 edit_decisions
fixture omits render_runtime, which edit_decisions.schema.json lists as
required. Per AGENT_GUIDE the runtime is locked at proposal and carried
through edit unchanged, so the fixture now sources it from the same
proposal_packet["production_plan"]["render_runtime"] ("remotion")
instead of hardcoding an unrelated value, keeping the fixture internally
consistent with the proposal it builds on.
---
 tests/qa/test_08_end_to_end.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/qa/test_08_end_to_end.py b/tests/qa/test_08_end_to_end.py
index 051950da..cbbee2da 100644
--- a/tests/qa/test_08_end_to_end.py
+++ b/tests/qa/test_08_end_to_end.py
@@ -424,6 +424,7 @@ for i, scene in enumerate(scene_plan["scenes"]):
 
 edit_decisions = {
     "version": "1.0",
+    "render_runtime": proposal_packet["production_plan"]["render_runtime"],
     "cuts": [
         {
             "id": f"cut_{scene['id']}",