@sangyaahub/pi-marg 1.0.4 → 1.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -71,4 +71,4 @@ if [[ "${runtime}" == "omp" || "${runtime}" == "both" ]]; then
71
71
  omp plugin install --scope user pi-marg@pi-marg-marketplace
72
72
  fi
73
73
 
74
- echo "PiMarg v1.0.4 installed for ${runtime}. Start a fresh runtime session, then run /pi-marg."
74
+ echo "PiMarg v1.0.6 installed for ${runtime}. Start a fresh runtime session, then run /pi-marg."
@@ -45,7 +45,7 @@ bun -e '
45
45
  const packageJson = await Bun.file("package.json").json();
46
46
  const marketplace = await Bun.file(".omp-plugin/marketplace.json").json();
47
47
  if (packageJson.name !== "@sangyaahub/pi-marg") throw new Error("Unexpected package name");
48
- if (packageJson.version !== "1.0.4") throw new Error("package.json must be v1.0.4");
48
+ if (packageJson.version !== "1.0.6") throw new Error("package.json must be v1.0.6");
49
49
  if (packageJson.license !== "MIT") throw new Error("package.json must declare MIT");
50
50
  if (packageJson.author !== "Sangyaa") throw new Error("Unexpected package author");
51
51
  if (!packageJson.keywords?.includes("pi-package")) throw new Error("Pi catalog keyword is missing");
@@ -125,6 +125,8 @@ ledger: <path>
125
125
 
126
126
  Reuse this state for normal follow-ups. Start over only when the user explicitly resets it or introduces a materially different outcome.
127
127
 
128
+ The v2 model route persists `boundary` (`Job/client` or `Personal`) and `skillMode` with the A/B/C/D selectors and backups. Reopening `/pi-marg` highlights those saved values. The conversational `context:` and `mode:` lines above are the same facts in the ledger's shorthand; they are not a second configuration store.
129
+
128
130
  ## Availability check
129
131
 
130
132
  Before declaring the task ready: