fusion

Files

gsxdsm 456f7b370b docs(test-failures): retract the connection-exhaustion cause, record the failed reproduction

Measured 14 backend connections against max_connections=100, so the api-lane
hook timeouts are not connection exhaustion; the PostgreSQL Failed query lines
are a torn-down reconciler polling after the fact. Full 15-lane run at 23,584
tests reproduced nothing, and the DDL admission gate never degraded, so that
mechanism is unsupported too. Records what a future attempt must capture.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-23 20:08:43 -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