Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

Release v0.60.719.0

garrytanc2dbc642da54
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 5ab6959492..0b01121bcf 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.718.0",
+ "version": "0.60.719.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 ec5d802c9f..3ccb8f068b 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.718.0",
+ "version": "0.60.719.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 f5b5e0079e..18d5545a5e 100644
--- a/BOOTSTRAP_FOR_AGENTS.md
+++ b/BOOTSTRAP_FOR_AGENTS.md
@@ -1,4 +1,4 @@
-<!-- gbrain-runbook-stamp: 0.60.718.0 -->
+<!-- gbrain-runbook-stamp: 0.60.719.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 933f0f956b..a01dfefb86 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,54 @@ 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.719.0] - 2026-11-14
+
+**A brain owner can now make member CLIs read-only: with `access.enforced_member_writes` set to `refuse`, every write under `GBRAIN_ENFORCED_MEMBER` refuses.**
+
+### Added
+- `gbrain config set access.enforced_member_writes refuse` makes enforced member mode refuse `put`, `link`, `unlink`, `tag`, `untag`, `timeline-add`, `remember`, `edit_page`, `append_page` and `git commit-push` with named paths, with exit 3 and reason `writes_off`. `refuse_pages` refuses the same page writes and leaves named-path `git commit-push` to its usual checks, for a host whose member turns still commit files. The refusal comes before any page, path or source lookup, so it reads the same for a new, readable or hidden target and names none. The key lives in the brain's database, so it works on a brain with no repository, and a member can't change it because `config` is refused under the mode. Unset or `checked` keeps today's checked writes; any other value, or a config read that fails, counts as `refuse`. Reads, a CLI without the variable, `git commit-push --pull` and `--dry-run`, `sync`, `sources refresh` and `write-request` are unchanged. See docs/guides/enforced-member.md#writes-off.
+
+**Upgrading from an older release (about v0.60.150 to v0.60.248) no longer ends in exit 1, and doctor no longer reports a stopped serve as a second running build.**
+
+### Fixed
+- `gbrain upgrade` run from an older release finishes with exit 0 again. Those releases load one more file from the new install into the old process after the swap, and that file pulled in code needing functions the old process didn't have, so the upgrade printed an `internal_error` and exited 1 even though the new binary and its migrations were in place. That file now loads nothing but the line it prints (GST-2688).
+- `gbrain doctor`'s `runtime_build_skew` check no longer counts a process that has already exited as a running build. An older serve stopped with SIGTERM can leave its heartbeat row looking fresh for up to 30 seconds; a row whose process the check can prove is gone (same machine boot, pid gone or reused) is now skipped, while a row it can't prove dead still counts (GST-2688).
+
+**On a source whose pages are canonical in Git, a fact the Google loops extraction saves for a person or company with no page is no longer thrown away when the database has a brief hiccup while gbrain prepares the write.**
+
+### Fixed
+
+- On a `canonical: git` source, a fact for an entity with no page is kept on a holding page (`memory/unattributed`, or its folder's holding page under a folder access rule) until the entity's page exists. Choosing that page takes one read of the access rules. If that read hit a passing database error while the write was being prepared (a cancelled statement, a stale cached plan, a lock or serialization conflict, a dropped connection, a pooler's client limit), gbrain treated it as "the access rules cannot be read" and refused the write for good with `access_policy_pending`. For the Google loops extraction, the only writer on that path, the commitment fact was dropped while the loop row stayed, so the open loop pointed at no fact.
+- Now that error is handed back to the write queue, which releases the write and prepares it again, the same way it already retries every other passing database error. The fact lands on the holding page with its entity, committed to Git, and the loop row points at it. A statement that keeps getting cancelled still stops after `persistence.max_transient_retries` tries and ends `write_interrupted` with nothing written.
+- Real refusals are unchanged. An exact page rule on the entity still refuses `git_home_required`, and an access state the database role really cannot read (for example permission denied on the access tables) still refuses `access_policy_pending`.
+- A hiccup on the same read earlier, while the loops job first hands the fact to gbrain, still loses that one fact as it did before. The loops job keeps the loop row and logs `fact projection failed`.
+- Facts dropped this way before the fix are not recovered by this change.
+- On the same kind of source, an owner's `gbrain trust release` of a held fact for an entity with no page used to report `released` while saving the fact only in the database, with no row in Git, whenever no holding page could carry it: an exact page rule on the entity, or access rules the database role could not read. Now the release refuses with nothing written and the fact stays held: `git_home_required` names the entity's page to create, and `access_policy_pending` asks you to retry. Creating that page does not unlock the release, because a page under its own rule counts as private for a release (`page_not_found`); drop the hold and remember the fact on the page instead. Facts released this way before the fix are not changed; `gbrain repair facts-home` lists them as `folder_restricted`. (GST-2676)
+
+**When a shallow checkout hides a folder's access-rule history, the first import now refuses with a code and the exact command to fix it, `gbrain access rule migrate` moves rules between git and the database, renamed pages keep their atom lineage, connection strings lose their password whatever the scheme, and a policy-only mirror no longer trips the git convergence check.** Community wave W-A1, second part: bug reports verified on master and fixed with our own code.
+
+### Fixed
+- **First access-rule import (GST-2638).** The first import of a source's access rules refused when it could not read their git history. It now tells a missing history apart from an unreadable one. An unreadable history refuses with the new code `access_policy_history_unreadable`, and the fix it names is `git -C <source root> fetch --unshallow` and then the same command again. A plain sync on a shallow checkout whose rules do have committed history still fails closed. `gbrain access rule migrate --to git|database` moves the rules from one store to the other, the preview shows when only the owner can read pending pages, and the command exits 1 when the result would be invalid.
+- **Policy-only mirrors (GST-2634).** `gbrain doctor`'s git_convergence check no longer flags a source whose mirror holds only access policy.
+- **Ingest refusals (#8982).** A refused `POST /ingest` now carries a code, a fix and a docs link.
+- **Renamed pages, config secrets and root metadata deletes (#8920).** When a later rename onto an old slug drops its alias, an atom is still judged by the private page its origin moved to. A concept is still judged as before: by its input atoms and their origins' rename aliases only. Config secret keys are redacted, and the password in a connection URL is removed for any scheme. Deleting a root metadata file publishes the change to the database only.
+
+<!-- behavior-change: access_first_import_history_gst2638 -->
+
+### Name the room on the CLI, and think answers and writes carry room marks too
+
+**`--room <list>` now works on every gbrain operation command, and `think`, `put_page` and `remember` answers are marked for the room like reads are.** A harness that runs gbrain as a command, or a person checking what a group chat could see, gets the same marks an MCP caller gets, and the agent writing into a room can tell which parts of a synthesized answer came from pages the room cannot read.
+
+- `gbrain <command> --room alice-example,group:team-a` prints exactly what the command prints without it. With `--json` every item carries `room_access` and the document carries `_meta.room` (a list becomes `{ results, _meta }`); without it stderr names what the room cannot read. The local CLI marks the brain owner's view, or the member `--as` names; with no owner set, every item is unknown and the notice says to run `gbrain access owner set`.
+- A trailing `--room` with no value is never dropped. The command runs, every item is marked unknown (`invalid`), the degraded stamp shows and it exits 0.
+- It works through a running `gbrain serve` that owns a PGLite brain (the owner marks the answer) and on a thin client (sent as `_meta.room`). A host or owner that predates room marks leaves every item unknown (`not_supported`).
+- A `think` answer is marked at the strictest class of everything its synthesis retrieved or was shown (the anchor and the graph pages its prompt names, each under its own source); an answer built partly from takes or a calibration profile, or with no recorded evidence, is unknown. `put_page` and `remember` mark the page or fact they wrote and are never stamped degraded for it, so a committed write never reads as one to retry.
+- The shipped access-policy and agent templates now say how an agent acts on its owner's own turn in a group chat (at the owner's scope, written for the room, with truly private material offered in a private chat and never a refusal; everyone else is answered at the group's level) and that a send the principal asks for in their own verified message goes out as asked, with no approval phrase or draft-first step. Existing installs keep their own files.
+- Guide: [docs/guides/rooms.md](docs/guides/rooms.md).
+
+<!-- behavior-change: room_cli_think_writes_gst2639 -->
+<!-- behavior-change: owner_turn_sends_templates_gst2656 -->
+
## [0.60.718.0] - 2026-11-14
**Three ways a commit could reach the remote past the push secret scan are closed, and the scan can no longer be skipped.** In a managed root that sits in a subfolder of its repository, a commit could change that root's own `.gbrain-scan-allow` (for example to allow every path) and be pushed along with the secret it hid; it is now held for review like one at the top level. A strict (`canonical: git`) source's commit is now trusted only when its files are exactly what gbrain wrote, so anything a Git clean filter added is scanned. Git replace refs can no longer slip files into a page-write commit the scan trusts. `commitAndPush` also lost its unscanned mode, so no caller and no push handed over from a busy publish lock can publish without the scan; it reads only the commits the remote lacks, fetching a missing remote-tracking branch first.
diff --git a/VERSION b/VERSION
index ac65e9db4b..f85f081794 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.60.718.0
+0.60.719.0
diff --git a/changelog.d/capy-enforced-member-writes-off.md b/changelog.d/capy-enforced-member-writes-off.md
deleted file mode 100644
index 2c1e1c8baa..0000000000
--- a/changelog.d/capy-enforced-member-writes-off.md
+++ /dev/null
@@ -1,4 +0,0 @@
-**A brain owner can now make member CLIs read-only: with `access.enforced_member_writes` set to `refuse`, every write under `GBRAIN_ENFORCED_MEMBER` refuses.**
-
-### Added
-- `gbrain config set access.enforced_member_writes refuse` makes enforced member mode refuse `put`, `link`, `unlink`, `tag`, `untag`, `timeline-add`, `remember`, `edit_page`, `append_page` and `git commit-push` with named paths, with exit 3 and reason `writes_off`. `refuse_pages` refuses the same page writes and leaves named-path `git commit-push` to its usual checks, for a host whose member turns still commit files. The refusal comes before any page, path or source lookup, so it reads the same for a new, readable or hidden target and names none. The key lives in the brain's database, so it works on a brain with no repository, and a member can't change it because `config` is refused under the mode. Unset or `checked` keeps today's checked writes; any other value, or a config read that fails, counts as `refuse`. Reads, a CLI without the variable, `git commit-push --pull` and `--dry-run`, `sync`, `sources refresh` and `write-request` are unchanged. See docs/guides/enforced-member.md#writes-off.
diff --git a/changelog.d/capy-gst-2688-old-updater-leaf.md b/changelog.d/capy-gst-2688-old-updater-leaf.md
deleted file mode 100644
index 8d42fa8637..0000000000
--- a/changelog.d/capy-gst-2688-old-updater-leaf.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-important: regression
----
-**Upgrading from an older release (about v0.60.150 to v0.60.248) no longer ends in exit 1, and doctor no longer reports a stopped serve as a second running build.**
-
-### Fixed
-- `gbrain upgrade` run from an older release finishes with exit 0 again. Those releases load one more file from the new install into the old process after the swap, and that file pulled in code needing functions the old process didn't have, so the upgrade printed an `internal_error` and exited 1 even though the new binary and its migrations were in place. That file now loads nothing but the line it prints (GST-2688).
-- `gbrain doctor`'s `runtime_build_skew` check no longer counts a process that has already exited as a running build. An older serve stopped with SIGTERM can leave its heartbeat row looking fresh for up to 30 seconds; a row whose process the check can prove is gone (same machine boot, pid gone or reused) is now skipped, while a row it can't prove dead still counts (GST-2688).
diff --git a/changelog.d/capy-holding-read-retry-gst2667.md b/changelog.d/capy-holding-read-retry-gst2667.md
deleted file mode 100644
index 1037778144..0000000000
--- a/changelog.d/capy-holding-read-retry-gst2667.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-important: data-loss
----
-
-**On a source whose pages are canonical in Git, a fact the Google loops extraction saves for a person or company with no page is no longer thrown away when the database has a brief hiccup while gbrain prepares the write.**
-
-### Fixed
-
-- On a `canonical: git` source, a fact for an entity with no page is kept on a holding page (`memory/unattributed`, or its folder's holding page under a folder access rule) until the entity's page exists. Choosing that page takes one read of the access rules. If that read hit a passing database error while the write was being prepared (a cancelled statement, a stale cached plan, a lock or serialization conflict, a dropped connection, a pooler's client limit), gbrain treated it as "the access rules cannot be read" and refused the write for good with `access_policy_pending`. For the Google loops extraction, the only writer on that path, the commitment fact was dropped while the loop row stayed, so the open loop pointed at no fact.
-- Now that error is handed back to the write queue, which releases the write and prepares it again, the same way it already retries every other passing database error. The fact lands on the holding page with its entity, committed to Git, and the loop row points at it. A statement that keeps getting cancelled still stops after `persistence.max_transient_retries` tries and ends `write_interrupted` with nothing written.
-- Real refusals are unchanged. An exact page rule on the entity still refuses `git_home_required`, and an access state the database role really cannot read (for example permission denied on the access tables) still refuses `access_policy_pending`.
-- A hiccup on the same read earlier, while the loops job first hands the fact to gbrain, still loses that one fact as it did before. The loops job keeps the loop row and logs `fact projection failed`.
-- Facts dropped this way before the fix are not recovered by this change.
-- On the same kind of source, an owner's `gbrain trust release` of a held fact for an entity with no page used to report `released` while saving the fact only in the database, with no row in Git, whenever no holding page could carry it: an exact page rule on the entity, or access rules the database role could not read. Now the release refuses with nothing written and the fact stays held: `git_home_required` names the entity's page to create, and `access_policy_pending` asks you to retry. Creating that page does not unlock the release, because a page under its own rule counts as private for a release (`page_not_found`); drop the hold and remember the fact on the page instead. Facts released this way before the fix are not changed; `gbrain repair facts-home` lists them as `folder_restricted`. (GST-2676)
diff --git a/changelog.d/capy-w-a1-access-history-group2.md b/changelog.d/capy-w-a1-access-history-group2.md
deleted file mode 100644
index e1baf20f55..0000000000
--- a/changelog.d/capy-w-a1-access-history-group2.md
+++ /dev/null
@@ -1,9 +0,0 @@
-**When a shallow checkout hides a folder's access-rule history, the first import now refuses with a code and the exact command to fix it, `gbrain access rule migrate` moves rules between git and the database, renamed pages keep their atom lineage, connection strings lose their password whatever the scheme, and a policy-only mirror no longer trips the git convergence check.** Community wave W-A1, second part: bug reports verified on master and fixed with our own code.
-
-### Fixed
-- **First access-rule import (GST-2638).** The first import of a source's access rules refused when it could not read their git history. It now tells a missing history apart from an unreadable one. An unreadable history refuses with the new code `access_policy_history_unreadable`, and the fix it names is `git -C <source root> fetch --unshallow` and then the same command again. A plain sync on a shallow checkout whose rules do have committed history still fails closed. `gbrain access rule migrate --to git|database` moves the rules from one store to the other, the preview shows when only the owner can read pending pages, and the command exits 1 when the result would be invalid.
-- **Policy-only mirrors (GST-2634).** `gbrain doctor`'s git_convergence check no longer flags a source whose mirror holds only access policy.
-- **Ingest refusals (#8982).** A refused `POST /ingest` now carries a code, a fix and a docs link.
-- **Renamed pages, config secrets and root metadata deletes (#8920).** When a later rename onto an old slug drops its alias, an atom is still judged by the private page its origin moved to. A concept is still judged as before: by its input atoms and their origins' rename aliases only. Config secret keys are redacted, and the password in a connection URL is removed for any scheme. Deleting a root metadata file publishes the change to the database only.
-
-<!-- behavior-change: access_first_import_history_gst2638 -->
diff --git a/changelog.d/gbra498-pr2-room-cli.md b/changelog.d/gbra498-pr2-room-cli.md
deleted file mode 100644
index 9f21502a4c..0000000000
--- a/changelog.d/gbra498-pr2-room-cli.md
+++ /dev/null
@@ -1,13 +0,0 @@
-### Name the room on the CLI, and think answers and writes carry room marks too
-
-**`--room <list>` now works on every gbrain operation command, and `think`, `put_page` and `remember` answers are marked for the room like reads are.** A harness that runs gbrain as a command, or a person checking what a group chat could see, gets the same marks an MCP caller gets, and the agent writing into a room can tell which parts of a synthesized answer came from pages the room cannot read.
-
-- `gbrain <command> --room alice-example,group:team-a` prints exactly what the command prints without it. With `--json` every item carries `room_access` and the document carries `_meta.room` (a list becomes `{ results, _meta }`); without it stderr names what the room cannot read. The local CLI marks the brain owner's view, or the member `--as` names; with no owner set, every item is unknown and the notice says to run `gbrain access owner set`.
-- A trailing `--room` with no value is never dropped. The command runs, every item is marked unknown (`invalid`), the degraded stamp shows and it exits 0.
-- It works through a running `gbrain serve` that owns a PGLite brain (the owner marks the answer) and on a thin client (sent as `_meta.room`). A host or owner that predates room marks leaves every item unknown (`not_supported`).
-- A `think` answer is marked at the strictest class of everything its synthesis retrieved or was shown (the anchor and the graph pages its prompt names, each under its own source); an answer built partly from takes or a calibration profile, or with no recorded evidence, is unknown. `put_page` and `remember` mark the page or fact they wrote and are never stamped degraded for it, so a committed write never reads as one to retry.
-- The shipped access-policy and agent templates now say how an agent acts on its owner's own turn in a group chat (at the owner's scope, written for the room, with truly private material offered in a private chat and never a refusal; everyone else is answered at the group's level) and that a send the principal asks for in their own verified message goes out as asked, with no approval phrase or draft-first step. Existing installs keep their own files.
-- Guide: [docs/guides/rooms.md](docs/guides/rooms.md).
-
-<!-- behavior-change: room_cli_think_writes_gst2639 -->
-<!-- behavior-change: owner_turn_sends_templates_gst2656 -->
diff --git a/openclaw.plugin.json b/openclaw.plugin.json
index ecf5c1f4cc..70b3313437 100644
--- a/openclaw.plugin.json
+++ b/openclaw.plugin.json
@@ -1,7 +1,7 @@
{
"id": "gbrain-context-engine",
"name": "gbrain",
- "version": "0.60.718.0",
+ "version": "0.60.719.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 b7866e295a..253dd8a723 100644
--- a/package.json
+++ b/package.json
@@ -260,7 +260,7 @@
"bun": ">=1.4.4"
},
"license": "MIT",
- "version": "0.60.718.0",
+ "version": "0.60.719.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 af3249246f..16a762f0e0 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.718.0",
+ "version": "0.60.719.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 2b9cc99a4b..d154bdd5da 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.718.0",
+ "version": "0.60.719.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 11f030fe51..351dd59a3f 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.718.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.719.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 d22ac9961e..b919c3d994 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.718.0",
+ "version": "0.60.719.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 b92b34fe70..0729b8616b 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.718.0",
+ "version": "0.60.719.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 e393d993da..ac5d893025 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.718.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.719.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 bb2e8c4b22..da207c902f 100644
--- a/plugin/README.md
+++ b/plugin/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.718.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.719.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 9085121b0a..f6cdfcb8a6 100644
--- a/src/core/behavior-changes.generated.ts
+++ b/src/core/behavior-changes.generated.ts
@@ -65,6 +65,9 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin
{ since: '0.60.717.0', id: 'owner_room_marks_gst2639', text: "A harness can now declare the group chat an answer goes into (the X-Gbrain-Room header, request-level _meta.room, or a room tool argument once whoami shows features.room). The caller's read is unchanged; every page and fact in the answer is marked room_access with whether the people in that chat could have read it, and the room_above_level notice tells the agent to keep those items out of the reply. A call with no room is unaffected. With mcp.strict_params set to reject, every tool schema now also declares the optional room argument. See docs/guides/rooms.md." },
{ since: '0.60.718.0', id: 'managed_push_scan_every_publish_gst2650', text: "Every push gbrain makes is now scanned for secrets with no opt-out: `commitAndPush` no longer has an unscanned mode, so a push handed over from a busy publish lock is scanned too. Only the commits the remote lacks are read, and a missing remote-tracking branch is fetched first instead of scanning the whole history. In a managed root below the repository's top level, a commit changing that root's own `.gbrain-scan-allow` is held like one at the top level, and its path globs match paths relative to that root. A strict (canonical: git) source's commit whose files a Git clean filter changed is scanned instead of trusted, and so is one made before this release that is still unpushed; either is still pushed when the scan finds nothing. Git replace refs no longer change what a page-write commit holds. A false positive in an unpushed commit holds the push with `publish_secret_found` naming the file, line and rule, never the value: add its fingerprint to `.gbrain-scan-allow`, then run `gbrain sources writer retry-effects <source> --parked-pushes`, or the push fix `gbrain doctor` names." },
{ since: '0.60.718.0', id: 'strict_fallback_refusal_gst2635', text: "On a source whose pages are canonical in Git (`canonical: git`), a fact the Google loops extraction (or any writer that keeps a fallback entity, writeSingleFact) finds for an entity with no page that an exact page rule names is now refused `git_home_required` (reason `facts_lane`) before anything is stored, with a fix that creates the entity's page; before, it was stored in the database only, with no file in Git, or refused with a message naming memory/unattributed. When the access rules cannot be read the write refuses `access_policy_pending` (retry), and that refusal's message now names the entity, for `remember` too. The loops job still records the loop and logs the refusal code with the entity's page; nothing is stored for that fact. Facts stored the old way are not changed: `gbrain repair facts-home` lists them as `folder_restricted`. Sources that are not strict and brains with no Git repository are unchanged." },
+ { since: '0.60.719.0', id: 'access_first_import_history_gst2638', text: "A folder-rule edit (gbrain access rule add, rm, revert or import) on a git-backed source that has no folder-rule revision yet now refuses before writing anything, with access_policy_history_unreadable, when its checkout is shallow or a partial clone missing the Git objects of its folder-rule history; it used to commit the file and leave the whole source reading as nobody. When you hit it, run git -C <source root> fetch --unshallow (for a partial clone, git -C <source root> log --first-parent -p HEAD -- .gbrain/access.yml, which fetches every version), then rerun the same gbrain access rule command; nothing was written, so the source keeps its current reads meanwhile. A first edit on a source with no folder-rule history no longer reads the whole source as nobody while it applies. An edit whose result state is invalid now exits 1 instead of 0. Unchanged: a plain gbrain sync of a shallow checkout whose commits already hold folder-rule history still fails closed as before, reading the whole source as nobody because the history cannot be replayed; recover the same way, git -C <source root> fetch --unshallow, then gbrain sync --source <id> --no-pull." },
+ { since: '0.60.719.0', id: 'room_cli_think_writes_gst2639', text: "`--room <list>` now works on every gbrain operation command (`gbrain query \"plan\" --room alice-example,group:team-a`). The command prints what it always printed; the room only adds marks. With --json every item carries room_access and the document carries _meta.room, and a list answer becomes { results, _meta } only when --room is given. Without --json, stderr adds a [gbrain room: ...] summary. The local CLI marks the brain owner's view (gbrain access owner set) or the member --as names; with no owner every item is unknown (unbound). A trailing --room with no value marks every item unknown (invalid) with the degraded stamp and exits 0. A running gbrain serve that owns a PGLite brain marks delegated answers, and a thin client sends the room as _meta.room; an owner or host that predates room marks leaves every item unknown (not_supported). With a room declared, think answers are now marked at the strictest class of everything their synthesis retrieved (unknown when built partly from takes or with no recorded evidence), and put_page and remember mark the page or fact they wrote without a degraded stamp, where before they answered op_not_covered. Calls with no room are unchanged. Guide: docs/guides/rooms.md." },
+ { since: '0.60.719.0', id: 'owner_turn_sends_templates_gst2656', text: "New installs get two changed templates. The access-policy template's group-chat rule now says a turn the owner sends, verified by sender identity, is done at the owner's scope exactly as in a private chat, written for the room, with truly private material offered in the owner's private chat and never a refusal; every other member is answered at the group's level, and a member saying the owner wants something is making their own ask. The agent template's red line on messaging third parties now says a send the principal asks for in their own verified message (or through a delegate the principal set up and the host authenticates) goes out as asked, in any chat and to any recipient, with no approval phrase and no draft-first step; the agent still never messages anyone as the principal on its own initiative, and a request another person quotes, forwards or relays is that person's. The money and deletion red lines are unchanged. Existing installs keep their own ACCESS_POLICY.md and AGENTS.md; to adopt the new wording, copy it from templates/ACCESS_POLICY.md.template and templates/bootstrap/template-repo/AGENTS.md." },
];
/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */
@@ -131,4 +134,7 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {
owner_room_marks_gst2639: '0.60.717.0',
managed_push_scan_every_publish_gst2650: '0.60.718.0',
strict_fallback_refusal_gst2635: '0.60.718.0',
+ access_first_import_history_gst2638: '0.60.719.0',
+ room_cli_think_writes_gst2639: '0.60.719.0',
+ owner_turn_sends_templates_gst2656: '0.60.719.0',
};
diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.md
index a01a188c53..4d92ac84eb 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.718.0 -->
+<!-- gbrain-template-stamp: 0.60.719.0 -->
This repository is the **"Use this template"** distribution artifact for a
[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same