validatelisted

Use automatic scope by default. Read the shared [repocli reference](../../references/repocli.md) for direct CLI inspection, installation and analysis boundaries. Do not select or pass `TEST_FILES` / `LINT_FILES` yourself unless the user explicitly requests an override. ```bash <PLUGIN_ROOT>/scripts/python <PLUGIN_ROOT>/scripts/run_validate.py <repo-or-component> <PLUGIN_ROOT>/scripts/python <PLUGIN_ROOT>/scripts/run_tests.py <repo-or-component> <PLUGIN_ROOT>/scripts/python <PLUGIN_ROOT>/scripts/run_lint.py <repo-or-component> ``` Normalization runs before one shared repocli analysis. The workflow selects affected files, including dependent tests in other Components, and adapts paths to project Make contracts. Unavailable, incompatible or uncertain analysis falls back to full checks with a Board reason. An actual check failure stays a failure. Use `--full` when the user or project gate requires full validation; do not repeat a full suite solely to replace a focused run's missing stamp. Focused results do not authorize a later bare commit. Validation consists of multiple checks. Run `make fix` normalization first, then read-only lint and test checks may run concurrently against the same stable content. Running one check or a focused selection is partial validation and must not be presented as complete Component validation. The scripts resolve the repo and affected Components, prepare dependencies, run canonical project targets, and update each check's `.devloop` validation