fusion

Files

gsxdsm 2c3a47368f FN-9136: Characterize PostgreSQL fork database reuse

Characterize safe per-fork PostgreSQL database reuse while documenting why the production experiment remains reverted.

- add a bounded pool primitive with reset, verification, discard, and ownership fencing
- cover recycling, poison handling, capacity, and reclaim namespace behavior
- align PostgreSQL campaign documentation with the dead-fork leak rejection

Files changed:
 .../test-failures/postgres-ddl-admission-bound.md  |   4 +-
 .../suite-only-flakes-observed-register.md         |   4 +-
 docs/testing.md                                    |   4 +-
 .../core/src/__test-utils__/pg-fork-db-pool.ts     | 184 +++++++++++++++++++++
 .../__tests__/pg-fork-db-pool-ownership.test.ts    |  36 ++++
 .../core/src/__tests__/pg-fork-db-pool.test.ts     |  60 +++++++
 6 files changed, 287 insertions(+), 5 deletions(-)

Fusion-Task-Id: FN-9136

Fusion-Task-Lineage: 9e14e0eb-d957-4207-977e-2d913e78750f

Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>

2026-08-16 22:06:38 -07:00

architecture

FN-8685: add durable cross-process task deletion consumers

2026-08-01 06:09:04 -07:00

architecture-patterns

fix(engine): make the planning->plan-review handoff atomic so planned cards stop stranding in Todo

2026-08-12 21:24:53 -07:00

best-practices

docs(solutions): finding 6 — read the implementation before claiming its output is wrong (#2649 )

2026-07-30 00:07:06 -07:00

build-errors

docs(solutions): capture eslint exhaustive-deps CI-lint gotcha