Trusted task service lifecycle

Verification Boundary

This suite sends requests through the real local API or trusted-service handler and verifies the responses and retained data.

What This Suite Proves

Local trusted invocation checks creation flags, repeated commands, attribution, role offers and offered reads, alongside HTTP and principal refusals.

The registered scenario bindings identify the assertion contributions this executable supplies. A compound scenario can require several suites.

What It Does Not Prove

It does not establish deployed Lambda transport, live Platform policy or end-user browser behavior.

Real Dependencies and Test Doubles

The local handler, schemas, signed-context checks and persistence execute against PostgreSQL. Generated signing keys and in-process request delivery replace deployment transport. Role eligibility uses local Platform security fixtures rather than a deployed security-service lifecycle.

Must Not Be Doubled

Route dispatch, schema checks, authority evaluation and database writes remain real.