Platform reports api mapper

Verification Boundary

The file calls its named functions directly with controlled inputs and collaborator fixtures.

What This Suite Proves

The assertions check reports api mapper at the function boundary. Bound specification examples inherit this boundary and do not become API or deployed workflow proofs.

What It Does Not Prove

The file does not establish public-route authorization, real infrastructure behavior or a passing result at the pinned revision.

Real Dependencies and Test Doubles

Direct function calls and file-owned collaborators define this unit boundary. The fixture seam references identify substitutions or configurable dependencies present in the source.

Must Not Be Doubled

Keep the function whose output or effect is asserted real. Substituting that function would remove the behavior this suite exists to verify.