feat: ~1M context floor for role picks; docs, tests, dead-sort removal #1
Loading…
Reference in a new issue
No description provided.
Delete branch "context-floor-and-role-picks"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a real context-window constraint to the analyzer and records the rules the
2026-09-11 role cut was actually made on.
Tool
context_lengthfrom the models API was being fetched and thrown away; it isnow used. New
--min-context(1m/256k/ raw int) filters before thePareto and knee maths, a
Ctxcolumn shows every row's window, andmin_contextis echoed in--json.floor, so they drop out rather than silently topping the frontier.
Tests / CI
test_openrouter_pareto.py: offline self-check for the size helpers(suffixes, case, floats, junk rejection, inclusive floor). Wired into the
smoke workflow, which stays network-free by design.
Docs + skill
smol.slow/task; intelligence ranksplan/advisor, with tau2 only a floor for the advisor since it readstool-use transcripts. Rank on marginal $ per intelligence point, and compare
in-family variants before paying a tier up.
key (e.g. inside
retry:) is parsed as that key's child and silently ignored,so the file reads correct while OMP uses defaults. Verify the effective value
with
omp config get, never the file.advisorpick in the skill, which contradicted thedecision it was illustrating.
Cleanup: removed an unused re-sort in
compute_pareto_frontier.Verified:
py_compile,test_openrouter_pareto.py,--help, a live--jsonrun, and-b hle --cost-metric task --min-context 1mall pass.