@getmonoceros/workbench 1.22.0 → 1.22.2

package/dist/bin.js

@@ -5359,6 +5359,22 @@ function generateAgentsMd(input) {
     "  it holds Monoceros-managed directories (`.devcontainer/`, `home/`,",
     "  `data/`, `logs/`), not your code. Cloned repos already live at",
     "  `projects/<repo>/` and are git repositories \u2014 commit normally.",
+    `- **Register new projects in \`${input.containerName}.code-workspace\`.** When`,
+    "  you scaffold a new project directly under `projects/` (not a clone of a",
+    "  repo already listed above), add it to the VS Code multi-root workspace so",
+    `  it shows up in the Explorer. Open \`/workspaces/${input.containerName}/${input.containerName}.code-workspace\``,
+    "  and append an entry to the `folders` array, for example",
+    '  `{ "path": "projects/<app>", "name": "<app>" }`.',
+    "  Add **exactly one** folder entry per directory directly under `projects/`:",
+    "  the top-level project directory itself, even when it contains several",
+    "  sub-projects (e.g. a `backend/` and a `frontend/`, or a multi-module",
+    "  layout). Do **not** register those sub-directories as separate roots \u2014 one",
+    "  root per top-level project keeps the Explorer readable as more projects",
+    "  land in the container. Cloned repos are added there automatically by the",
+    "  apply; projects you create yourself are not, so without this step VS Code",
+    "  (opened on the host from the workspace file) would not list them.",
+    "  Hand-added folder entries survive `monoceros apply`: the apply merges into",
+    "  the file, it does not overwrite your edits.",
     "- You run as the `node` user. `sudo` is available but its effects do",
     "  not persist across rebuilds.",
     "- A bare `EXPOSE` directive has no effect on host reachability. Ports",
@@ -7055,7 +7071,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    CLI_VERSION = true ? "1.22.0" : "dev";
+    CLI_VERSION = true ? "1.22.2" : "dev";
   }
 });