fix(context): resolve a reply whose reference Discord did not deliver inline #636

Merged

coilyco-ops merged 1 commit from coilyco-ops/resolve-a-reply-to-an-old-message into main

2026-08-13 17:39:20 +00:00

AGit

coilyco-ops commented

2026-08-13 17:38:16 +00:00

Member

closes #630 - a reply to a message outside the history window still produced no subject, which is the case the reply-context work was filed for. Also carries attachments, so replying to a screenshot stops reading as replying to empty text.

coilyco-ops added 1 commit

2026-08-13 17:38:16 +00:00

fix(context): resolve a reply whose reference Discord did not deliver inline

ci / image-build (pull_request) Successful in 24s

Details

ci / test (pull_request) Successful in 38s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

07b8a1d434

replyTarget read the Gateway payload and stopped there, so a reply whose
ReferencedMessage was absent produced no subject at all and the turn looked like
an ordinary message. Discord does not always populate that field, and it is
least likely to for old messages, which is the case sirens-echo#579 was filed
about: a reply to something outside the history window.

So the reply that most needed its subject named was the one still not getting it,
and it failed silently.

The harness already knows how to turn a MessageReference into a message.
summonedByReference does exactly this on the summon path, for the same reason.
This draws on the same lookup budget as the other gate-forced REST calls, so a
channel of old replies cannot become one lookup per message, and a reference
that cannot be read stays an ordinary message rather than becoming a failure.

Resolved before the turn runs rather than inside Current, because Current takes
no context and runTurn calls it before History.

The inline payload still wins wherever Discord supplied one, so a fetch can never
contradict what the Gateway already delivered.

Second, smaller: ReplySubject now carries Attachments. Without them, replying to
a screenshot rendered as replying to empty text, which is the defect the
attachment suffix on a transcript entry exists to prevent. It renders through
that same suffix rather than restating it.

Both halves were in pull request 617, closed as superseded because the version
that landed is better in two other places. This carries forward only what was
lost, onto their implementation. The behaviour was also undocumented, so the
prompt doc now describes it.

closes #630

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>

coilyco-ops requested review from coilysiren

2026-08-13 17:38:16 +00:00

coilyco-ops referenced this pull request

2026-08-13 17:38:31 +00:00

A reply to an old message still does not reach the model, which is the case the reply-context work was filed for #630

coilyco-ops merged commit 70bed39b83 into main

2026-08-13 17:39:20 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 17:39:21 +00:00

Merge pull request 'fix(context): resolve a reply whose reference Discord did not deliver inline' (#636) from coilyco-ops/resolve-a-reply-to-an-old-message into main