`poolTimeout` and other declared-but-unused config values fragment behavior

[nanaf6203-bit]

Context

PrismaService parses PGBOUNCER_POOL_TIMEOUT into a variable used nowhere (marked eslint-disable as unused); README documents PGBOUNCER_POOL_TIMEOUT as config; CACHE_WARMING_INTERVAL semantics are vague in .env.example.

Problem

Config that silently does nothing creates false assumptions during ops (tuning pool timeout has zero effect; warming interval expectations mismatch implementation). Either implement the knobs or document them as no-ops/invalid.

Proposed approach

Either wire pool timeout into Prisma client options (connection_timeout / statement_timeout) or remove the variable and README row; reconcile CACHE_WARMING_INTERVAL to the scheduling truth; add a config-docs smoke test listing implemented knobs.

Acceptance criteria

• Every documented knob has an effect or is removed from docs.

[damiedee96]

@damiedee96 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer, I'd love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @damiedee96 to this issue.

[beulah7717108-eng]

@beulah7717108-eng has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer
i have reviewed the acceptance criteria
please kindly assign me this issue to fix

ℹ️ Repo Maintainers: To accept this application, review their application or assign @beulah7717108-eng to this issue.

[drips-wave]

Congratulations, @beulah7717108-eng! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @beulah7717108-eng: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊