T-V7U3-task-mutators-scope-docs-generate

Status: closed/obsoleted · Impact: low · Complexity: small

Goal

The task-state mutators (ensure_ready_mutate.ts, start_task.ts) invoke sdlc docs generate as a side effect. In a consumer project that does not own the SDLC plugin’s documentation corpus, that side-effect resolves the wrong content root and sweeps the plugin’s own template docs into the consumer’s task-state commit on main. The fix is to make the docs-generate side-effect resolve the consuming project’s content root (or make it opt-in per project) so the mutators never write foreign generated docs into a consumer’s commits.

From T-VQ1N-ci-quality-checks in <git@github.com:sksizer/markdown-contract.git>: The task-lifecycle mutators (ensure_ready_mutate.ts, start_task.ts) run sdlc docs generate as a side effect and committed SDLC-plugin template docs (docs/index.md, docs/glossary.md, docs/references.md, titled ”# SDLC”, linking [PR-0001-sdlc](/planning/products/sdlc/) / the architecture map, today [D-VSLI-distributed-work-runner-architecture](/planning/decisions/distributed-work-runner-architecture/)) into markdown-contract on main — wrong corpus, broken wikilinks to entities this project does not own. Required an extra git rm commit to keep the PR clean — the docs-generate side-effect in the task-state mutators should resolve the consuming project’s content root (or be opt-in per project) so it does not sweep foreign generated docs into task-state commits.

See also (same project-root / content-root resolution family, for the receiver to fold or distinguish at definition time): T-44OO-plugin-scripts-self-discover-project-root (plugin scripts self-discover project root from cwd) and T-PA51-task-state-commits-regen-site-page (task-state commits and the derived site page, in the plugin’s own repo).