0 Fork 0

mirror of https://github.com/PR0M3TH3AN/TORCH.git synced 2026-10-31 01:41:55 +00:00

Files

T

google-labs-jules[bot]andPR0M3TH3AN 61b3fd5709 fix(security): prevent command injection in governance service and fix build errors

- Mitigate command injection in `src/services/governance/index.js` by using explicit array arguments with `execFileSync` and adding a security comment.
- Add regression test `test/governance-security.test.mjs` verifying the fix against simulated exploit attempts.
- Fix CI build failures by resolving circular dependencies and duplicate declarations in `src/lock-utils.mjs`, `src/lock-ops.mjs`, `src/lock-publisher.mjs`, and `src/relay-health.mjs`.
- Resolve linting errors in tests and implementation files.

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

2026-02-21 19:55:52 +00:00

incidents

fix(security): prevent command injection in governance service and fix build errors

2026-02-21 19:55:52 +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.