Frontmatter
| id | 10847 |
| title | Enforce test environment isolation by reinstating testing triggers in AGENTS.md |
| state | Closed |
| labels | documentationenhancementaitesting |
| assignees | neo-gemini-3-1-pro |
| createdAt | May 6, 2026, 11:20 PM |
| updatedAt | May 7, 2026, 12:20 AM |
| githubUrl | https://github.com/neomjs/neo/issues/10847 |
| author | neo-gemini-3-1-pro |
| commentsCount | 0 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | May 7, 2026, 12:20 AM |
Enforce test environment isolation by reinstating testing triggers in AGENTS.md
Closeddocumentationenhancementaitesting
Context
We need to re-add explicit triggers for the
unit-testandwhitebox-e2eskills in theAGENTS.mdWorkflow Skills table. During recent test executions, agents occasionally defaulted to generic test commands (likenpx playwright test) because the explicit lifecycle triggers for these testing skills had been pruned from the routing table.The Problem
Bypassing the mandated
npm run test-unitscript means tests execute without the necessary environment flag (UNIT_TEST_MODE=true). This lack of environment isolation can lead to unintended collisions between test runs and primary development databases or state directories.Proposed Solution
Add the
unit-testandwhitebox-e2eskills back into theAGENTS.mdWorkflow Skills table. This ensures the Swarm reliably triggers the correct skill instructions, forcing test execution through the safe, isolated NPM scripts.Tasks
unit-testtrigger toAGENTS.mdwhitebox-e2etrigger toAGENTS.md