Skip to content

chore: sync upstream (thinking_retention #88, fastokens removal #95, dyn-versioning #96) + migrate gemma4#10

Merged
joanvelja merged 5 commits into
mainfrom
chore/sync-upstream-thinking-retention
Jun 27, 2026
Merged

chore: sync upstream (thinking_retention #88, fastokens removal #95, dyn-versioning #96) + migrate gemma4#10
joanvelja merged 5 commits into
mainfrom
chore/sync-upstream-thinking-retention

Conversation

@joanvelja

Copy link
Copy Markdown
Owner

Syncs renderers fork to upstream main (3 commits: PrimeIntellect-ai#88 thinking_retention refactor, PrimeIntellect-ai#95 remove fastokens, PrimeIntellect-ai#96 dynamic versioning). Conflicts: only 2 versioning config files (resolved take-upstream). client.py untouched upstream (routed-experts safe).

gemma4 (fork-only) migrated to the new thinking_retention API (render + bridge, matches glm5/deepseek_v3 idiom; implied='all'). Proven via real differential rendering vs current (gemma-4-26B tokenizer, 16 convos x 3 policies):

  • render hot path + debate bridge: 1:1 (token-identical).
  • behavior changes (deliberate consistency fixes): full-render default now KEEPS past thinking (matches what the bridge always did via token reuse); tool_cycle bridge rerenders at a new user-query boundary.
  • gemma4 tests 22/22, ruff clean. test_gemma4.py adapted for Remove fastokens entirely PrimeIntellect-ai/renderers#95 load_tokenizer signature.

qwen35 differential verification in progress (separate; PrimeIntellect-ai#88 also touched it).

@joanvelja joanvelja force-pushed the chore/sync-upstream-thinking-retention branch from 85ad64e to 197a9f0 Compare June 27, 2026 21:47
…ate hot path 1:1, full-render keeps thinking) + fastokens test fix
@joanvelja joanvelja force-pushed the chore/sync-upstream-thinking-retention branch from 197a9f0 to 86afca1 Compare June 27, 2026 22:08
@joanvelja joanvelja marked this pull request as ready for review June 27, 2026 23:18
@joanvelja joanvelja merged commit 9de2e8d into main Jun 27, 2026
6 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.

2 participants