@kl-c/matrixos 0.1.7 → 0.1.10

package/.agents/command/adopt.md

@@ -0,0 +1,50 @@
+---
+description: Launch or re-run the Morpheus adoption ritual — establish user context and offer opt-in features (dashboard, kanban, cron, etc.)
+---
+
+<command-instruction>
+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.
+- 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.
+- 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.
+
+### 2. Ask the adoption questions (in conversation, French, interactive `question` tool)
+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.
+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`).

package/.agents/command/features.md

@@ -0,0 +1,35 @@
+---
+description: List and explain MaTrixOS capabilities (features) on demand — read from the feature inventory
+---
+
+<command-instruction>
+You are executing `/features` — the user wants to know what MaTrixOS can do.
+
+## Source of truth
+Read the feature inventory from:
+`packages/omo-opencode/src/features/matrix-inventory/features.ts` (export `MATRIX_FEATURES`, `OPT_IN_FEATURES`, `getFeature(id)`).
+
+This is the ONLY place you describe capabilities from. Do NOT guess or fouille the codebase for feature descriptions — the inventory is authoritative and kept in sync with the code.
+
+## Behavior
+
+### No argument: list everything
+Print a compact table of all features:
+- name | one-line description | status (native / opt-in / cli-only) | enabled by default?
+
+Group them: **Toujours actif** (enabledByDefault) first, then **Optionnel** (opt-in / cli-only).
+
+### With an argument (e.g. `/features dashboard`): detail one feature
+Look it up via `getFeature(<id>)`. Print:
+- Full name + description
+- Status + enabledByDefault
+- User benefit (what they get)
+- Provisioning: how to activate it (exact command/config), config path, and honest notes/caveats.
+For the Dashboard, be explicit: web UI on 127.0.0.1:9123, backend always present, frontend bundled by build; enable with `matrixos dashboard --daemon` (remote: `--host <tailscale-ip>`).
+
+### Offer next step
+End with: « Dis-moi si tu veux activer l'une de ces fonctionnalités — utilise `/adopt` pour lancer le rituel et choisir celles que tu veux. »
+
+## Rules
+- The inventory is the single source of truth. If a feature seems missing or outdated, say so and flag it for update — do not invent.
+- Keep it readable; no raw code dump. One screen max for the list.

package/.opencode/command/adopt.md

@@ -0,0 +1,50 @@
+---
+description: Launch or re-run the Morpheus adoption ritual — establish user context and offer opt-in features (dashboard, kanban, cron, etc.)
+---
+
+<command-instruction>
+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.
+- 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.
+- 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.
+
+### 2. Ask the adoption questions (in conversation, French, interactive `question` tool)
+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.
+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`).

package/.opencode/command/features.md

@@ -0,0 +1,35 @@
+---
+description: List and explain MaTrixOS capabilities (features) on demand — read from the feature inventory
+---
+
+<command-instruction>
+You are executing `/features` — the user wants to know what MaTrixOS can do.
+
+## Source of truth
+Read the feature inventory from:
+`packages/omo-opencode/src/features/matrix-inventory/features.ts` (export `MATRIX_FEATURES`, `OPT_IN_FEATURES`, `getFeature(id)`).
+
+This is the ONLY place you describe capabilities from. Do NOT guess or fouille the codebase for feature descriptions — the inventory is authoritative and kept in sync with the code.
+
+## Behavior
+
+### No argument: list everything
+Print a compact table of all features:
+- name | one-line description | status (native / opt-in / cli-only) | enabled by default?
+
+Group them: **Toujours actif** (enabledByDefault) first, then **Optionnel** (opt-in / cli-only).
+
+### With an argument (e.g. `/features dashboard`): detail one feature
+Look it up via `getFeature(<id>)`. Print:
+- Full name + description
+- Status + enabledByDefault
+- User benefit (what they get)
+- Provisioning: how to activate it (exact command/config), config path, and honest notes/caveats.
+For the Dashboard, be explicit: web UI on 127.0.0.1:9123, backend always present, frontend bundled by build; enable with `matrixos dashboard --daemon` (remote: `--host <tailscale-ip>`).
+
+### Offer next step
+End with: « Dis-moi si tu veux activer l'une de ces fonctionnalités — utilise `/adopt` pour lancer le rituel et choisir celles que tu veux. »
+
+## Rules
+- The inventory is the single source of truth. If a feature seems missing or outdated, say so and flag it for update — do not invent.
+- Keep it readable; no raw code dump. One screen max for the list.

package/dist/cli/config-manager/write-gateway-env.d.ts

@@ -0,0 +1,7 @@
+export declare const GATEWAY_ENV_FILENAME = ".klc-gateway.env";
+/**
+ * Write the Telegram bot token to a chmod-600 env file next to matrixos.json.
+ * The token is NEVER stored in matrixos.json — the gateway reads it via
+ * `env:TELEGRAM_BOT_TOKEN` at runtime. Returns the written file path.
+ */
+export declare function writeGatewayEnv(token: string): string;