feat(registration): add Gittensory registration readiness and config recommendation

[JSONbored]

Parent: #32

Goal

Prepare Gittensory itself, and future repo owners, for Gittensor registration with sane contributor lanes.

Requirements

• Add a registration-readiness report for JSONbored/gittensory.
• Evaluate direct-PR readiness, issue-discovery readiness, label policy, maintainer-cut readiness, test coverage health, queue health, contribution docs, and GitHub App behavior.
• Recommend initial Gittensor config: issue_discovery_share, label multipliers, maintainer_cut, linked-issue policy, and lane warnings.
• Keep output advisory and private/API-first.

Acceptance Criteria

• Gittensory can explain whether it is ready to attract Gittensor miner work.
• Direct-PR-first recommendation is explicit unless issue-discovery intake is ready.
• Maintainer economics are separated from miner rewards.
• Config recommendation includes tradeoffs and warnings.

Testing Requirements

This issue must preserve the repo's CI gate:

• npm run test:ci must pass.
• Global coverage must remain at or above 95% for lines, statements, functions, and branches.
• Add or update tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, public/private boundaries, scoring, queue pressure, or source-upload safety.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.

Required Test Scenarios

• Ready repo fixture.
• Not-ready repo fixture.
• Issue-discovery disabled recommendation.
• Maintainer-cut readiness.
• Missing labels/docs/test gate warnings.