docs: finalize VMLab strategic architecture contracts

[SSobol77]

docs: finalize VMLab strategic architecture contracts

Purpose

Finalize VMLab contract set before VMLab implementation starts.

Mandatory First Step

Before editing files:

1. Inspect the actual repository structure.
2. Verify real package roots, CLI entrypoints, and test conventions.
3. Do not assume imports from non-existent modules.
4. Adjust file paths to the real repository layout if required.
5. Document any path deviation in the PR description.

Development Log Invariant

All generated development logs, dry-run reports, smoke outputs, test evidence, and agent-generated debug artifacts must be written only under:

logs/

Forbidden generated-artifact locations:

.ecli/
.ecli/vmlab/
src/
tests/
tmp/
.tmp/
.cache/
$HOME/
/tmp/
project root outside logs/

Scope

Finalize:

• docs/extensions/vmlab-overview.md
• docs/extensions/vmlab-profile-schema.md
• docs/extensions/vmlab-qmp-client.md
• docs/extensions/vmlab-runtime-supervisor.md
• docs/extensions/vmlab-console-and-logs.md
• docs/extensions/vmlab-security-model.md
• docs/extensions/vmlab-implementation-prompt.md

Required corrections:

• every VMLab log/test/evidence location references repository-level logs/, not .ecli/vmlab/run during development.
• VMLab implementation prompt is skeleton-only.
• no real QEMU execution in Phase 2A.
• profile hashing and argv hashing specification is present.

Non-Goals

• no VMLab code
• no QEMU execution
• no QMP implementation
• no serial attach
• no privileged remediation

Dependencies

Blocked by ECLI architecture contracts where references or contract rules are shared.

Acceptance Criteria

• all VMLab contract documents exist
• all VMLab documents reference Services Foundation and CommandPlanService
• logs/ development invariant is included everywhere relevant
• VMLab profile schema includes hashing specification
• VMLab implementation prompt remains dry-run-only
• no implementation code is added in this issue

References

• docs/extensions/vmlab-overview.md
• docs/extensions/vmlab-profile-schema.md
• docs/extensions/vmlab-qmp-client.md
• docs/extensions/vmlab-runtime-supervisor.md
• docs/extensions/vmlab-console-and-logs.md
• docs/extensions/vmlab-security-model.md
• docs/extensions/vmlab-implementation-prompt.md

Labels

• type:docs
• type:architecture
• area:vmlab
• priority:high

Milestone

v0.3.0 — VMLab Skeleton

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• docs: finalize VMLab strategic architecture contracts #27

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!