From d5f7a61c0fed776252f3e1de18a8d1130f3f8808 Mon Sep 17 00:00:00 2001 From: Julian Lechner Date: Wed, 16 Sep 2026 19:18:24 +0200 Subject: [PATCH] chore(workflow): replace blanket validation with targeted checks --- AI-Instructions.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/AI-Instructions.md b/AI-Instructions.md index 6265c96..d7dfe5a 100644 --- a/AI-Instructions.md +++ b/AI-Instructions.md @@ -33,9 +33,10 @@ Write all repository content, generated instructions, scripts, prompts, document ## Workflow -- Run `scripts/build.ps1` to validate every project change before completion. -- Rebuild generated output after semantic changes. -- Run `scripts/doctor.ps1` when changes affect generated output, installation, client configuration, hooks, or environment validation. +- Choose the smallest sufficient verification based on the change's behavior, affected consumers, risk, and remaining uncertainty. Inspection may suffice for low-risk changes; full builds, test suites, and independent reviews are not automatic. +- Run `scripts/build.ps1 -Summary` to regenerate packages when shared definitions, adapters, or generation logic change. This generates configuration packages; it does not require building applications that use them. +- Run `scripts/doctor.ps1 -Summary` when installation, client configuration, hooks, or environment changes need its checks. Changes to instruction wording alone do not require it. +- Run focused script tests when script behavior changes. Broaden or repeat checks only when failures, affected dependencies, or unresolved risks justify it. - Preserve backward compatibility where practical. - Keep changes focused on the requested configuration behavior.