T-G6T3-baseline-capture-runs-worktree-init

Status: closed/superseded · Impact: medium · Complexity: small

Goal

/sdlc:task-work Step 3a captures the quality baseline from the main checkout against origin/main, before Step 4 runs worktree_init. In projects whose checks need installed dependencies (e.g. npm run test / npm run typecheck), the main checkout has no node_modules, so the baseline run records exit 127 (command not found) and meaningless command-echo “findings” instead of real ones — a misleading baseline that Step 7’s drift diff then subtracts against. Baseline capture should run against a dependency-installed tree (run worktree_init first, or capture from the initialised worktree) so the pre-existing-drift baseline reflects real check output.

From T-VQ1N-ci-quality-checks in <git@github.com:sksizer/markdown-contract.git>: The quality baseline (Step 3a) is captured from the main checkout, where node_modules is not installed, so both verbs recorded exit 127 (command not found) and meaningless npm-echo “findings” instead of real ones — a misleading baseline. Baseline capture should run worktree_init first (or capture from a deps-installed tree) so the pre-existing-drift baseline reflects real check output.

See also (related project-root / baseline-dir resolution work, for the receiver to fold or distinguish at definition time): T-44OO-plugin-scripts-self-discover-project-root — note that is about where the baseline file is written (project-root discovery), whereas this gap is about the checks recording exit 127 because dependencies are not installed when the baseline is captured.