feat: independent Yeoul workspace product (v0.4.0)

[bhyi4]

Summary

• Independent Yeoul product CLI: setup/new/status/doctor/connect/serve, observe/discuss/develop modes. Mirror installation is now explicit opt-in.
• CLI and MCP use the same managed permission, path, workspace-lock and durable receipt boundary.
• Three task tools provide prepared IDs, execution/replay and status. Operators alone configure permissions, approve verification and acknowledge recovery.
• Hash-pinned reviewed baselines, exact-file external ledger read grants, config history, audited recovery tombstones even when receipts are missing.
• Atomic arc allocation, refuse loop-state reset, preserve uncertain verification outcomes. Managed closes do not invoke external action recorders.
• Version 0.4.0 with independent setup documentation and compatibility boundaries. No LaneStack dependency or common workspace requirement.

Validation

• Linux/Python 3.10: product 11, runtime 21, hardening 26 tests; 72 shell gate checks; 5 surface, 8 subprocess and 8 serverInfo checks passed.
• Fresh isolated venv with NO Mirror installation: built-wheel product suite 11/11 passed outside checkout, including real stdio reconnect (MCP 1.30.0).
• sdist -> wheel succeeded; pre-publish scan passed against all staged files.
• Native Windows/macOS results pending CI. Raw scripts/older servers/arbitrary shell commands remain outside the cooperative product boundary.

Rollout

Stop servers and surviving children, back up workspace including control records, reinstall, doctor, reconnect.
No live business-data migration or existing MCP client config changes were made. Configuration updates are operator actions.