agent-valley 4.6.0 → 4.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -199,13 +199,16 @@ linear:
199
199
  # comment_relay:
200
200
  # enabled: false
201
201
  # ignore_authors: []
202
- # pull_request_reviews: false
203
202
 
204
203
  workspace:
205
204
  root: /absolute/path/to/target-repo
206
205
 
207
206
  delivery:
208
207
  mode: merge # merge (auto merge+push) or pr (create draft PR)
208
+ # pull_request_reviews:
209
+ # enabled: false
210
+ # webhook_secret: whsec_xxx # Linear tracker only; the GitHub tracker uses github.webhook_secret
211
+ # ignore_authors: []
209
212
 
210
213
  prompt: |
211
214
  You are working on {{issue.identifier}}: {{issue.title}}.
@@ -401,7 +404,9 @@ Alongside Linear, GitHub Issues can drive the orchestrator. Set `tracker.kind: g
401
404
 
402
405
  With `comment_relay.enabled: true` under the active tracker (`github:` or `linear:`), a new comment on an issue whose actor is running reaches that actor as an added instruction. GitHub relays repository owners, members and collaborators and needs the webhook subscribed to **Issue comments**; Linear relays workspace users (members and guests) and needs **Comment** events. Codex receives the comment in the running session; stateless actors such as Claude restart the attempt with it. Agent Valley's own comments (its hidden marker or the `Symphony:` prefix), bots and integrations, outside contributors, `ignore_authors`, edited or deleted comments and pull request comments are not relayed. `ignore_authors` accepts GitHub logins and Linear emails, user ids or names; add the account actors comment with when it is a person's token.
403
406
 
404
- With `pull_request_reviews: true` as well (GitHub tracker only), a submitted review of an open pull request on an Agent Valley branch (`<prefix>/<owner>/<repo>#<issue>`) becomes follow-up work, so PR delivery mode can answer review feedback. The webhook must also send **Pull request reviews**. The same author rules apply, approvals are skipped, and the review summary and its inline comments become the instruction. A running actor receives it like a relayed comment. A delivered issue (Done) is reopened to In Progress and retried with the review as context in the existing worktree; delivery then pushes to the same pull request. Reviews of fork branches, closed pull requests and other branches are ignored. A Linear tracker cannot follow up on GitHub reviews because it has no GitHub webhook receiver.
407
+ ### Pull request review follow-up
408
+
409
+ PR delivery mode can answer review feedback whichever service tracks the issues. With `delivery.pull_request_reviews.enabled: true`, a submitted review of an open pull request on an Agent Valley branch becomes follow-up work for the issue in the branch name (`feature/ACR-42` → Linear `ACR-42`, `feature/my-org/my-repo#42` → GitHub issue #42). Issues and code can live in different places: Linear issues with GitHub pull requests, or GitHub issues in one repository delivered to another. Point a GitHub webhook on each code repository at `/api/webhook/github` with **Pull request reviews**; on repositories other than the GitHub tracker's, send only that event. With the GitHub tracker the endpoint verifies `github.webhook_secret`, so every webhook uses that secret; with Linear, set `delivery.pull_request_reviews.webhook_secret`. Repository owners, members and collaborators count; approvals, bots, `ignore_authors` (GitHub logins), fork branches and closed pull requests are skipped. The review summary and its inline comments, read through the authenticated `gh` CLI that PR delivery already uses, become the instruction. A running actor receives it like a relayed comment. A delivered (Done) issue is moved back to In Progress and retried with the review as context in its existing worktree, after the retry delay; delivery then pushes to the same pull request.
405
410
 
406
411
  ### Observability (v0.2+)
407
412
 
@@ -443,6 +448,10 @@ Failed actor runs are retried with exponential backoff (`60s × 2^(attempt-1)`,
443
448
 
444
449
  On boot, the orchestrator fetches all Todo + In Progress issues from the configured tracker and reconciles the DAG cache. Existing in-progress issues resume automatically.
445
450
 
451
+ ### Durable State
452
+
453
+ Everything the orchestrator must remember across a restart lives in one SQLite file, `.agent-valley/state.db` inside the workspace root: active attempts, the retry queue, pending finalizations, the DAG cache, budget usage and webhook delivery keys. Each store writes in a transaction, so a crash never leaves a half-written record, and a tracker redelivery after a restart is still rejected. The first boot after upgrading imports the earlier `run-state.json`, `dag-cache.json` and `budget-usage.json` snapshots and renames them `*.migrated`.
454
+
446
455
  ---
447
456
 
448
457
  ## Development
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
3
3
  "name": "av",
4
- "version": "4.6.0",
4
+ "version": "4.8.0",
5
5
  "description": "Delegate repository goals to Agent Valley and inspect mission progress and verification evidence.",
6
6
  "author": {
7
7
  "name": "Agent Valley"