feat(mcp): expose jobs and trending resources

[JSONbored]

Summary

The MCP server currently exposes registry directory/category/entry resources. Jobs and trending discovery are useful read-only surfaces too, and MCP clients should be able to inspect them without scraping web pages.

Current state

• MCP resources include directory, category, and entry templates.
• Public jobs are exposed through /api/jobs.
• Trending exists internally through growth surfaces but does not yet have a public endpoint.

Desired behavior

• Add MCP resources for active jobs and trending/recent discovery once the corresponding public API/artifact is stable.
• Keep outputs bounded and public-safe.
• Include source/freshness/trust metadata where available.

Implementation notes

• Add resource URIs such as heyclaude://jobs/active, heyclaude://registry/trending, and possibly heyclaude://registry/recent.
• Reuse public API/artifact payloads instead of database access from the MCP package.
• Keep the no-key read-only policy explicit.

Acceptance criteria

• MCP resource listing includes jobs and discovery resources.
• Reading resources returns bounded JSON/markdown content.
• Resources degrade gracefully if dynamic state is unavailable.
• Tests cover resources over local MCP and remote HTTP route where practical.

Validation

• pnpm test:mcp
• pnpm validate:mcp-package
• Add or update focused unit tests for the touched API/helper surface.
• Run the narrow relevant validation command for the changed package or route.
• Run git diff --check before opening a PR.