feat(signals): add contribution policy snapshot API

[mkdev5]

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.

[mkdev5]

@MkDev11 please fix merge conflicts.

please check the update

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#369 is no longer open.	No action.

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[JSONbored]

@MkDev11 this is good to land.

A few notes:

• The previous requested change was the merge conflict, and the current branch now merges cleanly against origin/main.
• The internal read/write endpoints are protected and covered with auth, invalid JSON, readback, readiness, and public/private boundary assertions.
• Durable api_record snapshots make sense for maintainer-supplied policy.
• No code changes requested.