Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,15 @@ Hive did not historically maintain a complete changelog. This file starts a prag
### Fixed

- release: cap GitHub Release notes at `RELEASE_NOTES_MAX_CHARS` (120000) before the SBOM/NOTICE trailer, cutting the changelog section at a bullet boundary and linking the tag's full `CHANGELOG.md` section, so a first-on-the-line release such as v6.0.0 no longer fails `gh release create` with HTTP 422 "body is too long" after the tag and image retags have landed.
## 2026-11-08 (v5.202.0)

### Added

- crux: turn signals, the fifth work service of the Crux work-services RFC ([hivecommons/crux#114](https://github.com/hivecommons/crux/issues/114) S5). Every contained run now keeps an append-only `<workdir>/runs/<id>/signals.jsonl` of where its turn is and how it ended — `started` and `done` from the runner (`done` on every terminal path, with status, exit code and timed-out), `needs-input`, `input` and `blocked` from a gate opened with the new `run` field (`crux gate open --run`), and `thinking`, `tool`, `blocked`, `needs-input` or `input` posted by the run's owner. Read it with `GET /v1/runs/{id}/signals?since_seq=&limit=` or `crux --server … signal list`, post with `POST /v1/runs/{id}/signals` or `crux --server … signal emit`; each signal is also published as `run.signal` on `/v1/events`. The last kick outcome of every agent is saved under `<workdir>/signals/agents/` before `agent.kick_outcome` is published, and `GET /v1/agents/{name}/kick-outcome` answers it with `settled_for_last_kick`, so a driver that missed the event learns from the record whether its turn ended.

### Security

- The CLI-memory drain now reaches each memory store by opening its directories one component at a time from the filesystem root, refusing any component that is a symlink and requiring each opened directory to be the inode `Lstat` saw. `cliMemoryDrainSources` already resolved stores with `EvalSymlinks` and kept only those under the agent's own home, but the drain still opened the store root by path, so an agent that swapped `.claude`, `projects` or a project slug for a symlink after that listing could have had another agent's store (or any hive-readable `memory/*.md` tree) drained under its own name and, with `truncate`, emptied. Such a store is now reported in `kept` and the drain error, never followed ([#17256](https://github.com/hivecommons/hive/issues/17256)).

## 2026-11-08 (v5.201.1)

Expand Down
1 change: 1 addition & 0 deletions changelog.d/added-crux-s1-s2-followups.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- crux: checkout requests are bounded by a server ceiling (`--checkout-max-bytes`, `CRUX_CHECKOUT_MAX_BYTES`), private repositories clone with `CRUX_CHECKOUT_TOKEN` through a credential helper that never logs the token, and the `job` run backend isolates each Job with a deny-all NetworkPolicy by default (`job_network: none|host|default`)
1 change: 0 additions & 1 deletion changelog.d/added-crux-turn-signals.md

This file was deleted.

1 change: 1 addition & 0 deletions changelog.d/added-maintainer-notes.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- **Maintainer notes on the Activity Monitor.** With more than one maintainer running a hive, there was nowhere on the dashboard to leave a colleague a word about an item short of a GitHub comment everyone else could read. Each row now carries a 🗒 button with a count badge: click it for the item's maintainer notes — who wrote what, when — and a one-line composer (⌘/Ctrl+Enter). Notes are stored on the spoke in the append-only `/data/maintainer-notes.jsonl` and are never written to GitHub; every signed-in maintainer sees them, adding one takes write on the repo, deleting is author-or-owner, and the `maintainer-notes` SSE frame keeps the other browsers live. The scheduler types an item's notes into the agent's kick under `# Maintainer notes` (1 KB cap), so what a maintainer wrote on the row reaches whoever picks it up. `GET`/`POST /api/notes`, `DELETE /api/notes/{id}`; audited as `maintainer_note_add` / `maintainer_note_delete`.
272 changes: 272 additions & 0 deletions dashboard/openapi.json
Original file line number Diff line number Diff line change
Expand Up @@ -31431,6 +31431,278 @@
}
}
},
"/api/notes": {
"get": {
"tags": [
"Status"
],
"summary": "List maintainer notes for one item, or every live note in the hive",
"description": "Maintainer notes are the private, per-item notes maintainers leave each other on Activity Monitor rows. They live in the spoke's append-only /data/maintainer-notes.jsonl and are never written to or read from GitHub; every signed-in maintainer of the hive sees them and the scheduler injects an item's notes into the agent kick under `# Maintainer notes` (1 KiB cap). Adds and deletes are broadcast on the dashboard event stream as the `maintainer-notes` SSE event {seq, repo, number, count, action}. With repo and number: that item's live notes, oldest first. With neither: every live note (the SPA's count badges). Requires a signed-in GitHub user or a verified owner session.",
"parameters": [
{
"name": "repo",
"in": "query",
"required": false,
"schema": {
"type": "string"
},
"description": "owner/name; must be given together with number"
},
{
"name": "number",
"in": "query",
"required": false,
"schema": {
"type": "integer"
}
}
],
"responses": {
"200": {
"description": "Notes",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"notes": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"repo": {
"type": "string",
"description": "owner/name, lower-cased"
},
"number": {
"type": "integer"
},
"author": {
"type": "string",
"description": "GitHub login of the dashboard session that wrote it"
},
"text": {
"type": "string",
"maxLength": 2000
},
"created_at": {
"type": "string",
"format": "date-time"
},
"deleted_at": {
"type": "string",
"format": "date-time",
"description": "Set on the tombstone a DELETE returns; live notes omit it"
},
"deleted_by": {
"type": "string"
}
}
}
},
"repo": {
"type": "string"
},
"number": {
"type": "integer"
}
}
}
}
}
},
"400": {
"description": "repo without number (or the reverse), or a malformed repo"
},
"401": {
"description": "GitHub user session required"
}
}
},
"post": {
"tags": [
"Status"
],
"summary": "Append a maintainer note to one issue or pull request",
"description": "Maintainer notes are the private, per-item notes maintainers leave each other on Activity Monitor rows. They live in the spoke's append-only /data/maintainer-notes.jsonl and are never written to or read from GitHub; every signed-in maintainer of the hive sees them and the scheduler injects an item's notes into the agent kick under `# Maintainer notes` (1 KiB cap). Adds and deletes are broadcast on the dashboard event stream as the `maintainer-notes` SSE event {seq, repo, number, count, action}. The author is the dashboard session's GitHub login, never a body field. Same authorisation as the hold toggle (owner, or GitHub write/maintain/admin on the repository) plus a signed-in user. Written to the audit log as maintainer_note_add.",
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"type": "object",
"required": [
"repo",
"number",
"text"
],
"properties": {
"repo": {
"type": "string",
"description": "owner/name"
},
"number": {
"type": "integer"
},
"text": {
"type": "string",
"maxLength": 2000,
"description": "Plain text; trimmed, non-empty"
}
}
}
}
}
},
"responses": {
"201": {
"description": "Note appended",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"ok": {
"type": "boolean"
},
"note": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"repo": {
"type": "string",
"description": "owner/name, lower-cased"
},
"number": {
"type": "integer"
},
"author": {
"type": "string",
"description": "GitHub login of the dashboard session that wrote it"
},
"text": {
"type": "string",
"maxLength": 2000
},
"created_at": {
"type": "string",
"format": "date-time"
},
"deleted_at": {
"type": "string",
"format": "date-time",
"description": "Set on the tombstone a DELETE returns; live notes omit it"
},
"deleted_by": {
"type": "string"
}
}
}
}
}
}
}
},
"400": {
"description": "Empty or over-long text, or a bad repo/number"
},
"401": {
"description": "GitHub user session required"
},
"403": {
"description": "Repository write permission required"
},
"503": {
"description": "GitHub client unavailable for the permission check"
}
}
}
},
"/api/notes/{id}": {
"delete": {
"tags": [
"Status"
],
"summary": "Delete (tombstone) a maintainer note",
"description": "Maintainer notes are the private, per-item notes maintainers leave each other on Activity Monitor rows. They live in the spoke's append-only /data/maintainer-notes.jsonl and are never written to or read from GitHub; every signed-in maintainer of the hive sees them and the scheduler injects an item's notes into the agent kick under `# Maintainer notes` (1 KiB cap). Adds and deletes are broadcast on the dashboard event stream as the `maintainer-notes` SSE event {seq, repo, number, count, action}. Only the note's author or a verified owner may delete; the store appends a tombstone rather than rewriting. Written to the audit log as maintainer_note_delete.",
"parameters": [
{
"name": "id",
"in": "path",
"required": true,
"schema": {
"type": "string"
}
}
],
"responses": {
"200": {
"description": "Note deleted",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"ok": {
"type": "boolean"
},
"note": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"repo": {
"type": "string",
"description": "owner/name, lower-cased"
},
"number": {
"type": "integer"
},
"author": {
"type": "string",
"description": "GitHub login of the dashboard session that wrote it"
},
"text": {
"type": "string",
"maxLength": 2000
},
"created_at": {
"type": "string",
"format": "date-time"
},
"deleted_at": {
"type": "string",
"format": "date-time",
"description": "Set on the tombstone a DELETE returns; live notes omit it"
},
"deleted_by": {
"type": "string"
}
}
}
}
}
}
}
},
"401": {
"description": "GitHub user session required"
},
"403": {
"description": "Not the note's author and not an owner"
},
"404": {
"description": "Unknown or already deleted note"
}
}
}
},
"/api/repos/{owner}/{repo}/items/{number}/decide-delegated": {
"post": {
"tags": [
Expand Down
4 changes: 4 additions & 0 deletions src/cmd/hive/main.go
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,7 @@ import (
"github.com/hivecommons/hive/pkg/ioscan"
"github.com/hivecommons/hive/pkg/jev"
"github.com/hivecommons/hive/pkg/knowledge"
"github.com/hivecommons/hive/pkg/maintainernotes"
"github.com/hivecommons/hive/pkg/matrix"
"github.com/hivecommons/hive/pkg/msteams"
"github.com/hivecommons/hive/pkg/notify"
Expand Down Expand Up @@ -3636,6 +3637,9 @@ func (b *boot) bootSupervision() {
contributorClaimOverrideLookup(contributorClaimGuard.Load, claimsInflightLookup(b.issueClaims, b.cfg.Project.Org)),
verifyOnceLookup(b.ctx, b.cfg.Project.Org, b.issueClaims, func() *github.Client { return b.ghClient }, b.logger),
claimEscalationLookup(b.ctx, b.cfg, b.issueClaims, func() *github.Client { return b.ghClient }, b.logger)))
// Dashboard maintainer notes on a listed item ride its kick as private
// context (pkg/scheduler/kick_maintainer_notes.go).
b.sched.SetMaintainerNotesLookup(maintainernotes.Default().List)
// #9584: close answered question issues unless the author objects (default off).
b.questionAutoclose.Store(wireQuestionAutoclose(b.ctx, b.cfg, b.sched, func() *github.Client { return b.ghClient }, b.logger))
// The pr-request watcher's PR-opened hook (Linear session narration, the
Expand Down
Loading
Loading