Add an API resource to hominem

A resource (e.g. calendar, people, career) is exposed over two outward surfaces:

1. MCP tools — services/api/src/mcp/tools/*.ts, called by AI clients via callTool.
2. RPC routes — services/api/src/rpc/routes/*.ts, plain HTTP JSON under /api, called by web/mobile clients.

Golden rule: MCP and RPC are thin adapters over ONE shared implementation. Both surfaces import the same Zod schemas from services/api/src/schemas/ and the same query logic from services/api/src/application/*.service.ts. Never fork query logic or schemas between the two — a change to a resource's behavior must be a single edit in the application layer, verified by a single test suite, and both surfaces pick it up for free.

Layered dependency direction (never the reverse):