diff --git a/landing/index.html b/landing/index.html index dd881a1..9fdaf7e 100644 --- a/landing/index.html +++ b/landing/index.html @@ -1321,7 +1321,11 @@ npm install https://github.com/PR0M3TH3AN/TORCH/archive/refs/heads/main.tar.gz & 'telemetry-agent': 'πŸ“‘', 'test-coverage-agent': 'β˜”', 'ui-ux-agent': 'πŸ–ΌοΈ', - 'weekly-synthesis-agent': '🧠' + 'weekly-synthesis-agent': '🧠', + 'proposal-triage-agent': 'πŸ—³οΈ', + 'plan-agent': 'πŸ”­', + 'builder-agent': 'πŸ—οΈ', + 'governance-agent': 'βš–οΈ' }; const AGENT_CATEGORIES = { diff --git a/memory-updates/2026-02-21T20-22-32Z__proposal-triage-agent.md b/memory-updates/2026-02-21T20-22-32Z__proposal-triage-agent.md new file mode 100644 index 0000000..d6ed359 --- /dev/null +++ b/memory-updates/2026-02-21T20-22-32Z__proposal-triage-agent.md @@ -0,0 +1,13 @@ +# Memory Update β€” proposal-triage-agent β€” 2026-02-21 + +## Key findings +- The highest-value unblockers remain local and deterministic: missing `npm run format`, missing `src/lib/eventSchemas.js`, and scheduler preflight platform assertion drift. +- Coverage-gap ideas should be split by urgency; low-priority agent additions dilute execution if treated as near-term work. + +## Patterns / reusable knowledge +- Keep backlog focused on `ready-to-plan` items that remove recurring scheduler/test friction before adding net-new agent surface area. +- Retire upstream-only defects from implementation backlog, but retain them in known-issues/incidents for operator visibility. + +## Warnings / gotchas +- `../scheduler-flow.md` links in weekly prompt files resolve to `src/prompts/scheduler-flow.md`; direct parent-relative lookups from repo root can appear missing during manual checks. +- Artifact-verifier failures often stem from metadata/frontmatter omissions rather than code defects; triage should classify these separately. diff --git a/src/backlog/BACKLOG.md b/src/backlog/BACKLOG.md index d067b69..23b9dc9 100644 --- a/src/backlog/BACKLOG.md +++ b/src/backlog/BACKLOG.md @@ -1,106 +1,143 @@ # Implementation Backlog β€” 2026-02-21 ## Triage Summary -- Items evaluated: 12 -- New items added: 12 -- Items retired: 1 -- Items promoted to ready: 4 - ---- +- Items evaluated: 18 +- New items added: 7 +- Items retired: 2 +- Items promoted to ready: 1 ## Priority 1: Ready to Plan ### BACKLOG-001: Add `npm run format` script to package.json -- **Source:** KNOWN_ISSUES.md, style-agent daily failures -- **Impact:** Unblocks `style-agent` (daily cadence β€” currently non-functional) -- **Scope:** Add 1-2 script entries to `package.json` +- **Source:** `KNOWN_ISSUES.md`, `src/todo/TODO_2026-02-18.md` +- **Impact:** Unblocks formatting workflows and prevents repeated `style-agent` no-op/failure risk. +- **Scope:** Add `format` and `format:check` scripts in `package.json`; verify they run in this repo. - **Status:** ready-to-plan -- **Acceptance:** `npm run format` exits 0; `style-agent` completes successfully on next daily run +- **Acceptance:** `npm run format -- --check` and `npm run format:check` execute successfully. ### BACKLOG-002: Create `src/lib/eventSchemas.js` canonical event builders -- **Source:** event-schema-agent failures (2x on 2026-02-14) -- **Impact:** Unblocks `event-schema-agent` (weekly cadence β€” permanently broken) -- **Scope:** Extract event construction from `src/nostr-lock.mjs` into shared module +- **Source:** weekly `event-schema-agent` failures; missing `src/lib/eventSchemas.js` +- **Impact:** Unblocks schema-related weekly work and removes repeated missing-file dead end. +- **Scope:** Extract/centralize lock-event schema builders into `src/lib/eventSchemas.js` and wire current call sites. - **Status:** ready-to-plan -- **Acceptance:** `event-schema-agent` completes successfully; `src/nostr-lock.mjs` imports from new module; existing tests pass +- **Acceptance:** `src/lib/eventSchemas.js` exists, is imported by lock/event code paths, and related tests pass. -### BACKLOG-003: Revise content-audit-agent scope to match TORCH's actual features -- **Source:** docs/agent-handoffs/incidents/2026-02-20-content-audit-no-upload-surface.md -- **Impact:** Eliminates permanent no-op agent run from daily cadence -- **Scope:** Rewrite `src/prompts/daily/content-audit-agent.md` to audit actual TORCH content (docs, prompts, config files) rather than nonexistent upload/contribution features +### BACKLOG-003: Revise `content-audit-agent` scope to TORCH-relevant surfaces +- **Source:** `docs/agent-handoffs/incidents/2026-02-20-content-audit-no-upload-surface.md` +- **Impact:** Replaces a recurring no-op daily run with actionable audits. +- **Scope:** Update the prompt to target real TORCH docs/contracts and expected outputs. - **Status:** ready-to-plan -- **Acceptance:** content-audit-agent produces meaningful audit findings relevant to TORCH's actual codebase +- **Acceptance:** Next `content-audit-agent` run produces findings against existing TORCH files/features. -### BACKLOG-004: Implement prompt graph metadata extraction (Phase 0 of node-based editor) -- **Source:** docs/proposals/node-based-prompt-editor.md -- **Impact:** Machine-readable metadata for all 44+ agent prompts; enables visualization, dependency analysis, and gap detection -- **Scope:** 4 new scripts in `scripts/prompt-graph/`, output to `artifacts/prompt-graph/graph.json` +### BACKLOG-004: Implement prompt graph metadata extraction (Phase 0) +- **Source:** `docs/proposals/node-based-prompt-editor.md` +- **Impact:** Enables prompt fleet visibility, dependency mapping, and higher-quality governance analysis. +- **Scope:** Add extraction/build/validation scripts and emit graph artifact under `artifacts/prompt-graph/`. - **Status:** ready-to-plan -- **Acceptance:** `npm run graph:build` exits 0; `artifacts/prompt-graph/graph.json` contains nodes for all roster agents with extracted metadata +- **Acceptance:** `npm run graph:build` (or equivalent script) generates a valid prompt graph including all roster agents. ---- +### BACKLOG-012: Align scheduler preflight platform assertion with runtime contract +- **Source:** `KNOWN_ISSUES.md` (`KNOWN-ISSUE-scheduler-preflight-platform`), `reports/test-audit/test-audit-report-2026-02-21.md` +- **Impact:** Removes a deterministic false failure in scheduler E2E validation. +- **Scope:** Define a single platform source-of-truth and update scheduler/test expectations accordingly via spec-correction protocol. +- **Status:** ready-to-plan +- **Acceptance:** `node --test test/scheduler-preflight-lock.e2e.test.mjs` passes without weakening scenario assertions. ## Priority 2: Needs Scoping ### BACKLOG-005: Implement `e2e-agent` for scenario-first E2E test maintenance -- **Source:** docs/AGENT_COVERAGE_GAPS.md (priority: HIGH) -- **Impact:** Dedicated maintainer for end-to-end test quality per AGENTS.md scenario-first mandate -- **Scope:** New weekly agent prompt + supporting test infrastructure +- **Source:** `docs/AGENT_COVERAGE_GAPS.md` +- **Impact:** Adds explicit ownership for scenario-level regressions and anti-cheat integrity. +- **Scope:** New weekly agent plus deterministic validation workflow. - **Status:** needs-scoping -- **Open Questions:** What E2E scenarios exist today? What framework to use? What's the sandbox constraint impact? ### BACKLOG-006: Implement `memory-health-agent` for memory subsystem auditing -- **Source:** docs/AGENT_COVERAGE_GAPS.md (priority: HIGH) -- **Impact:** Quality assurance for memory retrieval relevance, embedding health, and pruning effectiveness -- **Scope:** New weekly agent prompt +- **Source:** `docs/AGENT_COVERAGE_GAPS.md` +- **Impact:** Adds quality controls for retrieval relevance and memory lifecycle behavior. +- **Scope:** New weekly agent with measurable health criteria. - **Status:** needs-scoping -- **Open Questions:** What metrics define "healthy" memory? How to test retrieval relevance? -### BACKLOG-007: Implement `relay-health-agent` for relay stability monitoring -- **Source:** docs/AGENT_COVERAGE_GAPS.md (priority: HIGH), recurring relay failures in task-logs -- **Impact:** Automated monitoring and rotation of unhealthy relays in `torch-config.json` -- **Scope:** New weekly agent prompt + relay rotation logic +### BACKLOG-007: Implement `relay-health-agent` for relay stability operations +- **Source:** `docs/AGENT_COVERAGE_GAPS.md`, relay incidents in `KNOWN_ISSUES.md` +- **Impact:** Improves lock reliability and actionable relay operations beyond current preflight checks. +- **Scope:** Define monitor/rotation policy and integration boundaries with existing `lock:health` flows. - **Status:** needs-scoping -- **Open Questions:** Auto-rotation policy? How to detect relay health from sandbox? Quarantine duration? ### BACKLOG-008: Implement project-type prompt packages system -- **Source:** docs/proposals/prompt-packages.md -- **Impact:** Curated agent sets per project type, dramatically improved onboarding for non-TORCH projects -- **Scope:** `torch init` wizard, package metadata schema, dynamic roster generation +- **Source:** `docs/proposals/prompt-packages.md` +- **Impact:** Improves onboarding and relevance outside TORCH’s own repo shape. +- **Scope:** `torch init` package selection, metadata schema, and package-aware prompt installation. - **Status:** needs-scoping -- **Open Questions:** Package registry format? Installation mechanism? Backward compatibility with current flat roster? ---- +### BACKLOG-013: Stabilize `test/memory-telemetry.test.mjs` child-process signal capture +- **Source:** `KNOWN_ISSUES.md` (`KNOWN-ISSUE-memory-telemetry-stdout-stderr`) +- **Impact:** Removes recurring false negatives in memory telemetry test coverage. +- **Scope:** Investigate environment-sensitive stdio capture and replace with deterministic boundary assertions. +- **Status:** needs-scoping + +### BACKLOG-014: Enforce artifact metadata requirements at prompt/template level +- **Source:** `docs/agent-handoffs/incidents/2026-02-20-pr-review-agent-artifact-metadata-failure.md`, `task-logs/daily/2026-02-20T04-25-38Z__load-test-agent__failed.md` +- **Impact:** Reduces scheduler failures due to missing or malformed run artifacts. +- **Scope:** Add explicit metadata template/guardrails for all agent prompts and verify against `verify-run-artifacts` expectations. +- **Status:** needs-scoping + +### BACKLOG-015: Consolidate persistent TODO debt into actionable tracked items +- **Source:** `src/todo/` backlog sprawl, `artifacts/todos.txt` +- **Impact:** Prevents repeated rediscovery loops and improves planner/builder throughput. +- **Scope:** Define archival policy for stale TODO artifacts and create a maintained actionable TODO registry. +- **Status:** needs-scoping ## Priority 3: Deferred ### BACKLOG-009: Build standalone binary distribution (Node.js SEA or pkg) -- **Source:** docs/architecture/distribution-plan.md -- **Impact:** Removes Node.js requirement for non-JS projects -- **Scope:** Build scripts, CI pipeline, release automation, multi-platform binaries +- **Source:** `docs/architecture/distribution-plan.md` +- **Impact:** Removes Node.js runtime requirement for some users. +- **Scope:** Build/release pipeline work across platforms. - **Status:** deferred -- **Blocked By:** Requires external tooling setup (SEA/pkg), CI infrastructure, release management -- **Rationale:** High value but high complexity; core agent pipeline improvements should come first -### BACKLOG-010: Build hosted dashboard at dashboard.torch.sh -- **Source:** docs/architecture/distribution-plan.md -- **Impact:** Shareable lock visibility without local setup -- **Scope:** Static HTML/JS site, GitHub Pages config, CDN setup +### BACKLOG-010: Build hosted dashboard at `dashboard.torch.sh` +- **Source:** `docs/architecture/distribution-plan.md` +- **Impact:** Provides shareable dashboard access without local runtime. +- **Scope:** Hosting/domain/release operational work. - **Status:** deferred -- **Blocked By:** Hosting infrastructure decisions, domain setup -- **Rationale:** Nice-to-have; local dashboard already functional ### BACKLOG-011: Implement `migration-agent` for database migration auditing -- **Source:** docs/AGENT_COVERAGE_GAPS.md (priority: Medium) -- **Impact:** Audit pending migrations, validate rollback scripts -- **Scope:** New weekly agent prompt +- **Source:** `docs/AGENT_COVERAGE_GAPS.md` +- **Impact:** Adds migration-focused audit coverage. +- **Scope:** New weekly agent and migration verification checks. - **Status:** deferred -- **Rationale:** Medium priority; higher-impact gaps should be addressed first ---- +### BACKLOG-016: Implement `prompt-contract-agent` +- **Source:** `docs/AGENT_COVERAGE_GAPS.md` +- **Impact:** Dedicated ownership for prompt-contract drift prevention. +- **Scope:** New weekly agent; likely overlaps with existing prompt-maintenance/governance workflows. +- **Status:** deferred + +### BACKLOG-017: Implement `skills-agent` +- **Source:** `docs/AGENT_COVERAGE_GAPS.md` +- **Impact:** Ongoing maintenance for skill definitions and usage quality. +- **Scope:** New low-priority weekly agent. +- **Status:** deferred + +### BACKLOG-018: Implement `landing-page-agent` +- **Source:** `docs/AGENT_COVERAGE_GAPS.md` +- **Impact:** Dedicated ownership of landing-page updates and release messaging. +- **Scope:** New low-priority weekly agent. +- **Status:** deferred + +## Completed (Last 4 Weeks) +- No backlog-tracked items have been transitioned to `completed` yet. ## Retired -### RETIRED-001: content-audit-agent upload/contribution audit scope -- **Rationale:** TORCH has no upload UI, API, storage, or moderation system. The agent was designed for a different product context and audits features that don't exist. Replaced by BACKLOG-003 which revises the agent's scope to match TORCH's actual features. +### RETIRED-001: `content-audit-agent` upload/contribution audit scope +- **Rationale:** TORCH has no upload/contribution product surface; replaced by `BACKLOG-003` scoped to real TORCH surfaces. +- **Retired:** 2026-02-21 + +### RETIRED-002: `plan-agent-architecture` proposal as a net-new pipeline request +- **Rationale:** Core pipeline agents (`proposal-triage-agent`, `plan-agent`, `builder-agent`) already exist in weekly roster and prompt set; remaining work is tracked as discrete backlog items. +- **Retired:** 2026-02-21 + +### RETIRED-003: Goose Desktop wrapper defects as direct repository backlog items +- **Rationale:** ETXTBSY and exit-code swallowing are upstream Goose wrapper defects outside this repo’s control; keep in `KNOWN_ISSUES.md`/incident notes until upstream remediation lands. - **Retired:** 2026-02-21 diff --git a/src/context/CONTEXT_2026-02-21T20-22-32Z.md b/src/context/CONTEXT_2026-02-21T20-22-32Z.md new file mode 100644 index 0000000..13df87a --- /dev/null +++ b/src/context/CONTEXT_2026-02-21T20-22-32Z.md @@ -0,0 +1,22 @@ +--- +agent: proposal-triage-agent +cadence: weekly +session: weekly-20260221T202232Z-proposal-triage-agent +run-start: 2026-02-21T20:22:32Z +prompt-file: src/prompts/weekly/proposal-triage-agent.md +--- + +Goal +- Re-triage pending proposals, unresolved incidents/issues, and operational dead ends into a single prioritized implementation backlog. + +Scope +- Inputs reviewed: `docs/proposals/*.md`, `docs/AGENT_COVERAGE_GAPS.md`, `KNOWN_ISSUES.md`, `task-logs/daily/`, `task-logs/weekly/`, `artifacts/`, `src/todo/`, `features/`, `docs/agent-handoffs/incidents/`, previous `src/backlog/BACKLOG.md`. + +Constraints +- No implementation planning/build execution in this run. +- Preserve existing backlog IDs and classify by triage status only. +- Keep scheduler-owned completion/logging out of scope for this spawned agent run. + +Issue handling +- No new reproducible issue was discovered during this triage pass. +- Existing unresolved issues remain tracked in `KNOWN_ISSUES.md` and corresponding incident notes; no updates were required in this run. diff --git a/src/decisions/DECISIONS_2026-02-21T20-22-32Z.md b/src/decisions/DECISIONS_2026-02-21T20-22-32Z.md new file mode 100644 index 0000000..be3ae00 --- /dev/null +++ b/src/decisions/DECISIONS_2026-02-21T20-22-32Z.md @@ -0,0 +1,30 @@ +--- +agent: proposal-triage-agent +cadence: weekly +session: weekly-20260221T202232Z-proposal-triage-agent +run-start: 2026-02-21T20:22:32Z +prompt-file: src/prompts/weekly/proposal-triage-agent.md +--- + +Decision +- Reclassify the implementation backlog to prioritize direct unblockers first (format script, missing event schema module, content-audit scope correction, prompt graph extraction, scheduler platform assertion alignment), while deferring lower-impact agent additions and upstream-only external defects. + +Rationale +- Current highest-friction failures are deterministic and local to this repository (`npm run format` absent, missing `src/lib/eventSchemas.js`, scheduler preflight platform mismatch). +- Coverage-gap proposals with lower immediate operational impact (`skills-agent`, `landing-page-agent`) should remain deferred. +- Goose wrapper ETXTBSY/exit-code defects are external to this repository and should be retired from implementation backlog while remaining tracked as operational known issues. + +Scoring notes (weighted: Unblock*3 + Value*2 + Scope*1 - Risk*1) +- BACKLOG-001 `npm run format`: score 14 (high unblock, low risk) -> `ready-to-plan` +- BACKLOG-002 `src/lib/eventSchemas.js`: score 13 (high unblock, bounded scope) -> `ready-to-plan` +- BACKLOG-012 scheduler platform assertion alignment: score 12 (high validation unblock) -> `ready-to-plan` +- BACKLOG-013 memory telemetry capture stabilization: score 8 (valuable but implementation uncertain) -> `needs-scoping` +- BACKLOG-016/017/018 new low-priority agent additions: score <=5 -> `deferred` + +Alternatives considered +- Keep prior backlog unchanged: rejected because it omitted active known-issue backlog items and several coverage-gap entries. +- Promote all coverage-gap agents to `needs-scoping`: rejected to avoid priority dilution and preserve execution focus for plan/builder. + +Consequences +- Plan-agent now has a tighter set of P1 items aligned to active failures. +- Deferred queue remains visible without blocking higher-value remediation. diff --git a/src/test_logs/TEST_LOG_2026-02-21T20-22-32Z.md b/src/test_logs/TEST_LOG_2026-02-21T20-22-32Z.md new file mode 100644 index 0000000..abd032e --- /dev/null +++ b/src/test_logs/TEST_LOG_2026-02-21T20-22-32Z.md @@ -0,0 +1,29 @@ +--- +agent: proposal-triage-agent +cadence: weekly +session: weekly-20260221T202232Z-proposal-triage-agent +run-start: 2026-02-21T20:22:32Z +prompt-file: src/prompts/weekly/proposal-triage-agent.md +--- + +# Test Log β€” proposal-triage-agent β€” 2026-02-21T20:22:32Z + +- Command: `SCHEDULER_CADENCE=weekly SCHEDULER_AGENT=proposal-triage-agent SCHEDULER_PROMPT_PATH=src/prompts/weekly/proposal-triage-agent.md SCHEDULER_RUN_ID=manual-proposal-triage-20260221T152500Z node scripts/memory/retrieve.mjs` + - Result: pass (`MEMORY_RETRIEVED`) + - Notes: Retrieval evidence refreshed under `.scheduler-memory/latest/weekly/`. + +- Command: `SCHEDULER_CADENCE=weekly SCHEDULER_AGENT=proposal-triage-agent SCHEDULER_PROMPT_PATH=src/prompts/weekly/proposal-triage-agent.md SCHEDULER_RUN_ID=manual-proposal-triage-20260221T152500Z SCHEDULER_MEMORY_FILE=memory-updates/2026-02-21T20-22-32Z__proposal-triage-agent.md node scripts/memory/store.mjs` + - Result: pass (`MEMORY_STORED`) + - Notes: Store evidence refreshed under `.scheduler-memory/latest/weekly/`. + +- Command: source review across triage inputs (`docs/proposals`, `docs/AGENT_COVERAGE_GAPS.md`, `KNOWN_ISSUES.md`, `task-logs`, `artifacts`, `src/todo`, `features`, `docs/agent-handoffs/incidents`, existing backlog) + - Result: pass + - Notes: Evidence collection for backlog reprioritization. + +- Command: `ls src/lib/eventSchemas.js` + - Result: fail (`MISSING src/lib/eventSchemas.js`) + - Notes: Confirms backlog blocker remains unresolved. + +- Command: `node -e "const p=require('./package.json'); ..."` and script-key check + - Result: fail (`format` / `format:check` scripts absent) + - Notes: Confirms BACKLOG-001 remains actionable. diff --git a/src/todo/TODO_2026-02-21T20-22-32Z.md b/src/todo/TODO_2026-02-21T20-22-32Z.md new file mode 100644 index 0000000..a47a646 --- /dev/null +++ b/src/todo/TODO_2026-02-21T20-22-32Z.md @@ -0,0 +1,22 @@ +--- +agent: proposal-triage-agent +cadence: weekly +session: weekly-20260221T202232Z-proposal-triage-agent +run-start: 2026-02-21T20:22:32Z +prompt-file: src/prompts/weekly/proposal-triage-agent.md +--- + +# TODO β€” proposal-triage-agent β€” 2026-02-21T20:22:32Z + +## Completed +- [x] Read required startup files and scheduler shared contract. +- [x] Executed weekly memory retrieval command and checked retrieval evidence. +- [x] Reviewed proposals, coverage gaps, known issues, incidents, task-log failures, artifacts, TODO debt, and existing backlog. +- [x] Re-scored and reprioritized backlog items. +- [x] Updated `src/backlog/BACKLOG.md` with preserved IDs and new sequential IDs. +- [x] Wrote context/decision/test-log artifacts for this run. +- [x] Wrote memory update content for this run. +- [x] Executed weekly memory store command and verified storage evidence marker. + +## Pending +- [ ] Hand off results to scheduler-owned completion pipeline. diff --git a/task-logs/weekly/2026-02-21T20-25-17Z__proposal-triage-agent__completed.md b/task-logs/weekly/2026-02-21T20-25-17Z__proposal-triage-agent__completed.md new file mode 100644 index 0000000..8487be3 --- /dev/null +++ b/task-logs/weekly/2026-02-21T20-25-17Z__proposal-triage-agent__completed.md @@ -0,0 +1,18 @@ +--- +cadence: weekly +agent: proposal-triage-agent +status: completed +reason: 'Completed successfully' +detail: 'Prompt executed, memory retrieval/storage evidence validated, lint passed, and completion published.' +created_at: 2026-02-21T20:25:17Z +timestamp: 2026-02-21T20:25:17Z +platform: 'codex' +prompt_path: 'src/prompts/weekly/proposal-triage-agent.md' +memory_file: 'memory-updates/2026-02-21T20-22-32Z__proposal-triage-agent.md' +--- +# Scheduler completed +- reason: Completed successfully +- detail: Prompt executed, memory retrieval/storage evidence validated, lint passed, and completion published. +- platform: codex +- prompt: src/prompts/weekly/proposal-triage-agent.md +- memory_file: memory-updates/2026-02-21T20-22-32Z__proposal-triage-agent.md diff --git a/task-logs/weekly/2026-02-21T20-27-39Z__repo-fit-agent__completed.md b/task-logs/weekly/2026-02-21T20-27-39Z__repo-fit-agent__completed.md new file mode 100644 index 0000000..15f96ad --- /dev/null +++ b/task-logs/weekly/2026-02-21T20-27-39Z__repo-fit-agent__completed.md @@ -0,0 +1,18 @@ +--- +cadence: weekly +agent: repo-fit-agent +status: completed +reason: 'Completed successfully' +detail: 'Prompt executed, memory retrieval/storage evidence validated, lint passed, and completion published.' +created_at: 2026-02-21T20:27:39Z +timestamp: 2026-02-21T20:27:39Z +platform: 'linux' +prompt_path: 'src/prompts/weekly/repo-fit-agent.md' +memory_file: 'memory-update.md' +--- +# Scheduler completed +- reason: Completed successfully +- detail: Prompt executed, memory retrieval/storage evidence validated, lint passed, and completion published. +- platform: linux +- prompt: src/prompts/weekly/repo-fit-agent.md +- memory_file: memory-update.md