---
id: TST-PFM-INT-059
title: Rhythm withdraws a private integration and renames it with a pre release while Northwind uses it
kind: browser-lifecycle
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - acceptance/integrations/playwright/journeys/adversarial/INT-ACC-0643.spec.ts
implements: []
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
isolation: >-
  Use the acceptance harness workspace restrictions, persona fixtures, run-marked records and cleanup;
  exclusive or destructive cases require the disposable workspace.
evidence:
  - 'react-console:acceptance/integrations/playwright/journeys/adversarial/INT-ACC-0643.spec.ts'
test_cases: []
acceptance_record: acceptance/integrations/journeys/adversarial/INT-ACC-0643.json
execution_modes:
  - deployed-dev
harness_limitations: Some steps explicitly report unavailable harness support; no whole-feature binding is inferred.
recorded_isolation: exclusive
recorded_automation:
  status: blocked
  isolation: exclusive
  blocked_reason: environment-wide change (changes an integration's availability); needs the owner's approval
---
# Rhythm withdraws a private integration and renames it with a pre release while Northwind uses it

## Verification Boundary

This browser suite exercises the console journey for rhythm withdraws a private integration and renames it with a pre release while northwind uses it. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

## What It Does Not Prove

Some steps report missing harness support. Those steps do not supply executable product proof. A mock run does not establish deployed persistence, provider effects or service authorization. The suite does not establish a complete feature sequence merely because it visits several screens.

## Real Dependencies and Test Doubles

The deployed mode uses the console and acceptance service clients. The mock mode substitutes responses through the harness. Run records and the suite definition identify any live-only or unavailable step.

## Must Not Be Doubled

The console interactions and assertions for a claimed browser outcome must execute. A deployed claim also requires the service and persistence effects checked by that step.