Differences

This shows you the differences between two versions of the page.

--- fxdemo:05-part:05-development-environment:05-8-environment-verification:start [2026/08/08 19:30] – created owen
+++ fxdemo:05-part:05-development-environment:05-8-environment-verification:start [2026/08/08 19:30] (current) – owen
@@ Line 7: / Line 7: @@
 The team should provide a repeatable way to verify the development environment before coding begins. The ''checkPrerequisites.sh'' script should check required tools, versions, commands, paths, environment variables, and basic runtime assumptions.
-Environment [[dido:99_annexes:annex-b-terms-and-definitions:v:verification|Verification]] should fail clearly when a required tool is missing, misconfigured, or unsupported. The script should explain what failed, why it matters, and what the developer should check next. It should return a non-zero exit code when the environment does not satisfy the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].
+Environment verification should fail clearly when a required tool is missing, misconfigured, or unsupported. The script should explain what failed, why it matters, and what the developer should check next. It should return a non-zero exit code when the environment does not satisfy the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].
 The Verification process should distinguish required tools from optional tools. Missing required tools should block Baseline execution. Missing optional tools should produce warnings rather than failures unless the developer requested a workflow that depends on them.