feat(release)!: rename plugin and repo from coord to repo-mailbox
The old name said that something was coordinated, but not what the thing was. The new one names what it is, reusing the vocabulary the code and docs already use throughout: mailbox, inbox, archive, broadcast. Renamed: Forgejo repo (open/coord -> open/repo-mailbox, old URL redirects), plugin manifest name, package name, README title and badge, CLAUDE.md heading and release command. BREAKING CHANGE: the skill is invoked as /repo-mailbox:coord-send rather than /coord:coord-send, and the plugin must be reinstalled under its new name. Deliberately unchanged: the CLI (coord-send.sh, coord-inbox.sh, coord-done.sh, coord-selftest.sh), the skill name coord-send, the mailbox root ~/.claude/coord/, and CLAUDE_COORD_DIR. Those name the transport protocol, not the product; renaming them would migrate live mailbox data and break message history in every participating repo for no gain. Selftest unchanged at 70/70 -- the engine was not touched.
This commit is contained in:
parent
4ae34658ff
commit
c27b20fc62
6 changed files with 46 additions and 11 deletions
|
|
@ -1,12 +1,12 @@
|
|||
{
|
||||
"name": "coord",
|
||||
"version": "0.2.2",
|
||||
"name": "repo-mailbox",
|
||||
"version": "0.3.0",
|
||||
"description": "Local mailbox for coordination between Claude Code sessions in different repositories. Directed messages and broadcasts as plain Markdown files on your own disk, injected as context at session start. Local, private, no network.",
|
||||
"author": {
|
||||
"name": "Kjell Tore Guttormsen"
|
||||
},
|
||||
"auto_discover": true,
|
||||
"license": "MIT",
|
||||
"repository": "https://git.fromaitochitta.com/open/coord",
|
||||
"repository": "https://git.fromaitochitta.com/open/repo-mailbox",
|
||||
"keywords": ["coordination", "mailbox", "inter-repo", "multi-repo", "session-start"]
|
||||
}
|
||||
|
|
|
|||
27
CHANGELOG.md
27
CHANGELOG.md
|
|
@ -5,6 +5,33 @@ All notable changes to this project will be documented in this file.
|
|||
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
||||
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
||||
|
||||
## [0.3.0] - 2026-07-25
|
||||
|
||||
### Changed
|
||||
|
||||
- **Renamed the plugin and repository from `coord` to `repo-mailbox`.** The old
|
||||
name said that something was coordinated but not what the thing was; the new
|
||||
one names what it is, using the same vocabulary the code and docs already use
|
||||
throughout (mailbox, inbox, archive, broadcast). The Forgejo repository moved
|
||||
from `open/coord` to `open/repo-mailbox` (the old URL redirects), and the
|
||||
marketplace entry, plugin manifest and package name follow.
|
||||
|
||||
**This is breaking for installed users:** the skill is now invoked as
|
||||
`/repo-mailbox:coord-send` rather than `/coord:coord-send`, and the plugin
|
||||
must be reinstalled under its new name.
|
||||
|
||||
**Deliberately unchanged:** the CLI (`coord-send.sh`, `coord-inbox.sh`,
|
||||
`coord-done.sh`, `coord-selftest.sh`), the skill name `coord-send`, the
|
||||
mailbox root `~/.claude/coord/`, and the `CLAUDE_COORD_DIR` override. Those
|
||||
name the transport protocol, not the product — renaming them would migrate
|
||||
live mailbox data and break message history in every participating repo for
|
||||
no gain in clarity.
|
||||
|
||||
### Fixed
|
||||
|
||||
- Catalog README listed `48 selftest checks` for this plugin; the actual count
|
||||
has been 70 since v0.2.2.
|
||||
|
||||
## [0.2.2] - 2026-07-25
|
||||
|
||||
### Changed
|
||||
|
|
|
|||
10
CLAUDE.md
10
CLAUDE.md
|
|
@ -1,4 +1,9 @@
|
|||
# coord
|
||||
# repo-mailbox
|
||||
|
||||
Renamed from `coord` in v0.3.0. The plugin/repo is `repo-mailbox`; the CLI
|
||||
(`coord-send.sh`, `coord-inbox.sh`, `coord-done.sh`), the mailbox root
|
||||
(`~/.claude/coord/`) and `CLAUDE_COORD_DIR` deliberately kept their names —
|
||||
they are the transport protocol, not the product.
|
||||
|
||||
## Context
|
||||
|
||||
|
|
@ -46,7 +51,8 @@ Version must agree across: `.claude-plugin/plugin.json`, `package.json`,
|
|||
README version badge, `skills/coord-send/SKILL.md` frontmatter, git tag
|
||||
`vX.Y.Z`, and the catalog `ref` in
|
||||
`ktg-plugin-marketplace/catalog/.claude-plugin/marketplace.json`. Release via
|
||||
the catalog's `scripts/release-plugin.mjs coord` (tag + ref bump together);
|
||||
the catalog's `scripts/release-plugin.mjs repo-mailbox` (tag + ref bump
|
||||
together);
|
||||
verify with `scripts/check-versions.mjs`. Never hand-edit a ref.
|
||||
|
||||
Two things that script does that its dry-run label does not suggest:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Coord
|
||||
# repo-mailbox
|
||||
|
||||
> Formerly `coord` (renamed in v0.3.0). The plugin is now `repo-mailbox`; the CLI (`coord-send`, `coord-inbox`, `coord-done`), the mailbox root `~/.claude/coord/` and `CLAUDE_COORD_DIR` keep their names — they are the transport protocol, not the product.
|
||||
|
||||
> A local mailbox for coordination between Claude Code sessions in different repositories. Session A in repo X leaves a message for repo Y; the next session in repo Y gets it injected as context at startup. Local, private, no network, no SaaS.
|
||||
|
||||
|
|
@ -6,7 +8,7 @@
|
|||
|
||||
*AI-generated: all code produced by Claude Code through dialog-driven development.*
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -18,7 +20,7 @@
|
|||
|
||||
When you work with an AI coding agent across several repositories, the sessions are islands. A decision made in repo X often matters to repo Y — a shared spec changed, a bug another repo depends on got fixed, a gate was re-pinned. Without a channel, you are the messenger: you remember to mention it in the next session, or it gets lost.
|
||||
|
||||
Coord is that channel, reduced to the simplest thing that works: a directory of Markdown files on your own disk. Sending is writing a file; receiving is a SessionStart hook that injects your repo's pending messages as context. No server, no daemon, no network, no accounts.
|
||||
repo-mailbox is that channel, reduced to the simplest thing that works: a directory of Markdown files on your own disk. Sending is writing a file; receiving is a SessionStart hook that injects your repo's pending messages as context. No server, no daemon, no network, no accounts.
|
||||
|
||||
**Transport, not state.** A coord message is a notice, not a source of truth. The durable record of any decision lives in the owning repo (its docs, its git history). Messages point at that record; they never replace it.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "coord",
|
||||
"version": "0.2.2",
|
||||
"name": "repo-mailbox",
|
||||
"version": "0.3.0",
|
||||
"private": true,
|
||||
"type": "module",
|
||||
"engines": {
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ description: >-
|
|||
beskjed til Y og Z", "kringkast at …", "svar på coord-meldingen", "når Z er ferdig,
|
||||
varsle X". Trigger even when the user names a repo plus something to convey without
|
||||
saying "coord" explicitly — routing a message to another repo IS this skill.
|
||||
version: "0.2.2"
|
||||
version: "0.3.0"
|
||||
---
|
||||
|
||||
# coord-send — natural-language front door for inter-repo messages
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue