@ssheleg/agent-sync 1.8.3 → 1.10.0

package/CHANGELOG.md

@@ -1,3 +1,40 @@
+## v1.10.0
+
+Following `task-pipeline` v1.53.0, which renamed the artifact root's default from
+`docs/superpowers/` to `docs/evidence/` and made the root resolvable (`paths.artifacts`
+in `pipeline.json`, else an existing `docs/evidence/`, else an existing
+`docs/superpowers/` — **the legacy name stays supported and no run warns about it**).
+
+Shipped surfaces name the new default now, which is why this is a minor rather than a
+patch. This project's own records moved with the directory and were not rewritten: a
+brief describes where things were when it was written.
+
+## v1.9.0
+
+### Changed
+
+- **The installer now offers the family's routing block** (closing B-06 in the
+  umbrella). Until now only `super-ux` delegated: install this skill on its own
+  and no router was written at all, so an agent had the skill and no rule saying
+  when to reach for it. The bundle installer wrote all eight, which is why
+  nothing looked broken — the gap only opened for someone installing one member.
+
+  Delegated to `npx sshlg-skills routers --member agent-sync` rather than
+  reimplemented, for three reasons:
+
+  - The block describes what the machine actually has. A lone member rendering
+    the whole thing would print a table for routers nobody installed.
+  - `--member` scopes the write to this skill's own section. Verified by damaging
+    two sections of a real block and running this installer: its own was
+    repaired, the other left exactly as it was.
+  - The launcher is the only writer that copies the operator's global instruction
+    file before touching it. That file has no version control behind it.
+
+  `--no-install` keeps it from silently downloading a package nobody asked for.
+  When the launcher is absent the command is printed instead of failing: ending
+  an install in an error over an optional follow-up reads as a failed install.
+  Both paths were exercised.
+
 ## v1.8.3
 
 ### Changed

package/agent-sync.example.json

@@ -19,7 +19,7 @@
     "docs/OPEN_QUESTIONS.md",
     "docs/ROADMAP.md",
     "docs/DOCMAP.md",
-    "docs/superpowers/retro.md"
+    "docs/evidence/retro.md"
   ],
   "claimTags": {
     "docs/ROADMAP.md": {

package/bin/agent-sync.js

@@ -95,6 +95,9 @@ function install(argv) {
       ? C.green('\n✓ installed')
       : C.red('\n✗ at least one channel failed — see the output above')
   );
+  // Before the "Next:" block, so the last thing on screen stays the instruction
+  // rather than the tail of a delegated command.
+  offerRouters();
   console.log(`
 ${C.bold('Next:')} restart Claude Code, then run ${C.bold('/agent-sync init')} in your project.
 It will ask where coordination state should live before writing anything.
@@ -102,6 +105,37 @@ It will ask where coordination state should live before writing anything.
   return ok ? 0 : 1;
 }
 
+/**
+ * Ask the family launcher to write the routing block, for this member only.
+ *
+ * Delegated rather than reimplemented, for three reasons. The block describes
+ * what the machine actually has, so a lone member rendering the whole thing
+ * would produce a table for routers nobody installed. `--member` limits the
+ * write to the `agent-sync` section and leaves everyone else's alone, which is
+ * what lets the bundle and a single installer both write. And the launcher is
+ * the only writer that copies the operator's global instruction file before
+ * touching it — that file has no version control behind it.
+ *
+ * `--no-install` keeps this from silently downloading a package nobody asked
+ * for. When the launcher is absent, print the command rather than fail: ending
+ * an install in an error because an OPTIONAL follow-up is missing reads as a
+ * failed install.
+ */
+function offerRouters() {
+  const r = spawnSync(
+    'npx',
+    ['--no-install', 'sshlg-skills', 'routers', '--member', NAME],
+    { stdio: 'inherit', shell: process.platform === 'win32' }
+  );
+  if (r.status !== 0) {
+    console.log(
+      `\nTo have this skill apply by default in every project, add the ` +
+      `family's\nrouting block to your agent's global instructions:\n\n` +
+      `  npx --yes sshlg-skills routers --member ${NAME}\n`
+    );
+  }
+}
+
 /**
  * The shadow regrows on its own: `npx skills add|update --global` auto-detects
  * Claude Code and recreates ~/.claude/skills/<name> — often as a symlink — even when

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ssheleg/agent-sync",
-  "version": "1.8.3",
-  "description": "Let concurrent coding agents share one project without colliding \u2014 leases with TTL, race-free id reservation, a run journal and a generated board, over a pluggable knowledge cloud.",
+  "version": "1.10.0",
+  "description": "Let concurrent coding agents share one project without colliding — leases with TTL, race-free id reservation, a run journal and a generated board, over a pluggable knowledge cloud.",
   "bin": {
     "agent-sync": "bin/agent-sync.js"
   },

package/plugins/agent-sync/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "name": "agent-sync",
   "displayName": "Agent Sync",
-  "version": "1.8.3",
-  "description": "Coordination layer for multi-agent repositories \u2014 leases with TTL, race-free ID reservation, a run journal, a cross-repo signal feed and a generated board, over a pluggable knowledge cloud.",
+  "version": "1.10.0",
+  "description": "Coordination layer for multi-agent repositories — leases with TTL, race-free ID reservation, a run journal, a cross-repo signal feed and a generated board, over a pluggable knowledge cloud.",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/agent-sync/skills/agent-sync/SKILL.md

@@ -4,7 +4,7 @@ description: "Use when several coding agents work one repository at the same tim
 compatibility: "Requires the task-pipeline skill for its stages (npx sshlg-skills install). Needs python3 3.9+ (stdlib only, HTTP included - nothing to pip install) and bash for the hooks. The knowledge backend is configured per project; with none configured it degrades to git-file leases. Enforcement hooks are Claude Code only - on other agents the same checks run as a self-check."
 license: MIT
 metadata:
-  version: "1.8.3"
+  version: "1.10.0"
   author: ssheleg
 ---
 

package/plugins/agent-sync/skills/agent-sync/references/pipeline-binding.md

@@ -108,7 +108,7 @@ since the pipeline's documentation track it is longer than the registers:
 | the decision register (`docs/DECISIONS.md` or `docs/adr/`) | append-only; a concurrent write loses an entry |
 | `docs/OPEN_QUESTIONS.md`, `docs/ROADMAP.md` | the same |
 | **`docs/DOCMAP.md`** | seeded into every project the pipeline touches; holds the registers, the propagation matrix and the ratchet floors. Losing it loses the map |
-| **`docs/superpowers/retro.md`** | capped at ten standing instructions, so a concurrent write silently **drops a lesson** instead of conflicting visibly |
+| **`docs/evidence/retro.md`** | capped at ten standing instructions, so a concurrent write silently **drops a lesson** instead of conflicting visibly |
 
 The schema keeps `agent-sync.json` to known keys, which is why this reasoning lives
 here and not as a comment in the config.

package/plugins/agent-sync/skills/agent-sync/scripts/agent_sync.py

@@ -33,7 +33,7 @@ from datetime import datetime, timezone
 from pathlib import Path
 from typing import Any
 
-VERSION = "1.8.3"
+VERSION = "1.10.0"
 
 CONFIG_PATH = Path(".claude/agent-sync.json")
 ENV_FILE = Path(".env.agent-sync")