@massa-ai/codex-plugin 1.25.0 → 1.26.0

package/install.sh

@@ -78,6 +78,12 @@ PLUGIN_DIR="$CODEX_DIR/plugins/massa-ai"
 HOOKS_JSON="$CODEX_DIR/hooks.json"
 AGENTS_DIR="$CODEX_DIR/agents"
 
+# Model-profile variant tree (T8, design Component 3 / MPS-04). Source is the
+# bundle's per-profile agent-profiles/<p>/ (sibling of agents/, A5); dest is
+# the engine's own host path table: $CODEX_DIR/massa-ai/agent-profiles/<p>/.
+VARIANTS_SRC="$SCRIPT_DIR/agent-profiles"
+VARIANTS_DEST="$CODEX_DIR/massa-ai/agent-profiles"
+
 # Array-append merge (F5 mitigation): for each of the 6 events, append the
 # massa-ai hook entry to the event's array if no entry with
 # _massaAiOwned: true already exists. Backup before first write. Uses node
@@ -299,10 +305,22 @@ if (typeof data.platforms !== "object" || data.platforms === null || Array.isArr
 data.version = 2;
 const prev = data.platforms[host];
 data.platforms[host] = { root, skillsOwner: "plugin", skills: ["massa-ai", "persona-router"] };
-// The whole-record replace must not drop the plugin version record a previous
-// successful install wrote (R2) — re-attach it.
-if (prev && typeof prev === "object" && !Array.isArray(prev) && prev.plugin && typeof prev.plugin === "object") {
-  data.platforms[host].plugin = prev.plugin;
+// The whole-record replace must not drop fields a previous successful install
+// wrote (R2) — re-attach them. modelProfile (T10, MPS-03 round-trip
+// obligation) is engine-owned; installRoute is installer-owned but written by
+// a LATER step of this same install (record_plugin_version) — both must
+// survive this earlier whole-record replace or a switched profile / recorded
+// route silently vanishes on the next skills-bundling pass.
+if (prev && typeof prev === "object" && !Array.isArray(prev)) {
+  if (prev.plugin && typeof prev.plugin === "object") {
+    data.platforms[host].plugin = prev.plugin;
+  }
+  if (prev.modelProfile && typeof prev.modelProfile === "object") {
+    data.platforms[host].modelProfile = prev.modelProfile;
+  }
+  if (typeof prev.installRoute === "string") {
+    data.platforms[host].installRoute = prev.installRoute;
+  }
 }
 fs.mkdirSync(path.dirname(file), { recursive: true });
 fs.writeFileSync(file, JSON.stringify(data, null, 2) + "\n");
@@ -376,18 +394,27 @@ record_plugin_version() {
     return 0
   fi
 
-  local version installed_at
+  local version installed_at route
   version="$(sed -n 's/.*"version"[[:space:]]*:[[:space:]]*"\([^"]*\)".*/\1/p' "$SCRIPT_DIR/package.json" | head -n 1)"
   installed_at="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
+  # installRoute (T8, design F1): installer-owned, engine-read-only. Unlike
+  # Claude, Codex's plugin/marketplace registration (register_codex_plugin) is
+  # ADDITIVE — it only affects /plugins visibility. The agent TOML files
+  # always land in $AGENTS_DIR regardless of whether that registration
+  # succeeds (see the unconditional copy loop below), so Codex has no
+  # "read in place, no local files" mode the way Claude's marketplace route
+  # does — installRoute is unconditionally "file" here, reflecting the one
+  # install shape Codex agents ever take. Written on EVERY install path.
+  route="file"
 
   # Tolerant of a corrupt/missing state file (rewrites a minimal valid one —
   # AC-8). A record-write failure warns but never fails the install: the next
   # run treats the host as unknown-version and reinstalls.
-  "$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" "$CODEX_DIR" "$version" "$installed_at" <<'NODE' || \
+  "$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" "$CODEX_DIR" "$version" "$installed_at" "$route" <<'NODE' || \
     echo "  ⚠ could not record the plugin version — next run will reinstall (unknown version)" >&2
 const fs = require("fs");
 const path = require("path");
-const [, , file, host, root, version, installedAt] = process.argv;
+const [, , file, host, root, version, installedAt, installRoute] = process.argv;
 let data = { version: 2, platforms: {} };
 try {
   const existing = JSON.parse(fs.readFileSync(file, "utf8"));
@@ -404,12 +431,54 @@ const rec =
     ? data.platforms[host]
     : { root, skillsOwner: "plugin", skills: [] };
 rec.plugin = { version, installedAt };
+// installRoute is installer-owned (like plugin above); modelProfile is NEVER
+// written here — the switch engine (packages/shared/src/profile-switch/) is
+// its sole writer, and this installer only ever reads it (see
+// apply_recorded_profile below).
+rec.installRoute = installRoute;
 data.platforms[host] = rec;
 fs.mkdirSync(path.dirname(file), { recursive: true });
 fs.writeFileSync(file, JSON.stringify(data, null, 2) + "\n");
 NODE
 }
 
+# ── Model-profile variant tree + recorded-profile re-apply (T8, MPS-04) ─────
+# Read-side only: this installer never writes platforms[host].modelProfile —
+# see the comment above record_plugin_version's NODE block. It only (a)
+# refreshes the on-disk variant tree so an offline switch has files to copy
+# from, and (b) re-applies a previously recorded profile's active agent set on
+# install/upgrade, so a plugin upgrade never silently reverts a switched
+# profile back to the shipped default.
+install_variant_tree() {
+  [[ -d "$VARIANTS_SRC" ]] || return 0
+  rm -rf "$VARIANTS_DEST"
+  mkdir -p "$VARIANTS_DEST"
+  cp -R "$VARIANTS_SRC/." "$VARIANTS_DEST/"
+  vecho "  + model-profile variant tree refreshed at $VARIANTS_DEST"
+}
+
+# Prints the recorded profile name (platforms[codex].modelProfile.profile), or
+# an empty string when unset/unreadable. Never throws — a corrupt or missing
+# state file just means "no recorded profile", not an install failure.
+recorded_profile() {
+  local runner="$1"
+  "$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" <<'NODE'
+const fs = require("fs");
+const [, , file, host] = process.argv;
+try {
+  const data = JSON.parse(fs.readFileSync(file, "utf8"));
+  const rec = data && data.platforms && data.platforms[host];
+  const profile =
+    rec && rec.modelProfile && typeof rec.modelProfile.profile === "string"
+      ? rec.modelProfile.profile
+      : "";
+  process.stdout.write(profile);
+} catch {
+  process.stdout.write("");
+}
+NODE
+}
+
 # ── Plugin-registry registration (delegated to the codex CLI) ───────────────
 # The CLI owns config.toml's [marketplaces.*] / [plugins."x@y"] tables and the
 # plugins/cache layout, so it is the only supported way to reach /plugins.
@@ -551,9 +620,33 @@ vecho "  + 6 massa-ai hook events wired (array-append, user hooks preserved)"
 # plugin dir — Codex custom agents load from the config-root agents/ dir, not
 # the plugin dir). Each file carries a "# massa-ai-owned" top comment for
 # scoped uninstall (R3: shared agents dir, user agents preserved).
+#
+# Model-profile re-apply (T8, MPS-04): if a switch previously recorded a
+# profile for this host, and the bundle ships that profile's variant, the
+# ACTIVE set comes from agent-profiles/<profile>/ instead of the shipped
+# default — an upgrade must never silently revert a switched profile.
+# Recorded-but-missing-from-bundle is a loud fallback to the default, never a
+# silent one.
 mkdir -p "$AGENTS_DIR"
+ACTIVE_AGENTS_SRC="$SCRIPT_DIR/agents"
+json_runner=""
+if command -v node &>/dev/null; then json_runner="node"
+elif command -v bun &>/dev/null; then json_runner="bun"
+fi
+if [[ -n "$json_runner" ]]; then
+  RECORDED_PROFILE="$(recorded_profile "$json_runner")"
+  if [[ -n "$RECORDED_PROFILE" ]]; then
+    if [[ -d "$VARIANTS_SRC/$RECORDED_PROFILE" ]]; then
+      ACTIVE_AGENTS_SRC="$VARIANTS_SRC/$RECORDED_PROFILE"
+      echo "  ↷ re-applying recorded model profile '$RECORDED_PROFILE'"
+    else
+      echo "  ⚠ recorded model profile '$RECORDED_PROFILE' is not in this bundle — falling back to the default profile" >&2
+    fi
+  fi
+fi
+
 specialist_count=0
-for src in "$SCRIPT_DIR/agents/"massa-ai-*.toml; do
+for src in "$ACTIVE_AGENTS_SRC/"massa-ai-*.toml; do
   [[ -f "$src" ]] || continue
   name="$(basename "$src")"
   cp "$src" "$AGENTS_DIR/$name"
@@ -562,6 +655,8 @@ for src in "$SCRIPT_DIR/agents/"massa-ai-*.toml; do
 done
 vecho "  + ${specialist_count} subagent specialists (generated from skills/agents/*/SKILL.md)"
 
+install_variant_tree
+
 # Skills bundling (PDO-08, 09): install massa-ai/persona-router into the
 # shared harness skills directory, unless scripts/install-skills.sh already
 # owns it for this platform.

package/package.json

@@ -1,9 +1,10 @@
 {
   "name": "@massa-ai/codex-plugin",
-  "version": "1.25.0",
+  "version": "1.26.0",
   "description": "massa-ai plugin for Codex — semantic code search, memory, and context compression",
   "files": [
     "agents",
+    "agent-profiles",
     "hooks",
     "skills",
     "install.sh",

package/skills/profile/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: profile
+description: Switch the installed massa-ai agents to a registry model profile (e.g. "work", "cheap", "home") or report the currently active profile per host. Use when the user asks to change/switch the model profile, asks which models the agents currently use, or asks to preview a profile switch. Do NOT use for editing the model registry itself (a registry edit is a massa-ai repository change, not a runtime switch) and do NOT claim the new profile is active before the user restarts the host session.
+license: MIT
+metadata:
+  author: Luiz Massa
+  version: 1.0.0
+---
+
+# Profile Switch Skill
+
+## Mission
+Drive the one massa-ai model-profile switch engine and relay its report — never a second implementation.
+
+## When To Use
+- The user asks to switch, change, or set the model profile (by name, e.g. "work", "cheap", "home", "balanced").
+- The user asks what profile is currently active, or which profiles are shipped.
+- The user asks to preview a switch without applying it.
+
+## How To Drive It
+There is exactly one switch implementation (`@massa-ai/shared`'s switch engine); every front — this skill, the MCP tools, and both `massa-ai-config` CLIs — calls the same engine and returns the same per-host report shape. Prefer whichever front is already available in the session:
+
+- **MCP tools** (preferred when the massa-ai MCP server is connected): call `profile_list` to report shipped profiles + per-host active profile + bundle version, and `profile_set` to switch (`{profile, host?, dryRun?}`).
+- **CLI fallback**: `massa-ai-config profile list` / `massa-ai-config profile show` / `massa-ai-config profile set <name> [--host <h>] [--dry-run]`.
+
+Default to a dry run first when the user has not explicitly asked to apply the switch immediately — `dryRun: true` (MCP) or `--dry-run` (CLI) previews the per-host plan and changes nothing.
+
+## Relaying The Result
+Always relay the per-host outcome and the restart notice verbatim in substance, not just "done":
+
+- Report each host as switched / skipped (with its reason) / unsupported (with its reason) / failed (with its reason). Cursor is always reported skipped — every tier resolves to inherit, so switching it is a no-op by design, not an error.
+- When at least one host switched (non-dry-run), state explicitly that a session restart of that host is required before the new models take effect — hosts load agent definitions at session start; there is no live in-session switch.
+- On a dry run, say so and that no files changed.
+- On a fully failed request (e.g. unknown profile name), relay the named error and the list of profiles the report says are actually available — never guess a profile name.
+
+## Restrictions
+- Never invent a profile name; only use names the engine's own report lists as shipped/available.
+- Never claim a profile switch is "live" before the affected host's session restarts.
+- Never edit the model-profile registry (`skills/model-profiles.json`) to satisfy a switch request — that is a build-time registry change owned by a different workflow, not a runtime switch.