[Bug] supervisor-owners registry ignores PRIME_AGENT_CODING_AGENT_DIR — isolated test runs leave stale owner records in the real ~/.prime (0.8.1)

[KoLyslaV]

Affected area

Daemon (supervisor ownership registry) / test isolation

Environment

• prime-agent 0.8.1, Node 22, Ubuntu; running the repo's own vitest suites (packages/coding-agent) on a machine that also runs a real daemon

What happened?

A test-run supervisor started with a fully isolated agent dir still writes its ownership record into the real user-level registry ~/.prime/supervisor-owners/.

Repro observed with:

export PRIME_AGENT_CODING_AGENT_DIR=/var/tmp/<isolated>/agent
export TMPDIR=/var/tmp/<isolated>/tmp
vitest run test/daemon-supervisor-process.test.ts ...

Afterwards the real registry contains e.g. ~/.prime/supervisor-owners/<generation>.owner/owner.json with:

{
  "socketPath": "/var/tmp/<isolated>/tmp/prime-supervisor-<pid>-<hash>.sock",
  "agentDir": "/var/tmp/<isolated>/tmp/prime-daemon-supervisor-test-<rand>/agent",
  "phase": "owner"
}

i.e. the record honors the isolated agentDir in its content but not in its location. If the test run is killed (CI abort, SIGSTOP/SIGKILL), the stale owner record stays in the production registry forever.

A second, worse variant: running the same suites without PRIME_AGENT_CODING_AGENT_DIR (easy to do from docs) had test supervisors log into the real ~/.prime/agent/logs/* and touch the real /tmp/prime-agent-<uid>/update-restart-coordinators while a production daemon was live on that socket dir.

Impact

• stale owner records pollute the singleton/takeover forensics of the real daemon
• unisolated runs can interact with a live production socket dir (update-restart coordination)
• confusing debugging: test-path stack traces appear in the production daemon log

Suggested fixes

1. Derive the supervisor-owners root from the same agent-dir resolution as everything else (so PRIME_AGENT_CODING_AGENT_DIR isolates it too), or honor an explicit override env.
2. Consider a guard that refuses to write test-scoped supervisor records into a registry whose default socket dir is currently owned by a live supervisor.