archal 0.9.12 → 0.9.13

package/dist/index.cjs

@@ -87281,6 +87281,16 @@ function looksLikeSkillsDir(candidate) {
   }
   return false;
 }
+function findPnpmWorkspaceRoot(start) {
+  let dir = start;
+  for (let i = 0; i < 10; i++) {
+    if ((0, import_node_fs53.existsSync)((0, import_node_path53.join)(dir, "pnpm-workspace.yaml"))) return dir;
+    const parent = (0, import_node_path53.dirname)(dir);
+    if (parent === dir) return null;
+    dir = parent;
+  }
+  return null;
+}
 function findRepoRoot(start) {
   let dir = start;
   for (let i = 0; i < 10; i++) {
@@ -87308,7 +87318,14 @@ function resolveSkillsDir() {
   );
 }
 function runPmAdd(pm, cwd, spec) {
-  const args = pm === "npm" ? ["install", "--save-dev", spec] : ["add", "-D", spec];
+  let args;
+  if (pm === "npm") {
+    args = ["install", "--save-dev", "--no-audit", "--no-fund", "--loglevel=error", spec];
+  } else if (pm === "pnpm" && findPnpmWorkspaceRoot(cwd) === cwd) {
+    args = ["add", "-D", "-w", spec];
+  } else {
+    args = ["add", "-D", spec];
+  }
   const result = (0, import_node_child_process10.spawnSync)(pm, args, { cwd, stdio: "inherit" });
   if (result.error) {
     throw new CliRuntimeError(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "archal",
-  "version": "0.9.12",
+  "version": "0.9.13",
   "description": "Test your agents & integrations against digital twins",
   "type": "module",
   "main": "dist/index.cjs",

package/skills/onboard/SKILL.md

@@ -38,17 +38,23 @@ Before asking anything, read the repo:
 
 ## Install + auth
 
-If you're here because the user ran `npx archal init`, the CLI is already
-a devDependency and the skills are in place. Skip to `archal login`.
+If you're here via `npx archal init`, archal is already a devDependency
+and the skills are already in place. Go straight to login:
 
 ```bash
-npx archal --version        # verify CLI is on PATH / in node_modules
-npx archal init --skills-only   # re-stage skills if they drifted
-archal usage                # check auth
 archal login                # OAuth browser flow, or: archal login --token <token>
+archal usage                # verify auth + plan
 ```
 
-In CI, use `ARCHAL_TOKEN` instead of `archal login`.
+In CI, set `ARCHAL_TOKEN` instead of running `archal login`.
+
+If something feels wrong (missing CLI, stale skills), these are the
+recovery commands — don't run them otherwise:
+
+```bash
+npx archal --version           # CLI reachable? prints e.g. 0.9.12
+npx archal init --skills-only  # re-stage skills if they drifted
+```
 
 ## Pick a workflow
 

package/skills/scenario/SKILL.md

@@ -99,6 +99,8 @@ Aliases for `evaluator-model`: `evaluator`, `evaluatormodel`, `model`.
 | `supabase` | `empty`, `small-project`, `saas-starter`, `ecommerce` |
 | `google-workspace` | `empty`, `assistant-baseline`, `gmail-busy-inbox`, `calendar-packed-week` |
 | `ramp` | `empty`, `default` |
+| `discord` | `empty`, `small-server`, `harvested` |
+| `telegram` | `empty`, `harvested` |
 
 ## Twin auto-detection from content
 
@@ -111,6 +113,12 @@ If no `twins:` config is set, Archal infers twins from keywords in Setup, Expect
 - `stripe`, `payment`, `refund`, `subscription`, `invoice` -> `stripe`
 - `supabase`, `database`, `sql query` -> `supabase`
 - `google workspace`, `gmail`, `calendar event`, `inbox` -> `google-workspace`
+- `discord`, `guild`, `text channel` -> `discord`
+
+Not every twin has auto-detect keywords — `telegram` in particular has
+none. If your scenario uses `telegram`, set `twins: telegram` in the
+Config block or in `.archal.json`. `ramp` auto-detects on `ramp`,
+`bill`, `expense`, `reimbursement`, `fund`, `card spend`.
 
 ## Multi-service scenarios
 

package/twin-assets/google-workspace/tools.json

@@ -13,7 +13,8 @@
           },
           "refresh_token": {
             "type": "string",
-            "minLength": 1
+            "minLength": 1,
+            "maxLength": 2048
           },
           "client_id": {
             "type": "string"