Repo-agnostic capability audit

[JSONbored]

Problem: Today's discovery and claim code was built against gittensory's own repos, labels, and scoring conventions. Before generalizing it, someone needs to know exactly everywhere it currently assumes "this specific ecosystem" rather than "an arbitrary repo."

Area: Product spec / audit

Proposal: Audit the miner package's discovery, claim, and scoring code, producing a concrete checklist of every hardcoded or implicitly gittensory-specific assumption (label names, issue-template shape, scoring weights, repo list) that must become per-tenant configuration instead of a default.

Deliverables:

• A written checklist, organized by file/module, that De-hardcode discovery from gittensory's own conventions #4784 executes directly.

Acceptance criteria:

• Checklist reviewed and confirmed complete by whoever implements De-hardcode discovery from gittensory's own conventions #4784 before that work starts.

Resources:

• The miner package's discovery, claim, and ledger modules.

Boundaries:

• Audit and document only — no code changes in this issue.

---

Part of #4778.

[linear-code]

JSO-3452