0 Fork 0

mirror of https://github.com/PR0M3TH3AN/TORCH.git synced 2026-10-29 00:41:58 +00:00

Files

T

google-labs-jules[bot]andPR0M3TH3AN c0c5ac5473 fix(torch-lock): re-apply fixes for circular deps and syntax errors

- Moved `withTimeout` implementation to `src/lock-utils.mjs` and exported it correctly.
- Removed duplicate local definitions of `withTimeout`, `mergeRelayList`, and `secureRandom` in `src/lock-ops.mjs` and `src/lock-publisher.mjs`.
- Fixed imports in `src/lock-ops.mjs`, `src/lock-publisher.mjs`, and `src/relay-health.mjs` to use `src/lock-utils.mjs` consistently.
- Updated `test/utils.test.mjs` and `test/utils-async.test.mjs` to fix broken imports and test definitions.
- Verified `npm run lock:complete` and `npm run scheduler:daily` execute correctly.
- Updated `src/todo/TODO_2026-02-20T03-00-00Z.md` to mark verification task as completed.
- Verified `src/relay-health.mjs` does not use `MINUTE_MS` locally, despite mysterious CI error. Confirmed imports are correct.

Co-authored-by: PR0M3TH3AN <[email protected]>

2026-02-21 19:23:48 +00:00

incidents

fix(torch-lock): re-apply fixes for circular deps and syntax errors

2026-02-21 19:23:48 +00:00

learnings

update

2026-02-20 12:51:17 -05:00

README.md

Refactor agent docs to repository-agnostic workflow

2026-02-13 22:34:57 -05:00

README.md

Agent Handoffs

This directory stores reusable context so future agents can work faster without repeating discovery.

Directory purpose

learnings/: successful patterns, proven fixes, and repeatable implementation guidance.
incidents/: failures, root causes, mitigations, and prevention guidance.

When to write a note

Create or update a note when your work reveals knowledge likely useful in future sessions.

Examples:

A reliable fix pattern that can be reused.
A recurring failure mode and its mitigation.
A validation approach that prevented regressions.

If the issue is still active/reproducible, also update KNOWN_ISSUES.md.

Naming convention

Use:

YYYY-MM-DD-short-topic.md

Examples:

2026-02-14-validation-before-summary.md
2026-02-14-missing-baseline-context.md

Required note structure

Each learning/incident note should include:

Context
Observation
Action taken
Validation performed
Recommendation for next agents

Writing guidelines

Keep entries short and actionable.
Prefer bullets over long narrative.
Include exact commands when useful for reproduction.
Avoid secrets, credentials, and identifying data.
Distinguish facts from assumptions.

Maintenance workflow

Search for an existing related note.
Update it if it already covers your case.
Otherwise, add a new note using the naming convention.
Cross-link related notes when helpful.