Skip to content

docs(swarm_map_policy): name the plugin's counterpart Swarm Map, not HSM - #124

Merged
juniperbevensee merged 3 commits into
mainfrom
dev/juniperbevensee/sm-plugin-docs
Jul 29, 2026
Merged

docs(swarm_map_policy): name the plugin's counterpart Swarm Map, not HSM#124
juniperbevensee merged 3 commits into
mainfrom
dev/juniperbevensee/sm-plugin-docs

Conversation

@juniperbevensee

Copy link
Copy Markdown
Collaborator

Companion to NimbleCoOrg/swarm-map#187. The control plane is now NimbleCoOrg/swarm-map; this updates the plugin's prose and repo link.

Docs-only, on purpose. These stay exactly as they are:

  • the swarm_map_policy plugin dir name
  • HSM_URL, HERMES_AGENT_NAME
  • the "HSM API URL" prompt and HSM-prefixed identifiers in the body

They're wired into every deployed agent's config.yaml plugin list and .env, and group checks are fail-closed — renaming any of them is a fleet-wide breaking change that would deny all group messages. "HSM" is the correct heritage shorthand here.

Refs: memory/plans/2026-07-18-swarm-map-org-transfer-runbook.md §2D

🤖 Generated with Claude Code

The control plane is now NimbleCoOrg/swarm-map. Prose and the repo link only.

Deliberately NOT renamed — these are wired into every deployed agent's
config.yaml plugin list and .env, and group checks are fail-CLOSED, so a rename
is a fleet-wide breaking change that denies all group messages:
  - the `swarm_map_policy` plugin dir name
  - `HSM_URL`, `HERMES_AGENT_NAME`
  - the "HSM API URL" prompt and HSM-prefixed identifiers in the body

Refs: memory/plans/2026-07-18-swarm-map-org-transfer-runbook.md §2D
Extends the plugin-docs change with the misses an audit found.

- GHCR (the one with teeth): FORK-NOTICE and README told users to pull
  `ghcr.io/nimblecoai/hermes-agent-mt`. That package is retained read-only and
  frozen at 2026-07-21, but it is still PUBLIC — so `docker pull` against it
  SUCCEEDS and silently returns pre-move code with no error. CI has published to
  `ghcr.io/nimblecoorg/...` since the transfer (ghcr-publish.yml:50 derives the
  namespace from `github.repository_owner`, verified). Repointed, and the banner
  now says plainly that the old path still resolves and is therefore a trap.
- Both rename banners described the superseded `hermes-agent` ->
  `hermes-agent-mt` rename under the OLD owner, and carried alias guidance that
  expired 2026-07-15. Rewritten to describe the current NimbleCoAI -> NimbleCoOrg
  move, with the earlier rename kept as one line of history.
- Five live current-tense references to "Hermes Swarm Map" ->
  `[Swarm Map](https://github.com/NimbleCoOrg/swarm-map)`, including two in
  patches/README.md that the first pass missed.

Deliberately NOT done: the audit suggested creating a placeholder repo at
NimbleCoAI/hermes-swarm-map to "remove the redirect dependency". That would
PERMANENTLY delete the transfer redirect every existing link depends on — the
documented kill-switch. Rejected. The old path must stay unclaimed.

Still not renamed (fleet-breaking, fail-closed group checks): the
swarm_map_policy dir, HSM_URL, HERMES_AGENT_NAME. patches/000*.patch untouched.
Audit finding: rewriting the banners dropped the old bullet's warning about
`ghcr.io/nimblecoai/hermes-agent` (the PRE-rename path), leaving the stalest
pins of all undocumented.

Verified before publishing the claim: that package is still public, `:latest`
returns manifest 200, its newest dated tag is 2026-07-21, and ghcr-publish.yml
now targets only `hermes-agent-mt` — so it receives nothing new while still
serving successful pulls. Same trap as the -mt package, one rename older.

Both old packages stay; they are the intended read-only grace window.
@juniperbevensee
juniperbevensee merged commit 2c19f56 into main Jul 29, 2026
32 checks passed
@juniperbevensee
juniperbevensee deleted the dev/juniperbevensee/sm-plugin-docs branch July 30, 2026 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant