Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

Release v0.60.713.0

garrytanf257352d93fa
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index d09a22235d..0314fd074d 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.712.0",
+ "version": "0.60.713.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 8e366faf54..3ab51e4694 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.712.0",
+ "version": "0.60.713.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 747e10fc1e..855416da7f 100644
--- a/BOOTSTRAP_FOR_AGENTS.md
+++ b/BOOTSTRAP_FOR_AGENTS.md
@@ -1,4 +1,4 @@
-<!-- gbrain-runbook-stamp: 0.60.712.0 -->
+<!-- gbrain-runbook-stamp: 0.60.713.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 b175771350..68af4a0bcf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,46 @@ 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.713.0] - 2026-11-13
+
+### A write killed in the middle no longer holds up its source
+
+**When a gbrain process dies while it holds the write at the head of a source's queue, the next write clears it at once instead of waiting.** A crash or `kill -9` used to leave that write's claim running with nobody renewing it, and every later write to the source waited behind it (`write_pending`) for the rest of its lease: 30 s while the write was preparing, about 6 minutes while it was publishing. On PGLite that wait happened on every such kill.
+
+- On a PGLite brain, the next gbrain process that opens the brain releases every claim written before it started and runs those writes again. The brain admits one process at a time, so their owners have exited. A process that cannot open the brain releases nothing.
+- On Postgres, a process killed on the same machine was already released at once; that is unchanged. A process on another machine, in another container or from before a reboot still waits out its lease, because gbrain cannot prove it is gone.
+- `gbrain sources writer status` now says so. A claim whose owner has provably exited reads `owner_exited: true`, `resumes_on_its_own: true` and `owner_live: false`, and its `next` is `claim_owner_exited` (nothing to do) instead of `claim_running` ("the owner is still renewing").
+- [docs/guides/troubleshooting.md](docs/guides/troubleshooting.md#stuck-write-head) lists how long each case takes and what status prints meanwhile.
+
+### A write receipt says when its Git commit landed
+
+**A receipt read after the write (`gbrain write-request <id>`, `get_write_request`, `list_write_requests`) now reports where Git is.** For a page on an ordinary (not `canonical: git`) checkout, `persistence.git_state` used to stay `queued` forever, even after the background Git effect committed the file, and no commit was named anywhere. It now comes from the Git effect: `committed` with the commit in `persistence.git_commit`, or `superseded`, `skipped`, `failed` or `retrying` with the cause in `persistence.git_reason`, and `queued` only while the effect is queued. Nothing stored is rewritten, so a Git effect from an earlier build, or one whose commit landed but whose push had to be retried, reads `committed` with no commit. Receipts of `canonical: git` sources are unchanged.
+
+Reported by @ethanbeard (#9227).
+
+<!-- behavior-change: stuck_head_released_9227 -->
+<!-- behavior-change: receipt_git_state_live_9227 -->
+
+### Label repairs no longer refuse pages over gbrain's own stamps
+
+**`gbrain repair visibility` and `gbrain repair private-labels` now label a page whose file differs from the database only by stamps gbrain keeps in the database, and they hold the pages they can't edit instead of failing the run (GST-2603).** A page retyped by a schema pack, a page with the `validate: false` grandfather stamp, or a page with a `legacy_type` retype record used to refuse every label repair, either as "cannot be made to the page's file line by line" or as `source_changed`. Enough of them in one window stopped the whole run as `item_failures_systemic`.
+- Those stamps no longer count as a difference. The page is labelled and its file still gains only the `visibility` line. A real difference (a date, the tags, the title, the body) still blocks the edit.
+- The preview checks every page in the window. A page whose file differs in a real key, or whose label line can't be edited as one line, is listed as held under `details.held` with the key that blocks it and its next step: `gbrain sources reconcile <id> <slug> --preview` for a file edited outside gbrain, or the line to fix. Held pages stay out of the preview hash and the approved set, so the rest of the window applies.
+- A page that starts refusing after the preview is declined with the new `label_edit_refused` code and nothing written. It never counts toward `item_failures_systemic`, the run exits 0, and the receipt names the pages that applied.
+- A brain without a repository writes the label to the database only, as before.
+- Labels and folder rules apply per source, so a page with the same slug in another source stayed readable after you labelled or ruled one copy, and a reader with no source filter found it by slug and in search. The previews of `gbrain repair visibility`, `gbrain repair private-labels --class restore` and `gbrain access rule add` / `import` now list those copies under `open_twins`: each same-slug page in another source that isn't private and that a caller outside the change could read, with their count and the command that covers them (the same repair or rule with `--source <other>`). The list is read-only and bounded, isn't part of the preview hash, and changes no copy for you.
+
+<!-- behavior-change: label_repairs_hold_refusals_gst2603 -->
+
+**Captured session files that mention a large entity page are extracted again instead of being stopped and later deleted.**
+
+### Fixed
+- The session sweep no longer fails every window whose facts name an entity page stored in segments (a page over about 1 MiB). Facts the extractor left without an entity and that mention such a page were checked against the page's whole body, which a segmented page refuses (`page_body_segmented`) after the model call; the window failed five times, stopped, and the session file was deleted at the un-ingested retention limit. The check now reads the page the way its writer does, so the window commits its facts onto the page's `## Facts` table, on a Git source and on a repo-less brain. Reported by @dvasselin (#9279).
+- A refusal that retrying cannot change now stops its window after the one paid attempt instead of five, retention keeps the session file it holds, and `gbrain doctor` (`memory_writeback`) counts these files as held. The first sweep after an upgrade retries each such window once, so a brain with files stopped by this bug recovers with no command.
+- A Gmail thread you purged while its import was still waiting to commit no longer leaves its open loops behind. `gbrain waiting` could keep listing the thread's subject and evidence quote after the purge; the sync now drops loops for threads it refused as purged in the same run when no page for them exists (#9011).
+
+<!-- behavior-change: corpus_segmented_entity_9279 -->
+
## [0.60.712.0] - 2026-11-13
### A page left behind when its file moved can be folded into the moved page
diff --git a/VERSION b/VERSION
index ab484bd3b0..7c461dc77b 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.60.712.0
+0.60.713.0
diff --git a/changelog.d/capy-gst-2572-stuck-head.md b/changelog.d/capy-gst-2572-stuck-head.md
deleted file mode 100644
index 1bf0424eee..0000000000
--- a/changelog.d/capy-gst-2572-stuck-head.md
+++ /dev/null
@@ -1,17 +0,0 @@
-### A write killed in the middle no longer holds up its source
-
-**When a gbrain process dies while it holds the write at the head of a source's queue, the next write clears it at once instead of waiting.** A crash or `kill -9` used to leave that write's claim running with nobody renewing it, and every later write to the source waited behind it (`write_pending`) for the rest of its lease: 30 s while the write was preparing, about 6 minutes while it was publishing. On PGLite that wait happened on every such kill.
-
-- On a PGLite brain, the next gbrain process that opens the brain releases every claim written before it started and runs those writes again. The brain admits one process at a time, so their owners have exited. A process that cannot open the brain releases nothing.
-- On Postgres, a process killed on the same machine was already released at once; that is unchanged. A process on another machine, in another container or from before a reboot still waits out its lease, because gbrain cannot prove it is gone.
-- `gbrain sources writer status` now says so. A claim whose owner has provably exited reads `owner_exited: true`, `resumes_on_its_own: true` and `owner_live: false`, and its `next` is `claim_owner_exited` (nothing to do) instead of `claim_running` ("the owner is still renewing").
-- [docs/guides/troubleshooting.md](docs/guides/troubleshooting.md#stuck-write-head) lists how long each case takes and what status prints meanwhile.
-
-### A write receipt says when its Git commit landed
-
-**A receipt read after the write (`gbrain write-request <id>`, `get_write_request`, `list_write_requests`) now reports where Git is.** For a page on an ordinary (not `canonical: git`) checkout, `persistence.git_state` used to stay `queued` forever, even after the background Git effect committed the file, and no commit was named anywhere. It now comes from the Git effect: `committed` with the commit in `persistence.git_commit`, or `superseded`, `skipped`, `failed` or `retrying` with the cause in `persistence.git_reason`, and `queued` only while the effect is queued. Nothing stored is rewritten, so a Git effect from an earlier build, or one whose commit landed but whose push had to be retried, reads `committed` with no commit. Receipts of `canonical: git` sources are unchanged.
-
-Reported by @ethanbeard (#9227).
-
-<!-- behavior-change: stuck_head_released_9227 -->
-<!-- behavior-change: receipt_git_state_live_9227 -->
diff --git a/changelog.d/capy-label-repair-derived-stamps.md b/changelog.d/capy-label-repair-derived-stamps.md
deleted file mode 100644
index 71af147def..0000000000
--- a/changelog.d/capy-label-repair-derived-stamps.md
+++ /dev/null
@@ -1,10 +0,0 @@
-### Label repairs no longer refuse pages over gbrain's own stamps
-
-**`gbrain repair visibility` and `gbrain repair private-labels` now label a page whose file differs from the database only by stamps gbrain keeps in the database, and they hold the pages they can't edit instead of failing the run (GST-2603).** A page retyped by a schema pack, a page with the `validate: false` grandfather stamp, or a page with a `legacy_type` retype record used to refuse every label repair, either as "cannot be made to the page's file line by line" or as `source_changed`. Enough of them in one window stopped the whole run as `item_failures_systemic`.
-- Those stamps no longer count as a difference. The page is labelled and its file still gains only the `visibility` line. A real difference (a date, the tags, the title, the body) still blocks the edit.
-- The preview checks every page in the window. A page whose file differs in a real key, or whose label line can't be edited as one line, is listed as held under `details.held` with the key that blocks it and its next step: `gbrain sources reconcile <id> <slug> --preview` for a file edited outside gbrain, or the line to fix. Held pages stay out of the preview hash and the approved set, so the rest of the window applies.
-- A page that starts refusing after the preview is declined with the new `label_edit_refused` code and nothing written. It never counts toward `item_failures_systemic`, the run exits 0, and the receipt names the pages that applied.
-- A brain without a repository writes the label to the database only, as before.
-- Labels and folder rules apply per source, so a page with the same slug in another source stayed readable after you labelled or ruled one copy, and a reader with no source filter found it by slug and in search. The previews of `gbrain repair visibility`, `gbrain repair private-labels --class restore` and `gbrain access rule add` / `import` now list those copies under `open_twins`: each same-slug page in another source that isn't private and that a caller outside the change could read, with their count and the command that covers them (the same repair or rule with `--source <other>`). The list is read-only and bounded, isn't part of the preview hash, and changes no copy for you.
-
-<!-- behavior-change: label_repairs_hold_refusals_gst2603 -->
diff --git a/changelog.d/capy-segmented-corpus-sweep.md b/changelog.d/capy-segmented-corpus-sweep.md
deleted file mode 100644
index d57b88bfde..0000000000
--- a/changelog.d/capy-segmented-corpus-sweep.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-important: data-loss
----
-**Captured session files that mention a large entity page are extracted again instead of being stopped and later deleted.**
-
-### Fixed
-- The session sweep no longer fails every window whose facts name an entity page stored in segments (a page over about 1 MiB). Facts the extractor left without an entity and that mention such a page were checked against the page's whole body, which a segmented page refuses (`page_body_segmented`) after the model call; the window failed five times, stopped, and the session file was deleted at the un-ingested retention limit. The check now reads the page the way its writer does, so the window commits its facts onto the page's `## Facts` table, on a Git source and on a repo-less brain. Reported by @dvasselin (#9279).
-- A refusal that retrying cannot change now stops its window after the one paid attempt instead of five, retention keeps the session file it holds, and `gbrain doctor` (`memory_writeback`) counts these files as held. The first sweep after an upgrade retries each such window once, so a brain with files stopped by this bug recovers with no command.
-- A Gmail thread you purged while its import was still waiting to commit no longer leaves its open loops behind. `gbrain waiting` could keep listing the thread's subject and evidence quote after the purge; the sync now drops loops for threads it refused as purged in the same run when no page for them exists (#9011).
-
-<!-- behavior-change: corpus_segmented_entity_9279 -->
diff --git a/openclaw.plugin.json b/openclaw.plugin.json
index 72f15c72b2..909481501b 100644
--- a/openclaw.plugin.json
+++ b/openclaw.plugin.json
@@ -1,7 +1,7 @@
{
"id": "gbrain-context-engine",
"name": "gbrain",
- "version": "0.60.712.0",
+ "version": "0.60.713.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 1aaeac3708..584c250d2e 100644
--- a/package.json
+++ b/package.json
@@ -258,7 +258,7 @@
"bun": ">=1.4.4"
},
"license": "MIT",
- "version": "0.60.712.0",
+ "version": "0.60.713.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 61abb5ed4e..645b5b6986 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.712.0",
+ "version": "0.60.713.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 9013dfc9fc..1fb346a678 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.712.0",
+ "version": "0.60.713.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 4a35beab6c..b9f1fbaf7e 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.712.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.713.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 618924e4af..18f14259ee 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.712.0",
+ "version": "0.60.713.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 06fe0ad5bc..4aec12866e 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.712.0",
+ "version": "0.60.713.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 f1350105f0..adad0dbbc4 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.712.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.713.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 58c83e59fd..379aa08296 100644
--- a/plugin/README.md
+++ b/plugin/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.712.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.713.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 7e575a213d..d06bc4a63c 100644
--- a/src/core/behavior-changes.generated.ts
+++ b/src/core/behavior-changes.generated.ts
@@ -45,6 +45,10 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin
{ since: '0.60.711.0', id: 'physical_root_moved_8625', text: "On a managed brain, a checkout moved to a new path (or whose parent folder was renamed) is now named: `gbrain sources add`, `gbrain sources set-path` and `gbrain sources writer claim` refuse with `recovery_required`, detail `physical_root_moved`, naming the recorded path, the worktree and the commands that bring it back, instead of a generic identity error (add, claim) or detail-less `source_checkout_missing` (set-path). Their `--dry-run` now refuses as the real run does: before, the add, claim and set-path dry runs of a moved checkout, the add and claim dry runs of a folder holding a copied ownership stamp, and the set-path dry run of a missing checkout exited 0. Nothing about ownership changed; the dry runs still write nothing." },
{ since: '0.60.712.0', id: 'moved_pages_fold_gst2584', text: "gbrain repair file-drift --held no longer offers a delete or a recreate for a page whose file moved while its deletion was held: it lists the page as moved_to <slug> with the new gbrain repair moved-pages --source <id> --slug <old-slug> fold command, and --prefer file skips it. A file that names the page type gbrain-base 1.0.0 gave its path, equal to the type copy an older gbrain stored in the page's frontmatter, now keeps the type a later schema pack gave the page on import, and the import records the rename as a legacy_type retype stamp; before, the next edit read the old type back into the page." },
{ since: '0.60.712.0', id: 'folder_holding_page_gst2492', text: "On a source whose pages are canonical in Git (`canonical: git`), a fact for an entity with no page under a folder access rule is no longer kept in the database only: it is held on the holding page of the entity's folder (`partners/memory/unattributed` for `partners/acme-example`), in Git (or database-only where the folder is) with exactly the readers the entity's page would have. The reply names that `page`. `gbrain access rule add` previews the held facts a new rule covers (`held_facts_moving`) and its apply moves them off their holding page (`held_facts`), as do `gbrain access apply`, `gbrain access resume` and a sync that applies a rule from Git; the moved rows and those entities' struck rows also leave that page's saved versions in the database (`held_versions_editing`, `held_versions_edited`), and Git history is not rewritten. A saved version stored in segments is not edited: the preview names how many (`segmented_versions_not_edited`) and the apply says `complete: false`. A move still pending is reported with its request id (`pending`, `HELD_FACT_PENDING`), not counted as moved. A held fact is now also hidden from a caller who cannot read its holding page, even under a rule with `covers_derived: false`. `gbrain repair facts-home` writes such facts to their folder's page and lists as `folder_restricted` only an exact page rule or unreadable rules. A `remember` for a page-less entity under an exact page rule now refuses `git_home_required` with a fix that creates the page, and one whose access rules this database role cannot read refuses `access_policy_pending`; both wrote the fact to the database before. An existing page whose slug ends in `/memory/unattributed` is now read as a holding page: a row with no `entity` cell becomes a fact with no entity, a row naming an entity in the page's own folder becomes that entity's held fact, and a row naming an entity of another folder is a fence problem. Non-strict sources and brains with no Git repository are unchanged." },
+ { since: '0.60.713.0', id: 'stuck_head_released_9227', text: "On a PGLite brain, the next gbrain process that opens the brain now releases at once every write claim an earlier, exited process left running and runs those writes again, instead of leaving later writes to the same source pending for the rest of the claim's lease (30 s, or about 6 minutes while publishing). `gbrain sources writer status` reports a claim whose owner has provably exited (that case on PGLite, a dead process on the same machine on Postgres) with `owner_exited: true`, `resumes_on_its_own: true`, `owner_live: false` and `next.code: claim_owner_exited`, where it said `claim_running`." },
+ { since: '0.60.713.0', id: 'receipt_git_state_live_9227', text: "A write receipt read after the write (`gbrain write-request`, `get_write_request`, `list_write_requests`) for a page on a checkout that is not `canonical: git` now takes `persistence.git_state` from the page's Git effect: `committed` with the commit in `persistence.git_commit`, or `superseded`, `skipped`, `failed` or `retrying` with `persistence.git_reason`, where it always said `queued`. Stored receipts are not rewritten; the stored `outcome` still says `queued`." },
+ { since: '0.60.713.0', id: 'label_repairs_hold_refusals_gst2603', text: "gbrain repair visibility and gbrain repair private-labels now ignore stamps gbrain keeps only in the database (a pack-renamed type, the validate: false grandfather stamp, a legacy_type retype record) when they edit a page's label line, so those pages are labelled. A page whose file still differs in a real key, or whose label line cannot be edited as one line, is held by the preview with the blocking key and its next step and is left out of the approved set. A page that starts refusing after the preview is declined with label_edit_refused, nothing is written for it, the run exits 0 and it no longer counts toward item_failures_systemic. Their previews, and those of gbrain access rule add and import, also list same-slug pages in other sources that the change leaves readable (open_twins), with their count and the command that covers them; nothing changes those pages for you." },
+ { since: '0.60.713.0', id: 'corpus_segmented_entity_9279', text: "Captured session files whose facts name a large entity page (one stored in segments, over about 1 MiB) are now extracted: facts inferred from a mention of that page were refused after the model call, so those files were retried five times and then stopped. The first sweep after this upgrade retries each file stopped that way once, at the cost of one model call per stopped window, with no command needed. From now on a refusal that retrying cannot change stops its window after one paid attempt instead of five, retention keeps the session file instead of deleting it at the un-ingested limit, and gbrain doctor (memory_writeback) counts these files as held. gbrain sweep --retry-failed --apply still retries them by hand." },
];
/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */
@@ -91,4 +95,8 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {
physical_root_moved_8625: '0.60.711.0',
moved_pages_fold_gst2584: '0.60.712.0',
folder_holding_page_gst2492: '0.60.712.0',
+ stuck_head_released_9227: '0.60.713.0',
+ receipt_git_state_live_9227: '0.60.713.0',
+ label_repairs_hold_refusals_gst2603: '0.60.713.0',
+ corpus_segmented_entity_9279: '0.60.713.0',
};
diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.md
index b15e41d9c9..38f73670b7 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.712.0 -->
+<!-- gbrain-template-stamp: 0.60.713.0 -->
This repository is the **"Use this template"** distribution artifact for a
[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same