chore: gardener housekeeping 2026-03-23

AGENTS.md watermarks refreshed to HEAD (209e0c7). Key content updates:
- root AGENTS.md: added packages/analytics/ to directory map
- landing/AGENTS.md: documented @harb/analytics integration and Umami funnel tracking
- web-app/AGENTS.md: documented analytics events (wallet_connect, swap_initiated, stake_created)
- onchain/AGENTS.md: documented AttackRunner fixes (taxRate as index, vm.warp, same-broadcast recenter), 2000-trade floor-ratchet evidence

Pending actions (6): promote #1083 and #1086 to backlog, unblock #1099.

gardener/pending-actions.json

@@ -1,52 +1,32 @@
 [
+  {
+    "action": "edit_body",
+    "issue": 1086,
+    "body": "Flagged by AI reviewer in PR #1065.\n\n## Problem\n\nBoth `candidate_commit` and `methodology` were added to `evidence/README.md` without a corresponding schema update. Future red-team runners have no schema definition for these fields, and automated validators may reject the file.\n\n## Affected files\n\n- `evidence/README.md` — add schema entries for `candidate_commit` and `methodology` fields\n\n## Acceptance criteria\n\n- [ ] `evidence/README.md` schema section defines the `candidate_commit` field (commit SHA of the optimizer candidate under test)\n- [ ] `evidence/README.md` schema section defines the `methodology` field (how the red-team run was conducted, e.g. snapshot-isolation)\n- [ ] Schema changes are backward-compatible with existing evidence JSON files\n\n## Related\n\n- #1083 (sibling — snapshot-isolation methodology doc for lm_eth fields)\n\n---\n*Auto-created from AI review of PR #1065*"
+  },
   {
     "action": "add_label",
+    "issue": 1086,
+    "label": "backlog"
+  },
+  {
+    "action": "edit_body",
+    "issue": 1083,
+    "body": "Flagged by AI reviewer in PR #1065.\n\n## Problem\n\n`evidence/README.md` is silent on whether `lm_eth_before`/`lm_eth_after` reflect cumulative or per-attack-reverted state. Now that snapshot isolation is the standard practice, the schema should define this so the fields are unambiguous to future test runners and the planner.\n\n## Affected files\n\n- `evidence/README.md` — add snapshot-isolation methodology section defining lm_eth field semantics\n\n## Acceptance criteria\n\n- [ ] `evidence/README.md` schema defines that `lm_eth_before`/`lm_eth_after` reflect per-attack state after snapshot isolation (not cumulative historical balance)\n- [ ] Schema clarifies that each attack begins from the same initial state via `vm.snapshot()`/`vm.revertTo()`\n- [ ] Schema clarifies that snapshot isolation is the standard methodology for all red-team runs\n\n## Related\n\n- #1086 (sibling — candidate_commit and methodology field schema)\n\n---\n*Auto-created from AI review of PR #1065*"
+  },
+  {
+    "action": "add_label",
+    "issue": 1083,
+    "label": "backlog"
+  },
+  {
+    "action": "remove_label",
     "issue": 1099,
-    "label": "backlog"
-  },
-  {
-    "action": "add_label",
-    "issue": 1100,
-    "label": "backlog"
-  },
-  {
-    "action": "add_label",
-    "issue": 1101,
-    "label": "backlog"
+    "label": "blocked"
   },
   {
     "action": "comment",
-    "issue": 1103,
-    "body": "Closing as actioned. This prediction was logged and labeled prediction/actioned. The underlying issue (preflight.sh CI DB unreachable) has been noted by the team. Closing to keep the backlog clean."
-  },
-  {
-    "action": "close",
-    "issue": 1103,
-    "reason": "prediction actioned and stale"
-  },
-  {
-    "action": "comment",
-    "issue": 1107,
-    "body": "Closing as actioned. The double-crash on 2026-03-21 was transient — subsequent gardener runs including 2026-03-22 06:00 and 2026-03-23 07:03 completed successfully (PHASE:done). No recurring crash pattern observed. Closing."
-  },
-  {
-    "action": "close",
-    "issue": 1107,
-    "reason": "transient crash resolved — subsequent runs successful"
-  },
-  {
-    "action": "comment",
-    "issue": 1020,
-    "body": "Closing: evidence/evolution/ now contains data (best.push3). The fitness baseline absence predicted here has been resolved."
-  },
-  {
-    "action": "close",
-    "issue": 1020,
-    "reason": "evidence/evolution/ now populated with best.push3"
-  },
-  {
-    "action": "comment",
-    "issue": 1022,
-    "body": "Partial resolution: evidence/holdout/ now contains 2026-03-22-issue517-adversarial-lp.json. evidence/user-test/ remains empty — UX conversion signal still absent. Keeping open for user-test gap."
+    "issue": 1099,
+    "body": "Unblocked: all upstream prerequisites (#1031, #997, #1067, #1054) closed. Dev-agent attempted PR #1139 but CI exhausted — blocked label removed so issue re-enters the queue for retry."
   }
 ]