Peritus v0.1.9

Peritus 0.1.9

Peritus now uses the selected hosted route and model's actual advertised token capacities throughout
its coding loop. Large-context models no longer inherit a universal 32,768-input / 4,096-output
ceiling from the generated fallback profile. This release is developed on develop, merged into
main, and tagged v0.1.9.

• Resolve route-specific input, output, and shared-context metadata before context selection,
  compaction, request negotiation, and generation. Model switches reuse the catalog while selecting
  the new model's own capacities. Review and fixer evidence projection use prepared metadata too.
• Distinguish a shared input-plus-output window from separate input and output maxima. Uncapped
  turns use the shared input window with minimum reply space; generation fits its output allowance
  to the remaining context and model maximum. A large output maximum is not reserved on every turn.
• Preserve deliberate fixed profiles through discover_model_limits = false. Existing generated
  32K/4K pairs automatically use discovery; other custom pairs stay fixed unless explicitly enabled.
  Missing metadata fields keep configured fallbacks. Compatible endpoints and account providers
  retain their existing configured behavior.
• Avoid repeated metadata loading during normal turns and model selection. Hosted HTTP catalog
  failure retains fallbacks without repeating discovery on every tool turn; explicit refresh can
  update the catalog. OpenCode retains its required exact-model catalog admission.

The live OpenCode Zen and Go SDK catalogs both advertised a 1,000,000-token shared window and
384,000 maximum output for deepseek-v4.1-flash during this campaign. These are route observations,
not a promise that every provider carrying the same model offers identical capacities. An uncapped
input target is now 999,999 tokens on those routes; the normal 85% compaction trigger is roughly
850K tokens. Explicit output allowances reserve their requested space. OpenCode output control
remains advisory because its runtime does not expose exact output-token enforcement.

The real-testing report and
compact evidence record actual provider catalogs,
configuration policies, model switches, durable-memory readbacks, and live inference. The final
campaign made nine actual inference requests: DeepSeek handled 82K+ estimated input without
compaction and returned exact fixture-file contents; the fixed 32K comparison compacted history;
an actual Codex account run retained its configured limits and completed its file-read workflow.
Six models from the real hosted HTTP catalog also resolved their own capacities.

The completed evidence is reused for this release. No unit, mock, formal-verification, or repository
qualification suites were run. The campaign did not execute full 1M-token inference, generate
384K output, or establish Go subscription entitlement; Go coverage is catalog/selection/policy
operation. Other hosted HTTP inference and UI onboarding were not repeated. Native packaging
builds all six supported OS/architecture packages and operates actual installation, offline
terminal startup, and clean shutdown on the four Unix hosts.

Rust and WebUI version metadata is synchronized to 0.1.9; external dependency pins are unchanged.
Deep Research remains separately distributed through the module market with the same wire contract.

All six native platform packages built successfully. Actual installation, offline terminal connection, clean client exit, and daemon shutdown passed on all four Unix hosts. Package manifests, checksums, and source provenance were checked against cdf106c9b0b13d50446e33606511fec15ce03f6f.

Native build run: https://github.com/Corvidae-Coding-Projects/Project-Peritus/actions/runs/39553792906