Proposal: add an agent-neutral task routing decision tool #5

Motivation

The existing tools can classify items and choose bounded alternatives, but agents still have to assemble the same task-routing questions and policy mapping themselves. A small, typed route decision would let any MCP-compatible agent use Jev for intent, risk, workflow, context, and review gating without coupling the server to Codex, Claude Code, Cursor, OpenCode, or a particular tool name.

Proposed change

Add one jev_route judgment tool that accepts:

• the task text
• the host agent capabilities it can actually use
• optional constraints such as read-only mode or confirmation requirements
• a caller-defined route catalog, or a documented default catalog

Return a typed, agent-neutral decision containing:

• intent and workflow
• risk level
• required capabilities
• context policy
• model tier
• execution mode
• whether review or confirmation is required
• confidence, margin, and an explicit fallback for uncertain decisions

The result must use capability identifiers such as repository.read, repository.edit, command.test, and code.review, rather than client-specific MCP or Skill names. The host agent remains responsible for mapping capabilities to its own tools and enforcing the returned policy.

Deliberate boundaries

• The server does not read repositories, run commands, invoke other MCP servers, apply changes, or implement an agent loop.
• Low-confidence or unsupported routes must return an explicit fallback such as ask_user or default_workflow.
• Existing jev_classify and jev_decide behavior remains unchanged.

Acceptance criteria

• Add the tool only after agreeing on the input and output contract.
• Validate typed answers and confidence/margin conservatively; malformed or incomplete answers cannot produce an automatic route.
• Add offline unit and mock wire tests for high-confidence, low-confidence, missing-capability, and malformed-answer cases.
• Document examples for multiple MCP-compatible agent hosts and explain that enforcement stays with the host.
• Keep the implementation small and provider-neutral.