docs(workspace): record packaging boundary

docs/CONSTITUTION.md

@@ -40,12 +40,23 @@ LLM dependencies enter at `runtime` through Planner behavior. HTTP and MCP
 dependencies enter at `api`. No LLM, HTTP, or MCP dependency may appear in
 `core`, `driver`, `device`, or `tools`.
 
+## Packaging Boundary
+
+The repository is a uv workspace with `device-agent-runtime` as the root
+member and outer platform packages as separate members. The cloud platform is
+owned by `packages/cloud-platform` and may depend on the Runtime through an
+explicit workspace source; the Runtime distribution must never depend on or
+package `cloud`.
+
+All Python members share the committed root `uv.lock`. The Vue/Vite `console/`
+remains outside the Python workspace and keeps its independent npm lifecycle.
+
 ## Change Discipline
 
 Future changes must keep the dependency direction:
 
 `core` -> `driver`/`device` -> `tools` -> `perception` -> `storage` -> `runtime`
--> `api`.
+-> `api` -> optional outer workspace applications.
 
 When a change needs a new external integration, add it at the adapter layer
 that owns that concern, not at the domain or device boundary.

docs/ROADMAP.md

@@ -80,6 +80,12 @@ coordinated execution while preserving the same device/runtime boundaries.
 Add device pools, scheduling, plugins, and platform APIs for distributed
 execution across many devices.
 
+The packaging baseline is complete: `device-agent-runtime` remains the root uv
+workspace member, while the existing `cloud` modules and SDK are published by
+the one-way dependent `device-cloud-platform` member under
+`packages/cloud-platform`. A deployable control plane and Host Agent execution
+loop remain separate follow-up work.
+
 ## Long-Term Direction
 
 The long-term v2.0 direction is a "DeviceOS" / Universal Device Runtime: one