@kl-c/matrixos 0.2.6 → 0.2.7

package/.agents/command/adopt.md

@@ -6,13 +6,13 @@ description: Launch or re-run the Morpheus adoption ritual — establish user co
 You are executing the **Morpheus adoption ritual** (`/adopt`). This is the first-contact (or re-adoption) ceremony that establishes the user's context and offers optional MaTrixOS features.
 
 ## When this runs
-- First launch, if `/root/MOS_Vault/04-Areas/user-context.md` is missing or still a template.
+- First launch, if `.matrixos/user-context.md` is missing or still a template.
 - Any time the user explicitly types `/adopt` to (re)do the ritual.
 
 ## Behavior
 
 ### 1. Detect current state
-Check whether `/root/MOS_Vault/04-Areas/user-context.md` exists and is filled.
+Check whether `.matrixos/user-context.md` exists and is filled.
 - If filled: tell the user "Tu as déjà un contexte d'adoption. Je relance le rituel pour le mettre à jour." and proceed to step 2 (re-adoption mode — EDIT sections, do NOT rewrite from scratch).
 - If missing/template: adoption mode — you will CREATE the file.
 
@@ -28,32 +28,20 @@ Keep it to one short paragraph — this is awareness, not the opt-in checklist (
 Pose ~5 targeted questions:
 1. **Qui es-tu ?** (nom/alias, rôle, ce que tu fais)
 2. **Pour quel projet / besoin m'as-tu déployé ?** (objectif, stack, périmètre)
-3. **Quelles contraintes / garde-fous ?** (infra, interdits, modèles si hors défaut)
-4. **Comment veux-tu collaborer ?** (style de réponse, proactivité, niveau de vérif)
-5. **À qui est-ce que je rends compte ?** (confirmation : toi seul, ou une entité que tu désignes)
-
-### 3. Offer opt-in features (DO NOT skip this)
-After the questions, read the feature inventory from:
-`packages/omo-opencode/src/features/matrix-inventory/features.ts` (export `OPT_IN_FEATURES`).
-
-Present the opt-in features as a checklist. For EACH, give: name, one-line description, and the honest provisioning note (especially the Dashboard — clarify it is a web UI served on 127.0.0.1:9123, backend always present, frontend bundled by the build; to enable: `matrixos dashboard --daemon`).
-
-Ask the user which they want activated. Confirm specifically the **Dashboard (Mission Control)** since the user explicitly cares about it.
-
-### 4. Synthesize
-Write/edit `/root/MOS_Vault/04-Areas/user-context.md`:
-- Adoption mode: fill sections 1–4, set `last_verified` to today, add a line in section 5 (Mises à jour) with today's date.
-- Re-adoption mode: edit only the sections the user changed; update `last_verified`; append a line in section 5.
-- **ALWAYS add a `## Features` section** (even in re-adoption) listing which opt-in features the user chose to activate (e.g. `Dashboard: activé`, `Kanban: non`, etc.). This marker tells the auto-adoption trigger that the feature checklist was presented — without it, the ritual will re-run on next launch.
-Never rewrite the whole file from scratch — preserve existing context.
-
-Also update `/root/MOS_Vault/MEMORY.md` routing if the user-context file was just created.
-
-### 5. Confirm
-End with: « C'est noté, je suis désormais configuré pour toi. Tu peux à tout moment utiliser `/features` pour voir ce que je peux faire, ou `/adopt` pour refaire ce rituel. »
-
-## Rules
-- User context is NEVER fixed: user can say "mets à jour mon contexte" → edit, not rewrite.
-- Do not invent a hierarchy/manager — Morpheus reports only to the user who installed it.
-- Do not store code-derivable facts in user-context.md (that belongs to Magic Context / MOS_Vault project files).
-- If the user wants a feature activated that requires provisioning (e.g. Dashboard), relay the exact provisioning steps from the inventory — and if you are instructed to actually enable it, follow the `provisioning.activation` recipe (e.g. launch `matrixos dashboard --daemon`).
+3. **Quel niveau d'automatisation veux-tu ?** (assistant, agent, team mode)
+4. **Veux-tu activer le dashboard ?** (Mission Control)
+5. **Veux-tu le gateway Telegram ?** (répondre depuis ton téléphone)
+
+### 4. Write user-context.md
+Write the answers to `.matrixos/user-context.md` in French, structured as YAML frontmatter + markdown sections.
+
+### 5. Offer feature toggles
+After writing context, offer to enable:
+- Dashboard (`matrixos dashboard --daemon`)
+- Gateway Telegram (`matrixos gateway adopt telegram`)
+- Kanban (`matrixos project switch`)
+- Cron / auto-audit (`matrixos self-audit --install-cron`)
+
+### 6. Confirm
+"Rituel terminé. Tu peux me demander n'importe quoi maintenant — je connais ton contexte."
+</command-instruction>

package/dist/cli/index.js

@@ -2163,7 +2163,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "@kl-c/matrixos",
-    version: "0.2.6",
+    version: "0.2.7",
     description: "MaTrixOS \u2014 Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
     main: "./dist/index.js",
     types: "dist/index.d.ts",

package/dist/cli-node/index.js

@@ -2163,7 +2163,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "@kl-c/matrixos",
-    version: "0.2.6",
+    version: "0.2.7",
     description: "MaTrixOS \u2014 Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
     main: "./dist/index.js",
     types: "dist/index.d.ts",

package/dist/index.js

@@ -368023,7 +368023,7 @@ function getCachedVersion(options = {}) {
 // package.json
 var package_default = {
   name: "@kl-c/matrixos",
-  version: "0.2.6",
+  version: "0.2.7",
   description: "MaTrixOS \u2014 Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
   main: "./dist/index.js",
   types: "dist/index.d.ts",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kl-c/matrixos",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "description": "MaTrixOS — Agentic OS for OpenCode. Personalizable, communicating, self-improving, resilient.",
   "main": "./dist/index.js",
   "types": "dist/index.d.ts",