docs(miner): add an 'Observing your miner' Grafana/ledger observability guide

[davion-knight]

Adds packages/gittensory-miner/docs/observability.md — the miner-specific guide for pointing Grafana at the local SQLite ledgers (#5190). Documentation only.

Contents

• What's observable — the attempt-log.sqlite3 (attempt_log_events) and prediction-ledger.sqlite3 ledgers under GITTENSORY_MINER_CONFIG_DIR.
• Point Grafana at the ledgers — concrete steps using the read-only frser-sqlite-datasource entries shipped in grafana/provisioning/datasources/ams-ledgers.yml (from Provision a Grafana datasource for AMS's local SQLite ledgers (attempt log + prediction ledger) #5184): install the plugin, mount the config dir read-only at /ams-ledgers, restart.
• Load a dashboard — how to add/import a dashboard from grafana/dashboards/ and point panels at the AMS Attempt Log / AMS Prediction Ledger datasources (incl. json_extract for payload fields).
• Linked from coding-agent-driver.md (the existing entry point) so it's discoverable; cross-references DEPLOYMENT.md; does not duplicate the general ops runbook.

Validation

• All relative links resolve (verified against the tree — ams-ledgers.yml, grafana/dashboards/, DEPLOYMENT.md all exist; no dead links — deliberately does not reference a not-yet-existing dashboard file).
• prettier-clean; the existing miner-mcp-tool-docs-parity + miner-operations-runbook doc tests still pass after the added cross-reference. Docs only — no code, no CI-logic surface.

Closes #5190

[superagent-security]

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

[loopover-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ Gittensory review result - approve/merge recommended

_{Review updated: 2026-07-12 19:03:23 UTC}

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

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR adds a docs-only observability guide for pointing Grafana at the miner's local SQLite ledgers, plus a cross-reference link and prettier reformatting in coding-agent-driver.md. The content is well-structured, links resolve to files referenced elsewhere in the repo (ams-ledgers.yml, grafana/dashboards/, DEPLOYMENT.md), and it closes the linked issue #5190. One inconsistency worth confirming: the relative link depth to ams-ledgers.yml differs between the new doc's two references.

Nits — 6 non-blocking

• packages/gittensory-miner/docs/observability.md:16-17 and :23 use `../../../grafana/provisioning/...` (three levels up) while the file itself lives at packages/gittensory-miner/docs/, which is only two levels below repo root if grafana/ is at the repo root — worth double-checking the relative path depth is correct rather than assuming it resolves, since a typo here would silently produce a dead link.
• The coding-agent-driver.md table reformatting (adding fixed-width padding to the markdown table) is unrelated prettier churn bundled with the observability cross-reference addition; harmless but worth calling out as noise in future diffs.
• observability.md doesn't mention what to do if `frser-sqlite-datasource` plugin installation fails or the ledger files don't exist yet (e.g., a fresh miner with no attempts) — minor gap for a first-time reader.
• Confirm the `../../../grafana/...` relative path in observability.md resolves correctly given the actual repo layout (verified per PR description, but worth a final sanity check since it's the crux of the guide's usability).
• Consider a one-line note in observability.md about empty/missing ledger files on a fresh install, since that's a common first-run confusion point for a new datasource.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#5190
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 (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 124 registered-repo PR(s), 89 merged, 2 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	davion-knight; Gittensor profile; 124 PR(s), 2 issue(s).
Gate result	✅ Passing	No configured blocker found.
Improvement	⚠️ ℹ️ Insufficient signal	risk: low · value: insufficient-signal — Nothing measurable for the structural-improvement analyzers on this PR (e.g. no code files changed).

Review context

• Author: davion-knight
• 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: 124 PR(s), 2 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

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