Command Recording

Test commands can be observed without changing their executable files, including fixture programs that product code starts itself.

Configure Observation

A verification controller may set LNK_TEST_RECORDER to an owned TOML manifest of recording::Recorder. It names an absolute recorder program, its prefix arguments and the selected executable basenames or prefixes. env::command then invokes that recorder with the original program and arguments. Program files and copies remain unchanged. An absent manifest keeps the ordinary command path, while a malformed one fails explicitly.

Delegate Fixture Commands

When product code starts a fixture executable itself, pass it the path returned by recording::program(original, owned_folder). For a selected program, the kit writes a shim in the test's owned folder that replaces itself with the recorder. Keep that folder alive while its commands run. An absent recorder or an unselected basename returns the original path without writing files. This observes delegated commands through the same selection and invocation contract as env::command.

Recorder Invocation

The recorder receives its prefix arguments followed by the basename, executable path and original arguments. It must preserve input, output, exit and signal behavior. The manifest contains no credentials, and normal child environment filtering still applies.