Awareness: Cross-Repo Contamination

From: Testing Director (Cowork agent) To: All agents (Testing + Coding) Priority: High awareness — not a bug to fix, but a discipline to enforce Date: 2026-02-06

What Was Observed

During session 98, the editor2 Cursor workspace showed 162 uncommitted changes that included:

1. Generated module files (modules/restaurant-platform-menu-management/) with full NX library structure (actions, components, models, manifest) — these were created during an E2E test of the AI Platform Generator on gspace1 port 6200
2. Session docs filed under S97 (97.14 through 97.20) — but the current session is 98
3. Config changes (tsconfig-paths/modules, generated.paths.json) being modified alongside session docs
4. Commit message referencing "session-98" while the daily summary file shows editor2-95.12

Why This Matters

For Coding Agents (Cursor/Claude Code)

• Generated module artifacts from E2E tests on gspace1 may appear in editor2's working tree
• Committing these changes without review could introduce test artifacts into the production codebase
• Session numbering inconsistencies make it hard to trace which agent made which change

For Testing Director (Cowork)

• When I trigger AI generation flows on gspace1 during testing, the output files may land in editor2
• I need to be aware that my testing actions have side effects on the other workspace
• I should note in test reports when generation flows were triggered

Root Cause Hypothesis

The two workspaces (gspace1 and editor2) likely share:

• The same modules/ directory (symlinked or both pointing to the same NX workspace)
• The same backend APIs (ports 3000, 3001, 3002)
• The same MongoDB database

When the AI Platform Generator on gspace1 port 6200 creates an NX library, it writes to the shared filesystem. The editor2 workspace then picks up these files as uncommitted changes.

Recommended Discipline

Before Committing (Coding Agents)

1. Review the diff carefully — look for test artifacts from gspace1 E2E testing
2. Check session numbers — ensure docs match the current session
3. Separate commits — don't mix generated module files with bug fixes or session docs
4. Use git status filter — identify files that don't belong to the current task

During Testing (Testing Director)

1. Note when generation flows are triggered — document in test reports
2. Warn coding agents after triggering AI generation that may produce file artifacts
3. Don't assume generated files are isolated to the gspace1 instance

Session Tracking (All Agents)

1. Verify session number at the start of each work session via MCP
2. Use consistent session IDs in all commits and docs
3. Cross-reference the MCP session with git branch names

Not a Bug — A Process Issue

This isn't something to "fix" in code. It's a natural consequence of two workspaces sharing the same underlying NX monorepo and backends. The solution is awareness and discipline in how we handle commits and file artifacts.