Skip to content

fix: return latest conversation messages from native backend - #8

Merged
HsukqiLee merged 1 commit into
mainfrom
fix/reviewed-audit-repairs
Nov 14, 2026
Merged

HsukqiLee merged 1 commit into
mainfrom
fix/reviewed-audit-repairs

Conversation

@HsukqiLee

Copy link
Copy Markdown
Contributor

Carry the latest-message window contract into the current Go backend: omitted offset returns the newest 50 messages in chronological order; explicit offset preserves history pagination. Regression exercises the production route with 60 messages and verifies account ownership. Reproduced the oldest-window failure before the fix; Linux full Go suite passed after it. Closes #5.

@HsukqiLee

Copy link
Copy Markdown
Contributor Author

Reviewed current Go route and regression: ownership is checked before either query; the omitted-offset branch selects newest records with deterministic created/id ordering and returns chronological order; explicit offset retains the history query. Linux and Windows backend checks, frontend gate, CAS contract/build and validation all passed on this head.

@HsukqiLee
HsukqiLee merged commit 6bd5882 into main Nov 14, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

默认会话消息窗口包含最新问答

1 participant