docs(blog): add bilingual Log Is the Runtime

[likun666661]

Summary

Add the Chinese and English versions of the Log Is the Runtime essay together in one pull request so the complete argument and translation can be reviewed as a unit.

Documents for review:

• English: Log Is the Runtime
• 中文：Log Is the Runtime

The essay connects log-centric database design to Maka RuntimeEvents, then explains append-only history, compaction as projection, KV-cache prefix reuse, and Tool Result offload. The documentation index links both language versions while keeping code and current contracts authoritative.

Review focus

• technical accuracy of the log-centric database analogy
• the boundary between canonical RuntimeEvents and model/UI projections
• the description of compaction as a durable but lossy projection
• Tool Result pruning as archive-backed, bounded, model-readable context offload
• semantic parity and natural wording between the English and Chinese versions

Verification

• git diff --exit-code 5f7670343bb837867fab23630acf1e849fcdf044 -- docs/README.md docs/blogs — the combined files match the previously merged bilingual state
• git diff --cached --check
• npm run check:asf-headers
• Full tests were not run because this PR changes Markdown documentation only.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex drafted and translated the essay from the current Maka architecture and implementation, prepared the bilingual documentation set, and verified this PR.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[MicroGery]

One inline architecture-accuracy concern.

[MicroGery]

[P2] Keep the store topology aligned with the implementation

This introduces context offload correctly, but the following description says the complete result is written to a separate context-offload store. Tool-result archives currently use the generic ArtifactStore; a dedicated SQLite ContextOffloadStore is the planned migration in #4071. Please phrase this as the architectural role rather than current implementation (or explicitly state the current ArtifactStore backing and the planned migration), so the article does not turn a target topology into a present fact.