From 07ceede552c3e62da58b0bd3ea88ece757464e6c Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com> Date: Sat, 14 Feb 2026 16:45:15 -0500 Subject: [PATCH] Normalize KNOWN_ISSUES path in prompts --- src/prompts/daily/deps-security-agent.md | 2 +- src/prompts/daily/known-issues-agent.md | 26 +++++++++++----------- src/prompts/daily/perf-agent.md | 2 +- src/prompts/daily/test-audit-agent.md | 2 +- src/prompts/scheduler-flow.md | 1 + src/prompts/weekly/race-condition-agent.md | 2 +- 6 files changed, 18 insertions(+), 17 deletions(-) diff --git a/src/prompts/daily/deps-security-agent.md b/src/prompts/daily/deps-security-agent.md index c419883..e288afa 100644 --- a/src/prompts/daily/deps-security-agent.md +++ b/src/prompts/daily/deps-security-agent.md @@ -37,7 +37,7 @@ Create/update these files/folders (commit them in the branch when PRing): - `test_logs/TEST_LOG_.md` — exact commands run and their outputs (timestamped). - Optionally: `torch/scripts/deps-audit.sh` for reproducible automation. -Also read `AGENTS.md` and `docs/KNOWN_ISSUES.md` for project-specific caveats (e.g., the repo uses `integration-tools`, `webtorrent`, `Playwright`, `Tailwind`). Tag these libraries for special handling. +Also read `AGENTS.md` and `KNOWN_ISSUES.md` for project-specific caveats (e.g., the repo uses `integration-tools`, `webtorrent`, `Playwright`, `Tailwind`). Tag these libraries for special handling. -------------------------------------------------------------------------------- PACKAGE MANAGER DETECTION diff --git a/src/prompts/daily/known-issues-agent.md b/src/prompts/daily/known-issues-agent.md index 3d803a1..26e005c 100644 --- a/src/prompts/daily/known-issues-agent.md +++ b/src/prompts/daily/known-issues-agent.md @@ -2,18 +2,18 @@ You are: **known-issues-agent**, a senior software engineer agent working inside this repository. -Mission: run a **daily KNOWN_ISSUES remediation loop**: triage every entry in `docs/KNOWN_ISSUES.md`, fix issues that are small + safe, convert larger/riskier items into GitHub issues, and keep `docs/KNOWN_ISSUES.md` accurate (links, repro steps, and last-checked notes). Every change must be traceable, reviewable, and compliant with repo policy. +Mission: run a **daily KNOWN_ISSUES remediation loop**: triage every entry in `KNOWN_ISSUES.md`, fix issues that are small + safe, convert larger/riskier items into GitHub issues, and keep `KNOWN_ISSUES.md` accurate (links, repro steps, and last-checked notes). Every change must be traceable, reviewable, and compliant with repo policy. ─────────────────────────────────────────────────────────────────────────────── AUTHORITY HIERARCHY (highest wins) 1. `AGENTS.md` — repo-wide agent policy (overrides everything below) 2. `CLAUDE.md` — repo-specific guidance and conventions -3. `docs/KNOWN_ISSUES.md` — current known issues contract (must stay accurate) +3. `KNOWN_ISSUES.md` — current known issues contract (must stay accurate) 4. Repo code + CI configs (`package.json`, `.github/workflows/**`) — source of truth 5. This agent prompt -If `docs/KNOWN_ISSUES.md` conflicts with the codebase reality, update the doc. +If `KNOWN_ISSUES.md` conflicts with the codebase reality, update the doc. If policy conflicts with the desired remediation, open an issue — do not bypass policy. @@ -21,14 +21,14 @@ policy. SCOPE In scope: - - Daily triage of `docs/KNOWN_ISSUES.md` entries: + - Daily triage of `KNOWN_ISSUES.md` entries: - test failures - environment quirks - build/CI instability - architectural limitations that affect contributors - Fixing **small, safe** issues (trivial or clearly bounded). - Opening GitHub issues for medium/large/risky items with good context. - - Maintaining `docs/KNOWN_ISSUES.md` hygiene: + - Maintaining `KNOWN_ISSUES.md` hygiene: - correct links - accurate repro steps - “last checked” notes @@ -43,7 +43,7 @@ Out of scope: ─────────────────────────────────────────────────────────────────────────────── GOALS & SUCCESS CRITERIA -1. Freshness — Every `docs/KNOWN_ISSUES.md` entry is reviewed daily (or explicitly +1. Freshness — Every `KNOWN_ISSUES.md` entry is reviewed daily (or explicitly marked as not re-checkable with reasons). 2. Accuracy — Repro steps and links work; claims match current repo behavior. 3. Progress — Small safe issues are fixed via small PRs; larger ones are tracked @@ -57,7 +57,7 @@ HARD CONSTRAINTS - Inspect first. Do not assume files, commands, or workflows exist—verify. - Minimal changes. Prefer the smallest fix that resolves an issue. -- No mission drift. Only address items present in `docs/KNOWN_ISSUES.md` (or discovered +- No mission drift. Only address items present in `KNOWN_ISSUES.md` (or discovered while verifying those items). - Security-sensitive guardrail: if an item touches areas flagged by `AGENTS.md` (e.g., shared signing/publishing, key handling, moderation, magnets/torrents, @@ -94,7 +94,7 @@ DAILY WORKFLOW (mandatory) - If the repo does not commit artifacts, keep the report in the PR body or in `docs/` per repo conventions. -2) Parse `docs/KNOWN_ISSUES.md` +2) Parse `KNOWN_ISSUES.md` - Enumerate each entry. - For each entry extract: - title/summary @@ -108,7 +108,7 @@ DAILY WORKFLOW (mandatory) - Attempt repro exactly as documented (where feasible). - If repro commands are missing or unclear: - inspect related tests/scripts/config to infer the correct repro - - update `docs/KNOWN_ISSUES.md` with the verified repro steps (do not guess) + - update `KNOWN_ISSUES.md` with the verified repro steps (do not guess) - Classify status: - ✅ Resolved (cannot reproduce; evidence recorded) - ⚠️ Active (reproduces; evidence recorded) @@ -132,7 +132,7 @@ DAILY WORKFLOW (mandatory) - Implement the smallest fix that resolves the issue. - Run verification commands relevant to the issue: - tests, lint, or a targeted repro (verify in `package.json` and CI workflows) - - Update `docs/KNOWN_ISSUES.md` entry: + - Update `KNOWN_ISSUES.md` entry: - mark as resolved or updated - add “last checked: YYYY-MM-DD” - link the PR @@ -144,13 +144,13 @@ DAILY WORKFLOW (mandatory) 6) Issue path (B) - Open (or update) a GitHub issue including: - - exact excerpt from `docs/KNOWN_ISSUES.md` + - exact excerpt from `KNOWN_ISSUES.md` - file/line pointers - repro steps (verified or best-known, clearly labeled) - observed behavior + logs (sanitized) - suggested next step (1–2 options) - labels per repo conventions (`ai`, `needs-review`, `security` etc.) only if they exist - - Update `docs/KNOWN_ISSUES.md` entry with: + - Update `KNOWN_ISSUES.md` entry with: - the issue link - “last checked” date - any clarifications discovered during triage @@ -210,6 +210,6 @@ OUTPUTS PER RUN Daily: - 0–1 small PR fixing a trivial, safe known issue (or none if nothing safe) -- Updated `docs/KNOWN_ISSUES.md` with last-checked notes and links +- Updated `KNOWN_ISSUES.md` with last-checked notes and links - 0–N GitHub issues for medium/large/risky items - A short daily remediation report (artifact or PR body) \ No newline at end of file diff --git a/src/prompts/daily/perf-agent.md b/src/prompts/daily/perf-agent.md index 632ba71..b315a5d 100644 --- a/src/prompts/daily/perf-agent.md +++ b/src/prompts/daily/perf-agent.md @@ -45,7 +45,7 @@ Commit early and often: - `INITIAL_BASELINE.md` — baseline metrics (login time, decrypt queue size, relay latencies, webtorrent count). - `perf/` (optional) — scripts and small helpers. -Read `AGENTS.md` and `docs/KNOWN_ISSUES.md` before edits. +Read `AGENTS.md` and `KNOWN_ISSUES.md` before edits. ------------------------------------------------------------------------------- DAILY WORKFLOW (run each day) diff --git a/src/prompts/daily/test-audit-agent.md b/src/prompts/daily/test-audit-agent.md index 014e57b..028cb3e 100644 --- a/src/prompts/daily/test-audit-agent.md +++ b/src/prompts/daily/test-audit-agent.md @@ -39,7 +39,7 @@ Create or update these files and folders in the repo before making changes: - `test-audit/coverage-summary.json` - `test-audit/mutation-summary.json` -Always read `AGENTS.md` and `docs/KNOWN_ISSUES.md` for repo-specific caveats (login/relay/video schemas, integration libs, etc.) before editing tests. +Always read `AGENTS.md` and `KNOWN_ISSUES.md` for repo-specific caveats (login/relay/video schemas, integration libs, etc.) before editing tests. =============================================================================== DAILY WORKFLOW (run every day or as scheduled) diff --git a/src/prompts/scheduler-flow.md b/src/prompts/scheduler-flow.md index 74a5128..54c7645 100644 --- a/src/prompts/scheduler-flow.md +++ b/src/prompts/scheduler-flow.md @@ -11,6 +11,7 @@ Every agent prompt invoked by the schedulers (daily/weekly) MUST enforce this co - `AGENTS.md` - `CLAUDE.md` - `KNOWN_ISSUES.md` + - Canonical path note: active issues are tracked in root `KNOWN_ISSUES.md` (not `docs/KNOWN_ISSUES.md`) - `docs/agent-handoffs/README.md` - Recent notes in `docs/agent-handoffs/learnings/` and `docs/agent-handoffs/incidents/` 2. **Update run artifacts** in `src/context/`, `src/todo/`, `src/decisions/`, and `src/test_logs/` during the run, or explicitly document why each artifact update is not needed for that run. diff --git a/src/prompts/weekly/race-condition-agent.md b/src/prompts/weekly/race-condition-agent.md index a844966..25f05df 100644 --- a/src/prompts/weekly/race-condition-agent.md +++ b/src/prompts/weekly/race-condition-agent.md @@ -117,7 +117,7 @@ WEEKLY WORKFLOW (mandatory) - branch/commit/PR conventions - any concurrency-related guidance or known issues - security constraints - - Read `docs/KNOWN_ISSUES.md` for pre-existing race-related failures. + - Read `KNOWN_ISSUES.md` for pre-existing race-related failures. - Confirm base branch per policy (often ``). - Record environment: - OS, Node version, browser version (if relevant).