Distillation

Date: Sep 16, 2026

• 🔴 [requested-validation] (22:47) User requires always running the repository’s full validation path, including the gateway pretest bundle and aggregate Vitest suite, before classifying a candidate.
• 🔴 [enforced-workflow] (22:47) User requires aggregate validation first; a completed aggregate run is conclusive even when it has failures, while all disjoint fallback shards should run only if the aggregate is genuinely inconclusive due to timeout, worker crash, or missing final totals.
• 🔴 (22:47) User requires exact validation reporting: exit codes, durations, test-file/test totals, failures, relevant environmental warnings, bundle artifacts, and hashes; production-build warnings must be distinguished from test failures.
• 🔴 (22:47) User requires Vitest diagnostic runs always to use --printConsoleTrace, because console output may be truncated or detached from asynchronous failures and stack traces identify the originating source path.
• 🔴 [enforced-workflow] (22:47) User requires confirming that no workspace-owned workers remain before fallback shards, cleaning up only workspace-owned workers, and verifying cleanup.
• 🔴 (22:47) User requires previously completed validation results to be reused after restart only when every frozen identity, hash, artifact, and state check still matches; otherwise the results must be invalidated.
• 🟡 (22:47) Context recall returned 90 results and displayed the top 15, with a score range of 0.065–0.046.
• 🟡 (22:47) Recall reported recurring tool failures: edit → other:could-not-find-oldstring 113 times across 45 sessions; plan_exit → other:the-user-dismissed-this 48 times across 39 sessions; read → not_found 40 times across 34 sessions; webfetch → other:statuscode-non-xx-status 69 times across 22 sessions; and bash → aborted 20 times across 16 sessions.