Deprecated User Service API Alias

user-service is no longer a canonical service boundary. Profile ownership now belongs to profile-service; identity, credentials, sessions, roles, and permissions belong to iam-service.

The remaining services/user-service runtime is a deprecated compatibility scaffold only. Responses include:

• Deprecation: true
• X-Hoctapaz-Service-Status: deprecated-compatibility
• X-Hoctapaz-Canonical-Identity-Service: iam-service
• X-Hoctapaz-Canonical-Profile-Service: profile-service

Use:

• docs/api/profile-service.md
• docs/api/iam-service.md
• contracts/openapi/services/profile-service.yaml
• contracts/openapi/services/iam-service.yaml

The old /v1/users/{userId}/profile* paths remain compatibility endpoints in the deprecated scaffold during migration; replacement ownership and new work must target profile-service or iam-service.

See User-Service Retirement Readiness for the current route inventory, IAM/Profile parity evidence, removal plan, and rollback criteria. The readiness slice does not approve deletion.