WSR for DeepSeek Harness

This repository is the release authority for the WSR Execution, WSR Studio, and combined WSR suite integrations for DeepSeek Harness.

Release set 0.2.5 qualifies Execution 0.2.4, Studio 0.1.2, and suite 0.2.4 coordinates.

Workspace packages:

• dsh-wsr-execution — display name WSR
• dsh-wsr-studio — display name WSR Studio
• dsh-wsr — compatible combination suite with no additional UI identity

Packages follow semantic versioning independently. The suite accepts
dsh-wsr-execution@^0.2.4 and dsh-wsr-studio@^0.1.2. DeepSeek Harness
compatibility remains fixed at 0.1.1-rc.2; immutable release evidence records
the exact Execution owner revision and asset digest used for qualification.
The current owner package is qualified from stable asset
wsr-execution-0.2.3.tgz in release 0.2.3 (SHA-256
6066972da9d3ff20ab370bdd921d14754cfc8de8069e3f1c985ef5a98ac273fd).
There is no ambient npm resolution of wsr-execution: DSH profiles install that
asset explicitly as a top-level root because DSH blocks exotic transitive
dependencies.

Development gates

Use Node 24.12.0 and npm 11.6.2:

npm ci --ignore-scripts --no-audit --no-fund
npm test
npm run build
npm run pack:verify
npm run qualify:clean-profile
npm run qualify:real-harness
WSR_QUALIFY_TERMINAL=1 npm run qualify:real-harness

WSR_QUALIFY_TERMINAL=1 adds deterministic completed/failed/cancelled owner
facts and exact adapter-private historical associations to the temporary clean
profile. The real Host and Chrome then verify terminal inventory, the current
Session's latest terminal Delivery, and reload without invoking a Provider.

npm run build generates the two CSP-compatible browser bundles and verifies
workspace identity, compatibility, dependency direction, activation
composition, and the active fixed-version Workspace UI fork. npm run boundaries:check -- <external-package.json...> additionally rejects
domain-owner repositories that depend back on a dsh-wsr* package.

npm run pack:verify creates temporary archives and checks their actual tar inventories, including license and source notices. npm run qualify:clean-profile uses temporary DSH homes, the pinned local DSH CLI, and the immutable Execution owner asset; it performs no publication. npm run qualify:real-harness additionally boots the real Host and Chrome against a clean profile. DSH 0.1.1-rc.2 emits no CSP header, so the automated bundle gate separately rejects eval, new Function, and inline-script injection; qualification does not claim a CSP header supplied by DSH.

The Release Candidate workflow runs clean-profile, lifecycle, real-Harness,
downstream-outage, and remote-artifact gates before creating an immutable
prerelease. Release Promote verifies the same bytes and qualification record,
publishes changed component packages before the compatible suite through npm OIDC, and
uses the scoped release App for the final GitHub release. See release and
installation lifecycle, changelog,
and security policy.

See foundation boundaries for repository ownership and the deferred Workspace UI fork decision.

Project context and system authorities remain in https://github.com/firestige/workflow-self-recursive.