[I] bug(cli): Runtime Host TUI can omit or retain stale ctx status [maka]

["uzqw (via GitHub)" <gi...@apache.org>]

uzqw opened a new issue, #3607:
URL: https://github.com/apache/maka/issues/3607

   ## What happened
   
   The Runtime Host-backed TUI can fail to show an accurate `ctx` segment even when the selected model has a known context window:
   
   - model discovery may return only a model ID, so the TUI does not receive the model's built-in context-window metadata and omits `ctx` entirely;
   - after a completed turn, the durable `token_usage` message does not contain `contextRemaining`, and the terminal transcript refresh does not reconcile usage, so the footer can remain `ctx ?/window` instead of showing measured usage;
   - after switching models, the previous model's measured `contextRemaining` can be interpreted against the new model's window, briefly showing a stale or misleading percentage.
   
   Expected: a known model window always gives the TUI a stable `ctx ?/window` fallback, a completed turn upgrades it to `ctx used/window pct%`, and changing models clears the old measurement until the new model reports usage.
   
   This is a Runtime Host propagation/reconciliation gap related to, but separate from, #3371.
   
   ## How to reproduce
   
   1. Configure a Runtime Host connection whose model discovery entry contains only an ID but whose context window exists in built-in metadata (for example `opencode-go` / `muse-spark-1.2-contributor`).
   2. Start the TUI on that model.
   3. Submit a prompt and wait for the turn to complete.
   4. Observe that the footer may omit `ctx` or remain at the unknown fallback instead of showing measured context usage.
   5. Switch to a model with a different context window and observe that the old measurement may be reused against the new window.
   
   ## Environment
   
   - Maka commit: `efddab2fb`
   - Surface: TUI / CLI via Runtime Host
   - OS: Linux
   - Node.js: >=22.19.0
   
   ## Acceptance criteria
   
   - Runtime Host model choices resolve context windows using declared/provider/static model facts, not only discovery payload fields.
   - Durable and live `token_usage` messages expose the same `contextRemaining` value when it can be computed.
   - A terminal transcript replacement refreshes the TUI usage summary from durable messages.
   - Switching models clears the prior model's measured `contextRemaining`; with a known new window the footer shows `ctx ?/window` until new usage arrives.
   - Existing omit-when-window-unknown behavior and context warning thresholds remain unchanged.
   
   _Issue drafted with AI assistance (Maka)._


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org

Re: [I] Opened in error; no action requested [maka]

["uzqw (via GitHub)" <gi...@apache.org>]

uzqw closed issue #3607: Opened in error; no action requested
URL: https://github.com/apache/maka/issues/3607


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org