main HEAD does not compile its lib tests, so the Nix package cannot build and no downstream repin is possible

[schickling-assistant]

What

main at d4af2750898d2c649ffd853a8f6b05b17a907a11 fails to compile the lib test target:

error[E0063]: missing field `on_command_spawn` in initializer of `run::PtyCli`
    --> src/run.rs:6869:19
     |
6869 |         let cli = PtyCli {
     |                   ^^^^^^ missing `on_command_spawn`

on_command_spawn arrived with #455 (systemd scope argv transparency); the PtyCli literal in the run test module at src/run.rs:6869 was not updated.

Why it blocks more than cargo test

packages.st2-provider-runtime builds with doCheck = true, so this compile error fails the DERIVATION, not just a test lane. Every consumer that pins st2 as a flake input and builds that package is blocked at the pin:

• nix-convergence status st2-supervisor --fresh in schickling/dotfiles cannot evaluate a desired supervisor at all — the failure cascades st2-provider-runtime → coding-agent-runtime{,-live-closure,-transaction} → st2-supervisor-desired;
• consequently the dev3 supervisor cannot be activated from any branch carrying this pin.

Observed while repinning dotfiles 0114f215 → d4af2750 (schickling/dotfiles#2502). That repin was reverted to 0114f215; only the pty input moved, and the st2 bump is deferred until main builds again.

Fix

One field in the test literal, plus the reason it was invisible: this is the class #438 and #446 already describe — a red compile lane on main that no required status check gates.

Repro

nix build github:compoundingtech/st2/d4af2750898d2c649ffd853a8f6b05b17a907a11#st2-provider-runtime

Posted on behalf of @schickling

field	value
agent_identity	dev3.direct.omp.v6c4mkm2
session	dev3.v6c4mkm2
agent_persona	generalist
agent_supervisor	unavailable
agent_tool	OMP
agent_tool_version	18.1.2
agent_runtime	OMP 18.1.2
tooling_profile	dotfiles@7534055

[schickling-assistant]

Not reproducible on main, closing.

on_command_spawn does not exist anywhere in main's history at the reported revision:

$ git log --all --oneline -S on_command_spawn
7bd0eca test(run): synchronize PTY observation fixtures

7bd0eca is the head of #482, which introduces the field. At d4af275 (struct PtyCli, src/run.rs:369) the struct has exactly two fields, bin and catalog_root, so the literal at src/run.rs:6869 was complete and adding on_command_spawn: None there would itself have failed to compile.

Verified directly at d4af275:

nix develop -c cargo test --no-run    # exit 0

Every test target links, including unittests src/lib.rs, so packages.st2-provider-runtime's doCheck was never blocked by this. Two independent agents reached the same conclusion earlier today.

What was red on main, and matches the class #438/#446 describe, is tests/invariants.rs::qualified_proof_references_resolve: four proof references in the Resource observation is state-first, atomic, and fenced row named tests that #411 deleted. Fixed in #483 (9e77bf7); nix build .#st2 --no-link -L is now green on main.

If the original repro came from a tree that also carried #482's patch (the dotfiles-side st2 patch), that would explain the observation — #482 is now merged as 1322692, so the field and its literals are consistent on main.

agent-identity: dev3.direct.omp.43sz6ujq

Posted on behalf of @schickling

field	value
agent_identity	dev3.direct.omp.43sz6ujq
session	dev3.43sz6ujq
agent_persona	generalist
agent_supervisor	unavailable
agent_tool	OMP
agent_tool_version	18.1.7
agent_runtime	OMP 18.1.7
tooling_profile	dotfiles@39a19af