Files
codebase-memory-mcp/tests
Martin Vogel f89e0c961f test(nix): correct enclosing-parity fixture — wrap the call so no top-level application
The Nix case asserted zero Module-sourced CALLS edges, but its 'in run 21' body
is a genuinely top-level application: production correctly attributes the
in-lambda call (double n -> run) to the function AND the top-level call
(run 21 -> Module) to the Module. The parity invariant counts every
non-Function-sourced edge as drift, so the legitimately-Module-sourced top-level
call produced a false RED.

Nix's function_expression call-scope resolution already works (named from the
parent binding's attr). Move 'run 21' inside a 'main' lambda and make the 'in'
body a bare reference, so every call is in-function — strengthening the
invariant (now double->run AND run->main are checked) without weakening it. The
contract_edge_async_calls unit test is pre-existing-flaky (passes on re-run;
unaffected by this repro-only change).

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
2026-06-28 07:49:00 +02:00
..
2026-06-03 02:13:30 +02:00