dev_agentandClaude Opus 5.5 8d8a5480b9 Keep candidates found at a rename's revision when clearing offers ...

A candidate search that read a dinner after its rename committed could
store fresh offers that the rename's own clear then dropped, so a valid
candidate for the renamed dinner was refused with a 400.

clearOffers now takes the revision below which offers are stale: a rename
passes its committed revision, so it drops only offers and in-flight
searches from earlier revisions, while grounding by hand and archiving
pass math.MaxInt64 and clear everything as before. A search finishing
late at an earlier revision no longer replaces offers already found at a
later one.

Fixes MQ-103-02.

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

2026-10-07 00:05:30 -04:00

..

dinners_test.go

Release corrections: candidate URL exposure, onboarding notification honesty, pasted link cleanup (#101)

2026-10-06 23:12:26 -04:00

dinners.go

Keep candidates found at a rename's revision when clearing offers

2026-10-07 00:05:30 -04:00

export_test.go

Keep candidates found at a rename's revision when clearing offers

2026-10-07 00:05:30 -04:00

grounding_test.go

Keep candidates found at a rename's revision when clearing offers

2026-10-07 00:05:30 -04:00

grounding.go

Keep candidates found at a rename's revision when clearing offers

2026-10-07 00:05:30 -04:00