/**
 * SMI-5980 (Wave 3): writeInstallFiles must route the companion-subagent
 * write through COMPANION_AGENT_TARGETS (install/paths.ts) for the caller's
 * `client`, not a hardcoded `path.join(os.homedir(), '.claude', 'agents')`
 * literal.
 *
 * `homedir()` is mocked to a controlled tmp directory BEFORE `paths.ts` is
 * first imported — COMPANION_AGENT_TARGETS is a module-level constant
 * computed once at import time from `homedir()`, so every assertion below
 * compares against that SAME already-resolved map rather than a second,
 * independently-hardcoded expectation. This also keeps the test from ever
 * writing to a real developer/CI machine's actual home directory.
 *
 * SMI-5982 (Wave 6): antigravity's `COMPANION_AGENT_TARGETS` entry uses a
 * RELATIVE `dir` (resolved against `process.cwd()`, not `homedir()`) — its
 * own dedicated describe block below chdir's into an isolated tmp directory
 * per test (never TEST_HOME, never the real repo checkout) rather than
 * relying on the homedir() mock every other client's assertions use.
 *
 * SMI-5982 code-review fix #1 (BLOCKING, cwd-dependent resolution):
 * `writeInstallFiles()` now resolves antigravity's relative `dir` via
 * `resolveCompanionAgentPath()`'s explicit `baseDir` param (defaulting to
 * `process.cwd()` at the call site, not deferred to whatever `fs` call
 * eventually consumes the path) — so `result.subagentPath` is now an
 * ABSOLUTE path even for antigravity, not the raw relative string. The
 * `it.each` below covers both the omitted-`companionBaseDir` (falls back to
 * `process.cwd()`, which this describe block's chdir controls) and an
 * explicit `companionBaseDir` override.
 *
 * Split out of skill-installation.io.test.ts to stay under the 500-line
 * CI gate (same rationale as skill-installation.io.symlink.test.ts).
 */
export {};
//# sourceMappingURL=skill-installation.io.client-agent-path.test.d.ts.map