From e01c82a7c2cccaa561d537616de10732932c546b Mon Sep 17 00:00:00 2001 From: Patrick Eanism Date: Sun, 20 Sep 2026 14:17:34 -0700 Subject: [PATCH] docs: workspaces eject too MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The eject section said workspace projects already build from a generated root workspace manifest. They do not — the generated workspace manifest lives in .horus/ like every other one — and softmata/horus#220 makes `horus eject` handle them: virtual root manifest with real member directories, each member manifest rebased into its own directory. --- content/docs/development/cli-reference.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/docs/development/cli-reference.mdx b/content/docs/development/cli-reference.mdx index b04ebbd..9d81159 100644 --- a/content/docs/development/cli-reference.mdx +++ b/content/docs/development/cli-reference.mdx @@ -245,9 +245,11 @@ What changes after an eject: - `horus build`/`run`/`test` still work: they detect the root manifest and run cargo against it. -An existing root `Cargo.toml` is refused unless `--force`. Workspace projects -already build from a generated root workspace manifest, and non-Rust projects -have no Cargo manifest to eject. To start cargo-native instead, use +An existing root `Cargo.toml` is refused unless `--force`. A workspace ejects +too: the generated virtual manifest becomes the root `Cargo.toml` with its +`members` pointing at the real member directories, and each member manifest +moves into its own directory with its paths rebased. Non-Rust projects have no +Cargo manifest to eject. To start cargo-native instead, use `horus new my_robot --cargo`. ---