feat(signals): add contribution policy snapshot API

[MkDev11]

Summary

• Add protected internal read/write API endpoints for repo-owner contribution policy snapshots.
• Persist API-derived policy snapshots through the existing focus-manifest signal snapshot path and keep explicit api_record snapshots durable instead of expiring them like repo-file fetch caches.
• Return normalized focus-manifest data plus the compiled policy partition so internal callers can distinguish public-safe guidance from authenticated maintainer context.
• Closes feat(signals): add repo-owner contribution policy snapshots #111.

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.06%, functions 98.36%, lines 99.65%.

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

• No visible UI changes.
• Internal policy snapshot responses include authenticated maintainer context; public readiness output is tested to avoid leaking the private note text or forbidden public-report terms.

[JSONbored]

@MkDev11 please fix merge conflicts.

[MkDev11]

@MkDev11 please fix merge conflicts.

please check the update

[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.

Signal	Status	Action
Linked issue	#111	Ready for issue-scoped review.
Duplicate risk	9+ scoped related-work signals	Advisory review only.
Review burden	High	Estimated from public PR metadata.
Repo queue	Critical	Repo-wide context only; this does not block the gate.
Contributor context	Confirmed Gittensor contributor	Official public API confirmed this GitHub user.
Gate result	Passing	No configured blocker found.

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: TypeScript, JavaScript, Python, CSS, Java, MDX, Rust, Scala
• Official Gittensor activity: 287 PR(s), 10 issue(s).
• PR-specific overlap: Items reference the same linked issue feat(signals): add repo-owner contribution policy snapshots #111. (issue feat(signals): add repo-owner contribution policy snapshots #111)
• PR-specific overlap: Titles share 153 meaningful terms. (PR feat(settings): wire policy compiler into registration readiness #350)
• PR-specific overlap: Titles share 143 meaningful terms. (PR feat(mcp): add custom agent profiles to init-client #351)
• PR-specific overlap: Titles share 152 meaningful terms. (PR feat(raycast): add miner command center #357)
• Additional scoped related-work signals hidden: 86.

Maintainer notes

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

Contributor next steps

• Review the scoped related-work signal before deep review; it is not a merge blocker by itself.
• Check active issues and PRs before submitting.

---

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