Activate user unit checks

Verification Boundary

The file evaluates production helpers with controlled inputs in-process. The assertion references identify the source checks for activate user.

What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

Real Dependencies and Test Doubles

The production decision runs in-process. The suite substitutes the clock, repository reads or writes where its dependency setup supplies them; those boundaries have no live-service proof here.

Must Not Be Doubled

Keep the production helper, schema, matcher or declaration under examination real. Substituting the decision itself would remove the behavior the assertions exercise.