@getmonoceros/workbench 1.15.0 → 1.16.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getmonoceros/workbench",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "Monoceros workbench CLI — local, reproducible dev containers with first-class AI coding tooling.",
   "keywords": [
     "devcontainer",

package/templates/components/README.md

@@ -2,8 +2,8 @@
 
 Every file under this directory is a **component** — a small,
 composable yaml snippet that contributes to a `SolutionConfig`. The
-`monoceros init` command picks components by name (via `--with=…`
-or by rendering them all as commented-out hints in the documented
+`monoceros init` command picks components by name (via the `--with-*`
+flags or by rendering them all as commented-out hints in the documented
 default) and merges them into the user's container-config yml.
 
 ## File layout
@@ -12,10 +12,10 @@ default) and merges them into the user's container-config yml.
 - `<group>/<name>.yml` — a sub-component of a parent feature
   (e.g. `atlassian/twg.yml` is a sub-component of `atlassian/`).
 
-Component names map 1:1 to their `--with=…` identifier:
+Component names map 1:1 to their `--with-*` identifier:
 
-- `--with=node` → `node.yml`
-- `--with=atlassian/twg` → `atlassian/twg.yml`
+- `--with-languages=node` → `node.yml`
+- `--with-features=atlassian/twg` → `atlassian/twg.yml`
 
 ## File schema
 
@@ -25,8 +25,8 @@ Component names map 1:1 to their `--with=…` identifier:
 displayName: Node 22 + pnpm
 
 # Longer block, shown as a comment above the section in documented
-# mode (i.e. `monoceros init <name>` with no --with). English, free
-# prose, can mention what it adds, where credentials come from, etc.
+# mode (i.e. `monoceros init <name>` with no --with-* flags). English,
+# free prose, can mention what it adds, where credentials come from, etc.
 description: |
   Node 22 + pnpm are already in the base image; this component
   declares the runtime as active so the scaffold wires it up.
@@ -49,13 +49,13 @@ contributes:
 - **Comments and prose are English**, even though the broader user
   docs are German. The rendered yml is a tool output and English
   reads more cleanly for the typical dev-yml shape.
-- **Sub-components set their flag to `true` AND every sibling flag
+- **Sub-components set their own flag to `true` AND every sibling flag
   to `false`.** Both `atlassian/twg.yml` and `atlassian/rovodev.yml`
   set both `rovodev` and `twg`, just with opposite truth values.
-  The init merge applies OR-semantics on booleans: when two
+  The init merge applies OR semantics on booleans: when two
   components contribute the same boolean key, `true` wins. That
-  way `--with=atlassian/twg` on its own opts out of the other
-  tool, while `--with=atlassian/twg,atlassian/rovodev` merges to
+  way `--with-features=atlassian/twg` on its own opts out of the other
+  tool, while `--with-features=atlassian/twg,atlassian/rovodev` merges to
   both `true`. Without the explicit `false`, the manifest defaults
   (`true` for both) would silently re-enable the unwanted tool.
 - **Auth/credential options live with the feature, not the
@@ -66,13 +66,13 @@ contributes:
 
 ## Adding a new component
 
-1. Decide the name and (if it's a sub-component) the group folder.
+1. Decide on the name and (if it's a sub-component) the group folder.
 2. Drop the yml file in. Use an existing component of the same
    category as a starting point.
 3. If the component activates a Monoceros feature, make sure that
    feature's manifest under `images/features/<feature>/` carries
    the right `x-monoceros.optionHints` for auth.
-4. Add a short note in this README's "Current components" table if
+4. Add a short note to this README's "Current components" table if
    you want it discoverable at a glance.
 
 ## Current components