From 05b01676aaa5f7c90a561e153a41c221390ae5e7 Mon Sep 17 00:00:00 2001 From: Taras Mankovski Date: Sun, 8 Nov 2026 08:59:12 -0500 Subject: [PATCH] =?UTF-8?q?=F0=9F=A7=AA=20Check=20the=20approved=20Plan's?= =?UTF-8?q?=20nonexecution=20in=20its=20own=20journey?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The approved-Plan test and the nonexecution test ran the same child with the same scenario and answer. The nonexecution guard now follows the first journey's Execution, and the duplicate journey is removed. Refs #1186 Co-Authored-By: Claude Opus 5.5 --- .../tests/document-suites/plan/Plan.test.md | 30 +++---------------- 1 file changed, 4 insertions(+), 26 deletions(-) diff --git a/packages/cli/tests/document-suites/plan/Plan.test.md b/packages/cli/tests/document-suites/plan/Plan.test.md index 30c39938f..2b8d62b71 100644 --- a/packages/cli/tests/document-suites/plan/Plan.test.md +++ b/packages/cli/tests/document-suites/plan/Plan.test.md @@ -41,33 +41,11 @@ all runtime state under that opaque identity. - - -## An approved Plan is source, not something that ran - -The program this scenario approves names a file. Approving it hands the source -back; it does not run it. The file is therefore the evidence: a child that -executed what it was given would have created it. - - - - - - - - - - - - - - - - -The source arrived, and the file it names is nowhere: the child ran in this -working directory, so a child that executed what it was given would have written -it here. +Approving the program hands its source back; it does not run it. The source +names a file, `planned.txt`, and once the child has finished that file is +nowhere: the child ran in this working directory, so a child that executed what +it was given would have written it here.