docs(ams): port docs/env-reference.md to a generated website docs page (docs.ams-env-reference.tsx)

[oktofeesh1]

Summary

• Extends packages/loopover-miner/scripts/generate-env-reference.mjs to also emit apps/loopover-ui/src/lib/ams-env-reference.ts (AMS_ENV_REFERENCE_ROWS + AMS_ENV_REFERENCE_MARKDOWN), mirroring scripts/gen-selfhost-env-reference.mjs's renderSelfHostEnvReferenceModule exactly. npm run miner:env-reference(:check) now writes/verifies both the existing markdown doc and the new TS module, so a new LOOPOVER_MINER_*/MINER_* read still fails CI drift-check until both are regenerated.
• packages/loopover-miner/docs/env-reference.md is untouched in content (still generator-owned, "do not edit manually") and stays the canonical source shipped in the npm package.
• Adds content/docs/ams-env-reference.mdx, which imports AMS_ENV_REFERENCE_MARKDOWN and renders it via <CodeBlock> — the same pattern docs.self-hosting-configuration.tsx already uses for SELFHOST_ENV_REFERENCE_MARKDOWN — not a hand-copied table, per the issue's explicit requirement.
• Adds apps/loopover-ui/src/routes/docs.ams-env-reference.tsx, a thin loader + docsClientLoader route matching every other migrated docs page.
• Adds the page to docs-nav.tsx's "AMS: deployment" subgroup and to docs.index.tsx's Maintainers audience card, and repoints ams-operations-runbook.mdx's and ams-config-precedence.mdx's GitHub-blob env-reference.md cross-references to the new in-app route.
• Extends test/unit/miner-env-reference-script.test.ts with module-generation, Prettier-quoting, and drift-detection tests mirroring test/unit/selfhost-env-reference-script.test.ts.
• packages/loopover-miner/scripts/generate-env-reference.d.mts (a hand-maintained sidecar declaration file) gained declarations for the new exports, and the generator's markdown-line embedding now replicates Prettier's fewer-escapes quote choice so its own output is already lint-clean.

This is a resubmission of #6376, which was auto-closed on a CI-only failure (Cannot find module 'collections/browser') — a known cache-hit gap in validate-code's dependency-restore step, unrelated to this page's content. The maintainer's own PR #6375 (merged) fixes it at the CI-workflow level by regenerating fumadocs collections unconditionally; this branch is rebased on top of that fix.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused: a generator script extension + one new docs page + nav wiring + a cross-reference cleanup in two already-migrated pages.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• Closes docs(ams): port docs/env-reference.md to a generated website docs page (docs.ams-env-reference.tsx) #6028

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally — packages/loopover-miner/scripts/** is outside vitest's coverage-collection scope (only src/**, packages/loopover-engine/src/**, and packages/loopover-miner/lib/** are instrumented per codecov.yml's own comment), and the .tsx/.mdx page is outside coverage.include; codecov/patch does not apply. New generator behavior is still covered by real unit tests regardless.
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate
• npm run miner:env-reference:check passes for both generated outputs
• Full npm run test:ci run locally from a clean npm ci install, rebased on top of fix(ci): regenerate fumadocs collections unconditionally in validate-code #6375's CI fix, green: 905 test files / 17,310 tests passed

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. — N/A, no such changes in this PR
• API/OpenAPI/MCP behavior is updated and tested where needed. — the generator's new module-emitting behavior is covered by new unit tests
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks. — N/A, static generated reference content only
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

Notes

• No UI Evidence table — new content page rendered through the same primitives as every other migrated docs page, no visual redesign.
• Continues the "AMS: deployment" nav-subgroup precedent set by docs(ams): port DEPLOYMENT.md to a website docs page (docs.ams-deployment.tsx) #6022-docs(ams): port docs/config-precedence.md to a website docs page (docs.ams-config-precedence.tsx) #6027.

[superagent-security]

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.60%. Comparing base (b41b957) to head (dc10cd4).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6385   +/-   ##
=======================================
  Coverage   95.60%   95.60%           
=======================================
  Files         599      599           
  Lines       47238    47238           
  Branches    15031    15031           
=======================================
  Hits        45160    45160           
  Misses       1291     1291           
  Partials      787      787           

Flag	Coverage Δ
shard-1	43.99% <ø> (-0.18%)	⬇️
shard-2	36.78% <ø> (+0.39%)	⬆️
shard-3	32.28% <ø> (-0.23%)	⬇️
shard-4	34.69% <ø> (+0.07%)	⬆️
shard-5	31.44% <ø> (-0.15%)	⬇️
shard-6	45.31% <ø> (+0.44%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-16 06:00:46 UTC}

11 files · 1 AI reviewer · no blockers · readiness 75/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR mechanically extends the existing self-host env-reference generator pattern to AMS, adding a `renderMinerEnvReferenceModule` function that mirrors `renderSelfHostEnvReferenceModule`, wiring the output into a new generated TS module, a new docs route, nav entries, and cross-reference updates. The approach is well-precedented (matches `docs.self-hosting-configuration.tsx`'s existing pattern exactly), the generator/module output is tested for determinism and Prettier-quote correctness, and CI is fully green. The `routeTree.gen.ts` diff is auto-generated router scaffolding, not hand-written risk.

Nits — 5 non-blocking

• The `as any` casts in `routeTree.gen.ts:364` etc. are pre-existing codegen boilerplate from TanStack Router, not something introduced by hand — but worth confirming this file is truly auto-generated and not meant to be hand-edited going forward.
• packages/loopover-miner/scripts/generate-env-reference.mjs's `quoteJsStringLiteral` only counts raw quote occurrences to decide single vs double quotes, which is a reasonable heuristic for this constrained domain (short table-cell strings) but wouldn't correctly replicate Prettier's actual escape-counting algorithm for more complex strings — fine here since inputs are `firstReference`/`defaultValue`/markdown lines with predictable, judgechecked shapes.
• The new `content/docs/ams-env-reference.mdx` file uses `<Callout>` and `<CodeBlock>` without a visible import in the shown diff — verify these are provided by the MDX pipeline's implicit component scope the same way `docs.self-hosting-configuration.mdx` does, since I can't see that file's content here.
• Test coverage ratio (0.18) is on the low side for ~367 new source lines, though most of the addition is a generated data file (`ams-env-reference.ts`) and JSX boilerplate (`docs.ams-env-reference.tsx`) that don't need dedicated unit tests beyond what's already covered by the generator tests and existing route-pattern precedent.
• Consider a quick manual/e2e check that `/docs/ams-env-reference` renders correctly with the CodeBlock content, since UI route correctness isn't provable from unit tests alone.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#6028
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 66 registered-repo PR(s), 54 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	oktofeesh1; Gittensor profile; 66 PR(s), 0 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: moderate

Review context

• Author: oktofeesh1
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 66 PR(s), 0 issue(s).
• Related work: Titles/paths share 8 meaningful terms. (issue #6029)
• Related work: Titles/paths share 8 meaningful terms. (issue #6031)
• Related work: Titles/paths share 8 meaningful terms. (issue #6030)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Start here: Review top overlaps.
• Then work through the remaining 3 steps in the Signals table above.

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.

🧪 Chat with LoopOver

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

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

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Visual preview

Route	Viewport	Before (production)	After (this PR's preview)	Diff
/docs/ams-env-reference	desktop	before /docs/ams-env-reference	after /docs/ams-env-reference	—
/docs/ams-env-reference	mobile	before /docs/ams-env-reference (mobile)	after /docs/ams-env-reference (mobile)	—
/docs	desktop	before /docs	after /docs	—
/docs	mobile	before /docs (mobile)	after /docs (mobile)	—

Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy.

_{🟩 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 LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.