Request
HarborFerry operations wants its running booking service adopted before the next release.
Evidence
The remote service ID is supplied in the first task. It is active and must retain that identity. No other team owns it in Terraform.
Handoff
Import the existing service, move its local address, apply the requested capacity and queue, then deliver service identity outputs and a passing capacity assertion.
HarborFerry already has a booking service, but its platform team lacks a Terraform binding for that object. Start by adopting its known remote identity. Then improve the configuration without replacing the service merely because its local address changes. Each later request adds a checked operating requirement, including a private queue and a capacity assertion. Preserve the original service identity through the handoff. The supplied records describe a fictional estate in the lab provider, so adoption never contacts a cloud account. Your final files and outputs should give the next operator enough evidence to distinguish a managed resource from an unmanaged object with a similar name.
The handoff grows from this starting configuration. Preserve completed work as the requirements change.