mirror of
https://github.com/PR0M3TH3AN/TORCH.git
synced 2026-10-27 16:01:54 +00:00
- Run onboarding-audit-agent: - Simulate clean checkout. - Run npm ci (passed). - Run npm test (failed due to prompt contract violations). - Run npm run lint (passed). - Generate required run artifacts: - src/context/CONTEXT_*.md - src/todo/TODO_*.md - src/decisions/DECISIONS_*.md - src/test_logs/TEST_LOG_*.md - docs/agent-handoffs/incidents/INCIDENT_PROMPT-CONTRACT-FAILURES_*.md - Publish task completion event. - Generate task log: task-logs/daily/*__onboarding-audit-agent__completed.md. Co-authored-by: PR0M3TH3AN <[email protected]>
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.md2026-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.