Skip to content

test(core): the PROJ-H3b anti-vacuity control demands a third getActor call - #170

Merged
cagodoy merged 1 commit into
mainfrom
feat/mvp-blockers-close
Sep 6, 2026
Merged

cagodoy merged 1 commit into
mainfrom
feat/mvp-blockers-close

Conversation

@cagodoy

@cagodoy cagodoy commented Sep 4, 2026

Copy link
Copy Markdown
Member

Summary

The PROJ-H3b anti-vacuity control demanded a second getActor call, but the behavior it guards only becomes observable on the third call. The test now asserts the third call, so it fails when the guarded behavior is removed and passes when it is present.

Verification

  • project_module suite green with the control in place; the assertion goes red when the guarded call is removed.

…r call, not a second

The control asserted `getActorCalls > 1` to prove that the "Nothing to commit"
guard polled before concluding the actor was absent. That threshold was
miscalibrated: addActor reads getActor once unconditionally (the existence
check at the top of the method) and the guard reads once more before it ever
enters its poll loop, so a guard WITHOUT a poll already produces two calls and
satisfied the old assertion.

Measured with a negative control: making the actor visible on the second read
(poll never exercised) gives exactly `Received: 2` — green under `> 1`, red
under `> 2`. The threshold is now `> 2`, with the calibration written next to
it. Registered in the project_module audit (Task 1.2g, ears_test + dependency
findings on PROJ-H3b); this closes it. 44/44.
@cagodoy
cagodoy merged commit 7f5d13c into main Sep 6, 2026
4 of 5 checks passed
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 5.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant