fix(grounding): an interval shorter than a turn dates an event inside it #611

Closed
coilyco-ops wants to merge 1 commit from coilyco-ops/a-moment-ago-is-this-turn into main AGit
Member

closes #601 - a moment ago is inside this turn, not reportage about an earlier day; also unbreaks main, red since aa289d4 because #604 and #606 were each green on their own branch

closes #601 - a moment ago is inside this turn, not reportage about an earlier day; also unbreaks main, red since aa289d4 because #604 and #606 were each green on their own branch
fix(grounding): an interval shorter than a turn dates an event inside it
All checks were successful
ci / test (pull_request) Successful in 36s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
ci / image-build (pull_request) Successful in 3m33s
272904d5af
ago sat unconditional in pastReference, so "a correction was filed
moments ago" was read as reportage about some earlier day and skipped
the check. It is a natural way for a model to claim it just acted.

turnReference already carried "just now", a short-interval time phrase
rather than an exchange-noun, so the short forms belong in that set
rather than in a restructuring of pastReference. That construction
needs no lookbehind, which RE2 lacks, and costs nothing: "a while ago"
and "an hour ago" still read as reportage.

The issue named that trade as needing a human decision. There is no
trade, so there is nothing to decide.

Also unbreaks main. #604 pinned "An issue has already been filed for
this" as an open 602 escape, #606 closed 602, and each was green on its
own branch. The merge is red and has been since aa289d4. The row now
records the fix, which is what its own failure message asks for.

Refs sirens-echo#601, sirens-echo#568

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Author
Member

Superseded by #614. Closing this one — Angie (ENG, claude seat). Same change, correct base, honest commit message. Nothing here is worth reviewing.

Two things went stale between opening this and now, and both are the tracker moving faster than a pull request.

The base moved. This was cut on aa289d4. Main is now 33c4095, and the two conflict in groundingcorpus_test.go, so this is unmergeable as it stands.

Half of it was already done by someone else. This carried a second change that unbroke main, and its commit message said so. #610 landed the same one-row fix first. Leaving that message in place would put a claim in main's history that this commit unbroke something another commit had already unbroken. 614 drops it.

I rebased and rewrote the message, which needs a force push, and force push is not available to this seat. Superseding is the honest way to get a corrected message in rather than the only way to get the code in.

What 614 contains

The production change is three lines in turnReference and nothing else:

(?:a\s+few\s+|a\s+|several\s+)?(?:moments?|seconds?)\s+ago

Plus eight corpus rows, five escapes closed and three false-positive guards, each verified load-bearing under a mutation. Detail is on 614 and on #601.

Also, a stray branch. I pushed fix/a-moment-ago-is-this-turn as a named branch before reading the merge lane, which says the AGit flow makes that unnecessary. Deleting it is also not available to this seat. It carries 272904d, which is superseded and should not be merged. Whoever has the permission can remove it.

**Superseded by https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/pulls/614. Closing this one — Angie (ENG, claude seat).** Same change, correct base, honest commit message. Nothing here is worth reviewing. Two things went stale between opening this and now, and both are the tracker moving faster than a pull request. **The base moved.** This was cut on `aa289d4`. Main is now `33c4095`, and the two conflict in `groundingcorpus_test.go`, so this is unmergeable as it stands. **Half of it was already done by someone else.** This carried a second change that unbroke main, and its commit message said so. https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/pulls/610 landed the same one-row fix first. Leaving that message in place would put a claim in main's history that this commit unbroke something another commit had already unbroken. 614 drops it. I rebased and rewrote the message, which needs a force push, and force push is not available to this seat. Superseding is the honest way to get a corrected message in rather than the only way to get the code in. ## What 614 contains The production change is three lines in `turnReference` and nothing else: ``` (?:a\s+few\s+|a\s+|several\s+)?(?:moments?|seconds?)\s+ago ``` Plus eight corpus rows, five escapes closed and three false-positive guards, each verified load-bearing under a mutation. Detail is on 614 and on https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/601. **Also, a stray branch.** I pushed `fix/a-moment-ago-is-this-turn` as a named branch before reading [the merge lane](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/src/branch/main/docs/sirens-echo-merge-lane.md), which says the AGit flow makes that unnecessary. Deleting it is also not available to this seat. It carries `272904d`, which is superseded and should not be merged. Whoever has the permission can remove it.
coilyco-ops closed this pull request 2026-08-13 17:13:11 +00:00
All checks were successful
ci / test (pull_request) Successful in 36s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
ci / image-build (pull_request) Successful in 3m33s

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo!611
No description provided.