Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

v0.60.733.0 release (#9508)

Garry Tan6ce7195b44a0
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index a0a5be4ee5..e3d875e130 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"description": "Personal knowledge brain for your coding agent — hybrid search, synthesis, graph traversal, and durable cross-session memory over Postgres/PGLite with pgvector, plus a curated brain-first skill set.",
"author": {
"name": "Garry Tan",
diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json
index a51e1c16b0..40db1ada2d 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"description": "Personal knowledge brain for your coding agent — hybrid search, synthesis, graph traversal, and durable cross-session memory over Postgres/PGLite with pgvector, plus a curated brain-first skill set.",
"author": {
"name": "Garry Tan",
diff --git a/BOOTSTRAP_FOR_AGENTS.md b/BOOTSTRAP_FOR_AGENTS.md
index 1bc000a281..2edf63c943 100644
--- a/BOOTSTRAP_FOR_AGENTS.md
+++ b/BOOTSTRAP_FOR_AGENTS.md
@@ -1,4 +1,4 @@
-<!-- gbrain-runbook-stamp: 0.60.732.0 -->
+<!-- gbrain-runbook-stamp: 0.60.733.0 -->
<!-- This stamp must equal the VERSION file at every release; CI enforces it
(scripts/check-bootstrap-tag.sh). `gbrain bootstrap status` compares it to
the installed binary and warns on skew. -->
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 17030f5954..8763100c81 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,107 @@ credits are retained; no result has been reassigned to another provider. Origina
identifiers and attribution are available in the pre-removal Git revision
`6040075c6cb95be5881cc2e1b76ef7d71f4e5d29` (retained on 2026-09-23).
+## [0.60.733.0] - 2026-11-16
+
+**`gbrain transcripts archive` no longer has a day page refused by the write gate over its name, and a run exits 1 exactly when its `errors` list is not empty.**
+
+### Fixed
+- Day page names always pass the write gate. A cron job name cut at 24 characters no longer ends in a hyphen, and a label's repeated hyphens fold into one and its leading or trailing hyphen drops.
+- Every day a run fails to write is listed in the run's `errors` (in `--json`) with its `day` and `code`, and a shared brain with no owner lists the `archive_owner_unset` hold there too. `run` and `backfill` exit 1 exactly when that list is not empty, and 0 otherwise.
+- `--dry-run` reports `write_mode: coordinator` when the real run would write through the write coordinator, even before the archive source exists.
+- Days recorded by `gbrain transcripts archive adopt-legacy` are still skipped after the brain turns shared and the archive moves to its owner-only source.
+
+**The conversation archive reads OpenClaw's Gateway in far fewer process starts, and `gbrain transcripts archive status` no longer reads any session.**
+
+### Changed
+- The OpenClaw Gateway reader asks `chat.history` for pages of up to 1,000 messages within a 4 MiB budget, and reads up to 4 sessions at once. Each `openclaw gateway call` is its own process, so on a test install with 350 sessions a read went from 162 process starts and 164 s to 52 starts and 16 s. A Gateway older than 2026.10 that refuses the byte budget is asked again without it. Pages of one session stay in order, conversations keep their `sessions.list` order, and a failed session still fails the whole read before any day is written.
+- `gbrain transcripts archive status` and `gbrain doctor --only transcript_archive_freshness` report what the last archive run read for each reader (conversations, newest session day, time and any error) instead of running the readers. They start no `openclaw` process and parse no session file. A reader no run has read yet says so. Each real run records this in `transcripts.archive.last_read.<source>`; a dry run records nothing.
+
+### Fixed
+- Doctor warns when no archive run has read a reader successfully within `transcripts.archive.stale_days`, for example when maintenance passes keep stopping at their deadline before that reader, and suggests `gbrain transcripts archive run`.
+
+**A keyword search that timed out on a cold Postgres cache comes back within about a minute instead of ten.**
+
+### Fixed
+- After hybrid search's keyword statement hits the keyword statement timeout, `gbrain serve` and MCP sessions still skip that exact statement (`keyword_arm_failed: skipped_after_timeout`), and now also re-run it once in the background 30 seconds later, then after 60, 120 and so on seconds while it keeps failing, never past `search.keyword_timeout_negative_cache_seconds` (default 600, unchanged). The first re-run that answers ends the skip. A re-run uses the same statement, scope and bound, starts only when the pool has no waiting query and keeps a connection free for other queries, runs one at a time per brain, throws its rows away, writes no timeout counter row and is not recorded as a search. Before, one timeout on a cold cache left every identical search keyword-less for ten minutes even after the cache had warmed (#7082).
+
+<!-- behavior-change: keyword_skip_rerun_7082 -->
+
+**A stuck shared-skills migration is reported as owed work everywhere, with a read-only first step, instead of being called history.**
+
+### Fixed
+- A migration that stopped three or more runs in a row on a source conflict and still owes host work (v0.53.0 today) is no longer called "history, not outstanding work" because a newer migration completed. `gbrain apply-migrations --list`, the notice on other commands and `gbrain serve` startup, and `gbrain doctor` (a warning) now say the same thing: the work is still owed, it does not clear without a person, and the first step is `gbrain apply-migrations --migration 0.53.0 --dry-run --json`, which lists each source's conflict and changes nothing. They give the order that works: review each conflict, clear the wedge with `gbrain apply-migrations --force-retry 0.53.0`, then run the command the inspect output names for that source, or `gbrain apply-migrations --yes`. That inspect command no longer refuses a wedged version as "not registered", and running a wedged migration by name (for example the accept command a conflict message names) still exits 2 but says it is wedged and names those steps. Nothing runs the migration again by itself, and no exit status changes.
+
+<!-- behavior-change: migration_host_work_owed -->
+
+**`bun run verify` now fails when a schema migration would take every page it touches out of search until `gbrain projections drain` rebuilds them, unless the migration is listed with the reason search keeps answering (#9192).**
+
+### For contributors
+- `bun run check:migration-projection`, part of `bun run verify`, fails on a migration whose SQL, or whose handler's own source, updates a page column the page revision trigger watches (`UPDATE pages ... SET` or an `INSERT INTO pages ... DO UPDATE SET` upsert) or writes `tags`. The dollar-quoted body of a `CREATE FUNCTION` or `CREATE PROCEDURE` is skipped; a `DO` block is read.
+- A migration that has to do this goes in `scripts/migration-projection-baseline.tsv` with the reason search keeps answering, or why it cannot. v153 and v189 are listed. A listed migration that no longer matches fails as stale.
+- The guard cannot see a handler that changes pages through helpers or functions defined elsewhere, SQL assembled at run time, or writes made by a database function the migration calls. Review those by hand.
+
+**`gbrain git commit-push` works on a checkout with a very large index, no longer commits a file that still has merge conflicts, and OpenClaw skill setup no longer fails on a busy machine.**
+
+### Fixed
+- `gbrain git commit-push` read each git command's output with Node's default 1 MiB limit, so on a large checkout (one report had about 385,000 tracked files) naming a folder killed git and the run failed with `git_unavailable` "git ls-files -v failed: exit -1". It now reads git's whole output, so the commit goes through. A git command stopped before it finishes (its time limit, or a signal such as the out-of-memory killer) now fails with `git_command_stopped` and its reason, still exit 1, instead of `git_unavailable`, and its partial output is never used, so a cut-off listing can no longer pick the wrong files to stage or restore. A push, fetch or remote listing stopped after the local commit still reports `push_unconfirmed` (exit 4), and a write-through file whose commit was stopped stays in the pending ledger for the next retry.
+- `gbrain git commit-push` refuses a named file that still has unresolved merge conflicts in the index (for example after a merge, rebase or stash pop that stopped on a conflict) with `commit_paths_unmerged`, before it stages anything. It used to commit the file, conflict markers included, as if it were resolved. Nothing is staged or committed, and the message says how to resolve the file first. Every gbrain write that commits named files goes through the same check.
+- `gbrain setup openclaw` checked its installed skill plugin by resolving one turn against the live per-turn deadline of 50 ms, so on a loaded or slow machine the check timed out and setup failed with `skill_resolver_selftest_failed`. The check now gives that one turn 10 seconds, because it tests that a turn resolves, not how fast. Live turns keep the 50 ms deadline.
+
+<!-- behavior-change: commit_paths_unmerged -->
+<!-- behavior-change: git_large_index_listing -->
+
+**After an upgrade from before v0.51, `gbrain projections drain` rebuilds the pages that are out of search first, and on Postgres it rebuilds 4 pages at once by default, so every page answers search much sooner.**
+
+### Fixed
+- The search-index rebuild that an upgrade from before v0.51 starts used to work through pages in queue order, so pages with a facts fence could wait hours behind pages that were still answering from their old index. `gbrain projections drain` now rebuilds the pages that are out of search first, then seals images, then rebuilds the pages still answering from their pre-upgrade index. `--dry-run` lists rows in the same order. A follow-up to #9192.
+- On Postgres the drain rebuilds several pages at once, each on its own pooled connection: 4 by default, or fewer when the pool is small, and `--concurrency N` goes up to the pool size less 2. On a 50,000-page test brain with 30,000 fenced pages behind an 18 ms round trip, every page was searchable after about 86 minutes at the default. PGLite, `gbrain serve` on PGLite and the drain inside `gbrain migrate --to` still rebuild one page at a time.
+- A refused or dropped extra connection lowers the width by one and the drain carries on; stderr names the new width. It never fails the drain.
+- The upgrade's `[153]` line gives the rebuild time at the default width, names the faster `--concurrency` command with its time, and counts only the Markdown and code pages the drain rebuilds, not images.
+
+**The check that runs before every search stays fast while a large brain's pages wait to be rebuilt after an upgrade from before v0.51.**
+
+### Fixed
+- After an upgrade from before v0.51, pages still answering from their old index were walked one by one by the readiness check that runs before every search, so the check cost 21 ms on a test brain with 20,000 such pages and 126 to 149 ms with 200,000. A new partial index (migration v317) holds only the pages that are out of search, so the check now takes about 2 ms and the index is empty once the rebuild finishes. On Postgres the index builds without blocking writes; nothing is rewritten. Follow-up to #9472 (#9192).
+
+**`gbrain doctor` checks for facts left behind by purged pages in about a second per million facts, instead of timing out on a large brain.** The `purged_page_facts` check used to run its exclusion tests (a withdrawal lookup that fingerprints each claim, plus the superseded and open-loop checks) on every active fact before asking whether the fact's page was gone, so on a brain with a few million facts it ran past its 15-second budget and reported nothing. It now finds the facts whose page is gone first and runs those tests only on them. It counts exactly what it counted before, and `gbrain repair purged-page-facts` is unchanged.
+
+### Fixed
+
+- Doctor `purged_page_facts`: on a generated brain with 1,000,000 active facts and nothing to report, the check took 6.7 to 7.0 s on Postgres and 24 to 26 s on PGLite, and now takes about 1.0 s on both.
+
+**A release's list of changes shows each change's headline alone, even when its changelog entry continues on the headline's line.**
+
+### Fixed
+- `scripts/changelog-entry.sh --pr-list` cuts each fragment's first bold line at its closing `**`. Before, a fragment whose body text followed the headline on the same line put that whole paragraph, with a stray `**`, into the release notes.
+
+### For contributors
+- `test/release-workflow.test.ts` covers a fragment with body text after its headline.
+
+**Three fixes from outside bug reports: retired atoms keep their trust tier, a provider answer that cannot be parsed is no longer retried, and doctor stops recommending a sync that refuses a source.**
+
+### Fixed
+- An atom a re-extraction retires keeps the trust tier and write origin its extraction gave it, and comes back at that tier when a later extraction produces it again. It used to be stored as `unknown` with no origin, and a revived atom stayed `unknown`. Every derived retirement (chronicle events, synthesis outputs, `gbrain repair stale-atoms`) now stamps its pages this way. Reported and first fixed by @howardpark (#9456).
+- A model provider that answers with a success status and a body that is not one JSON document now fails with the non-retryable code `provider_response_unparseable`. A facts job that hits it ends on its first attempt instead of paying for the same failing call again, `gbrain facts retry-dead` leaves it alone, and its recorded error names the parse failure without keeping any response text. Reported by @haumanto and first fixed by @Masashi-Ono0611 (#9466).
+- `gbrain doctor`'s `sync_freshness` no longer fails a source whose folder sits inside gbrain's own content directory, and no longer tells you to run `gbrain sync` for it, which refuses such a source with `sync_not_applicable`. It counts the source as a content directory and names `gbrain import <dir> --source <id>` instead. Reported by @railsloes and first fixed by @Masashi-Ono0611 (#9471).
+
+<!-- behavior-change: atom_retirement_keeps_tier_9456 -->
+<!-- behavior-change: provider_response_unparseable_9466 -->
+<!-- behavior-change: sync_freshness_content_directory_9471 -->
+
+**The daily stable check sees merged important fixes again, and stops with a clear error if it ever loses access to pull requests.**
+
+### Fixed
+- The daily stable check's GitHub token can read pull requests again. A recent permissions change had left it unable to see any pull request, so the search for merged `stable:important` fixes came back empty and the check reported nothing to promote.
+- Each run now logs how many labelled pull requests the search found. If the search sees no merged pull request at all, the check stops red and names the missing `pull-requests: read` permission instead of quietly reporting nothing.
+
+**`gbrain upgrade` and the stable release notes now start with a short summary of the behaviour changes since the version you had.**
+
+### Added
+- Once the new version is installed, `gbrain upgrade` (through `gbrain post-upgrade`) prints the summary before its migrations run: the changes that need you first, then changed defaults, then a count of fixes and additions, and a pointer to `gbrain doctor --only behavior_changes` for the full text. Each change shows its first sentence. Under `--json` the summary goes to stderr with the other human lines, so the JSON document on stdout is unchanged.
+- When stable moves, its GitHub release notes open with the same summary for the range since the previous stable release, above the changelog entries. A summary too long for the page by itself is left out, so the notes always fit.
+- Rows written before `kind:` existed are counted as not classified yet. The generated behaviour-change table now carries each row's `kind`, so new rows land in the right group.
+
## [0.60.732.0] - 2026-11-16
**Every pull request is now checked against stable's promise: removing a command, flag, MCP tool or parameter, config key or exit code needs a deprecation record whose 14-day notice has passed.**
diff --git a/VERSION b/VERSION
index 2a8ef10d65..18acb48e59 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.60.732.0
+0.60.733.0
diff --git a/changelog.d/capy-archive-slug-exit-fix.md b/changelog.d/capy-archive-slug-exit-fix.md
deleted file mode 100644
index 176aa7fb82..0000000000
--- a/changelog.d/capy-archive-slug-exit-fix.md
+++ /dev/null
@@ -1,7 +0,0 @@
-**`gbrain transcripts archive` no longer has a day page refused by the write gate over its name, and a run exits 1 exactly when its `errors` list is not empty.**
-
-### Fixed
-- Day page names always pass the write gate. A cron job name cut at 24 characters no longer ends in a hyphen, and a label's repeated hyphens fold into one and its leading or trailing hyphen drops.
-- Every day a run fails to write is listed in the run's `errors` (in `--json`) with its `day` and `code`, and a shared brain with no owner lists the `archive_owner_unset` hold there too. `run` and `backfill` exit 1 exactly when that list is not empty, and 0 otherwise.
-- `--dry-run` reports `write_mode: coordinator` when the real run would write through the write coordinator, even before the archive source exists.
-- Days recorded by `gbrain transcripts archive adopt-legacy` are still skipped after the brain turns shared and the archive moves to its owner-only source.
diff --git a/changelog.d/capy-conversation-archive-reads.md b/changelog.d/capy-conversation-archive-reads.md
deleted file mode 100644
index 5ac9ebc881..0000000000
--- a/changelog.d/capy-conversation-archive-reads.md
+++ /dev/null
@@ -1,8 +0,0 @@
-**The conversation archive reads OpenClaw's Gateway in far fewer process starts, and `gbrain transcripts archive status` no longer reads any session.**
-
-### Changed
-- The OpenClaw Gateway reader asks `chat.history` for pages of up to 1,000 messages within a 4 MiB budget, and reads up to 4 sessions at once. Each `openclaw gateway call` is its own process, so on a test install with 350 sessions a read went from 162 process starts and 164 s to 52 starts and 16 s. A Gateway older than 2026.10 that refuses the byte budget is asked again without it. Pages of one session stay in order, conversations keep their `sessions.list` order, and a failed session still fails the whole read before any day is written.
-- `gbrain transcripts archive status` and `gbrain doctor --only transcript_archive_freshness` report what the last archive run read for each reader (conversations, newest session day, time and any error) instead of running the readers. They start no `openclaw` process and parse no session file. A reader no run has read yet says so. Each real run records this in `transcripts.archive.last_read.<source>`; a dry run records nothing.
-
-### Fixed
-- Doctor warns when no archive run has read a reader successfully within `transcripts.archive.stale_days`, for example when maintenance passes keep stopping at their deadline before that reader, and suggests `gbrain transcripts archive run`.
diff --git a/changelog.d/capy-keyword-skip-rerun.md b/changelog.d/capy-keyword-skip-rerun.md
deleted file mode 100644
index e0b8be0606..0000000000
--- a/changelog.d/capy-keyword-skip-rerun.md
+++ /dev/null
@@ -1,6 +0,0 @@
-**A keyword search that timed out on a cold Postgres cache comes back within about a minute instead of ten.**
-
-### Fixed
-- After hybrid search's keyword statement hits the keyword statement timeout, `gbrain serve` and MCP sessions still skip that exact statement (`keyword_arm_failed: skipped_after_timeout`), and now also re-run it once in the background 30 seconds later, then after 60, 120 and so on seconds while it keeps failing, never past `search.keyword_timeout_negative_cache_seconds` (default 600, unchanged). The first re-run that answers ends the skip. A re-run uses the same statement, scope and bound, starts only when the pool has no waiting query and keeps a connection free for other queries, runs one at a time per brain, throws its rows away, writes no timeout counter row and is not recorded as a search. Before, one timeout on a cold cache left every identical search keyword-less for ten minutes even after the cache had warmed (#7082).
-
-<!-- behavior-change: keyword_skip_rerun_7082 -->
diff --git a/changelog.d/capy-migration-host-work-owed.md b/changelog.d/capy-migration-host-work-owed.md
deleted file mode 100644
index 49670de561..0000000000
--- a/changelog.d/capy-migration-host-work-owed.md
+++ /dev/null
@@ -1,6 +0,0 @@
-**A stuck shared-skills migration is reported as owed work everywhere, with a read-only first step, instead of being called history.**
-
-### Fixed
-- A migration that stopped three or more runs in a row on a source conflict and still owes host work (v0.53.0 today) is no longer called "history, not outstanding work" because a newer migration completed. `gbrain apply-migrations --list`, the notice on other commands and `gbrain serve` startup, and `gbrain doctor` (a warning) now say the same thing: the work is still owed, it does not clear without a person, and the first step is `gbrain apply-migrations --migration 0.53.0 --dry-run --json`, which lists each source's conflict and changes nothing. They give the order that works: review each conflict, clear the wedge with `gbrain apply-migrations --force-retry 0.53.0`, then run the command the inspect output names for that source, or `gbrain apply-migrations --yes`. That inspect command no longer refuses a wedged version as "not registered", and running a wedged migration by name (for example the accept command a conflict message names) still exits 2 but says it is wedged and names those steps. Nothing runs the migration again by itself, and no exit status changes.
-
-<!-- behavior-change: migration_host_work_owed -->
diff --git a/changelog.d/capy-migration-projection-guard-9192.md b/changelog.d/capy-migration-projection-guard-9192.md
deleted file mode 100644
index 90c1df99e6..0000000000
--- a/changelog.d/capy-migration-projection-guard-9192.md
+++ /dev/null
@@ -1,6 +0,0 @@
-**`bun run verify` now fails when a schema migration would take every page it touches out of search until `gbrain projections drain` rebuilds them, unless the migration is listed with the reason search keeps answering (#9192).**
-
-### For contributors
-- `bun run check:migration-projection`, part of `bun run verify`, fails on a migration whose SQL, or whose handler's own source, updates a page column the page revision trigger watches (`UPDATE pages ... SET` or an `INSERT INTO pages ... DO UPDATE SET` upsert) or writes `tags`. The dollar-quoted body of a `CREATE FUNCTION` or `CREATE PROCEDURE` is skipped; a `DO` block is read.
-- A migration that has to do this goes in `scripts/migration-projection-baseline.tsv` with the reason search keeps answering, or why it cannot. v153 and v189 are listed. A listed migration that no longer matches fails as stale.
-- The guard cannot see a handler that changes pages through helpers or functions defined elsewhere, SQL assembled at run time, or writes made by a database function the migration calls. Review those by hand.
diff --git a/changelog.d/capy-openclaw-plugin-flake.md b/changelog.d/capy-openclaw-plugin-flake.md
deleted file mode 100644
index 04e03bd8c3..0000000000
--- a/changelog.d/capy-openclaw-plugin-flake.md
+++ /dev/null
@@ -1,9 +0,0 @@
-**`gbrain git commit-push` works on a checkout with a very large index, no longer commits a file that still has merge conflicts, and OpenClaw skill setup no longer fails on a busy machine.**
-
-### Fixed
-- `gbrain git commit-push` read each git command's output with Node's default 1 MiB limit, so on a large checkout (one report had about 385,000 tracked files) naming a folder killed git and the run failed with `git_unavailable` "git ls-files -v failed: exit -1". It now reads git's whole output, so the commit goes through. A git command stopped before it finishes (its time limit, or a signal such as the out-of-memory killer) now fails with `git_command_stopped` and its reason, still exit 1, instead of `git_unavailable`, and its partial output is never used, so a cut-off listing can no longer pick the wrong files to stage or restore. A push, fetch or remote listing stopped after the local commit still reports `push_unconfirmed` (exit 4), and a write-through file whose commit was stopped stays in the pending ledger for the next retry.
-- `gbrain git commit-push` refuses a named file that still has unresolved merge conflicts in the index (for example after a merge, rebase or stash pop that stopped on a conflict) with `commit_paths_unmerged`, before it stages anything. It used to commit the file, conflict markers included, as if it were resolved. Nothing is staged or committed, and the message says how to resolve the file first. Every gbrain write that commits named files goes through the same check.
-- `gbrain setup openclaw` checked its installed skill plugin by resolving one turn against the live per-turn deadline of 50 ms, so on a loaded or slow machine the check timed out and setup failed with `skill_resolver_selftest_failed`. The check now gives that one turn 10 seconds, because it tests that a turn resolves, not how fast. Live turns keep the 50 ms deadline.
-
-<!-- behavior-change: commit_paths_unmerged -->
-<!-- behavior-change: git_large_index_listing -->
diff --git a/changelog.d/capy-parallel-projection-drain-9192.md b/changelog.d/capy-parallel-projection-drain-9192.md
deleted file mode 100644
index 5bcca5b043..0000000000
--- a/changelog.d/capy-parallel-projection-drain-9192.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-important: regression
----
-**After an upgrade from before v0.51, `gbrain projections drain` rebuilds the pages that are out of search first, and on Postgres it rebuilds 4 pages at once by default, so every page answers search much sooner.**
-
-### Fixed
-- The search-index rebuild that an upgrade from before v0.51 starts used to work through pages in queue order, so pages with a facts fence could wait hours behind pages that were still answering from their old index. `gbrain projections drain` now rebuilds the pages that are out of search first, then seals images, then rebuilds the pages still answering from their pre-upgrade index. `--dry-run` lists rows in the same order. A follow-up to #9192.
-- On Postgres the drain rebuilds several pages at once, each on its own pooled connection: 4 by default, or fewer when the pool is small, and `--concurrency N` goes up to the pool size less 2. On a 50,000-page test brain with 30,000 fenced pages behind an 18 ms round trip, every page was searchable after about 86 minutes at the default. PGLite, `gbrain serve` on PGLite and the drain inside `gbrain migrate --to` still rebuild one page at a time.
-- A refused or dropped extra connection lowers the width by one and the drain carries on; stderr names the new width. It never fails the drain.
-- The upgrade's `[153]` line gives the rebuild time at the default width, names the faster `--concurrency` command with its time, and counts only the Markdown and code pages the drain rebuilds, not images.
diff --git a/changelog.d/capy-projection-waiting-index-9192.md b/changelog.d/capy-projection-waiting-index-9192.md
deleted file mode 100644
index 64245ea87b..0000000000
--- a/changelog.d/capy-projection-waiting-index-9192.md
+++ /dev/null
@@ -1,4 +0,0 @@
-**The check that runs before every search stays fast while a large brain's pages wait to be rebuilt after an upgrade from before v0.51.**
-
-### Fixed
-- After an upgrade from before v0.51, pages still answering from their old index were walked one by one by the readiness check that runs before every search, so the check cost 21 ms on a test brain with 20,000 such pages and 126 to 149 ms with 200,000. A new partial index (migration v317) holds only the pages that are out of search, so the check now takes about 2 ms and the index is empty once the rebuild finishes. On Postgres the index builds without blocking writes; nothing is rewritten. Follow-up to #9472 (#9192).
diff --git a/changelog.d/capy-purged-page-facts-doctor-fast.md b/changelog.d/capy-purged-page-facts-doctor-fast.md
deleted file mode 100644
index 78bb52f120..0000000000
--- a/changelog.d/capy-purged-page-facts-doctor-fast.md
+++ /dev/null
@@ -1,5 +0,0 @@
-**`gbrain doctor` checks for facts left behind by purged pages in about a second per million facts, instead of timing out on a large brain.** The `purged_page_facts` check used to run its exclusion tests (a withdrawal lookup that fingerprints each claim, plus the superseded and open-loop checks) on every active fact before asking whether the fact's page was gone, so on a brain with a few million facts it ran past its 15-second budget and reported nothing. It now finds the facts whose page is gone first and runs those tests only on them. It counts exactly what it counted before, and `gbrain repair purged-page-facts` is unchanged.
-
-### Fixed
-
-- Doctor `purged_page_facts`: on a generated brain with 1,000,000 active facts and nothing to report, the check took 6.7 to 7.0 s on Postgres and 24 to 26 s on PGLite, and now takes about 1.0 s on both.
diff --git a/changelog.d/capy-release-notes-headline-cut.md b/changelog.d/capy-release-notes-headline-cut.md
deleted file mode 100644
index 32e6263843..0000000000
--- a/changelog.d/capy-release-notes-headline-cut.md
+++ /dev/null
@@ -1,7 +0,0 @@
-**A release's list of changes shows each change's headline alone, even when its changelog entry continues on the headline's line.**
-
-### Fixed
-- `scripts/changelog-entry.sh --pr-list` cuts each fragment's first bold line at its closing `**`. Before, a fragment whose body text followed the headline on the same line put that whole paragraph, with a stray `**`, into the release notes.
-
-### For contributors
-- `test/release-workflow.test.ts` covers a fragment with body text after its headline.
diff --git a/changelog.d/capy-small-fix-wave-4.md b/changelog.d/capy-small-fix-wave-4.md
deleted file mode 100644
index 6593f8c2f1..0000000000
--- a/changelog.d/capy-small-fix-wave-4.md
+++ /dev/null
@@ -1,10 +0,0 @@
-**Three fixes from outside bug reports: retired atoms keep their trust tier, a provider answer that cannot be parsed is no longer retried, and doctor stops recommending a sync that refuses a source.**
-
-### Fixed
-- An atom a re-extraction retires keeps the trust tier and write origin its extraction gave it, and comes back at that tier when a later extraction produces it again. It used to be stored as `unknown` with no origin, and a revived atom stayed `unknown`. Every derived retirement (chronicle events, synthesis outputs, `gbrain repair stale-atoms`) now stamps its pages this way. Reported and first fixed by @howardpark (#9456).
-- A model provider that answers with a success status and a body that is not one JSON document now fails with the non-retryable code `provider_response_unparseable`. A facts job that hits it ends on its first attempt instead of paying for the same failing call again, `gbrain facts retry-dead` leaves it alone, and its recorded error names the parse failure without keeping any response text. Reported by @haumanto and first fixed by @Masashi-Ono0611 (#9466).
-- `gbrain doctor`'s `sync_freshness` no longer fails a source whose folder sits inside gbrain's own content directory, and no longer tells you to run `gbrain sync` for it, which refuses such a source with `sync_not_applicable`. It counts the source as a content directory and names `gbrain import <dir> --source <id>` instead. Reported by @railsloes and first fixed by @Masashi-Ono0611 (#9471).
-
-<!-- behavior-change: atom_retirement_keeps_tier_9456 -->
-<!-- behavior-change: provider_response_unparseable_9466 -->
-<!-- behavior-change: sync_freshness_content_directory_9471 -->
diff --git a/changelog.d/capy-stable-daily-pr-search.md b/changelog.d/capy-stable-daily-pr-search.md
deleted file mode 100644
index dee3568987..0000000000
--- a/changelog.d/capy-stable-daily-pr-search.md
+++ /dev/null
@@ -1,5 +0,0 @@
-**The daily stable check sees merged important fixes again, and stops with a clear error if it ever loses access to pull requests.**
-
-### Fixed
-- The daily stable check's GitHub token can read pull requests again. A recent permissions change had left it unable to see any pull request, so the search for merged `stable:important` fixes came back empty and the check reported nothing to promote.
-- Each run now logs how many labelled pull requests the search found. If the search sees no merged pull request at all, the check stops red and names the missing `pull-requests: read` permission instead of quietly reporting nothing.
diff --git a/changelog.d/capy-stable-notes-header.md b/changelog.d/capy-stable-notes-header.md
deleted file mode 100644
index 64749bedc8..0000000000
--- a/changelog.d/capy-stable-notes-header.md
+++ /dev/null
@@ -1,6 +0,0 @@
-**`gbrain upgrade` and the stable release notes now start with a short summary of the behaviour changes since the version you had.**
-
-### Added
-- Once the new version is installed, `gbrain upgrade` (through `gbrain post-upgrade`) prints the summary before its migrations run: the changes that need you first, then changed defaults, then a count of fixes and additions, and a pointer to `gbrain doctor --only behavior_changes` for the full text. Each change shows its first sentence. Under `--json` the summary goes to stderr with the other human lines, so the JSON document on stdout is unchanged.
-- When stable moves, its GitHub release notes open with the same summary for the range since the previous stable release, above the changelog entries. A summary too long for the page by itself is left out, so the notes always fit.
-- Rows written before `kind:` existed are counted as not classified yet. The generated behaviour-change table now carries each row's `kind`, so new rows land in the right group.
diff --git a/openclaw.plugin.json b/openclaw.plugin.json
index 36ef4807c4..7c843d745e 100644
--- a/openclaw.plugin.json
+++ b/openclaw.plugin.json
@@ -1,7 +1,7 @@
{
"id": "gbrain-context-engine",
"name": "gbrain",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"description": "Personal knowledge brain with Postgres + pgvector hybrid search",
"family": "bundle-plugin",
"kind": "context-engine",
diff --git a/package.json b/package.json
index 97d88e49f9..ca90cef6c9 100644
--- a/package.json
+++ b/package.json
@@ -262,7 +262,7 @@
"bun": ">=1.4.4"
},
"license": "MIT",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"overrides": {
"@aws-sdk/util-format-url": "3.972.9",
"@ai-sdk/provider-utils": "4.0.56",
diff --git a/plugin-variants/gbrain-coding/.claude-plugin/plugin.json b/plugin-variants/gbrain-coding/.claude-plugin/plugin.json
index 83e2c7fbc0..1a00ae9686 100644
--- a/plugin-variants/gbrain-coding/.claude-plugin/plugin.json
+++ b/plugin-variants/gbrain-coding/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-coding",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"description": "Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant. (persona variant of the gbrain plugin — 21 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-coding/.codex-plugin/plugin.json b/plugin-variants/gbrain-coding/.codex-plugin/plugin.json
index 96b881b91c..5f8d7cff1b 100644
--- a/plugin-variants/gbrain-coding/.codex-plugin/plugin.json
+++ b/plugin-variants/gbrain-coding/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-coding",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"description": "Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant. (persona variant of the gbrain plugin — 21 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-coding/README.md b/plugin-variants/gbrain-coding/README.md
index 6a6937d735..14acdd9525 100644
--- a/plugin-variants/gbrain-coding/README.md
+++ b/plugin-variants/gbrain-coding/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.732.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.733.0 -->
# gbrain-coding (generated persona variant — do not hand-edit)
Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant.
diff --git a/plugin-variants/gbrain-daily/.claude-plugin/plugin.json b/plugin-variants/gbrain-daily/.claude-plugin/plugin.json
index cf831f4b99..354d6a671a 100644
--- a/plugin-variants/gbrain-daily/.claude-plugin/plugin.json
+++ b/plugin-variants/gbrain-daily/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-daily",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"description": "Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant. (persona variant of the gbrain plugin — 20 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-daily/.codex-plugin/plugin.json b/plugin-variants/gbrain-daily/.codex-plugin/plugin.json
index a69aa0a1e2..a5359fae25 100644
--- a/plugin-variants/gbrain-daily/.codex-plugin/plugin.json
+++ b/plugin-variants/gbrain-daily/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain-daily",
- "version": "0.60.732.0",
+ "version": "0.60.733.0",
"description": "Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant. (persona variant of the gbrain plugin — 20 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-daily/README.md b/plugin-variants/gbrain-daily/README.md
index f9dbe45983..0a7f4065ea 100644
--- a/plugin-variants/gbrain-daily/README.md
+++ b/plugin-variants/gbrain-daily/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.732.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.733.0 -->
# gbrain-daily (generated persona variant — do not hand-edit)
Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant.
diff --git a/plugin/README.md b/plugin/README.md
index 6d94b47fd7..324650b7ed 100644
--- a/plugin/README.md
+++ b/plugin/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.732.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.733.0 -->
# gbrain plugin skill tree (generated — do not hand-edit)
This tree is the curated skill set for the gbrain Codex and Claude Code
diff --git a/src/core/behavior-changes.generated.ts b/src/core/behavior-changes.generated.ts
index 6f510b60b7..63e89a7f1b 100644
--- a/src/core/behavior-changes.generated.ts
+++ b/src/core/behavior-changes.generated.ts
@@ -91,6 +91,13 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin
{ since: '0.60.726.0', id: 'transcript_archive_default_gst2768', text: "On a personal brain the conversation archive is now on: the maintenance pass (the idle upkeep of an agent's gbrain serve, gbrain maintain --unattended or its schedule, and autopilot) writes one redacted page per conversation per local day from your Claude Code, Codex, OpenClaw, Hermes and Grok sessions, plus a day index, into the conversations source, then fills in older days a capped run at a time. To turn it off, run gbrain transcripts archive off (pages already written stay). A shared team brain is only offered the archive and stays off until its owner runs gbrain transcripts archive on. On a keyless brain nothing leaves this machine. With an embedding key, the archived text of new days is sent to that provider to be embedded, like any new page (unattended upkeep caps that at maintenance.embed_daily_usd; autopilot and a managed brain's write coordinator embed new pages as they arrive); older history is written keyword-only and its embedding waits until you see the price with gbrain embed --held --dry-run and approve it. No facts are extracted and no Dream synthesis runs on archive pages. gbrain doctor --only transcript_archive_freshness says whether the archive is keeping up." },
{ since: '0.60.731.0', id: 'stable_important_three_classes_gst2818', text: "The stable channel now moves within a day only for a security fix, a data-loss fix or a fix for a regression in a release that is already on stable. Everything else, a fix that only unblocks one setup included, waits for the weekly move; if you need such a fix sooner, install its release by tag (docs/STABILITY.md, \"Pinning a version\")." },
{ since: '0.60.732.0', id: 'owner_purge_tombstones_survive_9469', kind: 'fix', text: "A page the owner purged while a derived page kept it private now gets its purge records whichever later run removes it (an automatic expiry purge, or a run after a failed or deferred one), on repo brains and on brains without a repository, so a restore no longer brings it back. Restoring a backup now removes the same rows a live page purge removes (write requests, files, derived generation items and their effects), not only the page itself, and stops with purge_replay_incomplete, naming the purge it could not replay, instead of reporting success on a partial sweep. A new doctor warning, purge_mirror, says when recent purges are missing from this machine's purge mirror, so restoring an older backup would not replay them (#9469)." },
+ { since: '0.60.733.0', id: 'keyword_skip_rerun_7082', kind: 'fix', text: "On Postgres, a hybrid keyword statement that hit the keyword statement timeout is still skipped by later identical searches in the same serving process (`keyword_arm_failed: skipped_after_timeout`), but the skip no longer always lasts the whole `search.keyword_timeout_negative_cache_seconds` (default 600 s, unchanged, now the longest skip). The serve re-runs the statement once in the background 30 s after the timeout, then after 60 s, 120 s and so on while it keeps failing, with the same scope and the same bound, only when the pool has no waiting query and keeps a connection free for other queries, and one at a time per brain. Its rows are thrown away and it is not recorded as a search. The first re-run that answers ends the skip, so a timeout on a cold cache stops costing keyword results within about a minute of the cache warming. One-shot CLI commands are unchanged." },
+ { since: '0.60.733.0', id: 'migration_host_work_owed', kind: 'fix', text: "A migration that stopped three or more runs in a row on a conflict in one or more sources, and recorded that host work is still owed (today only v0.53.0, the shared-skills content migration), is no longer called history once a newer migration completes. gbrain apply-migrations --list, the notice other commands and gbrain serve print at startup, and gbrain doctor (as a warning) now all say the work is still owed and that it does not clear without a person, and they all name the same first step, gbrain apply-migrations --migration 0.53.0 --dry-run --json, which lists each source's conflict and changes nothing. They give the order that works: after the user reviews each conflict, gbrain apply-migrations --force-retry 0.53.0 clears the wedge, then the command the inspect output names for that source (or gbrain apply-migrations --yes) settles it. That inspect command used to refuse a wedged version as not registered; it now works. Running a wedged migration by name, for example the accept command a conflict message names, still exits 2 but now says the version is wedged and names those steps, instead of calling it not registered. Nothing runs the migration again by itself, and the exit status of apply-migrations, post-upgrade and upgrade does not change." },
+ { since: '0.60.733.0', id: 'commit_paths_unmerged', kind: 'fix', text: "gbrain git commit-push now refuses, before staging anything, when a file you name still has unresolved merge conflicts in the index, for example after a merge, rebase or stash pop that stopped on a conflict. It used to stage the file and commit it with its conflict markers as if it were resolved, and on an ordinary checkout push it. The refusal is commit_paths_unmerged (exit 1): nothing is staged or committed, the file stays unmerged, and the message names each file. Resolve each one (edit out the markers, or keep one side with git checkout --ours or --theirs -- <file>), mark it resolved with git add -- <file>, then rerun the commit. The same check covers every gbrain write that commits named files, such as lint --fix and connector writes." },
+ { since: '0.60.733.0', id: 'git_large_index_listing', kind: 'fix', text: "gbrain git commit-push no longer fails on a large checkout with git_unavailable \"git ls-files -v failed: exit -1\". Its git calls were limited to 1 MiB of output, so naming a folder whose index listing passed that (a few thousand tracked files with long names, more on a checkout of hundreds of thousands) killed git; they now read git's whole output. A git command that is stopped before it finishes (its time limit, or a signal such as the out-of-memory killer) now reports git_command_stopped with its reason (timeout or signal) instead of git_unavailable, still exit 1, and gbrain never uses its partial output as the answer. A push, fetch or remote listing stopped after the local commit still reports push_unconfirmed (exit 4)." },
+ { since: '0.60.733.0', id: 'atom_retirement_keeps_tier_9456', kind: 'fix', text: "An atom a re-extraction retires now keeps the trust tier and write origin its extraction gave it, and an atom a later extraction produces again comes back at that tier. The retirement used to store the atom as unknown with no origin, so a revived atom stayed unknown. The same holds for every page a derived writer retires (chronicle events, synthesis outputs, gbrain repair stale-atoms). Atoms retired before this release keep the tier they were stored with." },
+ { since: '0.60.733.0', id: 'provider_response_unparseable_9466', kind: 'fix', text: "A model provider that answers with a success status and a body that is not one JSON document (a route that streams when a request omits stream is the common cause) now fails with the non-retryable code provider_response_unparseable instead of a transient error. A facts job that hits it ends on its first attempt instead of retrying the same paid call, gbrain facts retry-dead does not resubmit it, and its recorded error reads cause=AIConfigError provider_response_unparseable. No response text is kept. Fix the route, for example with gbrain config set provider_chat_options.<provider>:<model> '{\"stream\": false}', then retry the job." },
+ { since: '0.60.733.0', id: 'sync_freshness_content_directory_9471', kind: 'fix', text: "gbrain doctor's sync_freshness no longer fails a source whose folder sits inside gbrain's own content directory (for example one added beside the default source with gbrain sources add) and no longer tells you to run gbrain sync for it, a command that refuses such a source with sync_not_applicable. It counts the source as a content directory where sync does not apply and names gbrain import <dir> --source <id> for adding files instead." },
];
/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */
@@ -183,4 +190,11 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {
transcript_archive_default_gst2768: '0.60.726.0',
stable_important_three_classes_gst2818: '0.60.731.0',
owner_purge_tombstones_survive_9469: '0.60.732.0',
+ keyword_skip_rerun_7082: '0.60.733.0',
+ migration_host_work_owed: '0.60.733.0',
+ commit_paths_unmerged: '0.60.733.0',
+ git_large_index_listing: '0.60.733.0',
+ atom_retirement_keeps_tier_9456: '0.60.733.0',
+ provider_response_unparseable_9466: '0.60.733.0',
+ sync_freshness_content_directory_9471: '0.60.733.0',
};
diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.md
index d7c6b59647..1eb6aabc7a 100644
--- a/templates/bootstrap/template-repo/README.md
+++ b/templates/bootstrap/template-repo/README.md
@@ -1,6 +1,6 @@
# gbrain agent workspace — template
-<!-- gbrain-template-stamp: 0.60.732.0 -->
+<!-- gbrain-template-stamp: 0.60.733.0 -->
This repository is the **"Use this template"** distribution artifact for a
[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same