You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simplify feedback API to download-intent model; fix invalid non_responsive outcome
The feedback API is consolidated onto recordDownloadFeedback(intentId, outcome,
notes), which reports outcomes against the download intent created when a case
is downloaded for application. The prior recordApplicationResult/confirmCase/
refuteCase surface (keyed to a bare case ID) is removed in favor of this single
path, matching how the Cases API actually links reputation to download intents.
Also fixes recordDownloadFeedback and the GitHub Action's entrypoint accepting
"non_responsive" as a caller-supplied outcome: the Cases API's outcome alias
map (atvp-feedback-gateway.js) has no such entry, so every call using it would
have failed. That state is detected automatically by the server on deadline
timeout, not reported by a caller. Valid outcomes are now confirm, refute,
derive, and rollback, matching the server exactly.
Verified end-to-end: registered a real user, created a real API key, downloaded
a real case bundle to create a download intent, then ran the GitHub Action's
entrypoint.mjs (using the published @querykey-research/atvp-client package)
against a local server — feedback was recorded successfully. 38/38 unit tests
pass.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Creates a derived case when a published error signature reappears. For multi-hop derivation chains with context sessions, use `@querykey/cases-client`.
@@ -166,7 +142,7 @@ Runs a shell command and returns an evidence object `{ command, exitCode, output
Copy file name to clipboardExpand all lines: docs/github-action/README.md
+11-20Lines changed: 11 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@
2
2
3
3
GitHub Action to record the outcome of a fix application to the [QueryKey Cases](https://www.querykey.com) ATVP ledger.
4
4
5
+
In ATVP, application feedback is keyed to a **download intent** — the intent created when an agent downloads a published case to apply it. This action records the outcome against that intent.
6
+
5
7
## Usage
6
8
7
9
Add this step after your deployment to record whether the fix held:
@@ -11,43 +13,32 @@ Add this step after your deployment to record whether the fix held:
11
13
uses: querykey/record-fix-action@v1
12
14
with:
13
15
api_key: ${{ secrets.QUERYKEY_API_KEY }}
14
-
case_id: ${{ env.CASE_ID }}
15
-
result: success
16
+
intent_id: ${{ env.ATVP_INTENT_ID }}
17
+
outcome: confirm
16
18
notes: "Deployed to production, smoke tests passed"
17
-
evidence_command: "bash scripts/check.sh"
18
19
```
19
20
20
21
## Inputs
21
22
22
23
| Input | Required | Default | Description |
23
24
| :--- | :--- | :--- | :--- |
24
25
| `api_key` | **Yes** | — | QueryKey API key |
25
-
| `case_id` | **Yes** | — | ATVP case ID to record feedback for |
0 commit comments