refactor(ops): extract cmdRemove to src/cmd-remove.mjs

Co-authored-by: PR0M3TH3AN <[email protected]>
This commit is contained in:
google-labs-jules[bot]andPR0M3TH3AN committed 2026-02-21 20:32:12 +00:00
1 parent 9fef4c4f46
commit 7c8eeb939c
16 files changed
+350 -377

No files matched your search

@@ -1,20 +0,0 @@
---
agent: event-schema-agent
status: failed
date: 2026-02-14
---
# Preflight Check Failed
The `event-schema-agent` requires `src/lib/eventSchemas.js` as the canonical source of truth for event builders and sanitizers. This file does not exist in the `torch-lock` repository.
## Findings
1. **Missing Source of Truth**: `src/lib/eventSchemas.js` is referenced in the agent prompt but is absent from the codebase.
2. **Runtime Construction**: Event construction in this repository currently happens inline (e.g., in `src/nostr-lock.mjs`), which violates the pattern of using shared, canonical builders.
3. **Action**: Aborting execution. No validator harness can be generated without the canonical schemas.
## Recommendations
- Create `src/lib/eventSchemas.js` to centralize event construction (e.g., for the lock event).
- Update `event-schema-agent` prompt or repository documentation to reflect the actual location of schemas if they exist elsewhere.
@@ -1,14 +0,0 @@
---
agent: event-schema-agent
status: failed
---
# Weekly Scheduler Run Failed
reason: Lock backend error
## Details
- cadence: weekly
- excluded: []
- selected_agent: event-schema-agent
- lock_command: `AGENT_PLATFORM=codex npm run lock:lock -- --agent event-schema-agent --cadence weekly`
- lock_exit_code: 2
@@ -1 +0,0 @@
Preflight check failed: Required files `src/lib/eventSchemas.js`, `src/lib/clientFacade.js` (or defaultClient.js), and `js/dmDecryptor.js` are missing from the repository. This agent appears to be misconfigured for the current repository structure.
@@ -1,18 +0,0 @@
---
agent: prompt-maintenance-agent
status: failed
---
# Weekly Scheduler Run Failed
reason: Lock backend error
## Details
- cadence: weekly
- log_dir: task-logs/weekly/
- branch_prefix: agents/weekly/
- prompt_dir: src/prompts/weekly/
- excluded: [bug-reproducer-agent, changelog-agent, dead-code-agent, feature-proposer-agent, frontend-console-debug-agent, fuzz-agent, perf-deepdive-agent, perf-optimization-agent, pr-review-agent]
- selected_agent: prompt-maintenance-agent
- lock_command: `AGENT_PLATFORM=codex npm run lock:lock -- --agent prompt-maintenance-agent --cadence weekly`
- lock_exit_code: 2
- next_action: Retry scheduler cycle after relay connectivity is restored.
@@ -1,59 +0,0 @@
---
agent: perf-optimization-agent
cadence: weekly
platform: claude
status: failed
timestamp: "2026-02-19T00:58:49Z"
failure_class: backend_unavailable
failure_category: lock_backend_error
---
# Task Log — Failed
## Reason
Lock backend error
## Detail
Lock acquisition for `perf-optimization-agent` (weekly cadence) failed with exit code 2.
All Nostr relays returned `permanent_validation_error`: "Received network error or non-101 status code."
WebSocket connectivity to the relay pool is unavailable in this execution environment.
No prompt was executed. `lock:complete` was NOT published.
## Scheduler State
- **Selected agent:** perf-optimization-agent
- **Selection algorithm:**
- Roster source: `src/prompts/roster.json` (weekly key)
- Latest log file: `2026-02-18T19-54-03Z__perf-deepdive-agent__completed.md`
- Previous agent: `perf-deepdive-agent` (from filename convention, index 6)
- start_index: `(6 + 1) mod 21 = 7`
- Candidate at index 7: `perf-optimization-agent` — not in excluded set → selected
- **Excluded set (from lock:check:weekly):** bug-reproducer-agent, changelog-agent, dead-code-agent, feature-proposer-agent, frontend-console-debug-agent, fuzz-agent, perf-deepdive-agent, test-coverage-agent, ui-ux-agent, weekly-synthesis-agent
## Lock Failure Metadata
- **lock_command:** `AGENT_PLATFORM=claude npm run lock:lock -- --agent perf-optimization-agent --cadence weekly`
- **backend_category:** relay_publish_non_retryable
- **lock_correlation_id:** c5e5d9fc-85f5-41ca-b4d2-3671f815d157
- **lock_attempt_id:** 5403bebc-a9f5-4a30-a3dd-6df7af4ec213
- **successCount:** 0 / 3
- **requiredSuccesses:** 1
- **relay_list:**
- wss://nos.lol (publish:primary, reason=permanent_validation_error)
- wss://relay.damus.io (publish:primary, reason=permanent_validation_error)
- wss://relay.primal.net (publish:primary, reason=permanent_validation_error)
- **lock_stderr_excerpt:** "Failed relay publish quorum in publish phase: 0/3 successful (required=1, timeout=15000ms, attempts=4)"
## Retry Guidance
1. Verify relay connectivity: `npm run lock:health -- --cadence weekly`
2. Retry lock acquisition: `AGENT_PLATFORM=claude npm run lock:lock -- --agent perf-optimization-agent --cadence weekly`
3. If all relays remain unhealthy, consult `docs/agent-handoffs/incidents/` for relay remediation guidance.
4. See incident runbook: `docs/agent-handoffs/learnings/2026-02-15-relay-health-preflight-job.md`
## Prompt Not Executed
The selected prompt `src/prompts/weekly/perf-optimization-agent.md` was NOT executed.
@@ -1,8 +0,0 @@
---
agent: pr-review-agent
cadence: weekly
run_start: 2026-02-19T05:06:16Z
platform: linux
failure_reason: Validation failed (Verify: 1, Lint: 0)
---
Run failed.
@@ -0,0 +1,7 @@
---
agent: refactor-agent
cadence: weekly
platform: codex
---
Run completed successfully.