## MODIFIED Requirements

### Requirement: Reference Surge client config documents the chained proxy setup
The project SHALL generate a Surge client configuration file from a Jinja2 template after deployment, replacing the previous static reference file with placeholders. The generated config SHALL contain actual connection parameters.

#### Scenario: Config is generated, not static
- **WHEN** the playbook completes
- **THEN** `output/surge-client.conf` is generated with real IPs, ports, and passwords
- **THEN** no manual placeholder replacement is needed

#### Scenario: Static reference file removed
- **WHEN** the repository is inspected
- **THEN** `docs/surge-client.conf` no longer exists as a static placeholder file