chore(release): 0.11.0 -- a message can say it needs no answer, and 0.10.0 gets its changelog
Bumps plugin.json, package.json, the README badge and the three skill frontmatters, because release-plugin.mjs blocks on a plugin.json that does not already stand at the target version. Also closes a gap this release would otherwise have inherited: v0.10.0 shipped without a CHANGELOG section, and the next-cost fix sat under [Unreleased] even though it is inside v0.9.0..v0.10.0. Labelling that block 0.11.0 would have made a second wrong claim, so 0.10.0 now has its own section, written from the commits in the tag rather than from memory. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016iJoZVmU2guTEZcMghk88z
This commit is contained in:
parent
5754d67a6b
commit
6735298752
7 changed files with 28 additions and 7 deletions
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "repo-mailbox",
|
||||
"version": "0.10.0",
|
||||
"version": "0.11.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"
|
||||
|
|
|
|||
23
CHANGELOG.md
23
CHANGELOG.md
|
|
@ -5,7 +5,7 @@ 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).
|
||||
|
||||
## [Unreleased]
|
||||
## [0.11.0] - 2026-07-31
|
||||
|
||||
### Added
|
||||
|
||||
|
|
@ -67,6 +67,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
split Rule 6 exists to hold. Selftest section 20 pins both halves together, as
|
||||
it has since 0.5.0.
|
||||
|
||||
## [0.10.0] - 2026-07-31
|
||||
|
||||
### Added
|
||||
|
||||
- **`route.sh` + the `route` skill - the writer for the board's cost field.**
|
||||
`next-cost` had a reader and no writer, so it was retyped by hand every
|
||||
session; measured across the operator's tree, the existing board lines carried
|
||||
eight distinct spellings of a field with one documented form. `route.sh` is a
|
||||
pure calculator: four scored traits of the next task (`path`, `verification`,
|
||||
`reversibility`, `scope`) plus a required rationale, and it prints the rubric
|
||||
row, the `next-cost` value, a pasteable startup command and the one-row-cheaper
|
||||
fallback. Escalation is asymmetric - any single trait escalates, the cheapest
|
||||
row needs all four at the cheap end. The row table is a closed set of six, so a
|
||||
seventh spelling cannot enter circulation, and selftest section 6 runs the
|
||||
round trip (route emits, board parses) inside one repo instead of across two.
|
||||
|
||||
The table is the operator's global model rubric, moved here as the single
|
||||
copy: two copies of one policy drift, and a table in a prose file cannot be
|
||||
tested. Scoring is judgement and stays in the skill; turning scores into a row
|
||||
is a lookup and costs no model calls.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **The board line's `next-cost` field had two specs, and one of them was
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
|
||||
*AI-generated: all code produced by Claude Code through dialog-driven development.*
|
||||
|
||||

|
||||

|
||||

|
||||

|
||||

|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "repo-mailbox",
|
||||
"version": "0.10.0",
|
||||
"version": "0.11.0",
|
||||
"private": true,
|
||||
"type": "module",
|
||||
"engines": {
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ description: >-
|
|||
user names no repo and no tool — choosing *between* repos is this skill. Not for
|
||||
"where were we" inside the current repo: that is this repo's own STATE.md,
|
||||
already injected at session start.
|
||||
version: "0.10.0"
|
||||
version: "0.11.0"
|
||||
---
|
||||
|
||||
# board — which repo deserves the next session
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ description: >-
|
|||
covers retiring a broadcast that has become wrong or obsolete: "retract that
|
||||
broadcast", "that announcement is outdated, pull it", "trekk tilbake kringkastingen",
|
||||
"den broadcasten er utdatert".
|
||||
version: "0.10.0"
|
||||
version: "0.11.0"
|
||||
---
|
||||
|
||||
# coord-send — natural-language front door for inter-repo messages
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ description: >-
|
|||
the operator names no model and no tool — choosing the model for the next
|
||||
session IS this skill. Not for choosing which REPO gets the next session:
|
||||
that is the `board` skill.
|
||||
version: "0.10.0"
|
||||
version: "0.11.0"
|
||||
---
|
||||
|
||||
# route — what the next session should run with
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue