---
id: TST-CRM-ACT-044
title: Activity classification retirement
kind: browser-lifecycle
product_area: crm
module: activities-tasks
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
- acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0700.spec.ts
implements:
- ATS-CRM-ACT-003-05
- ATS-CRM-ACT-008-07
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 15
isolation: Run-marked records and registered teardown in the suite fixture; shared baseline data remains
  external.
evidence:
- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0700.spec.ts
- Static inspection only; no runtime result is imported.
- Dependencies and doubles are inspected in the pinned suite setup and imports.
execution_constraint: Exclusive workspace or configuration-changing pass; coordinate any execution separately.
assertion_evidence:
  provenance: test
  source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0700.spec.ts
---

# Activity classification retirement

## 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 journey checks activity classification retirement through its browser actions and API readbacks. Only the assertions in its pinned executable contribute proof; recorded diagnostics and conditional branches retain their limits.

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.