agent-afk 5.215.1 → 5.216.0

package/dist/agent/tools/bash-capture-index.d.ts

@@ -0,0 +1,13 @@
+export interface CaptureEntry {
+    sessionId: string;
+    toolUseId: string;
+    filePath: string;
+    mtimeMs: number;
+    sizeBytes: number;
+    preview: string;
+}
+export interface ListCapturesOptions {
+    sessionId?: string;
+    limit?: number;
+}
+export declare function listCaptures(options?: ListCapturesOptions): Promise<CaptureEntry[]>;

package/dist/bundled-plugins/awa-bundled/skills/review/SKILL.md

@@ -17,7 +17,7 @@ Never — not for a real bug, not for a blocking defect, not even when there is
 **Exception:** `gh pr merge` is permitted after a **MERGE** verdict on a PR review in-which the findings are docs/test-related only, but **only** after the user explicitly confirms via `ask_question` (see **Merge offer** below).
 - run any other write- or network-mutating shell command.
 
-The only shell permitted is **read-only inspection**: `git diff` / `git show` / `gh pr diff`, `grep` / `rg`, and file reads — plus dispatching the review sub-agents. Resolving findings, fixing bugs, resolving merge conflicts, and "making the branch mergeable" are explicitly **out of scope**: a fixable defect is a finding to report (`file:line` + a one-line fix in the `suggestion` field), never a license to act.
+The only shell permitted is **read-only inspection**: `git diff` / `git show` / `gh pr diff` / `gh repo view`, `grep` / `rg`, and file reads — plus dispatching the review sub-agents. Resolving findings, fixing bugs, resolving merge conflicts, and "making the branch mergeable" are explicitly **out of scope**: a fixable defect is a finding to report (`file:line` + a one-line fix in the `suggestion` field), never a license to act.
 
 ## Sub-agent contract
 /contract
@@ -144,7 +144,7 @@ State the counts that drove the decision on the same line, **with a dimension br
 
 This is the terminal step. A blocking bug is a finding to report, not a fix to apply -- no edits, commits, pushes, or PR/MR mutations.
 
-**Merge offer (docs/test-only PR reviews).** When **all four** hold: (1) the decision is **MERGE**, (2) the review target was a **PR** (URL or number), (3) every surviving finding is in the `test-coverage` dimension or is a documentation-only concern (comments, doc strings, README) -- no `security`, `correctness`, `api-compat`, `perf-observability`, or `spec-compliance` findings survived, and (4) every changed file in the PR is a test or documentation file (test files: `*.test.*`, `*.spec.*`, files under `__tests__/`, `/test/`, `/tests/`; doc files: `*.md`, `*.mdx`, doc-only config such as `typedoc.json`) -- no production source files changed -- ask the user: "Would you like me to merge this PR?" via `ask_question` with `type: "confirm"`. On accept (`value: true`), run `gh pr merge <pr-ref> --squash --match-head-commit <reviewed-ref>` where `<reviewed-ref>` is the SHA captured at triage time, so the merge is pinned to the exact commit that was reviewed. If `gh pr merge` exits non-zero, surface the error output to the user and stop. On decline, cancel, skip, non-PR target, or any condition not met: stop.
+**Merge offer (docs/test-only PR reviews).** When **all four** hold: (1) the decision is **MERGE**, (2) the review target was a **PR** (URL or number), (3) every surviving finding is in the `test-coverage` dimension or is a documentation-only concern (comments, doc strings, README) -- no `security`, `correctness`, `api-compat`, `perf-observability`, or `spec-compliance` findings survived, and (4) every changed file in the PR is a test or documentation file (test files: `*.test.*`, `*.spec.*`, files under `__tests__/`, `/test/`, `/tests/`; doc files: `*.md`, `*.mdx`, doc-only config such as `typedoc.json`) -- no production source files changed -- ask the user: "Would you like me to merge this PR?" via `ask_question` with `type: "confirm"`. On accept (`value: true`), determine the target repo's preferred merge strategy via `gh repo view <owner>/<repo> --json viewerDefaultMergeMethod` (derive `<owner>/<repo>` from the PR reference, not from the local checkout) and pass the corresponding flag (`--squash`, `--rebase`, or `--merge`) -- a strategy flag is mandatory because `gh pr merge` errors in non-interactive contexts without one. Run `gh pr merge <pr-ref> --<strategy> --match-head-commit <reviewed-ref>` where `<reviewed-ref>` is the SHA captured at triage time, so the merge is pinned to the exact commit that was reviewed. If `gh pr merge` exits non-zero, surface the error output to the user and stop. On decline, cancel, skip, non-PR target, or any condition not met: stop.
 
 **Severity rubric (impact axis only — severity measures blast radius and reachability, never category):**
 - `critical` — data loss, auth bypass, secret exposure, RCE. If it cannot cause unauthorized access or data loss, it is NOT critical.

package/dist/cli/commands/captures.d.ts

@@ -0,0 +1,2 @@
+import { Command } from 'commander';
+export declare function registerCapturesCommand(program: Command): void;