@yemi33/minions 0.1.1938 → 0.1.1940

package/dashboard/js/render-utils.js

@@ -60,7 +60,9 @@ function formatToolSummary(name, input) {
     }
     default: {
       var keys = Object.keys(inp);
-      if (keys.length === 0) return escHtml(name) + '()';
+      // No-input case (e.g. ACP chips that carry their full label in `name`
+      // like "Fetch /api/status") — render the name verbatim, no parens.
+      if (keys.length === 0) return escHtml(name);
       var firstKey = keys[0];
       var firstVal = String(inp[firstKey] || '');
       if (firstVal.length > 40) firstVal = firstVal.slice(0, 37) + '...';

package/docs/distribution.md

@@ -1,6 +1,37 @@
 # Distribution & Publishing
 
-Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized package boundary.
+Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized package boundary. The source lives across three GitHub remotes, with a strict one-way port direction (see [Three-Remote Topology](#three-remote-topology)).
+
+## Three-Remote Topology
+
+| Remote (local name on `D:/squad`) | URL | Role |
+|-----------------------------------|-----|------|
+| `origin` | `https://github.com/yemi33/minions` | **Authoring source of truth.** All normal code changes (engine, dashboard, playbooks, agents, etc.) land here first. Triggers npm publish + downstream mirrors. |
+| `emu` | `https://github.com/yemishin_microsoft/minions` | Microsoft-identity mirror of `yemi33/minions`. Automated via `.github/workflows/mirror-to-emu.yml`. |
+| `opg` | `https://github.com/opg-microsoft/minions` | **Compliant store** under the `opg-microsoft` org. Automated mirror to a sync branch via `.github/workflows/mirror-to-opg.yml`; `main` is reconciled by a maintainer PR because it carries enterprise/compliance-only commits (see below). |
+
+### Port direction
+
+**Strictly one-way: `yemi33` → `emu`, `yemi33` → `opg`.**
+
+- **Do NOT port from `emu` or `opg` back into `yemi33`.** Their `main` branches may carry org-specific compliance content (`.github/policies/*`, `.github/acl/*`, `.github/compliance/*`, JIT access policy, internal access lists, MS-org issue templates) that has no business in the personal-fork authoring source.
+- **Direct pushes to `opg-microsoft/minions` are allowed for enterprise/compliance-specific changes only.** Examples: editing `.github/policies/jit.yml`, updating `.github/acl/access.yml`, modifying `.github/compliance/inventory.yml`. These changes stay on `opg` and are not backported.
+- Other teams (Microsoft infra, compliance review) may also push to `opg-microsoft/minions` directly. Treat its `main` as potentially ahead of `yemi33`/`emu` on policy files.
+
+### Why opg can't use the same direct-mirror pattern as emu
+
+`mirror-to-emu.yml` does `git push emu HEAD:master` — direct overwrite, because `emu/master` is meant to be a 1:1 reflection of `yemi33/master`. `opg-microsoft/minions` is different: its `main` carries enterprise-only commits that don't exist on `yemi33/master`, so a force-push to `opg/main` would destroy them. Instead, `mirror-to-opg.yml` force-pushes `yemi33/master` to `opg/sync/yemi33-master` (a dedicated bot-owned branch), and a maintainer opens or updates a PR from `sync/yemi33-master` → `main` for review. The first such PR uses `--allow-unrelated-histories` to bridge the initial divergence; subsequent ones merge incrementally.
+
+### Required secrets on `yemi33/minions`
+
+| Secret | Purpose | Workflow |
+|--------|---------|----------|
+| `NPM_TOKEN` | npm publish | `publish.yml` |
+| `EMU_PUSH_TOKEN` | Push to `yemishin_microsoft/minions` | `mirror-to-emu.yml` |
+| `EMU_PACKAGES_TOKEN` | Publish to `@yemishin_microsoft` internal registry | `publish-internal-github-packages.yml` |
+| `OPG_PUSH_TOKEN` | Push to `opg-microsoft/minions` sync branch | `mirror-to-opg.yml` |
+
+Each mirror workflow gracefully skips with a warning if its token secret is unset, so unconfigured downstreams never block the primary publish path.
 
 ## Distribution Boundary
 

package/engine/cc-worker-pool.js

@@ -252,9 +252,7 @@ class Worker {
           try { this.inflight.onChunk(text); } catch { /* swallow */ }
         }
       } else if (update.sessionUpdate === 'tool_call' && this.inflight.onToolUse) {
-        // ACP `tool_call` (pending) → Claude-style {name, input} via
-        // _mapAcpToolCallToToolUse so the dashboard's formatToolSummary
-        // formatters (Bash → "$ <cmd>", etc.) work unchanged.
+        // ACP `tool_call` (pending) → chip label via _mapAcpToolCallToToolUse.
         const mapped = _mapAcpToolCallToToolUse(update);
         if (mapped) {
           try { this.inflight.onToolUse(mapped.name, mapped.input, update.toolCallId); }
@@ -447,50 +445,40 @@ function _extractChunkText(content) {
 // (Bash → "$ <cmd>", Read → "Reading <path>", etc.). Unknown kinds fall back
 // to ACP's human-readable `title` with the raw input attached, which renders
 // through the default `<title>(<key>: <val>)` formatter.
+// Map an ACP `tool_call` notification to a chip label. Strategy:
+//
+//   1. Detect well-known shapes by rawInput field presence and route through
+//      formatToolSummary's Claude-tool formatters (Bash → "$ <cmd>",
+//      Grep → "Searching `pat` in path", Read → "Reading <path>"). Preserves
+//      the granular detail you actually want when reading the chip list.
+//
+//   2. Fall back to ACP's human-curated `title` for anything that doesn't
+//      match. Title is always populated and immune to field-name drift, so
+//      the empty-`$` failure mode (kind:execute with no `command`) becomes
+//      a clean "Find work item W-..." chip instead of a broken stub.
+//
+// Kind-based routing is intentionally NOT used — ACP overloads `kind:read`
+// for both file-view and grep, and `kind:execute` sometimes arrives without
+// a `command`. Field-detection on rawInput is more reliable.
 function _mapAcpToolCallToToolUse(update) {
   if (!update || update.sessionUpdate !== 'tool_call') return null;
   const rawInput = (update.rawInput && typeof update.rawInput === 'object') ? update.rawInput : {};
-  const kind = String(update.kind || '').toLowerCase();
-  const title = update.title || '';
-
-  // Field-name normalization: Copilot ACP and Claude tool_use use different
-  // keys for the same concept (Copilot `path`, Claude `file_path`). Normalize
-  // here so the dashboard's formatToolSummary — written against Claude's
-  // names — produces the same chip text on both runtimes.
-  const filePath = rawInput.file_path || rawInput.path || rawInput.filePath || '';
-
-  // Pattern (Grep) — Copilot uses `paths` (plural) for the search scope where
-  // Claude's Grep takes `path`.
-  if (typeof rawInput.pattern === 'string') {
-    return {
-      name: 'Grep',
-      input: { pattern: rawInput.pattern, path: rawInput.paths || rawInput.path || '.' },
-    };
-  }
+  const title = update.title || update.kind || 'Tool';
 
-  switch (kind) {
-    case 'execute':
-      return { name: 'Bash', input: rawInput };
-    case 'read':
-      // ACP overloads `read` for both file-view and grep — the pattern check
-      // above already handled grep, so this branch is the file-view case.
-      return { name: 'Read', input: { file_path: filePath } };
-    case 'edit':
-      return { name: 'Edit', input: { file_path: filePath } };
-    case 'search':
-      // Pattern check above handled the grep case; arriving here means glob.
-      return { name: 'Glob', input: rawInput };
-    case 'fetch':
-      return { name: 'WebFetch', input: rawInput };
-    case 'think':
-      return { name: title || 'Think', input: rawInput };
-    default:
-      // Unknown kind — use ACP's human-readable title as the chip label and
-      // drop rawInput so formatToolSummary's default branch shows just the
-      // title (avoids `<title>(<key>: <val>)` clutter when the input shape
-      // is unfamiliar).
-      return { name: title || kind || 'Tool', input: {} };
+  if (typeof rawInput.command === 'string' && rawInput.command) {
+    return { name: 'Bash', input: { command: rawInput.command } };
+  }
+  if (typeof rawInput.pattern === 'string' && rawInput.pattern) {
+    return { name: 'Grep', input: { pattern: rawInput.pattern, path: rawInput.paths || rawInput.path || '.' } };
+  }
+  if (typeof rawInput.path === 'string' && rawInput.path) {
+    const isEdit = String(update.kind || '').toLowerCase() === 'edit';
+    return { name: isEdit ? 'Edit' : 'Read', input: { file_path: rawInput.path } };
+  }
+  if (typeof rawInput.url === 'string' && rawInput.url) {
+    return { name: 'WebFetch', input: { url: rawInput.url } };
   }
+  return { name: title, input: {} };
 }
 
 // ── Public API ────────────────────────────────────────────────────────────

package/engine/copilot-models.json

@@ -0,0 +1,5 @@
+{
+  "runtime": "copilot",
+  "models": null,
+  "cachedAt": "2026-05-14T21:44:50.675Z"
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.1938",
+  "version": "0.1.1940",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"