Align OpenRath v2.0.0 README and deployment reference

[Tokisakix]

Summary

• preserve the original OpenRath README structure, PyTorch framing, component documentation, workflow example, installation guide, and 12-step learning ladder
• expand the existing v2.0.0 section around OpenRath's move into production environments: durable Runs, Events, Checkpoints, worker recovery, Effect Ledger, Interrupts, tenant boundaries, PostgreSQL, Redis, artifacts, and operations
• provide matching English and Simplified Chinese documentation while consistently treating OpenRath as the product name and v2.0.0 as the release version
• remove the plural examples/ directory by moving the deployable Agent Server application to deploy/reference_app.py
• update Docker, Compose, Kubernetes, CI, release workflows, and deployment contract tests to use the new reference application path
• keep the singular example/ directory as the core API learning ladder and link complete scenarios from OpenRath-Example

Why

OpenRath v2.0.0 is primarily the release where OpenRath becomes deployable as a durable production runtime. The README should communicate that change without replacing the project's existing concepts and learning material. The deployable server application also belongs with deployment assets rather than tutorial examples.

Impact

Users retain the familiar README and API introduction while gaining a focused production overview and direct paths to deployment guidance. Deployment manifests and release checks continue to reference the same application after its relocation.

Validation

• uv run ruff check deploy/reference_app.py tests/deployment/test_reference_manifests.py
• uv run pytest -q tests/deployment/test_reference_manifests.py tests/deployment/test_release_assets.py ? 7 passed
• docker compose -f deploy/compose/compose.yaml config --quiet
• English and Chinese README local-link, code-fence, and Python syntax checks
• stale repository/path reference scan
• git diff --check

[kangkangzi2025]

Merged: OpenRath v2.0.0 documentation now highlights durable production deployment, while the relocated reference application and deployment assets remain fully validated.

[kangkangzi2025]

All required checks passed, approval is complete, and no conflicts remain. Ready to merge.