/**
 * E2E integration tests for cross-service references (Wave 3c).
 *
 * Scope note: these tests exercise the full cross-reads resolver against the
 * real filesystem (StateManager.loadStateReadOnly, migrateState, state merging,
 * per-service cache, transitive DFS). MetaPromptFile fixtures are typed objects
 * rather than on-disk pipeline content because Wave 3c is the first feature to
 * use the crossReads frontmatter field — no real pipeline step uses it yet.
 * CLI-wiring coverage (loadPipelineContext + runCommand.handler) lives in
 * src/cli/commands/run.test.ts's "cross-reads artifact gathering (Wave 3c)"
 * suite, which mocks resolveTransitiveCrossReads at the module boundary.
 *
 * Verifies:
 *  - resolveTransitiveCrossReads returns foreign service artifacts
 *  - transitive chain A → B → C surfaces C's artifact via B's crossReads
 *  - the read-only loader NEVER writes to foreign state — regression test for
 *    the Round-4 P0 (migrateState → saveState clobbering next_eligible)
 *  - cross-reads work while a foreign service's lock is held (no deadlock,
 *    no foreign-state write under concurrency)
 */
export {};
//# sourceMappingURL=cross-service-references.test.d.ts.map