@ssheleg/agent-sync 1.11.0 → 1.12.0

package/CHANGELOG.md

@@ -1,3 +1,66 @@
+## v1.12.0 — 246 kB of someone else's bytecode, in every install
+
+**The published tarball carried a `.pyc` both ignore files were written to exclude.**
+`@ssheleg/agent-sync@1.11.1` ships
+`plugins/agent-sync/skills/agent-sync/scripts/__pycache__/agent_sync.cpython-312.pyc` —
+**245.8 kB against 175.7 kB of source beside it**, 40% of the tarball, compiled by
+whatever interpreter the publisher happened to be running. Verified by unpacking the
+published artefact, not by reading the manifest.
+
+`.gitignore:3-4` and `.npmignore:1-2` both exclude `__pycache__/` and `*.pyc`. **Neither
+is consulted once `files` names a directory** — the whitelist wins, so the intent was
+recorded twice and enforced nowhere. `files` now carries `!plugins/**/__pycache__` and
+`!plugins/**/*.pyc`, and the packed result drops from **231.5 kB / 28 files to
+125.8 kB / 27**.
+
+**A filesystem walk would not have caught this**, which is why the new check asks npm.
+`check_the_tarball_carries_no_bytecode()` reads `npm pack --dry-run --json` — the
+packer's own answer to *what would ship* — and fails on any `.pyc` or `__pycache__` in
+it. Where npm is absent it discloses rather than passing: a check that cannot look must
+never read as one that looked. Watched failing against the exact state that shipped, and
+added to `--self-test`, now **38 fixtures**.
+
+### Fixed — three documents that told the reader something untrue
+
+- **`references/hooks.md` said the hooks are removed by editing `.claude/settings.json`.**
+  Nothing here ever writes a `hooks` block there, and Claude Code has no per-hook disable
+  for a hook a plugin ships. A user who wanted them gone edited a file with no such block
+  and concluded it had worked, while the SessionStart hook kept speaking in every session.
+  The two real levers are named now — `enabledPlugins[…] = false` or `plugin uninstall` —
+  plus the fact that every hook already self-disables in a project with no
+  `.claude/agent-sync.json`.
+- **`CONTRIBUTING.md` said five version surfaces move together; the validator enforces
+  six.** The missing one is `VERSION` in `scripts/agent_sync.py`, and it is exactly what
+  forced the 1.11.1 patch: a bump driver written from that page moved four of six and CI
+  refused the tag. It is the constant `status` prints into every session, so its drift is
+  invisible in the manifests and loud in the banner.
+- **`CONTRIBUTING.md` said the self-test injects five defects; it injected thirty-seven.**
+  The count is read off the run's own last line now. The number is the whole claim — a
+  contributor who reads *five* will not think to add a fixture for the sixth thing they
+  change.
+
+Found by the nine-repository audit of 2026-08-16 (umbrella `B-72`; the three documents
+are `F-agent-sync-05`, `-08` and `-11`).
+
+## v1.11.1 — the gate can see an invariant it breaks elsewhere
+
+**This gate can now see an invariant it breaks one repository away.** The family umbrella
+routes work by matching a prompt against a table in `lib/triggers.js`, and every trigger
+there must be a word this skill's own `description` advertises. Nothing here knew that
+table existed. On 2026-08-16 `sheleg-design` 1.37.0 shipped green having dropped a phrase
+that was still a live trigger, the umbrella found out minutes after the tag, and it cost a
+patch release — because the member releases FIRST and the umbrella re-pins after.
+
+`test/validate.py` now asks the umbrella's own checker (`test/advertised_check.js`), which
+reads the module the hook itself calls. **No copy of the table lives here**, so there is
+nothing to drift. With no umbrella above this checkout — a standalone clone, and CI — it
+discloses rather than passing, because a check that cannot look must never read as one
+that looked.
+
+Watched refusing a real drop before shipping: every one of the seven members carrying
+routed triggers had one of its own advertised phrases removed and every one of them failed
+its own gate.
+
 ## v1.11.0 — releasing stops rewinding a cell, and a register with no pattern says so
 
 Two more defects in the same afternoon that produced v1.10.1, both from using this tool

package/package.json

@@ -1,13 +1,15 @@
 {
   "name": "@ssheleg/agent-sync",
-  "version": "1.11.0",
-  "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.12.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"
   },
   "files": [
     "bin/",
     "plugins/",
+    "!plugins/**/__pycache__",
+    "!plugins/**/*.pyc",
     "agent-sync.schema.json",
     "agent-sync.example.json",
     "README.md",

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

@@ -1,7 +1,7 @@
 {
   "name": "agent-sync",
   "displayName": "Agent Sync",
-  "version": "1.11.0",
+  "version": "1.12.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",

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.11.0"
+  version: "1.12.0"
   author: ssheleg
 ---
 

package/plugins/agent-sync/skills/agent-sync/references/hooks.md

@@ -103,6 +103,18 @@ echo '{"tool_name":"Edit","tool_input":{"file_path":"docs/DECISIONS.md"},"cwd":"
 
 ## Removing them
 
-Delete the `hooks` block from the project's `.claude/settings.json`. The skill keeps
-working — every guard is also available as a command, and the board simply records
-runs as `ungated` from then on.
+**Not** by editing `.claude/settings.json` — nothing here ever writes a `hooks`
+block there, and Claude Code has no per-hook disable for a hook a plugin ships. A
+reader who follows that instruction edits a file with no such block and concludes
+the removal worked while every hook keeps firing.
+
+Two levers actually work:
+
+- `enabledPlugins["agent-sync@agent-sync"] = false` in `~/.claude/settings.json` —
+  enablement is the only switch a plugin hook has; or
+- `claude plugin uninstall agent-sync@agent-sync`.
+
+And one you usually do not need: every hook already self-disables in a project with
+no `.claude/agent-sync.json` (`hooks/_lib.sh`), so a repository that never opted in
+is not paying for them. The skill keeps working either way — every guard is also
+available as a command, and the board simply records runs as `ungated` from then on.

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.11.0"
+VERSION = "1.12.0"
 
 CONFIG_PATH = Path(".claude/agent-sync.json")
 ENV_FILE = Path(".env.agent-sync")