Goal
Design an eval scenario that proves the file-edit tracker (introduced in b5d2c95) correctly scopes committed checks per-session when two agents work in the same project concurrently.
Each agent should be able to commit only its own edited files and exit cleanly — without false-positive uncommitted-changes warnings triggered by the other agent's in-progress work.
Why
The tracker implementation is complete:
- PostToolUse hook appends to .kata/sessions/{sessionId}/edits.jsonl
- kata enter captures baseline dirty files
- can-exit scopes the committed stop condition to session-edited files (advisory for others)
But no eval exercises the multi-agent path. Unit tests exist (src/tracking/edits-log.test.ts), and integration tests cover single-session scoping, but the original motivation — two agents, clean per-agent commits — is unverified end-to-end.
Out of scope
- Changing tracker implementation
- Baseline capture semantics
- Advisory message copy
Goal
Design an eval scenario that proves the file-edit tracker (introduced in b5d2c95) correctly scopes committed checks per-session when two agents work in the same project concurrently.
Each agent should be able to commit only its own edited files and exit cleanly — without false-positive uncommitted-changes warnings triggered by the other agent's in-progress work.
Why
The tracker implementation is complete:
But no eval exercises the multi-agent path. Unit tests exist (src/tracking/edits-log.test.ts), and integration tests cover single-session scoping, but the original motivation — two agents, clean per-agent commits — is unverified end-to-end.
Out of scope