v0.4.2 — activate Jev latest alias

Fixes the OpenRouter Decisions model identifier to use the ~typesafe/jev-latest moving alias. This makes Jev the actual primary classifier instead of immediately falling back to the chat classifier.\n\nVerified with the full test suite, build, package dry-run, and live OpenRouter gateway probes returning classifier: "jev".

v0.4.1 — executable gateway hotfix

This hotfix preserves the executable mode and npm bin mapping for switchyard-gateway. It also adds a manifest regression test and a clean npm publish dry-run check before release.

All Jev-first classifier functionality from v0.4.0 is included.

v0.4.0 — Jev-first classification

Switchyard now uses TypeSafe Jev through OpenRouter Decisions as its primary remote task classifier. Invalid, unavailable, or low-confidence decisions fall back to the existing chat classifier and then to local keyword classification.

This release also adds bounded decision caching and outage cooldowns, keeps explicit task constraints authoritative, excludes decision-only models from execution, adds deterministic classifier evaluation, and documents the remote-classification privacy boundary.

See CHANGELOG.md for the complete release notes.

v0.3.6

Fixed

• Align keyword uncertainty with all six complexity boundaries.
• Preserve Pi/OMP admission decisions with explicit notify, escalate, and ignore policies.
• Route with live host context/tool constraints and optional operator constraints.
• Smooth verified outcome history by sample size, recency, complexity, and privacy-safe project scope.

Closes #5, #6, #7, and #8.

v0.3.5

Fixed

• Keep cold-start benchmark priors separate from measured outcome history.
• Refresh Pi/OMP catalog and Codex capacity during long-running sessions.
• Learn model quality only from explicit failures and verified outcomes.

Added

• Add opt-in Pi/OMP routing through switchyard/auto, including OMP prewalk handoffs.
• Add commands to mark the last routed run as verified successful or failed.

v0.3.4

Fixed

• OpenCode now reuses its saved OpenRouter API credential automatically.
• An explicit OPENROUTER_API_KEY still takes precedence.

v0.3.3

Added

• Add native Oh My Pi plugin discovery alongside the existing Pi extension manifest.
• Document OMP installation and clarify how Switchyard model routing complements OMP's built-in automatic reasoning-effort selection.

v0.3.2

What changed

• Classify Pi tasks with a compact, cached repository profile built from project structure, safe manifest metadata, and Pi-loaded context files.
• Keep classifier cache entries isolated per codebase and work without AGENTS.md, CLAUDE.md, or a known manifest.
• Prevent project context from lowering complexity that is explicit in the current task.
• Document the privacy boundary and the projectContext opt-out.

Verification

• 93 tests passed
• TypeScript typecheck passed
• All workspaces built
• npm package dry-run verified @vepando/switchyard@0.3.2

Switchyard v0.3.1

OpenCode integration

• Install with one opencode plugin @vepando/switchyard command.
• Register switchyard/auto automatically through the documented config hook.
• Close plugin-owned gateways cleanly when OpenCode disposes the plugin.
• Add regression and black-box coverage for OpenCode model discovery.

Package migration

• Adds a compatibility bridge for the historical @vepando/switchyard-opencode package; new installs should use @vepando/switchyard.

v0.3.0 — one package, safer routing

Switchyard 0.3.0 consolidates Pi, OpenCode, and the OpenAI-compatible gateway into one self-contained public package: @vepando/switchyard.

Highlights:

• One npm install for Pi, OpenCode, and gateway clients.
• Safer Codex subscription routing that preserves supported instructions and keeps tools, multimodal input, and unsupported controls on API models.
• Valid API fallback after Codex failures, side-effect-free explain mode, and OpenAI-compatible streaming chunks.
• Correct handling of zero-percent outcome signals, real Pi Codex model IDs, and interrupted runs.
• Professional README, security policy, contribution guide, changelog, and release documentation.
• Trusted npm publishing through GitHub Actions with provenance and exact tag/version validation.

Validation:

• Typecheck passed.
• 84 tests passed across 8 test files.
• Release bundle and npm tarball checks passed.
• Pi, OpenCode, and gateway entry points loaded from a clean tarball installation.

See CHANGELOG.md for the detailed list of changes.