Migrated from spboyer/waza#438
Summary
waza check currently has a binary token budget result: pass or fail. There's no warning state for skills approaching the limit.
Desired Behavior
Three-state token budget display in waza check:
| State |
Condition |
Display |
| Pass |
tokens < warning_threshold |
320/500 |
| Warning |
warning_threshold <= tokens < limit |
480/500 |
| Error |
tokens >= limit |
620/500 |
Config
warning_threshold already exists in .waza.yaml and is used by waza tokens profile, but waza check ignores it. Wire it into the TokenBudgetChecker and summary table.
Changes Needed
internal/checks/token_budget.go - Add Warning bool field to result
cmd/waza/cmd_check.go - Three-state logic in display and summary table
- CI exit code: warning = 0 (pass), error = 1 (fail)
Summary
waza checkcurrently has a binary token budget result: pass or fail. There's no warning state for skills approaching the limit.Desired Behavior
Three-state token budget display in
waza check:320/500480/500620/500Config
warning_thresholdalready exists in.waza.yamland is used bywaza tokens profile, butwaza checkignores it. Wire it into the TokenBudgetChecker and summary table.Changes Needed
internal/checks/token_budget.go- Add Warning bool field to resultcmd/waza/cmd_check.go- Three-state logic in display and summary table