feat(app): expose recommendation rerun reasons

[MkDev11]

Summary

• Add public-safe changed-since-last-run metadata to miner dashboard next actions and repo-fit rows.
• Group deterministic rerun reasons by repo state, contributor state, validation state, and policy/context state.
• Render changed and unchanged recommendation states in the miner dashboard.

Closes #242

Scope

• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked an issue, or this is small enough that the summary explains why an issue is not needed.

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally; global coverage stays at or above 97% for lines, statements, functions, and branches (aim for 98%+ branch coverage locally so CI variance does not fail near the threshold)
• 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
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

If any required check was skipped, explain why:

• None. Full npm run test:ci passed locally. Coverage summary: statements 99.05%, branches 97%, functions 98.43%, lines 99.62%.

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.
• API/OpenAPI/MCP behavior is updated and tested where needed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
• Visible UI changes include screenshots or a short recording.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

Notes

• API payload changes are additive on /v1/app/miner-dashboard; OpenAPI remains the existing generic app response schema.
• No docs or changelog update is needed for this feature PR.
• UI evidence:
  • Desktop: https://raw.githubusercontent.com/MkDev11/gittensory/pr-evidence-issue-242-rerun-reasons/pr-evidence/issue-242-desktop.png
  • Mobile: https://raw.githubusercontent.com/MkDev11/gittensory/pr-evidence-issue-242-rerun-reasons/pr-evidence/issue-242-mobile.png

[gittensory]

Important

Gittensory found maintainer review notes

Scoped related-work signals were found for this PR. They are advisory unless the gate reports a blocker.

Readiness score: 75/100

Signal	Result	Evidence	Action
Linked issue	✅ Linked	#242	No action.
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.	Review top overlaps.
Review load	❌ 8/20	Readiness component derived from cached public PR metadata and labels; size label size:XL.	Add scope summary.
Validation evidence	✅ 25/25	PR body includes validation/test evidence.	No action.
Open PR queue	❌ 3/10	17 open PR(s), 15 likely reviewable.	Expect slower review.
Contributor context	✅ Confirmed Gittensor contributor	MkDev11; Gittensor profile; 289 PR(s), 10 issue(s).	No action.
Gate result	✅ Passing	No configured blocker found.	No action.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Review load = cached public PR metadata such as size labels, changed paths, and preflight status.
• Open PR queue = repo-wide review pressure; it is not a PR quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

Review context

• Author: MkDev11
• 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: 289 PR(s), 10 issue(s).
• Related work: Items reference the same linked issue feat(agent): expose recommendation changes and rerun reasons in miner dashboard #242. (issue #242)
• Related work: Open PR work references issue feat(agent): expose recommendation changes and rerun reasons in miner dashboard #242. (issue #242)
• Related work: Titles/paths share 6 meaningful terms. (PR #422)
• Additional title-only matches omitted; title-only overlap does not block.

Maintainer notes

• Possible duplicate or overlapping work: 73 related open work cluster(s) were detected.

Contributor next steps

• Review top overlaps.
• Add scope summary.
• Expect slower review.
• Check active issues and PRs before submitting.

• Re-run Gittensory review

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. Learn more about Gittensor contribution workflows.