agent-conduct

To enforce agent-name independence, you review test suites and CI configuration for hardcoded squad agent references, replace them with generic parameterized fixtures like test-agent-1, then run the affected tests to verify isolation before submitting changes.

Cross-squad product isolation ensures that product code, CI workflows, and test suites never depend on specific agent identities from any particular squad. It enforces the use of generic or parameterized identifiers instead of hardcoded agent names to maintain strict separation.

Validate CI regressions before finishing code changes by running the relevant test suite for the specific files you touched. You must check for CI regressions and document any updates when learning from mistakes encountered during the peer quality validation process.

Yes, your test suite needs parameterized fixtures or obviously-fake generic identifiers to avoid referencing specific agent names. This is a hard product isolation rule that prevents tests from breaking when squad agent identities change or are reassigned.

You should run affected tests immediately after updating shared agent-related tooling and replacing hardcoded agent names. Running the relevant test suite for the files you touched and checking for CI regressions is required before completion to satisfy peer quality checks.