Preserve native token boundaries during trajectory replay - #924
Conversation
|
Consolidated review record (automated agent review traffic removed 2026-09-17) Change. Exact replay left rendered closing tool markup behind, so later histories gained different prefixes and double-counted canonical action tokens. Complete sampled responses now extend through the renderer-proven stop within the current message; truncated responses keep served boundary whitespace but reject inserted text. Review. Minsky and McCarthy reviewed pre-fix head Findings addressed during review.
Deferred / follow-ups.
|
Exact replay exposed a rerendering bug: replacing a complete native tool response left rendered closing markup behind. Later histories then acquired different prefixes and counted canonical action tokens twice. Extend complete sampled responses through the renderer-proven assistant stop, bounded to the current message. Adjacent assistant messages can share a role mask; a matching completed-message render now proves the boundary before expansion. Preserve additional served whitespace before a truncated response's proven stop tail without accepting changed stop tokens or other inserted text.
Validation
33467475revision. The formerly failing capture selects exactly 7,418 canonical tokens instead of 12,063.3e201039fpasses: 785 Megatron tests; 1,629 unit tests passed, 73 skipped, 2 deselected by the existing workflow; lint, format, type, and lock checks passed.33467475passes both Adam updates, publication, checkpoint verification (124 files; all 41,460 optimizer states at step 2), and final validation on 32 fresh generations. The review fix at3e201039fhas regression and saved-input equivalence checks; no new GPU run was launched. GPU qualification uses deployed Caladan protocol 7 and does not qualify protocol-8 migration.Related Caladan #441. Qualification report. Local review packet:
/home/brad/.local/share/neumann/056-smoke-20260916/HAYEK_REVIEW.md.