docs: refresh KNOWN_ISSUES (daily)

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-10-27 07:52:03 +00:00 · 2026-02-25 21:32:23 +00:00
1 parent 94bb42d3df
commit 92e51cadf8
@@ -1,34 +1,3 @@
-### 1. [2026-02-25] (scheduler, daily, store, insight)
+### 1. [2026-02-25] (scheduler, daily, retrieve)

-### 1. [2026-02-25] (torch, init, reinstall)
-If `npx --no-install torch-lock init --help` prints initialization prompts, it may be interactive; use `printf '\n' | npx --no-install torch-lock init --force` to accept defaults non-interactively in CI/agent runs.
-
-### 2. [2026-02-25…
-
---
-
-### 2. [2026-02-25] (scheduler, daily, store, insight)
-
-### 1. [2026-02-25] (torch, scheduler, host-mode)
-When running `npm run --prefix torch scheduler:daily`, the scheduler resolves config from `torch/torch-config.json` (cwd-scoped), not the repo-root `torch-config.json`.
-
-### 2. [2026-02-25] (torch, scheduler, handoff)
-A non-inter…
-
---
-
-### 3. [2026-02-25] (scheduler, daily, retrieve)
-
-Memory retrieval seed for daily :: scheduler memory retrieval
-
---
-
-### 4. [2026-02-25] (scheduler, daily, retrieve)
-
-Memory retrieval seed for daily :: scheduler memory retrieval
-
---
-
-### 5. [2026-02-25] (scheduler, daily, retrieve)
-
-Memory retrieval seed for daily :: scheduler memory retrieval
+Memory retrieval seed for daily :: Known Issues Agent
@@ -176,5 +176,56 @@
      "merged_into": null,
      "pinned": false
    }
+  ],
+  [
+    "6b410c6a-f1eb-4e5f-b510-c4b92c7fdd58",
+    {
+      "schema_version": 1,
+      "id": "6b410c6a-f1eb-4e5f-b510-c4b92c7fdd58",
+      "agent_id": "known-issues-agent",
+      "session_id": "session-mm2jk9lj",
+      "type": "batch_window",
+      "content": "Memory retrieval seed for daily :: Known Issues Agent",
+      "summary": "Memory retrieval seed for daily :: Known Issues Agent",
+      "tags": [
+        "scheduler",
+        "daily",
+        "retrieve"
+      ],
+      "importance": 0.4,
+      "embedding_id": null,
+      "created_at": 1772054612119,
+      "last_seen": 1772054612130,
+      "source": "scheduler-retrieve",
+      "ttl_days": null,
+      "merged_into": null,
+      "pinned": false
+    }
+  ],
+  [
+    "834be1dd-10b6-48c4-a4f4-57668c926e14",
+    {
+      "schema_version": 1,
+      "id": "834be1dd-10b6-48c4-a4f4-57668c926e14",
+      "agent_id": "known-issues-agent",
+      "session_id": "session-mm2jog2v",
+      "type": "batch_window",
+      "content": "# Learnings from known-issues-agent run\n\n- Initialized `KNOWN_ISSUES.md` as it was missing.\n- Verified that `npm run --prefix torch lint` requires `npm install --prefix torch` to be run first.\n- Confirmed that `landing/index.html` no longer contains `innerHTML` violations.\n- Confirmed `torch-config.json` correctly defines scheduler handoff commands.\n- Consolidated resolved issues into `KNOWN_ISSUES.md` for historical tracking.",
+      "summary": "# Learnings from known-issues-agent run\n\n- Initialized `KNOWN_ISSUES.md` as it was missing.\n- Verified that `npm run --prefix torch lint` requires `npm install --prefix torch` to be run first.\n- Confirmed that `landing/index.html` no longer contains `innerHTML` violations.\n- Con…",
+      "tags": [
+        "scheduler",
+        "daily",
+        "store",
+        "insight"
+      ],
+      "importance": 0.8,
+      "embedding_id": null,
+      "created_at": 1772054807144,
+      "last_seen": 1772054807144,
+      "source": "agent-output",
+      "ttl_days": null,
+      "merged_into": null,
+      "pinned": false
+    }
  ]
 ]
@@ -0,0 +1,18 @@
+{
+  "cadence": "daily",
+  "operation": "retrieve",
+  "runId": "session-mm2jk9lj",
+  "servicePath": "src/services/memory/index.js#getRelevantMemories",
+  "inputs": {
+    "agentId": "known-issues-agent",
+    "promptPath": "torch/src/prompts/daily/known-issues-agent.md",
+    "promptIntent": "Known Issues Agent",
+    "query": "scheduler | daily | agent | known-issues-agent | intent | Known Issues Agent",
+    "events": 1
+  },
+  "outputs": {
+    "ingestedCount": 1,
+    "retrievedCount": 1
+  },
+  "status": "ok"
+}
@@ -0,0 +1 @@
+MEMORY_RETRIEVED
@@ -0,0 +1,20 @@
+{
+  "cadence": "daily",
+  "operation": "store",
+  "runId": "session-mm2jog2v",
+  "servicePath": "src/services/memory/index.js#ingestEvents",
+  "inputs": {
+    "agentId": "known-issues-agent",
+    "promptPath": "torch/src/prompts/daily/known-issues-agent.md",
+    "promptIntent": "Known Issues Agent",
+    "events": 1,
+    "sourceFile": "memory-update.md"
+  },
+  "outputs": {
+    "storedCount": 1,
+    "summaries": [
+      "# Learnings from known-issues-agent run\n\n- Initialized `KNOWN_ISSUES.md` as it was missing.\n- Verified that `npm run --prefix torch lint` requires `npm install --prefix torch` to be run first.\n- Confirmed that `landing/index.html` no longer contains `innerHTML` violations.\n- Con…"
+    ]
+  },
+  "status": "ok"
+}
@@ -0,0 +1 @@
+MEMORY_STORED
@@ -0,0 +1,34 @@
+# Known Issues
+
+This file tracks persistent, verifiable issues that affect the codebase or development workflow.
+It is updated daily by the `known-issues-agent`.
+
+## Status Definitions
+- **Active**: Reproduces consistently. Needs fix or workaround.
+- **Resolved**: Fixed and verified.
+- **Unknown**: Cannot verify due to missing context/env.
+
+## Issues
+
+### [Resolved] Missing ESLint Configuration in `torch/`
+- **Symptoms**: `npm run --prefix torch lint` fails with "ESLint configuration not found".
+- **Repro**: `npm run --prefix torch lint`
+- **Workaround**: Ensure `eslint.config.mjs` is present and `npm install` is run.
+- **Root Cause**: `npm install` not run in restricted environments.
+- **Status**: Resolved (verified by `known-issues-agent` on 2026-02-25).
+- **Last Checked**: 2026-02-25
+
+### [Resolved] Scheduler Configuration Missing Handoff Command
+- **Symptoms**: Multiple agents failed with `Missing scheduler handoff command for non-interactive run`.
+- **Repro**: `node bin/torch-lock.mjs check --cadence daily` without `torch-config.json` correctly populated.
+- **Root Cause**: Missing or misconfigured `torch-config.json`.
+- **Status**: Resolved (verified `torch-config.json` contains `handoffCommandByCadence` on 2026-02-25).
+- **Last Checked**: 2026-02-25
+
+### [Resolved] InnerHTML Usage in `landing/index.html`
+- **Symptoms**: `style-agent` reported `innerHTML` violations.
+- **Repro**: `grep "innerHTML" landing/index.html`
+- **Workaround**: Refactor to use `textContent`.
+- **Root Cause**: Unsafe DOM manipulation.
+- **Status**: Resolved (verified file content on 2026-02-25).
+- **Last Checked**: 2026-02-25
@@ -1,8 +1,7 @@
-### 1. [2026-02-25] (torch, scheduler, host-mode)
-When running `npm run --prefix torch scheduler:daily`, the scheduler resolves config from `torch/torch-config.json` (cwd-scoped), not the repo-root `torch-config.json`.
+# Learnings from known-issues-agent run

-### 2. [2026-02-25] (torch, scheduler, handoff)
-A non-interactive scheduler run now requires `scheduler.handoffCommandByCadence.<cadence>` in the active torch config; missing it hard-fails after lock acquisition.
-
-### 3. [2026-02-25] (torch, scheduler, lint)
-After `torch-lock update --force`, `torch/eslint.config.mjs` is restored and `npm run --prefix torch lint` passes when `torch/node_modules` is installed.
+- Initialized `KNOWN_ISSUES.md` as it was missing.
+- Verified that `npm run --prefix torch lint` requires `npm install --prefix torch` to be run first.
+- Confirmed that `landing/index.html` no longer contains `innerHTML` violations.
+- Confirmed `torch-config.json` correctly defines scheduler handoff commands.
+- Consolidated resolved issues into `KNOWN_ISSUES.md` for historical tracking.
@@ -0,0 +1,19 @@
+# Daily Known Issues Report: 2026-02-25
+
+## Headline
+✓ Verified multiple previously failed agents and issues as resolved or environment-related.
+No active issues found.
+
+## Issues Status
+| Issue | Status | Last Checked |
+|---|---|---|
+| Missing ESLint Configuration | Resolved | 2026-02-25 |
+| Missing Handoff Command | Resolved | 2026-02-25 |
+| InnerHTML Usage in `landing/index.html` | Resolved | 2026-02-25 |
+
+## Actions Taken
+- Initialized `KNOWN_ISSUES.md`.
+- Consolidated scattered issue reports into `KNOWN_ISSUES.md`.
+- Verified `torch-config.json` content.
+- Verified `npm run --prefix torch lint` functionality.
+- Verified absence of `innerHTML` in `landing/index.html`.
@@ -0,0 +1,14 @@
+# Decision: Initialize KNOWN_ISSUES.md
+
+## Context
+Multiple agent failures were observed in `torch/task-logs/daily/`, and scattered issue files existed in `torch/src/issues/`.
+No central `KNOWN_ISSUES.md` existed.
+
+## Decision
+Create `KNOWN_ISSUES.md` and populate it with the investigation results of the recent failures and issue files.
+Since all investigated issues (lint config, scheduler config, innerHTML usage) were found to be resolved or environment-specific, they are marked as [Resolved] in the initial file.
+
+## Consequences
+- A central source of truth for known issues now exists.
+- Future agents can check this file before reporting duplicate issues.
+- The `known-issues-agent` now has a file to triage daily.
@@ -0,0 +1,16 @@
+---
+agent: known-issues-agent
+cadence: daily
+status: completed
+platform: linux
+prompt: torch/src/prompts/daily/known-issues-agent.md
+---
+
+# Scheduler Success Log
+
+- Initialized `KNOWN_ISSUES.md`.
+- Verified and consolidated resolved issues.
+- Created daily report `reports/known-issues/known-issues-report-2026-02-25.md`.
+- Confirmed `landing/index.html` resolved `innerHTML` issue.
+- Confirmed `torch-config.json` handoff command issue resolved.
+- Confirmed `lint` issue resolved by environment setup.