agent-afk 5.235.1 → 5.236.0

package/dist/agent/gh-fix-of-fix.d.ts

@@ -0,0 +1,18 @@
+import type { ExecFn } from './gh.js';
+export declare const FIX_OF_FIX_WINDOW_DAYS = 7;
+export declare const FIX_OF_FIX_LABEL = "fix-of-fix";
+export declare function extractReferencedPrNumbers(text: string): number[];
+export declare function getPrMergedAt(prNumber: number, execFn?: ExecFn): Promise<string | null>;
+export declare function isMergedWithinDays(mergedAt: string, withinDays: number, now?: Date): boolean;
+export declare function ensureFixOfFixLabel(execFn?: ExecFn): Promise<void>;
+export declare function applyFixOfFixLabel(prNumber: number | string, execFn?: ExecFn): Promise<void>;
+export interface FixOfFixResult {
+    isFixOfFix: boolean;
+    recentlyMergedRefs: number[];
+    allRefs: number[];
+}
+export declare function detectAndLabelFixOfFix(currentPrNumber: number | string, prBodyOrTitle: string, opts?: {
+    execFn?: ExecFn;
+    now?: Date;
+    windowDays?: number;
+}): Promise<FixOfFixResult>;

package/dist/bundled-plugins/awa-bundled/skills/ground-state/SKILL.md

@@ -66,6 +66,31 @@ Return: relevant facts with 1-line summaries, **plus the stores actually consult
 
 Read `SPINE.md` from the repo root (same directory as `AFK.md`). If the file does not exist or is empty, skip silently -- do not mention it in the snapshot. If it exists and has entries, extract its invariant (INV-*), rejected-pattern (REJ-*), and taste entries (TST-*) and include them in the snapshot so architectural constraints are visible before proposing changes.
 
+### Eval-pipeline recency survey *(bash — software domain only)*
+
+For software-domain sessions, check whether the eval-run pipeline is current. This guard catches silent regressions that accumulate when the pipeline goes unrun during high-velocity sprints.
+
+Run:
+```
+tail -1 ~/.afk/agent-framework/improve/eval-runs/.index.jsonl 2>/dev/null
+```
+
+Parse the `timestamp` field from the output. Then compute the age in days relative to today's date.
+
+**Threshold**: Read `AFK_EVAL_STALENESS_DAYS` from the environment (default: 7). If the env var is `0`, skip this check silently.
+
+**Surface as a warning finding when any of these are true:**
+- The index file does not exist → `⚠ Eval-pipeline has NEVER run. Run \`afk improve eval-run\` to establish a baseline.`
+- The file exists but the timestamp is absent or unparseable → `⚠ Eval-pipeline recency guard: index unreadable.`
+- Age in days ≥ threshold → `⚠ Eval-pipeline is STALE: last eval-run was N days ago (exceeds AFK_EVAL_STALENESS_DAYS=N threshold). Run \`afk improve eval-run\`.`
+
+Skip this check silently when:
+- Domain is not `software`, OR
+- Working directory has no `package.json` / `pyproject.toml` / `Cargo.toml` / `go.mod` at root level (heuristic that this is not a software project), OR
+- `AFK_EVAL_STALENESS_DAYS=0`.
+
+Include the result (fresh or warning) in the Implementation risks line of the snapshot.
+
 ## Synthesis
 
 Assemble the survey results into a ground-truth snapshot (6 lines minimum, 7 when SPINE.md has entries):
@@ -74,7 +99,7 @@ Assemble the survey results into a ground-truth snapshot (6 lines minimum, 7 whe
 - Infrastructure: CI present? package scripts? authoritative configs for this task
 - Memory hits: facts (1-line each) + which stores were consulted, or `none (consulted: …)`
 - Spine constraints *(only when SPINE.md exists with entries)*: INV-*, REJ-*, TST-* entries. Omit this line entirely when SPINE.md is absent or empty.
-- Implementation risks: e.g. "branch is `main`, don't edit directly"; "CI runs on push"; "memory says prior attempt used approach X"
+- Implementation risks: e.g. "branch is `main`, don't edit directly"; "CI runs on push"; "memory says prior attempt used approach X"; include any eval-pipeline staleness warning here.
 - Epistemic confidence: `<high|medium|low>` — based on how much state could be verified. Flag if working directory is sparse, if domain is unfamiliar, or if key artifacts may be missing.
 
 Surface the snapshot and stop. The orchestrator then uses these verified facts — not assumptions — to decide the next step. This skill never edits files.

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

@@ -124,6 +124,40 @@ gh pr create \
 
 PR bodies are markdown: they routinely carry backticks (inline code), `$(...)`, and quotes. **Never** inline the body as `--body "$(cat <<'EOF' … EOF)"` — the shell parses backticks/`$(` inside the command substitution before `gh` ever runs, so the call fails (or worse, opens the PR with a truncated/garbled body and you don't notice). `--body-file` reads the file verbatim: no shell quoting, no escaping. Only `--title` stays inline — keep it a single plain line with no backticks.
 
+**Phase 8b — Fix-of-fix detection (runs immediately after the PR URL is returned by Phase 8).**
+Scan the PR title and body for cross-references to other PRs. If any referenced PR was merged within the last 7 days, apply the `fix-of-fix` label and record a structured metadata block.
+
+```
+# 1. Extract referenced PR numbers from the PR body using the patterns:
+#    #NNNN, fix(#NNNN), regression from #N, follow-up to #N, addresses #N,
+#    fixes/closes/resolves #N
+#
+# 2. For each referenced PR number (excluding the current PR):
+gh pr view <N> --json mergedAt --jq .mergedAt
+#    If mergedAt is non-null and within 7 days → it qualifies.
+#
+# 3. If any qualify:
+gh label create fix-of-fix \
+  --description "PR that fixes a bug introduced by a recently-merged PR (merged within 7 days)" \
+  --color D93F0B --force
+gh pr edit <current-PR-number> --add-label fix-of-fix
+#
+# 4. Append a machine-readable cross-reference section to the PR body:
+gh pr edit <current-PR-number> --body-file <updated-body-file>
+```
+
+Structured metadata to append (only when fix-of-fix is detected):
+
+```markdown
+## Cross-references
+
+<!-- fix-of-fix: true -->
+<!-- referenced-prs: <N1>, <N2>, ... -->
+Recently-merged PRs referenced by this fix: #N1, #N2, …
+```
+
+**Skip gracefully** when `gh` is unavailable or any step fails — the PR is already open and that is the deliverable. Never abort Phase 8b failure back to the user as a blocking error; log a one-line note instead (e.g. `fix-of-fix detection skipped: <reason>`).
+
 **Phase 9 — Reclaim the worktree.**
 Skip entirely unless the work you just shipped lives under `.afk-worktrees/` (check the invocation cwd from Phase 1 — if the path has no `.afk-worktrees/` segment, there is nothing to reclaim; go straight to the PR URL).