From 54a1842b90e45e5247fd7cc391f50c8b237a2854 Mon Sep 17 00:00:00 2001 From: Svrnty Date: Wed, 17 Jun 2026 02:20:33 -0400 Subject: [PATCH] Refresh CTO target sandbox gate evidence --- docs/LEGACY-INGEST.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/LEGACY-INGEST.md b/docs/LEGACY-INGEST.md index e99ced6..143e6f0 100644 --- a/docs/LEGACY-INGEST.md +++ b/docs/LEGACY-INGEST.md @@ -89,11 +89,12 @@ The useful idea is an explicitly owned, noncritical, disposable target repositor Current evidence: -- current path is not a Git repository. -- `python3 tools/validate_cto_stage5_target_sandbox_child.py` passes in the target. -- `python3 tools/validate_cto_child.py` passes in CTO while the root path exists. -- `tools/validate_cto_child.py` hard-codes the target path and admission record fields. -- `.case/tasks/active/*.task.json` still contains `active` and `implementing` task states. +- 2026-06-17 refresh: current path is not a Git repository. +- 2026-06-17 refresh: `python3 tools/validate_cto_stage5_target_sandbox_child.py` passes in the target. +- 2026-06-17 refresh: `python3 tools/validate_cto_child.py` passes in CTO while the root path exists. +- 2026-06-17 refresh: `tools/validate_cto_child.py` hard-codes the target path and admission record fields. +- 2026-06-17 refresh: `.case/tasks/active/*.task.json` contains six active task records; two have `agents.implementer.status` set to `running` and no `completed` timestamp. +- 2026-06-17 refresh: the target task records still use active or implementing states, so they are not archive-stable closure evidence. Movement gate: