chore(daily): run onboarding-audit-agent

- Executed onboarding-audit-agent.
- Verified npm ci, build, lint.
- Recorded npm test timeout in incident report.
- Updated KNOWN_ISSUES.md.
- Created task completion log.

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

KNOWN_ISSUES.md

@@ -45,6 +45,16 @@ Track only **active, reproducible, unresolved** issues.
 - **Impact:** CI/local testing blocked.
 - **Last verified:** 2026-02-14
 
+### `npm test` hangs/times out in full suite run
+- **Status:** Active
+- **Area:** Test
+- **Symptom:** `npm test` times out after 400s when running all tests together.
+- **Trigger/Conditions:** Running `npm test` in CI/Sandbox.
+- **Workaround:** Run individual test files or subsets (`npm run validate:scheduler`, `npm run test:integration:e2e`, then specific unit tests).
+- **Impact:** Cannot verify all tests in a single pass.
+- **Related notes:** `docs/agent-handoffs/incidents/2026-02-16-npm-test-timeout.md`
+- **Last verified:** 2026-02-16
+
 ### Recurring scheduler lock backend failures in recent task logs
 - **Status:** Monitoring
 - **Area:** Runtime

artifacts/onboarding-audit-agent/report.md

@@ -0,0 +1,51 @@
+# Onboarding Audit Report
+
+**Date:** 2026-02-16
+**Agent:** onboarding-audit-agent
+
+## Headline
+⚠️ Onboarding failures found
+
+## Environment
+- **Platform:** Jules Sandbox (Linux)
+- **Node Version:** v22.22.0
+- **npm Version:** 11.10.0
+
+## Steps Executed
+1. `npm ci`
+2. `npm run build`
+3. `npm test`
+4. `npm run lint`
+
+## Results
+
+| Command | Result | Exit Code | Notes |
+|---------|--------|-----------|-------|
+| `npm ci` | Pass | 0 | Installed dependencies cleanly. |
+| `npm run build` | Pass | 0 | Build output to `dist/`. |
+| `npm test` | **Fail** | Timeout | Command timed out after 400s. |
+| `npm run lint` | Pass | 0 | 12 warnings found (no errors). |
+
+## Failures
+
+### `npm test` Timeout
+The command `npm test` (which runs `npm run validate:scheduler && npm run test:integration:e2e && node --test test/*.test.mjs tests/*.test.js`) timed out after 401 seconds.
+
+**Investigation:**
+- `npm run validate:scheduler` passed (200ms).
+- `npm run test:integration:e2e` passed (692ms).
+- `node --test test/*.test.mjs tests/*.test.js` is the likely cause of the timeout.
+- Individual runs of `test/lock-ops.test.mjs`, `test/lock-ops-publish-retry.test.mjs`, `test/relay-fanout-quorum.integration.test.mjs`, `test/lock-acquisition-resilience.integration.test.mjs`, and `tests/memory.test.js` all passed quickly.
+- The timeout suggests either a deadlock or extreme slowness when running the full suite in this environment.
+
+### Lint Warnings
+`npm run lint` passed but emitted 12 warnings (mostly `no-unused-vars`). These should be addressed but did not break the build.
+
+## Recommendations
+1. **Investigate Test Suite Performance:** The test suite takes too long or hangs in the sandbox environment. Investigate `test/*.test.mjs` for potential deadlocks or resource contention.
+2. **Address Lint Warnings:** Clean up unused variables to keep the codebase clean.
+3. **Docs Update:** No documentation changes required as the commands are correct, but the execution reliability needs improvement.
+
+## Actions Taken
+- Verified individual test files passed.
+- Recorded full timeout failure.

docs/agent-handoffs/incidents/2026-02-16-npm-test-timeout.md

@@ -0,0 +1,23 @@
+# Incident: `npm test` Timeout in Sandbox Environment
+
+## Context
+Running `npm test` as part of the `onboarding-audit-agent` daily check.
+
+## Observation
+`npm test` timed out after 401 seconds.
+The command runs: `npm run validate:scheduler && npm run test:integration:e2e && node --test test/*.test.mjs tests/*.test.js`.
+- `validate:scheduler` passed (200ms).
+- `test:integration:e2e` passed (692ms).
+- `node --test test/*.test.mjs tests/*.test.js` timed out.
+Individual runs of many test files passed quickly.
+
+## Action taken
+Recorded the timeout in `artifacts/onboarding-audit-agent/report.md`.
+Verified individual tests passed.
+
+## Validation performed
+Ran individual tests (`lock-ops.test.mjs`, `lock-acquisition-resilience.integration.test.mjs`, etc.) and they passed.
+
+## Recommendation for next agents
+Investigate why running the full suite causes a timeout. It might be resource contention or a specific test that hangs only in the full suite context.
+Workaround: Run specific test subsets or increase timeout if possible.

task-logs/daily/2026-02-16T21-20-49Z__onboarding-audit-agent__completed.md

@@ -0,0 +1,18 @@
+# Agent: onboarding-audit-agent
+# Status: completed
+
+## Output
+- Ran onboarding audit.
+- Confirmed `npm ci` and `npm run build` pass.
+- `npm test` timed out after 400s; investigated and created incident report.
+- `npm run lint` passed with warnings.
+- Updated `KNOWN_ISSUES.md` with `npm test` timeout issue.
+- Created `artifacts/onboarding-audit-agent/report.md`.
+- Created `docs/agent-handoffs/incidents/2026-02-16-npm-test-timeout.md`.
+
+## Artifacts
+- `artifacts/onboarding-audit-agent/report.md`
+- `docs/agent-handoffs/incidents/2026-02-16-npm-test-timeout.md`
+
+## Next Steps
+- Investigate `npm test` timeout in full suite context.