Task console lifecycle in development

Verification Boundary

This suite exercises the scoped browser journey with service readback and the assertions present in the pinned executable.

What This Suite Proves

The browser checks personal views, teammate assignment, completion, queue creation context and claims, plus configuration-to-entry type availability with direct service readback.

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 a passing run here. Diagnostic observations, conditional steps and soft assertions retain their recorded limits; unrelated feature scenarios remain outside this suite.

Real Dependencies and Test Doubles

The browser uses the deployed console, CRM, Platform authentication and any query or lifecycle services requested by the journey. API helpers create run-owned fixture records; those fixtures do not replace the deployed handlers.

Must Not Be Doubled

The browser controls, deployed authorization, service mutations and readbacks that supply the asserted outcome remain real.