mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 04:32:42 +00:00
Antiheld86
19b69dee21
Three failures in the integration run, all mine, none in the product. The two delegation cases set the account selector as a header on the NextRequest. Nothing reads it there. `readSelectorHeader()` resolves through `next/headers`, which this suite mocks against the shared `headerJar`, so the carrier came back `none` and both cases quietly exercised the ordinary own-record path instead of the one they name. The scoped case wrote to its own record and returned 201; the wildcard control wrote to the caller rather than the owner. Neither was testing delegation at all. That is worse than a broken test. The refusal these two cover is the regression this change could most easily have shipped in silence, and the tests standing in front of it were not looking at it. They now set the selector on the jar, through the exported ACCOUNT_SELECTOR_HEADER rather than a literal, so a rename cannot reintroduce the same gap. The third failure is unrelated and smaller: the read-leg case read the audit row once, racing a fire-and-forget write, and reported `undefined` for a row about to exist. It now polls, matching B1, which carries a comment about this exact hazard that I did not follow. Not verified here: this environment has no Docker daemon, so the integration suite cannot be run against a real Postgres. The diagnosis is from the mock and the resolver, not from a green run.