Conversation
The gate job now builds a state file from the issue, runs actions/jev-decide, writes the type, fields and area labels it decided at or above threshold through actions/set-issue-fields, uploads the decisions as an artifact, and stops before the picker when the text is prompt injection or spam. The agent gets a pre-classification block and the field writer's path instead of inline GraphQL, and still writes the plan or the questions and Triage state. With no AI_GATEWAY_API_KEY the run is unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
azlekov
force-pushed
the
feat/jev-triage-wiring
branch
from
September 18, 2026 08:52
7894445 to
4dc47f1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #40; retarget to
mainonce that merges.What
The triage gate job now builds a state file from the issue (title, body, author type, labels, type, current field values, the repo's area vocabulary, and the last comments on a reopen), runs
actions/jev-decide, and writes the type, fields and area labels it decided at or above threshold throughactions/set-issue-fields. Every run uploads its decisions record as thejev-decisions-<n>artifact. Text addressed to an assistant, or not a real request, stops the run before the picker with a short comment and clearsagent:triage.The agent gets a
## Pre-classificationblock saying what was already set and what is still open, and a call to the exported field writer instead of the inline GraphQL walkthrough. It still writes the plan or the questions andTriage state. The verify step is unchanged.New input
jev-mode(active | shadow | off), new optional secretAI_GATEWAY_API_KEY. Callers usesecrets: inherit, so an org secret needs no caller change. With no key the run is unchanged.Rollout
Set the secret on one repo first. Its artifacts and job summaries are the calibration set;
jev/scripts/eval.tsreports accuracy against final field values per threshold. Promote to the org once the numbers hold.Verification
Self test gains two checks: gate step order (
agent-gate<jev-decide<set-issue-fields<pick-runner, picker guarded ondecide, prompt uses the field writer, verify step present) and the prompt's option table againstpolicy.ts. All checks pass locally.🤖 Generated with Claude Code