Context
packages/loopover-miner/scripts/generate-env-reference.mjs's DEFAULT_SOURCE_ROOTS (lines 9-12) only scans packages/loopover-miner/{bin,lib,scripts} — it never scans packages/loopover-engine/src/miner/**, where the coding-agent driver actually lives. Four env vars are read there but absent from the generated packages/loopover-miner/docs/env-reference.md:
MINER_CODING_AGENT_PAUSED — the coding-agent kill-switch, read at packages/loopover-engine/src/miner/coding-agent-mode.ts:26.MINER_CODING_AGENT_TIMEOUT_MS — packages/loopover-engine/src/miner/driver-factory.ts:50-51,88.MINER_CODING_AGENT_CLAUDE_MODEL — driver-factory.ts:50,215.MINER_CODING_AGENT_CODEX_MODEL — driver-factory.ts:51,217.
MINER_CODING_AGENT_PROVIDER (the same feature family's provider-selection var, presumably read from a file already inside the scanned roots) already appears in the generated doc — these four sibling vars from the same family are silently missing because the file that reads them (packages/loopover-engine/src/miner/*.ts) is outside the generator's scan scope.
Requirements
- Add
packages/loopover-engine/src/miner to DEFAULT_SOURCE_ROOTS in packages/loopover-miner/scripts/generate-env-reference.mjs.
- Regenerate
packages/loopover-miner/docs/env-reference.md (npm run miner:env-reference or the repo's equivalent script name — confirm the exact script) and commit the result in the same PR — a stale generated file fails CI.
- Do not manually hand-edit the generated file — it must come from running the generator.
- Verify the newly-scanned root doesn't pull in unrelated
packages/loopover-engine env vars that belong to a different generator/doc (scope the addition narrowly to src/miner specifically, not the whole package, unless the generator's own logic already filters correctly).
Deliverables
Test Coverage Requirements
99%+ Codecov patch coverage on every changed line and branch, plus the regression test above.
Expected Outcome
All four coding-agent driver env vars are documented in the generated miner env reference, matching what the code actually reads, alongside the already-documented MINER_CODING_AGENT_PROVIDER.
Links & Resources
packages/loopover-miner/scripts/generate-env-reference.mjs:9-12 (DEFAULT_SOURCE_ROOTS). packages/loopover-engine/src/miner/coding-agent-mode.ts:26, driver-factory.ts:50-51,88,215,217 — the actual read sites.
Context
packages/loopover-miner/scripts/generate-env-reference.mjs'sDEFAULT_SOURCE_ROOTS(lines 9-12) only scanspackages/loopover-miner/{bin,lib,scripts}— it never scanspackages/loopover-engine/src/miner/**, where the coding-agent driver actually lives. Four env vars are read there but absent from the generatedpackages/loopover-miner/docs/env-reference.md:MINER_CODING_AGENT_PAUSED— the coding-agent kill-switch, read atpackages/loopover-engine/src/miner/coding-agent-mode.ts:26.MINER_CODING_AGENT_TIMEOUT_MS—packages/loopover-engine/src/miner/driver-factory.ts:50-51,88.MINER_CODING_AGENT_CLAUDE_MODEL—driver-factory.ts:50,215.MINER_CODING_AGENT_CODEX_MODEL—driver-factory.ts:51,217.MINER_CODING_AGENT_PROVIDER(the same feature family's provider-selection var, presumably read from a file already inside the scanned roots) already appears in the generated doc — these four sibling vars from the same family are silently missing because the file that reads them (packages/loopover-engine/src/miner/*.ts) is outside the generator's scan scope.Requirements
packages/loopover-engine/src/minertoDEFAULT_SOURCE_ROOTSinpackages/loopover-miner/scripts/generate-env-reference.mjs.packages/loopover-miner/docs/env-reference.md(npm run miner:env-referenceor the repo's equivalent script name — confirm the exact script) and commit the result in the same PR — a stale generated file fails CI.packages/loopover-engineenv vars that belong to a different generator/doc (scope the addition narrowly tosrc/minerspecifically, not the whole package, unless the generator's own logic already filters correctly).Deliverables
DEFAULT_SOURCE_ROOTSincludespackages/loopover-engine/src/minerenv-reference.mdincludes all fourMINER_CODING_AGENT_*varsTest Coverage Requirements
99%+ Codecov patch coverage on every changed line and branch, plus the regression test above.
Expected Outcome
All four coding-agent driver env vars are documented in the generated miner env reference, matching what the code actually reads, alongside the already-documented
MINER_CODING_AGENT_PROVIDER.Links & Resources
packages/loopover-miner/scripts/generate-env-reference.mjs:9-12(DEFAULT_SOURCE_ROOTS).packages/loopover-engine/src/miner/coding-agent-mode.ts:26,driver-factory.ts:50-51,88,215,217— the actual read sites.