[Muhd010]

Overview

This PR wires a configurable reconnect grace period into the API gateway so that a dropped multiplayer player's seat can be held for a short window before release. The changes are limited to gateway configuration and proxy module setup; session-side seat reservation, rejoin handling, expiry, and notifications are not implemented in these files.

Related Issue

Changes

🔌 Gateway Configuration

• [MODIFY] microservices/api-gateway/src/config/configuration.ts

  • Adds a reconnect grace period setting, read from the environment with a default value, so the hold window can be tuned per deployment.

• [MODIFY] microservices/api-gateway/src/proxy/proxy.module.ts

  • Exposes the grace period configuration to the proxy layer so multiplayer routes forwarded through the gateway can use it.

Verification Results

Not run as part of this change. No test files were modified in this PR.

Acceptance Criteria	Status
Players rejoin within the window with progress intact	⏳ Pending: requires session-side seat hold and rejoin logic
Seats released after expiry	⏳ Pending: requires session-side expiry handling
Other players are notified	⏳ Pending: requires session-side drop/rejoin notifications

Closes #480