docs: define English-authoritative milestones and sequential DG-1 delivery

[novelKR]

Problem and result

DevGuard needs an executable delivery plan and explicit consumer gates before runtime work begins. This PR records all seven milestones as 46 proposed implementation units in 23 logical PR groups, with prerequisites, commit/PR boundaries, meaningful failure and race tests, completion evidence, rollback and handoff.

English is now the authoritative editorial source. The new English design reference and planning documents have 14 reviewed Korean counterparts, tracked by source/translation hashes. The originally approved docs/design.ko.md remains byte-for-byte unchanged. Existing documentation commits and immutable links are preserved by an append-only preparation commit.

Decisions and delivery

• Register only the execution-owning Runner: Gateway PID in InProcess, worker PID in UDS, with one static reservation covering both control costs.
• Limit initial recovery to Gateway restart/reconnection while an independent Runner survives; preserve existing mode shutdown contracts.
• Deliver DG1-P1 through P6 sequentially through current-head review/CI, normal merge, separate main verification and evidence-preserving cleanup.
• Use foreground daemons through P4 and a current-user LaunchAgent from P5.
• At C10, first functionally test and freeze a parent artifact containing parent-budget support, then immediately begin bounded real self-use. The earlier P4/P5 bootstrap artifacts are not assumed to support newly added parent operations. C12 separately qualifies the measured release.
• Preserve existing CodeSpace runtime/Codex pins, and keep Linux enforcement, cache and additional adapters outside the DG-1 sequence.

Validation

Exact documentation head: 3abf08f6feffeda63f58b17ac2bbe8fff19ec20b.

• Rust 1.95.0: formatting, Clippy with warnings denied, and the existing 44 contract/core tests.
• Documentation checker: 14 reviewed translation pairs, 46 unique work units, 23 logical groups, complete fields, acyclic dependencies and local links.
• Seven documentation-check regression cases: current content, stale source/translation, missing/duplicate pairs, broken links, dependency cycles and missing test fields.
• Original approval checksum remains 97b67a1f9518c1781156a4b3b26829b285f84f5c9a44da60f3c5dcf1bc768df8.
• Runtime crates, Cargo dependencies, LICENSE/NOTICE, approval metadata and existing CI workflows are unchanged from the DG-0 implementation baseline.

Local evidence is retained under evidence/dg1-delivery/preparation/. Existing macOS and Ubuntu CI remain required; the validator adds documentation checks without removing contract/dependency gates.

Scope, dependency and rollback

This remains documentation and documentation-validation work. It does not implement a daemon, OS controls, self-use, CodeSpace runtime integration or SLO qualification, and does not mark future milestones complete. Fake-backend results do not qualify native behavior.

Merge and verify this PR first. Then update and deliver CodeSpace #65 using this immutable documentation revision and verify its separate main/publication workflows before DG1-P1 starts. Documentation revision and runtime dependency pin are distinct values.

Rollback appends a documentation revert/revision and refreshes dependent links/reviewed hashes. Do not rewrite already referenced history. No operational journal migration is introduced.