security: enforce model-registry auth in release compose

[man4ish]

Summary

Fix a critical HIPAA security gap where the model-registry service was deployed without authentication and organization enforcement in the release Compose configuration.

The model-registry application already had the required Phase 2A–2E organization-ownership enforcement, but the release deployment did not enable it.

Before this fix, AUTH_ENABLED was unset in the release configuration and therefore defaulted to false.

The vulnerability was independently reproduced:

• Unauthenticated POST /v1/register → 200
• No Authorization header was required.
• Model-registry was exposed on all interfaces in the release configuration.

Fix

Added the existing repository-standard authentication wiring to the model-registry service in both release Compose variants:

• AUTH_ENABLED: "true"
• JWT_SECRET: ${AUTH_SECRET_KEY:?AUTH_SECRET_KEY must be set}
• IAM_URL: http://auth-service:8001
• AUDIT_URL: http://security-audit:8004

Also:

• Added model-registry to EXPECTED_SECRET_WIRING.
• Added regression coverage requiring AUTH_ENABLED == "true" in both release files.
• Corrected the inaccurate security documentation.
• Did not modify the existing model-registry Phase 2A–2E ownership implementation.

Verification

Pre-fix vulnerability reproduced:

• Unauthenticated POST /v1/register → 200

Post-fix verification:

• Unauthenticated GET /v1/models → 401
• Unauthenticated POST /v1/register → 401
• Invalid/expired token → 401
• Organization A can register/read its own model → 200
• Organization B cannot read Organization A's model
• Organization B cannot tag Organization A's model
• Organization B cannot promote Organization A's model
• Cross-organization responses retain the existing anti-enumeration behavior.

Configuration verification:

• docker compose config confirms all required model-registry authentication variables.
• Missing AUTH_SECRET_KEY causes Compose configuration to fail closed.
• YAML validation passes.
• Ruff passes on the changed test file.

Tests:

• 75 passed — release/network configuration tests
• 101 passed — non-integration Studio tests
• Model-registry test suite passes with 95.76% coverage
• Integration tests were not run successfully because they require the live stack; connection-refused failures are unrelated to this configuration change.

Scope

This PR intentionally does not modify:

• omnibioai-model-registry
• RAG
• TES
• dev-hub
• Control Center public-read-only work
• Existing organization ownership logic

Separate follow-up investigations are recommended for the release-auth configuration observed in dev-hub, RAG, and TES.

Review request

Please review specifically for:

1. Correct release authentication wiring.
2. Fail-closed behavior when AUTH_SECRET_KEY is missing.
3. Regression-test coverage preventing the release configuration from reverting to unauthenticated mode.
4. Preservation of existing model-registry organization isolation.

If CI is green and there are no substantive review concerns, this PR is GO for merge.

🤖 Generated with Claude Code