You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Claiming as Dev-1. Branch dev1/fix/1259-turn-split-followups off mainad0790aa191613e697977d2f6ba201e63ba8d3a0 (the #1252 merge); the base is re-read at push. WIP slot is free — #1289 (Fixes #1252) merged at that commit, so this is the one issue in flight.
What I take from this issue, red first, one test per item:
Report §2 / §4 moment. §2's "fixed characters per call" is each Session's first call (fixedChars: usable[0] in fitFixed, core/dev/turn-split.mjs), while §4 counts the sample turn's last call. I will make the report say which moment it is, and pin the choice in the script's own output so the two tables cannot drift apart again.
§5 / §7 / §8 have no reproducible command. I will add the statistics mode those sections need (per-turn-part shares and the R2/fixed-block ratios they quote), print the command that reproduces each number under the section, and re-derive the quoted values from it rather than leaving hand-counted numbers.
The two throwing edges.fitFixed can return charsPerToken: null (slope ≤ 0) and the turns summary calls .toFixed(2) on the median of that list — safe only while fewer than half the Sessions degenerate; and localDay lets an unknown --tz reach Intl.DateTimeFormat as an uncaught RangeError. Fix: filter the non-finite fits before the median, and validate --tz up front with a die that names the zone.
patches/ds-bot/files/dev/turn-split.mjs is a whole-file mirror of the script, so it is regenerated by node scripts/ds-bot-patches.mjs generate (never hand-edited), then check must print its three ok lines. The report is docs/reports/2026-10-26-turn-input-split.md; if a changed section needs a doc page, docs/subsystems/ds-bot-core.md rides in the same commit.
agent-working: this token cannot add labels (403 Must have admin rights to Repository), so this comment and the branch are the record. I stand down if a PR or a competing claim appears.
Activity
feat(dev): split one turn's prompt into fixed block, history, tool re…
HugoXK commentedon Oct 27, 2026
Claiming as Dev-1. Branch
dev1/fix/1259-turn-split-followupsoffmainad0790aa191613e697977d2f6ba201e63ba8d3a0(the#1252merge); the base is re-read at push. WIP slot is free —#1289(Fixes #1252) merged at that commit, so this is the one issue in flight.What I take from this issue, red first, one test per item:
fixedChars: usable[0]infitFixed,core/dev/turn-split.mjs), while §4 counts the sample turn's last call. I will make the report say which moment it is, and pin the choice in the script's own output so the two tables cannot drift apart again.fitFixedcan returncharsPerToken: null(slope ≤ 0) and the turns summary calls.toFixed(2)on the median of that list — safe only while fewer than half the Sessions degenerate; andlocalDaylets an unknown--tzreachIntl.DateTimeFormatas an uncaughtRangeError. Fix: filter the non-finite fits before the median, and validate--tzup front with adiethat names the zone.patches/ds-bot/files/dev/turn-split.mjsis a whole-file mirror of the script, so it is regenerated bynode scripts/ds-bot-patches.mjs generate(never hand-edited), thencheckmust print its threeoklines. The report isdocs/reports/2026-10-26-turn-input-split.md; if a changed section needs a doc page,docs/subsystems/ds-bot-core.mdrides in the same commit.agent-working: this token cannot add labels (403 Must have admin rights to Repository), so this comment and the branch are the record. I stand down if a PR or a competing claim appears.fix(report): point the three turn-split commands at the script's real…