feat(config): add Gittensory repo focus manifest

[JSONbored]

Parent roadmap: #82

Background

If Gittensory attracts miners, they need clear direction toward high-value backend/MCP/GitHub App work rather than website polish or vague cleanup.

Goal

Add a repo focus manifest that defines wanted work, out-of-scope work, required tests, public-safety boundaries, and preferred modules.

Current Behavior

Contributor issues can describe focus, but there is no machine-readable project focus policy for Gittensory itself.

Desired Behavior

Gittensory can feed its own focus manifest into decision packs, local preflight, issue drafting, and maintainer guidance.

Implementation Requirements

• Define .gittensory.yml or API-backed equivalent for this repo.
• Include wanted areas, blocked areas, labels, test expectations, public/private boundaries, and maintainer notes.
• Validate manifest.
• Feed into recommendations.
• Keep private notes private.

Public/Private Output Boundaries

Self-dogfood reports may include private maintainer/config readiness in authenticated views. Public docs/issues must stay advisory and must not imply guaranteed Gittensor payouts.

Acceptance Criteria

• Manifest validates.
• Wanted paths influence recommendations.
• Website-only work is discouraged unless safety/release related.
• Malformed manifest warns safely.

Testing Requirements

• npm run test:ci must pass.
• Global coverage must remain at or above 97% for lines, statements, functions, and branches.
• Aim for 98%+ branch coverage locally to avoid CI variance.
• Add tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, scoring, queue pressure, source-upload safety, public/private boundaries, or upstream drift.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.
• MCP/local tooling must prove source contents are not uploaded.

Additional Test Scenarios

• Valid manifest fixture.
• Malformed manifest fixture.
• Blocked path fixture.
• Recommendation influence test.
• Public/private boundary regression.