# work-charter-dsh status and recovery Last updated: 2026-09-27 ## Published successor - GitHub Pre-release [v0.2.0-alpha.1](https://github.com/junwei529/work-charter-dsh/releases/tag/v0.2.0-alpha.1) is published: release ID `397642170`, `draft=false`, `prerelease=true`, published `2026-09-27T12:32:42Z`, requested `latest=false`. - Reviewed product commit `1d9d5cc26f3cb934028ffc6257385dbe82db1cd8` is on public main and is the target of annotated tag `v0.2.0-alpha.1` (tag object `17e4bd9f4c76d8a6244176c10bbc6ec9e8a050cc`). Later documentation commits do not move this tag or replace its assets. - All four uploaded assets were downloaded and matched the local bytes. Tarball SHA-256 is `f2b602d0ad5ed87d183f25c106ee72b11a10188f1cd45e39ccb3584caf3bf913`; provenance binds the actual product commit. Exact hashes and limits are in VERIFICATION. There was no npm publication or existing-profile/data mutation. - This post-publication documentation closeout records formed external facts only. The primary retains the authorized writer role through its documentation commit/push, then returns to none. The separately authorized SCDP retirement/archive and GitHub profile update proceed in their own repositories, in that order. ## Successor publication continuation - Authority: on 2026-09-27 the user approved proceeding through independent clean installation/profile qualification, final commit, ordinary push/main integration, and GitHub Pre-release `v0.2.0-alpha.1`. The same request authorizes subsequent SCDP retirement README/canonical-state updates and push, SCDP repository archival, then the GitHub profile README update. It does not authorize npm publication, changing old releases/data, or installing into an existing user profile. - Writer: the primary resumes sole-writer responsibility for this publication tranche; existing cumulative review findings and qualified product bytes remain the starting checkpoint. New release-facing changes receive independent review before commit. - Preflight: connector and CLI both identify `junwei529`; the three exact repositories grant admin/push access. Live WCDP `main` equals baseline `c71d0a9cbc399c61470159c0f595de5e7ed079c0`, is unprotected, and the release list has only `v0.1.0-alpha.1`. The CLI initially hit the sandbox network boundary; the authorized network-enabled metadata check then exited zero. No remote mutation has occurred at this checkpoint. - Release checkpoint: clean dependency installation, native consumer/Client checks, actual official CLI final-bundle installation, fresh Web profile Host health and authenticated HTTP startup pass. Real browser UI remains unverified (`ERR_BLOCKED_BY_CLIENT`); this explicit limitation is retained in release notes. Final archive is 103,216 bytes, SHA-256 `f2b602d0ad5ed87d183f25c106ee72b11a10188f1cd45e39ccb3584caf3bf913`; only bilingual README bytes differ from the earlier reviewed tarball. Exact evidence is in VERIFICATION. - Release review: the same independent Reviewer inspected the five changed publication documents, release notes, actual tarball/sidecars/provenance and clean-consumer/profile evidence. No new P1/P2 or commit/Pre-release blocker; prior findings remain closed. The primary accepts this bounded release result with the browser/live-model limitations intact. The review did not rerun author checks or verify remote permissions. - Next: create the authorized local commit, fill provenance with its actual SHA, integrate/push main without force, then publish `v0.2.0-alpha.1` with four checksum-bound assets and verify the remote state. SCDP retirement/archive and profile updates follow verified publication. Only mechanical formed-result recording was added after review. ## Successor design checkpoint - Current work: the approved Work Charter `0.9.1` successor is implemented in this working tree with native Team scope and no SCDP runtime. Scope and versions are in [SPEC](SPEC.md#successor-design-work-charter-091-and-scdp-retirement). This is an unpublished candidate, not the old release. - Live baseline: `D:/GitLib/dsh/work-charter-dsh`, branch `codex/wcdp-v0.1.0-alpha.1-release`, HEAD `c71d0a9cbc399c61470159c0f595de5e7ed079c0`, sole listed worktree, clean index/worktree at entry. The former documentation writer window is completed; its text below is a historical release checkpoint, not current authority. - Current writer: no active implementation writer after this closeout. The primary completed the approved source/test/documentation work as sole writer and stopped target edits during each independent review. The remaining dirty tree is the intentional uncommitted successor delivery. Resume by checking this checkpoint, exact Git state and new authorized scope. Legacy runtime stores, old verification artifacts, other repositories and installed profiles remain outside this work. - Confirmed baseline: installed Codex Skill `0.9.1`, package receipt tree `39659168b5fb20899335dd0923c87b65d5a95e36`; all six installed file hashes match the receipt. This establishes inspected installed-file identity, not fresh model-loading or runtime efficacy. - Confirmed decision: `SC-01` option A, native-Team scope, approved by the user on 2026-09-27. Independent Sessions may run separate Direct work, but are not grouped into one successor Charter. No separate SCDP runtime or cross-Team coordination is retained. - Runtime checkpoint: the approved DSH graph is installed locally with lifecycle scripts disabled. Direct without Team, native first-call/restart frozen model routes, Phased E/R/P/O result/review/acceptance, logged context, incompatible-store rejection without writes, and lost-reply UNKNOWN across restart pass keyless deterministic qualification. Exact evidence and limitations are in VERIFICATION; these are not natural-language efficacy claims. - Confirmed decisions: `SC-02` package `0.2.0-alpha.1`, contract/logical storage `2`, DSH `0.1.7-rc.2@477b4f420553e8a52c2fbccc464d7561b239c443`; `SC-03` fresh isolated successor profile/store without automatic legacy migration. Do not reopen these decisions. A later dependency-closure approval gate does not change them. - Implementation checkpoint: strict arrangement-v1 schemas, separate contract/run state, exact Agent/native role binding, CAS mutations, preserved authority/evidence/notices, same-author/R corrections, YAML model selection, pre-first-call and cold-resume model routing, read-only Client, Skill/tool contracts and successor package/audit scripts are connected. Build, configured strict typecheck, full lint, 59 tests, native Host/restart/Phased qualification, native SlotRegistry/jsdom Client coexistence, artifact audit and extracted-package imports pass. Old profiles/data/artifacts are unchanged. Full real-browser/profile installation and natural-language efficacy are not claimed. - Review: the initial three-document design review had no blocking findings. Implementation round 1 identified `RM-R1` (P2), scalar-only validation of shared parameters; round 2 confirmed its repair and identified `RM-R2` (P2), raw prohibited keys disappearing before validation, and `RM-R3` (P2), locale-equivalent distinct Unicode keys breaking structural comparison. The primary fixed both with raw pre-validation and exact string ordering, plus regression tests. The same R's final re-review closed all three findings with no unresolved P1/P2 or new blocking finding. This qualifies only the scoped model-core checkpoint, not the complete successor. - Dependency authority: the user approved the recorded project-local installation and isolated validation proposal on 2026-09-27, including DSH `0.1.7-rc.2`, Cordis `4.0.4`, Schemastery `3.18.4`, and js-yaml `4.3.2`; do not ask again. Preserve old profiles and stores and disable lifecycle scripts. - Supplemental acquisition: following the recorded automatic rejection, the user explicitly approved exactly `@deepseek-ai/dsh-api-gateway`, `@deepseek-ai/dsh-client-connection`, and `@deepseek-ai/dsh-client-store` at `0.1.7-rc.2`. The approved project-local install then exited `0`, scripts disabled. The ClientRemote declaration/lint blocker is resolved; failed and rejected prior attempts remain evidence. - Independent review: same-R round 3 closed WCDP-R6 after its dual-subject positive/negative probe. WCDP-R1 through R6 and RM-R1 through RM-R3 are all closed; no unresolved blocking finding. The primary dispositions the local implementation and bounded qualification as complete under the approved scope, with evidence limits retained in VERIFICATION. This is not a claim of user acceptance or a new release. - Delivery: `.verification/successor-0.2.0-alpha.1/package/3448f875-9049-4093-bb41-e8df8d0d1f37/work-charter-dsh-0.2.0-alpha.1.tgz`; SHA-256 `b7d1bc6b27222710a4eedb1fdb32dcddf2351a102ab48243e89584be22a86466`. Exact evidence/checks are in VERIFICATION. No required work remains within the completed local candidate scope. Commit/push/publication, upstream changes, user-profile installation and legacy-data mutation remain outside current authority. ## Existing release checkpoint (historical) - Phase: base exact-artifact qualification, dedicated L4 Standard O/P/E qualification, the DSH bundle-install correction against official DSH `dsh-v0.1.2-alpha.1`, and public GitHub Pre-release publication are complete. No controlled baseline comparison or independent semantic assessment has run. - Repository subject: public `main@f734c2a6e2b8bb8e57475365d6d165f1d4f41d5c`; release-qualification commit `dae0362b15dc62278f16754ec6fc7ac3c5a92aa9`; and bundle-correction/release commit `09e52fd9860c6d3c8813f71f16c004f2a392c0a3` on branch `codex/wcdp-v0.1.0-alpha.1-release`. Annotated tag object `d5a7bd6baf17848c6d1fed31a5b019333c32eed3` for `v0.1.0-alpha.1` peels to that release commit. Post-release documentation commits do not move the tag or alter the published artifact identity. - Package identity: private `work-charter-dsh@0.1.0-alpha.1`, owned by `package.json`. The exact current release and runtime subject is `.verification/release-readiness/final/work-charter-dsh-0.1.0-alpha.1.tgz`, 39 entries, 98,593 bytes, npm SHA-1 `74a13559a6acf689d941584d144ab966668a43a6`, SHA-256 `40b2b176ad44a5ab888f36c555ad26ac23fe87aac7ed228a75717db2ac6f711b`, and SHA-512 `6c8350817e4429dd1e6b0998fe584b2576dc403d728315094ed69ee340fe38996f6227d2d24ac3520b9d74490b804deb879591f435f18e29eeb82b9007c32ea7`. Its packaged 52-line README is the checksum-bound pre-publication snapshot and still contains the then-true statement that the tag and Release did not yet exist; this post-release documentation tranche does not alter or replace the published and verified bytes. The asset name or URL alone is not the qualified identity. - Writer disposition: the current root Codex task is the sole writer only for the authorized bilingual README and canonical release-state alignment through native review and one local commit. A verified commit plus clean worktree closes this window and leaves repository writer `none`. - Authorized effects for the current documentation tranche: update the English and Chinese README, reconcile canonical publication state required by review, stage the exact documentation files, run native review, and create one local commit. - Excluded current effects: push, pull/rebase/merge, moving or replacing `v0.1.0-alpha.1`, changing the GitHub Release or its assets, npm publication, dependency installation, global configuration, DSH or scdp tracked-source changes, and unrelated cleanup. ## Bound dependencies - `WC-UPSTREAM`: installed Codex Skill `junwei529/work-charter` `0.3.0`, package SHA-256 `7b67ea1f7073fa66ac91c36f3e39c735b54c04174e2fa3672068f8fa8948a5b2`, normalized package tree `0ac3cbb0f1fa8fa51d8f832c8127eabc9863ec9e`. - DSH: task-owned clean detached checkout `.verification/dsh-v0.1.2-alpha.1`, exact tag `dsh-v0.1.2-alpha.1`, commit `cd5ef8148158c3a752a658978873241fdf8e2bbc`. Its official build and 241-package release pack completed without tracked-source drift. The complete 241-tarball plus publish-order manifest has 242 rows and SHA-256 `b8aa5da1d0fec2abd7bf581819d7638de6e859adfd60c530a466b1c7ff90b1c6`. - Coordination dependency: private `session-coordinator-dsh@0.1.1-alpha.1`, public contract `3`, logical schema `2`, accepted source commit `8bed40f3e18b106c69e3dadbef6f029092e73424`, and public GitHub Pre-release tag `v0.1.1-alpha.1`. The exact published 31-entry, 97,138-byte artifact copied under `.verification/release-inputs/session-coordinator-dsh-v0.1.1-alpha.1-published/` has SHA-256 `9575d1edf782f16b2d87b49bc27e290ecf841fa607a7d4a4468a41de2389b269` and SHA-512 `2cffe633734aea39989dd28d70e811536dd54aace5038b87ece3416013809fabf1394e053559e2f6c9b61c67f35ecd22a10972621cb3bdf79b097dd0bc2df2df`. - Registry boundary: the exact alpha.1 DSH packages and scdp package are not published to npm. WCDP release production and consumer qualification therefore use the exact local DSH artifacts plus the checksum-bound public scdp GitHub asset. Ordinary registry-backed installation remains `BLOCKED`; local two-producer release reproducibility is accepted only for this exact graph. ## What is implemented - Authoritative Host state with strict runtime schemas, compare-and-set revisions, role/writer policy, current Workstream-member revalidation, evidence/decision/notice state, unique checkpoint-per-route notices, latest-result acceptance gating, and fail-closed transitions. - Plugin-owned storage with metadata/row validation and explicit incompatible or unknown states. - Public-contract-only scdp integration for Workstream/Session validation, addressed Result Notices, causal dispositions, delivery state, idempotency, and unknown/conflict recovery. - A DSH Skill, five model tools, and bounded active/paused runtime context reconstructable from the DSH Session log. - Host Node ESM, generated Typert/Remote declarations, and DSH lazy-CJS Client packaging with exact peer/development identities. - An installable DSH bundle declaration whose packaged `cordis.patch.yml` mounts the plain scdp profile dependency before the WCDP policy layer. - Additive global and per-Session read-only browser UI that leaves authoritative mutation on the Host/model-tool path and leaves DSH goal, plan, workflow, approval, Conversation, Trajectory, root/sidebar, and scdp ownership outside Work Charter authority. - Alpha.1 split-Client adaptation using public Cordis, API Remotes, UI Renderer, UI Session, Conversation, Layout, and Sidebar faces; the removed aggregate Client runtime is absent. ## Qualification checkpoint - Work Charter `build`, strict `typecheck`, `lint`, and full tests pass at 6 files / 33 tests. The added release tests fail closed on metadata, package-file, path/source-map, license, DSH/scdp binding, generated-lock, provenance, and concurrent final-evidence drift. - `release:reproduce` and `release:audit` PASS. Two isolated offline/frozen producers used the same generated source-bound lock and prepared frozen store, produced byte-identical 39-entry tarballs and identical package manifests, and recorded 26 source rows, 39 package rows, the complete 242-row DSH manifest, the exact public scdp artifact, and unsigned provenance. The final four files are retained under `.verification/release-readiness/final/`. - The published scdp candidate's final qualification passed `build`, strict `typecheck`, `lint`, and 8 files / 93 tests; public contract `3`, schema `2`, and Host/storage behavior are preserved. Its runtime JS, declarations, source maps, and package manifest are byte-identical to the older WCDP qualification input; only four packaged documentation files changed. - Exact DSH CLI/profile installation PASS at `.verification/dsh-profile-install-v0.1.0-alpha.1-r1`: pnpm `11.7.0` installed the published scdp and final WCDP tarballs into one fresh profile, recorded WCDP after `@deepseek-ai/dsh-base` in `dsh.profile.bundles`, composed scdp before WCDP, and an actual profile boot returned scdp contract `3` / schema `2` plus WCDP contract `1` / schema `1` from the mounted Host services. - A fresh frozen/offline consumer at `.verification/clean-consumer-release-v0.1.0-alpha.1-r2` installs 81 local artifacts: 79 distinct DSH packages all at `0.1.2-alpha.1`, published scdp, and the final WCDP tarball. Cordis `4.0.1`, React `18.3.1`, scdp, and WCDP each resolve to one installed path. Its 347,320-byte lock has SHA-256 `eb3e092249d87374c1237b088bd2a880d2a9fcb2455ee95582fc88fb53ffd19e`; strict NodeNext typecheck with `skipLibCheck: false` passes. - Real Cordis Loader/runtime PASS on the final artifact in run `a6fe68de-71a7-41d9-b74c-61fd2801719c`: Workstream Charter creation, stale/unauthorized rejection, Host/model-tool mutation plus the exact four-method read-only Remote surface, Result Notice/disposition delivery, closed-state rejection, idempotency/conflict handling, JSON and JSONL persistence, application restart, Session-log context recovery, atomic accepted-close writer release, and Loader disposal/reload. - Dedicated L4 Standard O/P/E PASS on the final artifact in run `6e136d76-f1da-4ba4-88fe-24c182180278`: three distinct real O/P/E AgentLoops received active `standard-ope` context; O→P, P→E, E→P, P→E, P→O, and O→P all used the Work Charter/scdp path, reached durable `acknowledged` state, and were consumed by the target role model. P→O is accepted only after the latest execution result has an accepted disposition, and both phase records preserve the causal chain. - Real Chromium `149.0.7827.55` PASS on the final artifact: `WC 1`, global/per-Session actions, Host-authoritative read-only overlay, scdp/native owner preservation, zero leaked requests, and Work Charter Client dispose/reload. The 44,547-byte screenshot SHA-256 is `5f9b5c6d18ac57e481ab6939694fe8c1c24ddf4866a2c2131674d09ceec7ed4d`. - Exact hashes, run identities, commands, correction history, screenshot, and limitations are in `docs/VERIFICATION.md`. ## Open facts and blockers - L4 proves the bounded deterministic Standard O/P/E role, policy, causal-delivery, and AgentLoop-consumption path on the exact final local graph. It does not establish natural-language model quality, broad Work Charter efficacy, or independent semantic acceptance. - No controlled upstream-baseline/candidate comparison or independent semantic assessment has run. Overall Work Charter efficacy and v1 semantic acceptance remain `UNKNOWN`/open. - Browser evidence proves real Work Charter/scdp/DSH infrastructure plus additive ownership. Six native-feature entries are fixture ownership sentinels, not full semantic end-to-end tests of goal/plan/workflow/approval/Conversation/Trajectory. - The tracked alpha.1 scdp lock remains historical by design, while WCDP's release provenance embeds a generated source-bound lock with relative artifact locations and exact integrity. That generated lock is evidence, not a replacement tracked dependency lock. - DSH's packed `@deepseek-ai/dsh-client-ui-primitives` manifest references a missing `lib/index.js.map`; Vite warns, while relevant transforms/tests/runtime pass. The clean upstream checkout was not modified. - Compatibility with later DSH versions, Node 22, other storage providers, multi-process/cross-host behavior, registry installation, full native-feature browser semantics, and production support remains `UNKNOWN`. Public WCDP GitHub Pre-release publication has occurred; npm publication has not. - The published tarball remains byte-for-byte the accepted artifact and therefore retains its packaging-time README. Current repository documentation corrects release status for source readers but is not retroactive artifact content. - MIT is selected with `Copyright (c) 2026 junwei529`; the root `LICENSE` and package SPDX metadata are part of the release candidate. The Client source map identifies Zod `4.4.3` as the sole bundled third-party package, and its MIT grant is preserved in `THIRD_PARTY_NOTICES.md`. ## Historical release closeout instruction The former instruction was to complete the authorized bilingual README and canonical release-state commit, then stop clean. Entry at `c71d0a9cbc399c61470159c0f595de5e7ed079c0` is clean; do not repeat that commit or reuse its writer window. The successor design checkpoint above owns the current next action. The published tag and Release remain historical immutable subjects. ## Recovery read order Read `AGENTS.md`, `README.md`, `docs/SPEC.md`, this file, and `docs/VERIFICATION.md`. For successor work, reconcile the current design checkpoint, SC decisions, installed 0.9.1 identity, live diff and named writer before proceeding; do not resume the historical release closeout. For the existing release evidence only: 1. revalidate repository, branch, HEAD, index, and worktree; when the commit containing this status is present and the tree is clean, preserve writer `none` and do not repeat it; 2. revalidate the exact upstream Work Charter, DSH, published scdp asset, final WCDP artifact, provenance, and clean-consumer lock identities above; 3. preserve the current root, exact DSH/scdp subjects, and retained ignored evidence byte-for-byte unless a new action is explicitly authorized; 4. inspect the latest result and limitations in `docs/VERIFICATION.md`; 5. resume only at a user-selected next direction; do not infer push, tag, GitHub Release, npm publication, cleanup, evaluation, or a new DSH target from the completed local qualification.