mirror of
https://github.com/PR0M3TH3AN/TORCH.git
synced 2026-11-06 04:42:24 +00:00
update
This commit is contained in:
1 parent
03b6725cfc
commit
2b8a0c3d0d
25 files changed
+1126
-5
No files matched your search
@@ -0,0 +1,38 @@
|
||||
---
|
||||
agent: docs-agent
|
||||
cadence: daily
|
||||
run-start: "2026-02-20T05:00:00Z"
|
||||
prompt: src/prompts/daily/docs-agent.md
|
||||
---
|
||||
|
||||
# Context — docs-agent — 2026-02-20
|
||||
|
||||
## Goal
|
||||
|
||||
Audit key documentation files (`README.md`, `AGENTS.md`) for accuracy relative to the codebase and fix any inaccuracies found.
|
||||
|
||||
## Scope
|
||||
|
||||
- Baseline reads: `AGENTS.md`, `CLAUDE.md`, `KNOWN_ISSUES.md`, `docs/agent-handoffs/README.md`
|
||||
- Audit targets: `README.md`, `AGENTS.md`, `CONTRIBUTING.md`
|
||||
- Verify all scripts/commands against `package.json`
|
||||
- Fix P1 inaccuracies (missing env vars, missing config keys)
|
||||
- Write run artifacts in canonical paths
|
||||
|
||||
## Constraints
|
||||
|
||||
- Do not invent commands or APIs not verified in code
|
||||
- Minimal edits — prefer targeted fixes over wholesale rewrites
|
||||
- Do not change test behavior or policy intent in AGENTS.md/CLAUDE.md
|
||||
|
||||
## Open questions
|
||||
|
||||
- None. All referenced files found and verified.
|
||||
|
||||
## Findings
|
||||
|
||||
1. `README.md` environment variables section is missing 4 env vars present in `TORCH.md` and used in `src/torch-config.mjs`: `NOSTR_LOCK_PUBLISH_TIMEOUT_MS`, `NOSTR_LOCK_MIN_SUCCESSFUL_PUBLISHES`, `NOSTR_LOCK_RELAY_FALLBACKS`, `NOSTR_LOCK_MIN_ACTIVE_RELAY_POOL`.
|
||||
2. `README.md` `torch-config.json` section is missing 8 config keys fully documented in `TORCH.md`: `publishTimeoutMs`, `minSuccessfulRelayPublishes`, `relayFallbacks`, `minActiveRelayPool`, `handoffCommandByCadence`, `strict_lock`, `degraded_lock_retry_window`, `max_deferrals`.
|
||||
3. `CONTRIBUTING.md` — accurate; all commands verified against `package.json`. No issues found.
|
||||
4. `AGENTS.md` — accurate; no broken paths or incorrect commands.
|
||||
5. `.env.example`, `torch-config.example.json`, `docs/lib-overview.md`, `docs/lock-ops-overview.md`, `skills/`, `dashboard/` — all exist ✓
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
agent: docs-alignment-agent
|
||||
cadence: daily
|
||||
run-start: "2026-02-20T06:00:00Z"
|
||||
prompt: src/prompts/daily/docs-alignment-agent.md
|
||||
---
|
||||
|
||||
# Context — docs-alignment-agent — 2026-02-20
|
||||
|
||||
## Goal
|
||||
|
||||
Verify, correct, and validate that development documentation matches codebase reality (daily diff-driven pass). Trace concrete doc claims to code and fix confirmed mismatches.
|
||||
|
||||
## Scope
|
||||
|
||||
- Audit targets: `docs/lib-overview.md`, `docs/lock-ops-overview.md`, `docs/memory-index-overview.md`, `docs/removal.md`, `docs/architecture/system-overview.md`, `docs/AGENT_COVERAGE_GAPS.md`, `src/constants.mjs` (USAGE_TEXT)
|
||||
- Verify each claim by tracing to `src/` code
|
||||
- Fix P1 (incorrect) and P2 (incomplete) issues in targeted docs
|
||||
- Write claims map, diagnosis, and validation notes
|
||||
|
||||
## Constraints
|
||||
|
||||
- No inventing behavior — trace every claim to code
|
||||
- Minimal edits only
|
||||
- Constants USAGE_TEXT fix is a doc string in source code — small, safe, and a clear correctness fix
|
||||
|
||||
## Open questions
|
||||
|
||||
- None. All relevant source files found and inspected.
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
agent: docs-code-investigator
|
||||
cadence: daily
|
||||
run-start: "2026-02-20T07:00:00Z"
|
||||
prompt: src/prompts/daily/docs-code-investigator.md
|
||||
---
|
||||
|
||||
# Context — docs-code-investigator — 2026-02-20
|
||||
|
||||
## Selected target file
|
||||
|
||||
- **File:** `scripts/agent/run-scheduler-cycle.mjs`
|
||||
- **Line count:** 926 lines
|
||||
- **Reason for selection:**
|
||||
- Largest undocumented source file in the repo (existing overview docs cover only `src/lib.mjs`, `src/lock-ops.mjs`, `src/services/memory/index.js`).
|
||||
- Central orchestrator for all agent scheduling — highest maintenance risk.
|
||||
- Recent active commits with no corresponding documentation.
|
||||
- No `TODO/FIXME/XXX` but function-level complexity warrants JSDoc and a flow overview.
|
||||
- **Last significant commits:**
|
||||
- `a5f08ff` feat(scheduler): add local time-window guard (recent)
|
||||
- `9278dad` Print final run summary in scheduler cycle
|
||||
- `ae2e382` Fix: Correctly detect agent platform for locks
|
||||
|
||||
## Plan
|
||||
|
||||
1. Add top-of-file flow comment (16-step outline per `src/prompts/scheduler-flow.md`).
|
||||
2. Add JSDoc to all internal helper functions.
|
||||
3. Add targeted inline comments where intent is non-obvious.
|
||||
4. Produce `docs/scheduler-cycle-overview.md`.
|
||||
5. Write run artifacts.
|
||||
|
||||
## Constraints
|
||||
|
||||
- Documentation only — no behavioral changes.
|
||||
- No crypto code in this file; no security issue to open.
|
||||
- Single file scope: only `scripts/agent/run-scheduler-cycle.mjs` modified.
|
||||
- `npm run lint` and `npm test` not runnable in Claude Code sandbox (KNOWN-ISSUE-sandbox-eprem-tests).
|
||||
Reference in new issue
Block a user