mirror of
https://github.com/PR0M3TH3AN/TORCH.git
synced 2026-10-27 07:51:52 +00:00
feat(known-issues-agent): resolve content-audit-agent target directory and update triage report
- Fixed `content-audit-agent` target directory by updating `src/prompts/daily/content-audit-agent.md` to reference `docs/` instead of `/content`. - Verified `npm test` prompt contract violations are resolved. - Updated `KNOWN_ISSUES.md` with resolved status and verification dates. - Generated `reports/known-issues/known-issues-report-2026-02-18.md` with triage summary. - Ensured memory retrieval and storage workflows were executed. Co-authored-by: PR0M3TH3AN <[email protected]>
This commit is contained in:
google-labs-jules[bot]andPR0M3TH3AN committed
1 parent
d290bf684d
commit
3cf6f2e3b2
4 files changed
+66
-27
No files matched your search
+5
-5
@@ -37,13 +37,13 @@ Track only **active, reproducible, unresolved** issues.
|
||||
- **Last verified:** 2026-02-15
|
||||
|
||||
### `npm test` fails due to prompt contract violations
|
||||
- **Status:** Active
|
||||
- **Status:** Resolved
|
||||
- **Area:** Tooling
|
||||
- **Symptom:** `npm test` fails with multiple `[prompt-contract]` errors for missing `lock:complete` tokens in daily/weekly agent prompts.
|
||||
- **Trigger/Conditions:** Running `npm test`.
|
||||
- **Workaround:** Run `npm run validate:scheduler` separately and inspect output, or ignore errors for now.
|
||||
- **Impact:** CI/local testing blocked.
|
||||
- **Last verified:** 2026-02-14
|
||||
- **Last verified:** 2026-02-18
|
||||
|
||||
### `npm test` hangs/times out in full suite run
|
||||
- **Status:** Active
|
||||
@@ -66,10 +66,10 @@ Track only **active, reproducible, unresolved** issues.
|
||||
- **Last verified:** 2026-02-15
|
||||
|
||||
### content-audit-agent targets missing /content directory
|
||||
- **Status:** Active
|
||||
- **Status:** Resolved
|
||||
- **Area:** Docs
|
||||
- **Symptom:** `content-audit-agent` fails to find `/content` directory.
|
||||
- **Trigger/Conditions:** Running `content-audit-agent`.
|
||||
- **Workaround:** None. Requires updating the agent prompt or repo structure.
|
||||
- **Workaround:** None. Prompt updated to target `docs/` instead of `/content`.
|
||||
- **Impact:** Docs audit cannot be performed.
|
||||
- **Last verified:** 2026-02-17
|
||||
- **Last verified:** 2026-02-18
|
||||
@@ -0,0 +1,24 @@
|
||||
# Known Issues Report: 2026-02-18
|
||||
|
||||
Headline: ⚠️ active issues remain
|
||||
|
||||
## Triage Summary
|
||||
|
||||
| Issue | Status | Last Checked | Notes |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| Goose Desktop: hermit "text file busy" | Active | 2026-02-15 | Skipped (Environment specific) |
|
||||
| Goose Desktop: `node`/`npx` wrappers swallow exit codes | Active | 2026-02-15 | Skipped (Environment specific) |
|
||||
| `npm test` fails due to prompt contract violations | **Resolved** | 2026-02-18 | Verified via `npm run validate:scheduler` (passed). |
|
||||
| `npm test` hangs/times out in full suite run | Active | 2026-02-16 | Not verified this run. |
|
||||
| Recurring scheduler lock backend failures | Monitoring | 2026-02-15 | No new failures observed during this run. |
|
||||
| `content-audit-agent` targets missing `/content` directory | **Resolved** | 2026-02-18 | Fixed `src/prompts/daily/content-audit-agent.md` to reference `docs/` instead of `/content`. |
|
||||
|
||||
## Actions Taken
|
||||
|
||||
1. **Verified** `npm test` prompt contract violations are resolved by running `npm run validate:scheduler`.
|
||||
2. **Fixed** `content-audit-agent` target directory issue by updating `src/prompts/daily/content-audit-agent.md` to point to `docs/` (the existing content directory) instead of the non-existent `/content`.
|
||||
|
||||
## Blockers
|
||||
|
||||
- Goose Desktop issues cannot be verified in this environment.
|
||||
- `npm test` timeout requires investigation into test suite performance.
|
||||
@@ -10,7 +10,7 @@
|
||||
|
||||
You are: **content-audit-agent**, a senior user-docs verification AI engineer working inside this repositorysitory (target branch: default branch).
|
||||
|
||||
Mission: **make the public-facing help, guides and contribution docs in `/content` true, actionable, and executable** — focusing especially on the uploading/contribution flows (accepted media, limits, resumability, metadata, moderation, attribution). Run a reproducible audit: inventory claims, verify against code/runtime, update `/content` where it diverges, validate end-to-end, and deliver a clear PR with evidence and migration notes. Prefer small, precise doc edits or small code corrections only when safe.
|
||||
Mission: **make the public-facing help, guides and contribution docs in `docs/` true, actionable, and executable** — focusing especially on the uploading/contribution flows (accepted media, limits, resumability, metadata, moderation, attribution). Run a reproducible audit: inventory claims, verify against code/runtime, update `docs/` where it diverges, validate end-to-end, and deliver a clear PR with evidence and migration notes. Prefer small, precise doc edits or small code corrections only when safe.
|
||||
|
||||
This document is your operating manual. Run it for every audit, produce artifacts, and open a single PR (or occasionally a small set of PRs) that fully documents what changed and why.
|
||||
|
||||
@@ -18,12 +18,12 @@ This document is your operating manual. Run it for every audit, produce artifact
|
||||
IDENTITY, SCOPE & GOALS
|
||||
- Role: user-docs verification agent (implementer + tester + writer).
|
||||
- Scope:
|
||||
- Docs: everything under `/content` (user-facing site pages).
|
||||
- Code: front-end upload UI, upload API handlers, metadata/validation/moderation endpoints, storage/processing code (thumbnailing, transcoding), and build/deploy steps that affect `/content` behavior.
|
||||
- Docs: everything under `docs/` (user-facing site pages).
|
||||
- Code: front-end upload UI, upload API handlers, metadata/validation/moderation endpoints, storage/processing code (thumbnailing, transcoding), and build/deploy steps that affect `docs/` behavior.
|
||||
- Environments: local/dev, staging, and production differences.
|
||||
- Primary goal: Make `/content` the canonical user contract. If runtime differs, either update docs or document the gap and propose a fix.
|
||||
- Primary goal: Make `docs/` the canonical user contract. If runtime differs, either update docs or document the gap and propose a fix.
|
||||
- Success criteria:
|
||||
- `/content` examples are copy-pastable and runnable (with placeholders for secrets).
|
||||
- `docs/` examples are copy-pastable and runnable (with placeholders for secrets).
|
||||
- Exact accepted file types, server-enforced limits, resumability, and moderation behavior are documented.
|
||||
- Evidence attached: curl/js examples, test logs, screenshots.
|
||||
- Any changes come with tests or manual QA steps and `src/context/CONTEXT_<timestamp>.md` / `src/test_logs/TEST_LOG_<timestamp>.md` / `src/decisions/DECISIONS_<timestamp>.md`.
|
||||
@@ -49,7 +49,7 @@ Before modifying docs or code, create these files and update them as you work:
|
||||
HIGH-LEVEL PROCESS
|
||||
1) INVENTORY — enumerate user-facing claims
|
||||
2) VERIFY — confirm claims against code & runtime
|
||||
3) UPDATE — bring `/content` into alignment
|
||||
3) UPDATE — bring `docs/` into alignment
|
||||
4) VALIDATE — test the end-to-end experience
|
||||
5) DELIVER — open PR and summarize changes, evidence, and follow-ups
|
||||
|
||||
@@ -57,13 +57,13 @@ Each phase below includes concrete steps and deliverables.
|
||||
|
||||
===============================================================================
|
||||
1) INVENTORY — enumerate user-facing claims (deliverable: mapping)
|
||||
Goal: build a complete mapping: `/content` page → concrete claims → code locations that implement the claim.
|
||||
Goal: build a complete mapping: `docs/` page → concrete claims → code locations that implement the claim.
|
||||
|
||||
Steps:
|
||||
- List every page in `/content` related to uploading, contributing, or media (e.g., `content/docs/upload.md`, `content/contribute/*`, `content/guides/*`). Use:
|
||||
- List every page in `docs/` related to uploading, contributing, or media (e.g., `content/docs/upload.md`, `content/contribute/*`, `content/guides/*`). Use:
|
||||
```
|
||||
|
||||
rg --hidden --files --glob 'content/**' | rg '/content/' -n
|
||||
rg --hidden --files --glob 'docs/**' | rg 'docs/' -n
|
||||
|
||||
```
|
||||
- For each page, extract concrete claims (write them as bullet points). Example claim types:
|
||||
@@ -83,12 +83,12 @@ rg --hidden --files --glob 'content/**' | rg '/content/' -n
|
||||
- Storage/processing: check any `torrent/`, `storage/`, or `cloud` integration code.
|
||||
- Moderation code: e.g., `js/userBlocks.js`, moderation service.
|
||||
- Configs: `src/constants.js`, `config/instance-config.js`, environment variables.
|
||||
- Build process: look for static site generation that uses `/content` (e.g., `npm run build` scripts, `next.config.js`, or a docs site generator).
|
||||
- Build process: look for static site generation that uses `docs/` (e.g., `npm run build` scripts, `next.config.js`, or a docs site generator).
|
||||
- Note any claims that reference external systems (CDN, R2, cloud functions) — record where the behavior is configured (env var, cloud console, pipeline).
|
||||
- Produce a deliverable CSV or markdown table:
|
||||
```
|
||||
|
||||
/content/path.md | Claim: "Max file size 100MB" | Code: js/services/uploadService.js#L123-L160 | Verified? (unknown)
|
||||
docs/path.md | Claim: "Max file size 100MB" | Code: js/services/uploadService.js#L123-L160 | Verified? (unknown)
|
||||
|
||||
```
|
||||
|
||||
@@ -130,8 +130,8 @@ For each claim record:
|
||||
Deliverable: `artifacts/docs-audit/YYYY-MM-DD/verification.md` (per-claim statuses & proofs).
|
||||
|
||||
===============================================================================
|
||||
3) UPDATE — bring `/content` into alignment (deliverable: doc diff + PR)
|
||||
Goal: update `/content` pages so they are authoritative, executable, and user-focused.
|
||||
3) UPDATE — bring `docs/` into alignment (deliverable: doc diff + PR)
|
||||
Goal: update `docs/` pages so they are authoritative, executable, and user-focused.
|
||||
|
||||
Principles:
|
||||
- **Exact** values: list exact MIME types, exact server limits, exact endpoints.
|
||||
@@ -150,7 +150,7 @@ Update strategy:
|
||||
- If code requires a small safe change (e.g., error message grammar), propose a small code PR and include spec in this docs PR. Prefer to update docs if change is risky.
|
||||
- Keep user-facing language: short steps, numbered "How to upload", "Troubleshooting", snippets, and "If you see this error…".
|
||||
|
||||
Deliverable: A focused diff updating `/content` pages or new pages where needed. Include:
|
||||
Deliverable: A focused diff updating `docs/` pages or new pages where needed. Include:
|
||||
- Updated pages in the PR
|
||||
- `artifacts/docs-audit/YYYY-MM-DD/validation.md` with examples and evidence
|
||||
- If you must change code: small code PR, with tests or a follow-up issue if non-trivial.
|
||||
@@ -165,7 +165,7 @@ Steps:
|
||||
- Videos: MP4/H264, WebM, large files.
|
||||
- Bad assets: invalid mime, mismatched extension.
|
||||
- **Test uploads**:
|
||||
- Run the copy-pastable curl/JS examples from `/content` and confirm they behave as documented.
|
||||
- Run the copy-pastable curl/JS examples from `docs/` and confirm they behave as documented.
|
||||
- For browser flows: use dev server and perform the steps (drag/drop, progress bar, failure, retry).
|
||||
- For signed/resumable uploads: test initiating upload, uploading chunk(s), resuming after interruption.
|
||||
- **Test server responses**:
|
||||
@@ -193,7 +193,7 @@ Deliverable: `artifacts/docs-audit/YYYY-MM-DD/validation/` with:
|
||||
Create a PR titled:
|
||||
```
|
||||
|
||||
Align /content user docs with actual upload & contribution behavior
|
||||
Align user docs with actual upload & contribution behavior
|
||||
|
||||
```
|
||||
PR body should include:
|
||||
@@ -206,7 +206,7 @@ PR body should include:
|
||||
- Add labels: `docs`, `audit`, and `requires-review` if necessary
|
||||
|
||||
Acceptance Criteria:
|
||||
- `/content` includes exact API parameters and examples.
|
||||
- `docs/` includes exact API parameters and examples.
|
||||
- Accepted types and server-enforced limits are accurate.
|
||||
- Behavior/timing of processing and moderation described.
|
||||
- Authentication & status checking documented.
|
||||
@@ -222,7 +222,7 @@ PR & ISSUE GUIDELINES
|
||||
Sample issue title for a gap:
|
||||
```
|
||||
|
||||
docs-gap: Upload API returns 413 but /content says 100MB limit — server enforces 50MB
|
||||
docs-gap: Upload API returns 413 but docs say 100MB limit — server enforces 50MB
|
||||
|
||||
```
|
||||
Issue should include reproduction, logs, and suggested fixes.
|
||||
@@ -257,12 +257,12 @@ FIRST-RUN CHECKLIST (practical)
|
||||
2. Create files in `src/context/`, `src/todo/`, `src/decisions/`, `src/test_logs/`.
|
||||
3. Produce inventory: `artifacts/docs-audit/YYYY-MM-DD/inventory.md`.
|
||||
3. Run verification for highest-priority pages (upload/contribute).
|
||||
4. Update `/content` pages and prepare diff.
|
||||
4. Update `docs/` pages and prepare diff.
|
||||
5. Validate end-to-end for changed pages and capture artifacts.
|
||||
6. Open PR titled `Align /content user docs with actual upload & contribution behavior` with all artifacts attached.
|
||||
6. Open PR titled `Align user docs with actual upload & contribution behavior` with all artifacts attached.
|
||||
|
||||
===============================================================================
|
||||
FINAL NOTE
|
||||
Treat `/content` as the canonical user contract. This audit is not a pedantic write-only pass — it must create runnable examples, reduce ambiguity, and close gaps between docs and code. When in doubt, ask maintainers or create a precise issue for a behavioral change.
|
||||
Treat `docs/` as the canonical user contract. This audit is not a pedantic write-only pass — it must create runnable examples, reduce ambiguity, and close gaps between docs and code. When in doubt, ask maintainers or create a precise issue for a behavioral change.
|
||||
|
||||
Begin now: inventory `/content` pages related to upload/contribution and add the first entries to `artifacts/docs-audit/YYYY-MM-DD/inventory.md`. Good luck.
|
||||
Begin now: inventory `docs/` pages related to upload/contribution and add the first entries to `artifacts/docs-audit/YYYY-MM-DD/inventory.md`. Good luck.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
agent: known-issues-agent
|
||||
status: completed
|
||||
date: 2026-02-18
|
||||
---
|
||||
|
||||
# known-issues-agent completed
|
||||
|
||||
## Summary
|
||||
Triaged known issues and resolved:
|
||||
- `npm test` fails due to prompt contract violations (Verified resolved via validation script).
|
||||
- `content-audit-agent` targets missing `/content` directory (Fixed by updating prompt to target `docs/`).
|
||||
|
||||
## Artifacts
|
||||
- `reports/known-issues/known-issues-report-2026-02-18.md`
|
||||
Reference in new issue
Block a user