97e56b9275eb59ca4d0af33dec4efaeb65284818
Real LLM Usage is already recorded (InferenceCompletedEvent.tokensUsed), aggregated per-session (MetricsProjection), exposed via correx stats + server MetricsInspectionService, and rendered in tui-go. The only remaining hardcoded length/4 estimates were the journal context-entry budget and the compaction threshold — both pre-injection (no LLM response exists for the journal text), so estimation is legitimate, but they now use the real tokenizer estimateTokens() for consistency with sibling context entries instead of length/4.
fix: workflow inference chain — surface llama-server errors, user-turn-last, bundle-relative prompts
Description
No description provided
Languages
Kotlin
88.4%
Go
11.4%
Python
0.2%