docs: specify DevGuard adoption gates and link detailed plans

[novelKR]

Problem and result

CodeSpace needs an explicit adoption boundary before consuming the independent DevGuard authority. This documentation PR adds the bilingual roadmap, minimum readiness gates, single execution-owner registration model, and initial Gateway recovery scope, then links the detailed DevGuard execution plan by immutable revision.

DevGuard's authoritative documents are English with reviewed Korean counterparts. This guide now references documentation revision 3abf08f6feffeda63f58b17ac2bbe8fff19ec20b from DevGuard #1, with language-appropriate planning links and the preserved historical approval source.

Consumer and delivery boundaries

• The Runner registers once: Gateway PID for InProcess, worker PID for UDS; Gateway and Runner share one static control reservation.
• Prepare resources and acquire process slots before spawn and approval consumption; preserve uncertain execution and separate helper readiness from executable success.
• Protect the complete control path, including transport, queues, replay, buffers, shared locks and callbacks.
• Initial recovery reconnects a Gateway to a surviving independent Runner; existing modes retain their shutdown contracts.
• DG-1 is delivered through six sequential implementation PR groups. Real bounded self-use begins at C10 only after a functionally tested parent containing parent-budget capability has been frozen; C12 separately establishes SLO qualification.
• Documentation references, runtime client pins, installed artifacts and Runner wire versions remain distinct.

No runtime crates, configuration behavior, Cargo dependencies, Codex gitlink, journal schema or workflows change. DG-1 and CodeSpace integration remain unimplemented at this documentation baseline.

Validation

Documentation head: 35f5ec17c94979a790680b7297538f29ff81edaa.

• Bilingual registry: 17 reviewed pairs; only devguard-integration hashes updated.
• Node 24.21.0 / npm 11.19.0 documentation tests: 5 passed.
• Pinned production build and manifest integrity: 37 HTML pages, 155 hashed files, actual source-head metadata.
• Browser review: English/Korean content, light/dark presentation, narrow layout, language navigation, local search and copied Korean Markdown; corrected a literal Markdown emphasis marker found during review.
• Existing full runtime and documentation CI remain required; documentation changes do not waive those checks.
• Original CodeSpace checkout, user branch and staged .codex/config.toml are preserved.

The PR also includes existing roadmap commit fb822fc24c98f6628dce62d33a5cc67275f8ca34; runtime inspection remains based on e94d21475643608ad2a466256fb57266b86faa47. The Codex pin remains 6b9826e3aa83b1a5947db50f4332cb9c65f1b340.

Merge order and rollback

Merge DevGuard #1 and verify its separate main workflows first. Then normally merge this PR after current-head checks/review and verify CodeSpace main CI plus documentation publication before DG1-P1 implementation starts.

Rollback is an appended documentation revert/new immutable reference with reviewed translation hashes. Do not rewrite referenced history. No runtime migration or service change is introduced; fake-backend and documentation checks do not qualify native protection or product SLOs.