Repository Jev policy: check current repository instructions and accepted local ADR mapping. Without adoption, do not consult under this policy. For an adopted host scope, before substantive work on a new task or material task/capability change, use eligible jev-capability-advisor Recommend (general/current). Skip unchanged continuations, confirmations, status requests and the consultation itself. Adoption is not host activation, TypeSafe processing consent or qualification. Require explicit scoped processing authority, qualified hook/inventory/delivery and existing credentials. Use reliable current host availability and restrictions; model-visible or installed skills and missing flags are not a complete eligibility export. Respect explicit user choices, explicit-only rules, permissions and Plan/read-only limits. Send a minimal task summary and bounded approved capability metadata, excluding secrets, customer data, private paths, raw prompts/transcripts, unrelated content and tool results; minimization is not guaranteed redaction. Validate returned IDs and retain host execution control. If prerequisites or valid read-only preparation are unavailable, or advice fails/times out/is cancelled, continue native selection and briefly name the unmet obligation in adopted scope. Keep existing request/deadline limits; no new retries, caches, setup or repeated status for skipped messages.
