Clarify memory and architecture in README

[exqqstar]

Summary

• call out project memory as a first-class ExAgent capability
• add a public architecture-at-a-glance section to both English and Chinese READMEs
• expand repository layout with app-server, runtime submodules, MCP, workflow, and memory/state areas

Verification

• git diff --check README.md README.zh-CN.md
• gitleaks detect --source . --redact --exit-code 1 --no-banner

Notes: this is a sanitized README summary based on public repo structure, not a copy of private Obsidian architecture notes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 053ae7a66b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Qualify disabled workflow runs

In the desktop UI, WORKFLOW_RUNTIME_ENABLED is hard-coded to false, which keeps canStartWorkflow false and shows users that starting new workflow runs is temporarily disabled / the public build does not expose the run entry (apps/desktop/src/components/WorkflowLibrary.tsx). Advertising “workflow runs” here as a current recoverable-agent capability makes Download/Quickstart users expect a feature they cannot start, so please mark it as in-progress or architecture-only, and mirror the clarification in the Chinese README.

Useful? React with 👍 / 👎.