v3.8.0

Run402 3.8.0 makes server project identity authoritative across the CLI/SDK/MCP path. Project list/get/use flows now validate with the current principal instead of treating local cached keys as project inventory, while explicit local key operations move under credentials project-keys with local_cache provenance. Custom-domain commands default to principal auth with explicit project_id, with --auth service-key kept as the compatibility path for callers that intentionally want the local project-key cache.\n\nPublished packages: run402-mcp@3.8.0, run402@3.8.0, @run402/sdk@3.8.0.\n\nFull changelog: v3.7.14...v3.8.0