# TASK 1.3: Add Redshift Connectivity and Configuration

## Summary

Add the configuration and connectivity layer required for tenant-aware Redshift access.

This task should make the platform Redshift-ready in local/dev environments without yet changing existing runtime behavior to use Redshift.

It should also prepare the configuration path needed for a phase-1 CLI bootstrap command that calls the foundation bootstrap service.

It should also provide the configuration needed by the backend tenant warehouse smoke path from TASK 1.4.

The configuration should be wired for the new `Kds.Ai.Warehouse` module.

It should support both phase-1 administrative CLI operations:

- tenant registration,
- tenant bootstrap.

## Dependencies

- TASK 1.2 (tenant warehouse foundation abstractions)

## Files to Create

### 1. Redshift configuration/settings types

Create any required settings/options classes to represent Redshift connectivity and tenant-aware connection configuration.

## Files to Modify

### 2. `backend/Kds.Ai.AppHost/AppHost.cs`

Add the configuration shape required for Redshift connectivity in local/dev environments.

### 3. Backend DI/setup modules as needed

Wire up the Redshift-compatible connection path for the new foundation layer.

## Required Behavior

- Use Redshift-compatible Npgsql configuration.
- Support the connection model required by the tenant warehouse connection factory.
- Support execution from `Kds.Ai.Cli` for explicit bootstrap operations.
- Support execution from `Kds.Ai.Cli` for tenant warehouse validation operations.
- Support execution from `Kds.Ai.Cli` for explicit tenant registration operations.
- Keep the old shared warehouse path intact for now, because simulator/runtime migration is not part of this phase.

## Acceptance Criteria

- [x] Redshift configuration model is introduced
- [x] AppHost/configuration supports Redshift connectivity for phase 1
- [x] Redshift-compatible Npgsql configuration is defined
- [x] The foundation layer can obtain the configuration it needs for tenant warehouse access
- [x] `Kds.Ai.Cli` can obtain the configuration required to invoke bootstrap service logic
- [x] `Kds.Ai.Cli` can obtain the configuration required to invoke tenant warehouse validation logic
- [x] Existing PostgreSQL-based runtime paths are not broken by this task
- [x] Solution builds without errors

## Notes

- This task prepares the infrastructure contract for later consumption.
- It must not switch the anomaly detector or simulator to Redshift yet.
- Local Aspire should provide `ConnectionStrings__redshiftwarehousedb` as the base Redshift template connection string.
- Existing PostgreSQL connection strings remain additive and unchanged for legacy consumers.