docs(miner): regenerate env-reference.md for GITTENSORY_MINER_KILL_SWITCH

[JSONbored]

Summary

`npm run miner:env-reference:check` has been failing on `main` since #5198/#5500 added the `env.GITTENSORY_MINER_KILL_SWITCH` read in `lib/config-precedence.js` (`config-precedence.js:14`) without regenerating this generated doc. Found while running the full local gate for an unrelated fix and confirmed the drift is real and still present at current `main`.

Ran `npm run miner:env-reference` and committed the regenerated `packages/gittensory-miner/docs/env-reference.md` (single line added, matching the file's own "Generated by ... Do not edit manually" contract).

Validation

• `npm run miner:env-reference:check` — clean after regeneration
• Confirmed `GITTENSORY_MINER_KILL_SWITCH` is a genuine, currently-live read (not dead code)

Mechanical, zero-risk generated-artifact fix — no behavior change.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-12 23:59:01 UTC}

1 file · 1 AI reviewer · 2 blockers · readiness 93/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This is a mechanical regeneration of the generated env-reference.md doc, adding a single alphabetically-correct row for GITTENSORY_MINER_KILL_SWITCH (first referenced in lib/config-precedence.js, default "") to fix drift flagged by the miner:env-reference:check script. The row's shape, formatting, and alphabetical placement match the generator's documented output format (renderMinerEnvReferenceMarkdown in generate-env-reference.mjs) and the surrounding table entries. This closes a real, reproducible check failure with a single-line, zero-behavior-change diff, exactly matching the stated intent.

Blockers

• PR description: you need to close or clearly link an eligible open issue for this contributor PR; add `Closes #<eligible-open-issue>` or explain the maintainer-authorized issue this generated-doc fix belongs to.

Nits — 3 non-blocking

• No linked issue number is given in the description beyond referencing Document and test .gittensory-miner.yml config precedence against MINER_* env vars and CLI flags #5198/docs(miner): document and test .gittensory-miner.yml config precedence (#5198) #5500 as the drift's origin; per repo convention this generated-artifact fix should still cite/close a tracking issue if one exists for the check failure.
• Consider adding a CI step that runs miner:env-reference:check on every PR touching lib/config-precedence.js-style env reads so this drift can't recur silently.
• PR description: keep the current validation notes, but add the eligible issue link next to the summary so the scope check is unambiguous.

Concerns raised — review before merging

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.
• Maintainer requires a linked issue — Link the relevant issue (for example Closes #123) before opening the PR.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

2. Maintainer requires a linked issue — Link the relevant issue (for example `Closes #123`) before opening the PR.

Signal	Result	Evidence
Code review	❌ 2 blockers	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 44 registered-repo PR(s), 36 merged, 424 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 424 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	⚠️ ℹ️ Insufficient signal	risk: clean · value: insufficient-signal — Nothing measurable for the structural-improvement analyzers on this PR (e.g. no code files changed).

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
• Official Gittensor activity: 44 PR(s), 424 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

[BETA] Chat with Gittensory

Ask Gittensory a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @gittensory ask <question> answers contribution-quality Q&A with source citations and freshness.
• @gittensory chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @gittensory mention with a real question is routed to the closest matching read-only command automatically -- no exact syntax required.

Full command reference: https://gittensory.aethereal.dev/docs/gittensory-commands

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review