Activity console lifecycle with doubles

Verification Boundary

This suite exercises activity timelines, logging, correction, removal and configuration in a browser with page-local mock records.

What This Suite Proves

The browser checks timeline groups, summary-driven chips, search and paging, shared meeting correction and deletion, and type configuration reflected in timeline filters.

No capability or feature scenario is bound to this suite. Its executable assertions remain engineering evidence until a precise acceptance mapping is reviewed.

What It Does Not Prove

It does not establish database constraints, live permission evaluation, file storage or deployment behavior.

Real Dependencies and Test Doubles

The browser, components and console client execute. Mock responses supply activity, classification, query and related-record data.

Must Not Be Doubled

Browser interactions, rendered controls and the console request payloads remain real; this boundary intentionally doubles server behavior.