From 3f0c8d5342ec29bc72bae5ceaf0a2005abb624bf Mon Sep 17 00:00:00 2001 From: johba Date: Wed, 25 Mar 2026 09:36:59 +0100 Subject: [PATCH] =?UTF-8?q?chore:=20planner=20run=20=E2=80=94=20Phase=201?= =?UTF-8?q?=20complete,=20bottleneck=20shifts=20to=20Phase=202=20(#1157)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Automated planner run — prerequisite tree update and journal entry. ## Changes - Phase 1 marked DONE (E2E quality gate, conversion funnel, analytics, release pipeline) - Bottleneck shifted to Phase 2 launch preparation - New issues filed: #1155 (pitch deck), #1156 (wallet connector fix) - Predictions triaged: #1148→#1154, #1149 dismissed, #1150 dismissed, #1141 watching, #1104 dismissed - Priority labels applied to #1154, #1155, #1156 Reviewed-on: https://codeberg.org/johba/harb/pulls/1157 --- AGENTS.md | 4 +-- gardener/pending-actions.json | 33 +-------------------- landing/AGENTS.md | 3 +- planner/journal/2026-03-25.md | 53 +++++++++++++++++++++++++++++++++ planner/prerequisite-tree.md | 55 ++++++++++++++++++++++------------- 5 files changed, 93 insertions(+), 55 deletions(-) create mode 100644 planner/journal/2026-03-25.md diff --git a/AGENTS.md b/AGENTS.md index 0b63999..ae37c13 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,4 +1,4 @@ - + # Agent Brief: Harb Stack ## What is KRAIKEN? @@ -21,7 +21,7 @@ KRAIKEN couples Harberger-tax staking with a dominant Uniswap V3 liquidity manag | `formulas/` | TOML pipeline definitions (sense/act) for the evaluator | [formulas/AGENTS.md](formulas/AGENTS.md) | | `scripts/` | `dev.sh`, bootstrap, build helpers; `harb-evaluator/` red-team agent | [scripts/harb-evaluator/AGENTS.md](scripts/harb-evaluator/AGENTS.md) | | `packages/analytics/` | `@harb/analytics` — self-hosted Umami wrapper for funnel tracking | — | -| `tests/e2e/` | Playwright end-to-end tests | — | +| `tests/e2e/` | Playwright end-to-end tests — desktop + mobile viewports (iPhone 14, Pixel 7), Chromium + Firefox cross-browser matrix; includes conversion funnel spec (`07-conversion-funnel.spec.ts`) | — | | `docs/` | Architecture, product truth, environment, ops guides | — | ## Quick Start diff --git a/gardener/pending-actions.json b/gardener/pending-actions.json index 355c22a..fe51488 100644 --- a/gardener/pending-actions.json +++ b/gardener/pending-actions.json @@ -1,32 +1 @@ -[ - { - "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": "blocked" - }, - { - "action": "comment", - "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." - } -] +[] diff --git a/landing/AGENTS.md b/landing/AGENTS.md index a6e4d6d..3d29943 100644 --- a/landing/AGENTS.md +++ b/landing/AGENTS.md @@ -1,4 +1,4 @@ - + # Landing Interface - Agent Guide Vue 3 + Vite application that delivers the public marketing site and forthcoming staking UI. @@ -39,6 +39,7 @@ The landing page uses `@harb/analytics` (a self-hosted Umami wrapper) for conver - `initAnalytics(VITE_UMAMI_URL, VITE_UMAMI_WEBSITE_ID)` is called in `main.ts` — the Umami `