Ship OpenManager 0.4 as a lightweight DSH workbench

[Adkid-Zephyr]

What changed

• refocus OpenManager as a lightweight project workbench above DeepSeek Harness and other local agent runtimes
• simplify onboarding to a name, intended outcome, and optional existing code folder; prefer DSH for new projects when installed
• add a DSH connection center for the CLI, web/headless profiles, Cordis bundle, DSH Web, and the five exposed capabilities
• add previewable cross-project memory transfer that only writes to the review inbox and can undo unreviewed candidates
• add versioned project backup, validated preview, atomic restore as a separate project, and recoverable local archives
• add native folder selection, path/session confinement, request limits, atomic index writes, responsive layouts, inline errors, and updated bilingual guides

Why

OpenManager should complement DSH rather than duplicate its model, tool, sandbox, session, and Trajectory UI. This iteration concentrates on the continuity layer: projects, one next action, portable memory, explicit data boundaries, and recovery.

The DSH integration follows A Programming Paradigm for Spatiotemporal Composability: Cordis owns runtime service/effect lifecycles, while persistent OpenManager state outside that boundary uses approval, validation, idempotency, preview, and explicit undo/recovery.

User impact

• ordinary DSH vibe-coding users can start without understanding provider/model plumbing
• each project keeps an independent code folder, Harness choice, focus, sessions, tasks, and curated memory
• memory can move between projects without silently becoming durable state
• backup restore never overwrites a project; archive never deletes an external code folder
• connection problems appear as separate CLI/profile/plugin/Web states instead of one vague status

Validation

• npm test — unit, production build, API smoke, and focused Playwright regression
• npm run typecheck
• npm pack --dry-run
• npm audit --omit=dev --audit-level=high — 0 vulnerabilities
• secret-pattern scan and git diff --check
• real openmanager dsh doctor against the running local API
• real DSH headless boot on 0.1.0-rc.6 with the plugin installed
• desktop, connection-center, migration-center, and 430px mobile visual QA

Compatibility and safety

• existing schema-3 projects remain compatible; older runtime mappings are unchanged
• provider credentials stay in the selected Harness
• backup files contain session text and may be sensitive even though credentials and source code are excluded
• privileged desktop actions are disabled when OpenManager is network-exposed