Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
v0.60.736.0 release (#9657)
Garry Tan4d1628afb4b4
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex 0f0e5fe5bf..5b4fb0de9b 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "gbrain",- "version": "0.60.735.0",+ "version": "0.60.736.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.jsonindex 2154378e15..6bef93329e 100644--- a/.codex-plugin/plugin.json+++ b/.codex-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "gbrain",- "version": "0.60.735.0",+ "version": "0.60.736.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.mdindex 83e0153e73..523f8d283f 100644--- a/BOOTSTRAP_FOR_AGENTS.md+++ b/BOOTSTRAP_FOR_AGENTS.md@@ -1,4 +1,4 @@-<!-- gbrain-runbook-stamp: 0.60.735.0 -->+<!-- gbrain-runbook-stamp: 0.60.736.0 --><!-- This stamp must equal the VERSION file at every release; CI enforces it(scripts/check-bootstrap-tag.sh). `gbrain bootstrap status` compares it tothe installed binary and warns on skew. -->diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 0bf99ed166..a95d1ae7ae 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,6 +10,159 @@ credits are retained; no result has been reassigned to another provider. Originaidentifiers and attribution are available in the pre-removal Git revision`6040075c6cb95be5881cc2e1b76ef7d71f4e5d29` (retained on 2026-09-23).+## [0.60.736.0] - 2026-11-17++**Contributors: the pre-merge check now accepts changes to the macOS helper's files under `apple/helper/`, which build and test only in their own macOS workflow.**++### Changed+- `.gstack/pregate.json` lists `apple/helper/**` as having no local test run, the same way `scripts/bench/**` is listed. The helper's Swift tests run on every change to `apple/**` in the `Apple helper` workflow. Nothing changes for gbrain users. (#9627)++**A private fact restated as world and held for the owner's accept stays hidden in more places from callers who cannot read the private fact: `think` leaves it out, the reply to the held write reads like an ordinary save, and a restatement written onto another page about the same entity is held too.**++<!-- behavior-change: held_private_replies_2900 -->++### Fixed+- `think` now leaves a held fence row out of the pages it reads and the evidence it delivers for callers who cannot read the private fact, as get_page and search already do. The owner's callers and the local CLI read the same as before.+- The reply to a held write (`remember`, `put_page` and the other page writes) named the owner's proposal in `contested.proposal_ref`, which told a caller who guessed a claim that a more private copy of it exists. For a caller who cannot read that private fact, the reply, its `outcome` and `write_request` copies, `get_write_request` and `list_write_requests` now leave the reference out, so the reply reads like a saved write. The owner's callers, the local CLI and callers who can read the private fact still get it, and a `contested` reference for any other reason (a write that tried to replace a more trusted fact) is unchanged.+- A page write whose `## Facts` row restated a more trusted private fact about the page's own entity, kept off that page (a remembered fact with no page row, or a row on a holding page), was stored as world. It is now stored private with a proposal, like a restatement on the same page, and `gbrain trust confirm tp<N>` makes it world. Like the same-page hold, this applies to the owner's own local writes and sync too, when the private copy is more trusted than the writer.+- A credential with a `private_facts: granted_sources` grant reads a held row again in `get_page`, search and `think`, as it did before the held-row page reads, when it can read every private copy the row restates. A row restating a copy the grant can't read (on a member or restricted page, or on no page) stays held from it. Known: such a credential's `put_page` still restores a held row it can see, so its edit or delete of that row doesn't stick and an edit can leave two rows.+- A remote `get_page` or `get_versions` of a page stored in segments reported a size that counted held rows. It now reports the size of what the caller can read.+- Still not held: a restatement about another entity, a reworded claim, captured prose and extracted facts. A writer that cannot read the private fact still can't read its own held row back (page reads and recall leave it out) until the owner accepts it, which a saved row would not do.++**A private fact restated as world and held for the operator's accept no longer reaches remote callers through page, chunk, search and edit reads: get_page, get_versions, fetch, search, query, search_exact, get_chunks, the entity card and the edit_page diff leave the held row out for callers who cannot read the private fact.**++<!-- behavior-change: held_row_page_reads_2891 -->++### Fixed+- A remote `put_page` that restated a private fence row as world (#9196), or a remote `remember` that restated a private fact (GST-2875), stored the new fact private until the operator accepts the widening, but the page body kept the restatement in a world cell. Every remote caller who cannot read the private fact (another member, an unbound token) read it through get_page (whole, include_content, lines, grep, section, outline, as_of, known_as_of and windows around a chunk), get_versions with include_body (known_as_of bodies and diffs too), fetch, keyword and hybrid search, query, search_exact (snippets, and the match itself, on pages stored in segments too), get_chunks (on any source) and the entity card. A recorded-time read at the slug a page had before a rename leaves it out too, and search_exact still finds a page's public hit when an earlier hit in the same text is a held row. Those reads now leave out a world fence cell whose fact is stored narrower than world, including a row a chunk boundary cut in half and chunks written before the upgrade, so no rechunk is needed. The owner's callers, the local CLI and a member reading their own member page read exactly what they read before. If the held-row lookup fails, a page read fails rather than return the page, and search drops every fence row.+- Such a caller's `put_page` keeps the held row it could not read. Writing back a page read without it (a get_page, edit, put_page round trip, a whole new body, or a body with the lines around it deleted) restores the row exactly as stored, so the operator's accept still widens it. A row the writer sends at the held row's number cannot replace or reword it. A different claim moves to a new row number, and the same claim keeps every stored cell except a narrower visibility the writer chose. A member session under GBRAIN_ENFORCED_MEMBER reads such a page the same way, so its put_page keeps the held row and its edit_page diff leaves it out. The owner's own writes and the local CLI's are unchanged.+- The `edit_page` diff showed a remote caller the held row as unchanged context when an edit landed near it, on inline and segmented pages alike. The diff now leaves it out for callers who cannot read the private fact, as get_page does.+- An edit elsewhere in a held page (a hand edit synced from the repository, or a local `put_page`) could re-derive the held row as world without the accept when the private copy was less trusted than `user_confirmed`. A held row now stays private whatever the writer's tier until the operator accepts it. Accept still makes it world, and reject and undo still work.+- A remote writer could skip the GST-2875 hold by first saving the same claim as a world fact about another entity. The hold looked for an existing world copy anywhere in the source, found that one, and stored the restatement on the confirmed private fact's entity as world, so remote recall returned it. The world copy now has to be on the same entity.+- Not covered: the page file in the brain repository still carries the world cell, so anyone who reads the repository directly, or a Markdown export, reads it. Restatements that were never held (capture, extract_facts, a restatement written onto another page or entity, a reworded claim, and a remember whose private copy is no more trusted than the writer) stay world as before.++**Link context no longer shows remote callers private or held fact rows: get_backlinks, get_links, traverse_graph (walks and hops), the relationship-chain evidence on search, query and recall results, the entity card, context_pack and delta's belief changes leave that text out for callers who may read only world facts, and context_pack's always-loaded core block leaves held rows out for them too.**++### Fixed+- A link's stored context is a short excerpt of the page around the reference. When the reference sat in or next to a page's `## Facts` table, the excerpt carried rows of that table, including rows saved private and world rows held until the operator accepts a widening. Remote callers who may read only world facts (another member, an unbound token) read that text through get_backlinks, get_links, traverse_graph walks and hops, the chain evidence on search, query and recall results, the entity card's edges and context_pack's cards. An attendance edge, stored on the attendee's page but cut from the meeting page, carried the meeting's rows the same way. For those callers, a context cut from a page is now returned only when it reads, word for word, inside that page as it is now and as the caller may see it; otherwise it comes back empty. That also covers a page whose table was removed by an edit that left its links unchanged. The page bodies for one read are loaded together, for at most 200 pages; contexts cut from pages beyond that come back empty for those callers. A context written by add_link or derived from frontmatter is unchanged unless it holds a facts or takes table marker.+- unify-types' `preserve_notes` stored the first 240 characters of a converted page as the new link's context, facts and takes tables included. It now leaves those tables out, so links written from now on store a shorter excerpt for every reader, the owner included. Contexts it stored before are emptied for callers who may read only world facts when they hold a table marker.+- `delta` with `beliefs: true` returned each changed link's stored context in its before and after values. Those callers now get the link change without the context.+- With `memory.core.enabled` on, context_pack's core memory block showed those callers a core page's held rows. It now leaves them out, as get_page does.+- The owner's remote callers and the local CLI read stored links exactly as before. Stored links are not rewritten and no migration runs.++**A connection gbrain throws away now frees its slot in the connection pool even when the database host has stopped answering, and the background job worker keeps running while PostgreSQL shuts down or after a TCP server has stopped.**++### Fixed+- When gbrain discards a Postgres connection (a cancelled bounded read, an aborted transaction, a statement that would not cancel) and the server or pooler at the other end has gone silent, the pool slot comes back within about 2 seconds. Before, the slot stayed taken until the operating system gave up on the socket, so a process with a small pool could stop being able to connect. Follow-up to #8155.+- `gbrain jobs work` no longer exits when a claim meets a PostgreSQL server that is shutting down and refusing new connections (SQLSTATE 57P03), or one that has stopped listening on TCP (`connect ECONNREFUSED`). The worker reconnects and claims again on its next poll, as it already did for a vanished Unix socket. Follow-up to #9540, reported and first fixed by @javieraldape in #9624.++**A pull request landed as one squashed commit now reuses its passed full test run on master again, even when master was merged into it with no file change just before landing.**++### Fixed+- `scripts/ci-reuse.ts`: a one-parent push to master looked for a passed full run only on the head GitHub names for the landed pull request. Landing first merges master into the branch, and when that merge changes no file the new head has the tested tree but only a pull-request run, so every landing ran Test and E2E in full again (about 18 minutes instead of about 4). The push's tree now decides, as in the remote gate. The newest full run on any head with that tree wins, and those heads are the pull request head, its first parents with the same tree and the heads of recent dispatch and push runs. A newer failed or in-progress full run on the tree still runs in full, and what counts as a complete full run is unchanged. A hand revert or direct push whose tree matches a passed full run now reuses it too. docs/ci-event-parity.md, "Master-push reuse", says so.++**When a scoped graph walk or typed hop chain ends early, the next call it suggests now keeps the caller's source scope.**++### Fixed+- `traverse_graph` returns a `graph_walk_truncated` notice when a walk stops at its cap, with a ready-to-run retry one level shallower. That retry dropped the caller's `source_id` and `all_sources`, so an agent that followed it walked its default source instead of the one it asked for. The retry now carries both, and still leaves them out when the call didn't set them (#8498).+- The same holds for a `hops` chain that finds no edges, stops at an empty hop or hits a chain cap: its suggested `traverse_graph` call now keeps `source_id` and `all_sources` (#8498).++### Tests+- `test/degraded-stamp-paths.serial.test.ts` checks the retry for a walk scoped to one source, an all-sources walk and an unscoped walk.+- `test/traverse-graph-hops.test.ts` checks the no_edges and empty_hop suggestions for the same three cases.++**Long-running gbrain processes recover from a lost database connection: a bounded read cancelled while the database stops answering frees its connection at once, and the background job worker keeps running through a PostgreSQL shutdown instead of exiting.**++### Fixed+- A bounded read (a statement with a time limit) whose caller cancels it after it has a connection now sends the database a cancel request, discards that connection and returns at once. Before, the call waited until the database answered, and the connection stayed reserved the whole time, so a process that hit a stalled socket or pooler again and again could run out of connections. (#8155)+- `gbrain jobs work` no longer exits when PostgreSQL shuts down and removes its local Unix socket (`connect ENOENT <dir>/.s.PGSQL.<port>`). The worker reconnects and claims again on its next poll, the same as for other lost connections. A first connect to a socket path that doesn't exist still fails at once. (#9540)++**The Rust engine setup script is safer on shared and already-used machines: each run logs to its own private folder, it ignores `PGHOST`, `PGHOSTADDR` and `PGSERVICE`, and it no longer resets an existing `gbrain` database role.**++### Fixed+- `scripts/dev/rust-engine-bootstrap.sh` now writes each run's step logs to a new private folder, and refuses a `GBRAIN_DEV_LOG_DIR` that another user can write to.+- The script unsets `PGHOST`, `PGHOSTADDR` and `PGSERVICE` for itself, so its database steps always reach the local Postgres 16 cluster.+- The script creates the `gbrain` role only when it is missing. An existing role keeps its password and flags; if it cannot be used, the step fails with a message that names the setting to change.++**Contributors working on the Rust engine can now set up an Ubuntu machine with one command: `scripts/dev/rust-engine-bootstrap.sh` installs the pinned Bun, Postgres 16 with pgvector, Rust and the napi-rs CLI, and prints a pass/fail line per step.**++### Added+- `scripts/dev/rust-engine-bootstrap.sh`: a non-interactive, rerunnable dev setup for Ubuntu. It installs the Bun version from `package.json`, starts Postgres 16 with pgvector and a test database, installs the Rust stable toolchain and the napi-rs CLI, runs `bun install`, and writes `~/.gbrain-rust-dev.env`. It does not change gbrain itself.+- `docs/research/rust-engine/dev-environment.md`: how to run the script, what each step does, how to run the engine parity tests, measured timings and known problems.++**Install guides now say Bun's installer needs `unzip`, show how to get it, and give a tested route for machines where packages can't be installed.**++### Documentation+- README.md, INSTALL_FOR_AGENTS.md, docs/INSTALL.md, AGENTS.md and the company-brain tutorial say Bun's installer stops with `error: unzip is required to install bun` when `unzip` is missing, and give the check (`command -v unzip`) and the apt, dnf and apk install commands.+- INSTALL_FOR_AGENTS.md#no-unzip is a tested route for Linux machines with no `unzip` and no package manager: it puts Bun's own build in `~/.bun/bin` using only `curl` and `tar`, and checks that `gbrain` runs from a fresh login shell.+- docs/guides/troubleshooting.md has a row for the `unzip is required` error.++**gbrain git commit-push --untrack now takes every file under a declared, ignored database-only folder, .json and other non-Markdown files included.**++### Fixed+- In a managed checkout, `gbrain git commit-push --untrack -- <folder>` refused `untrack_not_db_only` for a folder declared under `storage.db_only` and ignored by `.gitignore` when it held `.json` (or other non-Markdown) files, because each file was matched by its page slug. A file is now matched by its path under the declared folder. A Markdown page still needs its slug under the folder; a code-extension file is checked against the brain and refuses when it is a live page, when the source's strategy imports code (sync imports it as a page), when the source's last finished sync has not seen it at its current version (run `gbrain sync --source <id>`, then rerun), or when the brain cannot be read. Symlinks out of the folder, folders reached through a symlink and sibling folders that only share the name refuse. Each refusal's fix now names what is missing for that file, and `--dry-run --untrack` lists exactly the files the real run removes.+- The managed sync note about pages kept from the working tree no longer tells a page under a declared `storage.db_only` folder to be committed.+- For a source rooted in a folder of its repository (`brain/`, with `brain/gbrain.yml`), `--untrack` read the repository's top-level `gbrain.yml`: every file refused `untrack_not_db_only`, and a folder only a stray top-level `gbrain.yml` declared was admitted, so the next sync deleted its pages. In a managed checkout every untrack now reads the source's folder from the brain, read-only for at most 10 seconds, and refuses every file when the brain cannot be read. On PGLite, stop a running `gbrain serve` or sync before an untrack. The refusal names the `gbrain.yml` it read.++<!-- behavior-change: untrack_db_only_by_path_gst2964 -->+<!-- behavior-change: untrack_reads_brain_gst2964 -->++**A large capture's receipt now reports the same date as the page slug it created, and five tests that failed now and then pass every run.**++### Fixed+- `gbrain capture --file` with a file over the page size limit took the slug date and the receipt's `captured_at` from two separate clock reads, so a capture that ran across UTC midnight could print a receipt dated one day for a page slug dated the next. Both now come from one timestamp. (#7980)+- The forget test for twin inline and segmented pages froze no clock, so a run that crossed UTC midnight stamped the two pages with different dates and failed. Both halves now run under one frozen time. (#8674)+- The sync dry-run test compared request rows read in no fixed order. It now orders them by id and compares whole rows, so it also catches a dry run that edits a request. (#8416)+- The private-queue recovery test gave its orphan job a 1 ms lease and relied on it running out before reconcile looked. The test now expires the lease explicitly. (#8739)+- The reranker failure test freed a random port and assumed nothing would take it again. It now points the dead endpoint at port 1, where nothing listens. (#9616)++**The query facts block now shows a later retraction right after the fact it calls off.**++<!-- behavior-change: facts_block_retractions_gbra574 -->++### Added+- When the facts block shows a fact about a person or company, a later fact about the same entity that retracts it or calls it off ("retracted", "scratch that", "I was wrong", "cancelled", "called off", "fell through", "never happened", "just a rumour" and similar) follows it, with its own date header, inside the block's usual share of the token budget and row count. The later fact pairs only when it is dated after the fact, its cue is not negated ("not cancelled", "wasn't called off" and "isn't a rumour" never pair), and it carries the same slot (dimension and value) or, leaving out the entity's name and the cue words, every word it has is in the fact or it shares at least two words with it. It is read under the caller's read policy, so a retraction a remote caller or another member cannot read never appears, and a forgotten or withdrawn fact never appears. No model call; a question with no such later fact gets exactly the block it got before.++**The brain owner's own remote agents now get the owner's private facts on the entity and context_pack cards, in search's facts about an entity, in the list of facts saved without an entity and in forget's similar-facts check.**++<!-- behavior-change: owner_remote_fact_reads_more_gst2951 -->++### Fixed+- The `entity` card (recent facts and `active_fact_count`) and the `context_pack` cards built from it, the entity facts and saved facts that `search` and `query` attach, `extraction_pending`'s unattributed list and `forget`'s `similar_active` decided fact visibility from the raw remote flag, so a credential bound to the brain owner got world facts only. They now use the same owner rule as recall, think and `find_trajectory`, and the owner's reads use the owner-aware page rule, so a fact from a private page the owner reads stays visible.+- Nothing widens for anyone else: another member, a labelled-only member, an unbound token, a call with no credential and the owner speaking for an audience of several read what they read before, and a private-facts grant works where it already did. Member access still applies to the owner, and withdrawn facts stay out of every read.++**The brain owner's own remote agents now get the owner's private facts from trajectories, ontology reads and write attribution, as they already did from recall, query and think.**++<!-- behavior-change: owner_remote_fact_ops_gst2951 -->++### Fixed+- `find_trajectory`, `ontology_get`, `ontology_conflicts` and `volunteer_chronicle` decided fact visibility from the raw remote flag, so a credential bound to the brain owner got world facts only and a trajectory built from private facts came back empty. They now use the same owner rule as recall and think. `get_write_attribution` finds a private fact for the owner's admin credential the same way.+- The owner also gets facts taken from a private page it can read on the ontology reads and in write attribution, as `find_trajectory` and recall already allowed.+- A newer observation from a diary page no longer hides the older value behind it on `ontology_get` and `volunteer_chronicle`, and no longer makes a false conflict on `ontology_conflicts`. Diary observations are left out before each value resolves, for every remote caller, and still never reach one.+- Nothing widens for anyone else: another member, a labelled-only member, an unbound token, a call with no credential and the owner speaking for an audience of several read no private fact they did not read before. Page rules, member access and source grants still apply to the owner, and withdrawn facts stay out of every read.++**Files in a folder whose name starts with two dots, such as `..drafts` or `...`, are no longer refused or reported as outside the brain by sync, git commit-push, doctor, frontmatter, skills and the other checks listed below.**++<!-- behavior-change: dotdot_folder_names_inside -->++### Fixed+- Many path checks asked "does this path start with two dots?" to catch a path that goes up and out of a folder. That question also matched a normal folder named `..drafts`, `..x` or `...`, so a file inside the brain was refused, skipped or called "outside". All of these checks now look at the first folder name exactly, through one shared helper. Remote file uploads into such a folder are still refused; a separate fix covers that check.+- `gbrain git commit-push -- ..drafts/a.md` commits the file instead of failing with "outside the checkout", and a `gbrain.sourceRoot` of `..drafts` now scopes the commit to that folder instead of being dropped (which scoped it to the whole checkout).+- Sync markers no longer report a file that was never committed as committed when the source sits in a `..` folder of its repository.+- Skill packs and the skills catalog (`get_skill`, `list_skills`) read a `SKILL.md` that sits in, or is linked to, an in-pack `..shared` folder.+- `gbrain frontmatter` expects the slug `..drafts/note` for `..drafts/note.md`, as for any other folder, instead of reporting a false slug mismatch; its backups of two `note.md` files in different `..` folders no longer overwrite each other.+- Doctor's git-writer and foreign-writer checks, brain-repo hardening (including a `core.hooksPath` of `..hooks`), the first-turn brain rule, extract-benchmark, extract-atoms transcript labels, skillpack update bases, sync applicability, fence-write and reconcile path states, and the LongMemEval call plan treat such folders as inside.+- Real escapes stay refused with the same messages as before: `../x`, an absolute path elsewhere, a sibling folder that shares the root's name prefix, a symlinked parent that points outside, and another Windows drive.++### Added+- `bun run verify` runs `check:relative-dotdot`, which refuses a new `.startsWith('..')` containment check in `src/` and points at `relativeEscapesRoot` in `src/core/path-confine.ts`.++**On Postgres, file records now report their size as a plain number, and closing the engine a second time no longer runs its shutdown steps again. PGLite already worked this way.**++### Fixed+- On Postgres, `getFile` and `listFilesForPage` returned `size_bytes` as a BigInt. PGLite returned a number, and the declared type is a number. Both engines now return a number. The output of the `gbrain files` CLI and the MCP file operations does not change, because those paths already converted the value.+- On Postgres, a second `disconnect()` of an engine that was already closed ran the registered shutdown hooks again. A second `disconnect()` now does nothing, as on PGLite.+## [0.60.735.0] - 2026-11-17**Conversation archive pages written while a brain was personal are now kept to the owner as soon as a command makes the brain shared, instead of staying readable by every member until the next archive run.**diff --git a/VERSION b/VERSIONindex dda0409d19..130d30a560 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-0.60.735.0+0.60.736.0diff --git a/changelog.d/apple-helper-pregate-lane.md b/changelog.d/apple-helper-pregate-lane.mddeleted file mode 100644index b0cd1b66d1..0000000000--- a/changelog.d/apple-helper-pregate-lane.md+++ /dev/null@@ -1,4 +0,0 @@-**Contributors: the pre-merge check now accepts changes to the macOS helper's files under `apple/helper/`, which build and test only in their own macOS workflow.**--### Changed-- `.gstack/pregate.json` lists `apple/helper/**` as having no local test run, the same way `scripts/bench/**` is listed. The helper's Swift tests run on every change to `apple/**` in the `Apple helper` workflow. Nothing changes for gbrain users. (#9627)diff --git a/changelog.d/capy-held-private-replies-2900.md b/changelog.d/capy-held-private-replies-2900.mddeleted file mode 100644index bcda92c1be..0000000000--- a/changelog.d/capy-held-private-replies-2900.md+++ /dev/null@@ -1,14 +0,0 @@-----important: security-----**A private fact restated as world and held for the owner's accept stays hidden in more places from callers who cannot read the private fact: `think` leaves it out, the reply to the held write reads like an ordinary save, and a restatement written onto another page about the same entity is held too.**--<!-- behavior-change: held_private_replies_2900 -->--### Fixed-- `think` now leaves a held fence row out of the pages it reads and the evidence it delivers for callers who cannot read the private fact, as get_page and search already do. The owner's callers and the local CLI read the same as before.-- The reply to a held write (`remember`, `put_page` and the other page writes) named the owner's proposal in `contested.proposal_ref`, which told a caller who guessed a claim that a more private copy of it exists. For a caller who cannot read that private fact, the reply, its `outcome` and `write_request` copies, `get_write_request` and `list_write_requests` now leave the reference out, so the reply reads like a saved write. The owner's callers, the local CLI and callers who can read the private fact still get it, and a `contested` reference for any other reason (a write that tried to replace a more trusted fact) is unchanged.-- A page write whose `## Facts` row restated a more trusted private fact about the page's own entity, kept off that page (a remembered fact with no page row, or a row on a holding page), was stored as world. It is now stored private with a proposal, like a restatement on the same page, and `gbrain trust confirm tp<N>` makes it world. Like the same-page hold, this applies to the owner's own local writes and sync too, when the private copy is more trusted than the writer.-- A credential with a `private_facts: granted_sources` grant reads a held row again in `get_page`, search and `think`, as it did before the held-row page reads, when it can read every private copy the row restates. A row restating a copy the grant can't read (on a member or restricted page, or on no page) stays held from it. Known: such a credential's `put_page` still restores a held row it can see, so its edit or delete of that row doesn't stick and an edit can leave two rows.-- A remote `get_page` or `get_versions` of a page stored in segments reported a size that counted held rows. It now reports the size of what the caller can read.-- Still not held: a restatement about another entity, a reworded claim, captured prose and extracted facts. A writer that cannot read the private fact still can't read its own held row back (page reads and recall leave it out) until the owner accepts it, which a saved row would not do.diff --git a/changelog.d/capy-held-row-page-reads-2891.md b/changelog.d/capy-held-row-page-reads-2891.mddeleted file mode 100644index 6933671042..0000000000--- a/changelog.d/capy-held-row-page-reads-2891.md+++ /dev/null@@ -1,14 +0,0 @@-----important: security-----**A private fact restated as world and held for the operator's accept no longer reaches remote callers through page, chunk, search and edit reads: get_page, get_versions, fetch, search, query, search_exact, get_chunks, the entity card and the edit_page diff leave the held row out for callers who cannot read the private fact.**--<!-- behavior-change: held_row_page_reads_2891 -->--### Fixed-- A remote `put_page` that restated a private fence row as world (#9196), or a remote `remember` that restated a private fact (GST-2875), stored the new fact private until the operator accepts the widening, but the page body kept the restatement in a world cell. Every remote caller who cannot read the private fact (another member, an unbound token) read it through get_page (whole, include_content, lines, grep, section, outline, as_of, known_as_of and windows around a chunk), get_versions with include_body (known_as_of bodies and diffs too), fetch, keyword and hybrid search, query, search_exact (snippets, and the match itself, on pages stored in segments too), get_chunks (on any source) and the entity card. A recorded-time read at the slug a page had before a rename leaves it out too, and search_exact still finds a page's public hit when an earlier hit in the same text is a held row. Those reads now leave out a world fence cell whose fact is stored narrower than world, including a row a chunk boundary cut in half and chunks written before the upgrade, so no rechunk is needed. The owner's callers, the local CLI and a member reading their own member page read exactly what they read before. If the held-row lookup fails, a page read fails rather than return the page, and search drops every fence row.-- Such a caller's `put_page` keeps the held row it could not read. Writing back a page read without it (a get_page, edit, put_page round trip, a whole new body, or a body with the lines around it deleted) restores the row exactly as stored, so the operator's accept still widens it. A row the writer sends at the held row's number cannot replace or reword it. A different claim moves to a new row number, and the same claim keeps every stored cell except a narrower visibility the writer chose. A member session under GBRAIN_ENFORCED_MEMBER reads such a page the same way, so its put_page keeps the held row and its edit_page diff leaves it out. The owner's own writes and the local CLI's are unchanged.-- The `edit_page` diff showed a remote caller the held row as unchanged context when an edit landed near it, on inline and segmented pages alike. The diff now leaves it out for callers who cannot read the private fact, as get_page does.-- An edit elsewhere in a held page (a hand edit synced from the repository, or a local `put_page`) could re-derive the held row as world without the accept when the private copy was less trusted than `user_confirmed`. A held row now stays private whatever the writer's tier until the operator accepts it. Accept still makes it world, and reject and undo still work.-- A remote writer could skip the GST-2875 hold by first saving the same claim as a world fact about another entity. The hold looked for an existing world copy anywhere in the source, found that one, and stored the restatement on the confirmed private fact's entity as world, so remote recall returned it. The world copy now has to be on the same entity.-- Not covered: the page file in the brain repository still carries the world cell, so anyone who reads the repository directly, or a Markdown export, reads it. Restatements that were never held (capture, extract_facts, a restatement written onto another page or entity, a reworded claim, and a remember whose private copy is no more trusted than the writer) stay world as before.diff --git a/changelog.d/capy-link-context-world-rows-2957.md b/changelog.d/capy-link-context-world-rows-2957.mddeleted file mode 100644index 9dcabe6561..0000000000--- a/changelog.d/capy-link-context-world-rows-2957.md+++ /dev/null@@ -1,11 +0,0 @@-----important: security-----**Link context no longer shows remote callers private or held fact rows: get_backlinks, get_links, traverse_graph (walks and hops), the relationship-chain evidence on search, query and recall results, the entity card, context_pack and delta's belief changes leave that text out for callers who may read only world facts, and context_pack's always-loaded core block leaves held rows out for them too.**--### Fixed-- A link's stored context is a short excerpt of the page around the reference. When the reference sat in or next to a page's `## Facts` table, the excerpt carried rows of that table, including rows saved private and world rows held until the operator accepts a widening. Remote callers who may read only world facts (another member, an unbound token) read that text through get_backlinks, get_links, traverse_graph walks and hops, the chain evidence on search, query and recall results, the entity card's edges and context_pack's cards. An attendance edge, stored on the attendee's page but cut from the meeting page, carried the meeting's rows the same way. For those callers, a context cut from a page is now returned only when it reads, word for word, inside that page as it is now and as the caller may see it; otherwise it comes back empty. That also covers a page whose table was removed by an edit that left its links unchanged. The page bodies for one read are loaded together, for at most 200 pages; contexts cut from pages beyond that come back empty for those callers. A context written by add_link or derived from frontmatter is unchanged unless it holds a facts or takes table marker.-- unify-types' `preserve_notes` stored the first 240 characters of a converted page as the new link's context, facts and takes tables included. It now leaves those tables out, so links written from now on store a shorter excerpt for every reader, the owner included. Contexts it stored before are emptied for callers who may read only world facts when they hold a table marker.-- `delta` with `beliefs: true` returned each changed link's stored context in its before and after values. Those callers now get the link change without the context.-- With `memory.core.enabled` on, context_pack's core memory block showed those callers a core page's held rows. It now leaves them out, as get_page does.-- The owner's remote callers and the local CLI read stored links exactly as before. Stored links are not rewritten and no migration runs.diff --git a/changelog.d/capy-postgres-discard-silent-peer.md b/changelog.d/capy-postgres-discard-silent-peer.mddeleted file mode 100644index c1b941092c..0000000000--- a/changelog.d/capy-postgres-discard-silent-peer.md+++ /dev/null@@ -1,5 +0,0 @@-**A connection gbrain throws away now frees its slot in the connection pool even when the database host has stopped answering, and the background job worker keeps running while PostgreSQL shuts down or after a TCP server has stopped.**--### Fixed-- When gbrain discards a Postgres connection (a cancelled bounded read, an aborted transaction, a statement that would not cancel) and the server or pooler at the other end has gone silent, the pool slot comes back within about 2 seconds. Before, the slot stayed taken until the operating system gave up on the socket, so a process with a small pool could stop being able to connect. Follow-up to #8155.-- `gbrain jobs work` no longer exits when a claim meets a PostgreSQL server that is shutting down and refusing new connections (SQLSTATE 57P03), or one that has stopped listening on TCP (`connect ECONNREFUSED`). The worker reconnects and claims again on its next poll, as it already did for a vanished Unix socket. Follow-up to #9540, reported and first fixed by @javieraldape in #9624.diff --git a/changelog.d/capy-squash-landing-reuse-same-tree-head.md b/changelog.d/capy-squash-landing-reuse-same-tree-head.mddeleted file mode 100644index caedd60d46..0000000000--- a/changelog.d/capy-squash-landing-reuse-same-tree-head.md+++ /dev/null@@ -1,4 +0,0 @@-**A pull request landed as one squashed commit now reuses its passed full test run on master again, even when master was merged into it with no file change just before landing.**--### Fixed-- `scripts/ci-reuse.ts`: a one-parent push to master looked for a passed full run only on the head GitHub names for the landed pull request. Landing first merges master into the branch, and when that merge changes no file the new head has the tested tree but only a pull-request run, so every landing ran Test and E2E in full again (about 18 minutes instead of about 4). The push's tree now decides, as in the remote gate. The newest full run on any head with that tree wins, and those heads are the pull request head, its first parents with the same tree and the heads of recent dispatch and push runs. A newer failed or in-progress full run on the tree still runs in full, and what counts as a complete full run is unchanged. A hand revert or direct push whose tree matches a passed full run now reuses it too. docs/ci-event-parity.md, "Master-push reuse", says so.diff --git a/changelog.d/capy-traversegraphs-retry-after-a.md b/changelog.d/capy-traversegraphs-retry-after-a.mddeleted file mode 100644index c91e1fa569..0000000000--- a/changelog.d/capy-traversegraphs-retry-after-a.md+++ /dev/null@@ -1,9 +0,0 @@-**When a scoped graph walk or typed hop chain ends early, the next call it suggests now keeps the caller's source scope.**--### Fixed-- `traverse_graph` returns a `graph_walk_truncated` notice when a walk stops at its cap, with a ready-to-run retry one level shallower. That retry dropped the caller's `source_id` and `all_sources`, so an agent that followed it walked its default source instead of the one it asked for. The retry now carries both, and still leaves them out when the call didn't set them (#8498).-- The same holds for a `hops` chain that finds no edges, stops at an empty hop or hits a chain cap: its suggested `traverse_graph` call now keeps `source_id` and `all_sources` (#8498).--### Tests-- `test/degraded-stamp-paths.serial.test.ts` checks the retry for a walk scoped to one source, an all-sources walk and an unscoped walk.-- `test/traverse-graph-hops.test.ts` checks the no_edges and empty_hop suggestions for the same three cases.diff --git a/changelog.d/capy-w4-db-connection-loss.md b/changelog.d/capy-w4-db-connection-loss.mddeleted file mode 100644index dfb462a325..0000000000--- a/changelog.d/capy-w4-db-connection-loss.md+++ /dev/null@@ -1,5 +0,0 @@-**Long-running gbrain processes recover from a lost database connection: a bounded read cancelled while the database stops answering frees its connection at once, and the background job worker keeps running through a PostgreSQL shutdown instead of exiting.**--### Fixed-- A bounded read (a statement with a time limit) whose caller cancels it after it has a connection now sends the database a cancel request, discards that connection and returns at once. Before, the call waited until the database answered, and the connection stayed reserved the whole time, so a process that hit a stalled socket or pooler again and again could run out of connections. (#8155)-- `gbrain jobs work` no longer exits when PostgreSQL shuts down and removes its local Unix socket (`connect ENOENT <dir>/.s.PGSQL.<port>`). The worker reconnects and claims again on its next poll, the same as for other lost connections. A first connect to a socket path that doesn't exist still fails at once. (#9540)diff --git a/changelog.d/dev-rust-engine-bootstrap-fixes.md b/changelog.d/dev-rust-engine-bootstrap-fixes.mddeleted file mode 100644index a4723a010a..0000000000--- a/changelog.d/dev-rust-engine-bootstrap-fixes.md+++ /dev/null@@ -1,6 +0,0 @@-**The Rust engine setup script is safer on shared and already-used machines: each run logs to its own private folder, it ignores `PGHOST`, `PGHOSTADDR` and `PGSERVICE`, and it no longer resets an existing `gbrain` database role.**--### Fixed-- `scripts/dev/rust-engine-bootstrap.sh` now writes each run's step logs to a new private folder, and refuses a `GBRAIN_DEV_LOG_DIR` that another user can write to.-- The script unsets `PGHOST`, `PGHOSTADDR` and `PGSERVICE` for itself, so its database steps always reach the local Postgres 16 cluster.-- The script creates the `gbrain` role only when it is missing. An existing role keeps its password and flags; if it cannot be used, the step fails with a message that names the setting to change.diff --git a/changelog.d/dev-rust-engine-bootstrap.md b/changelog.d/dev-rust-engine-bootstrap.mddeleted file mode 100644index cecb9bafe7..0000000000--- a/changelog.d/dev-rust-engine-bootstrap.md+++ /dev/null@@ -1,5 +0,0 @@-**Contributors working on the Rust engine can now set up an Ubuntu machine with one command: `scripts/dev/rust-engine-bootstrap.sh` installs the pinned Bun, Postgres 16 with pgvector, Rust and the napi-rs CLI, and prints a pass/fail line per step.**--### Added-- `scripts/dev/rust-engine-bootstrap.sh`: a non-interactive, rerunnable dev setup for Ubuntu. It installs the Bun version from `package.json`, starts Postgres 16 with pgvector and a test database, installs the Rust stable toolchain and the napi-rs CLI, runs `bun install`, and writes `~/.gbrain-rust-dev.env`. It does not change gbrain itself.-- `docs/research/rust-engine/dev-environment.md`: how to run the script, what each step does, how to run the engine parity tests, measured timings and known problems.diff --git a/changelog.d/docs-bun-installer-needs-unzip.md b/changelog.d/docs-bun-installer-needs-unzip.mddeleted file mode 100644index f79e613ed6..0000000000--- a/changelog.d/docs-bun-installer-needs-unzip.md+++ /dev/null@@ -1,6 +0,0 @@-**Install guides now say Bun's installer needs `unzip`, show how to get it, and give a tested route for machines where packages can't be installed.**--### Documentation-- README.md, INSTALL_FOR_AGENTS.md, docs/INSTALL.md, AGENTS.md and the company-brain tutorial say Bun's installer stops with `error: unzip is required to install bun` when `unzip` is missing, and give the check (`command -v unzip`) and the apt, dnf and apk install commands.-- INSTALL_FOR_AGENTS.md#no-unzip is a tested route for Linux machines with no `unzip` and no package manager: it puts Bun's own build in `~/.bun/bin` using only `curl` and `tar`, and checks that `gbrain` runs from a fresh login shell.-- docs/guides/troubleshooting.md has a row for the `unzip is required` error.diff --git a/changelog.d/fix-untrack-db-only-paths-gst2964.md b/changelog.d/fix-untrack-db-only-paths-gst2964.mddeleted file mode 100644index e0b76813a9..0000000000--- a/changelog.d/fix-untrack-db-only-paths-gst2964.md+++ /dev/null@@ -1,9 +0,0 @@-**gbrain git commit-push --untrack now takes every file under a declared, ignored database-only folder, .json and other non-Markdown files included.**--### Fixed-- In a managed checkout, `gbrain git commit-push --untrack -- <folder>` refused `untrack_not_db_only` for a folder declared under `storage.db_only` and ignored by `.gitignore` when it held `.json` (or other non-Markdown) files, because each file was matched by its page slug. A file is now matched by its path under the declared folder. A Markdown page still needs its slug under the folder; a code-extension file is checked against the brain and refuses when it is a live page, when the source's strategy imports code (sync imports it as a page), when the source's last finished sync has not seen it at its current version (run `gbrain sync --source <id>`, then rerun), or when the brain cannot be read. Symlinks out of the folder, folders reached through a symlink and sibling folders that only share the name refuse. Each refusal's fix now names what is missing for that file, and `--dry-run --untrack` lists exactly the files the real run removes.-- The managed sync note about pages kept from the working tree no longer tells a page under a declared `storage.db_only` folder to be committed.-- For a source rooted in a folder of its repository (`brain/`, with `brain/gbrain.yml`), `--untrack` read the repository's top-level `gbrain.yml`: every file refused `untrack_not_db_only`, and a folder only a stray top-level `gbrain.yml` declared was admitted, so the next sync deleted its pages. In a managed checkout every untrack now reads the source's folder from the brain, read-only for at most 10 seconds, and refuses every file when the brain cannot be read. On PGLite, stop a running `gbrain serve` or sync before an untrack. The refusal names the `gbrain.yml` it read.--<!-- behavior-change: untrack_db_only_by_path_gst2964 -->-<!-- behavior-change: untrack_reads_brain_gst2964 -->diff --git a/changelog.d/fix-w18-flaky-clock-ordering.md b/changelog.d/fix-w18-flaky-clock-ordering.mddeleted file mode 100644index a7b3794bcb..0000000000--- a/changelog.d/fix-w18-flaky-clock-ordering.md+++ /dev/null@@ -1,8 +0,0 @@-**A large capture's receipt now reports the same date as the page slug it created, and five tests that failed now and then pass every run.**--### Fixed-- `gbrain capture --file` with a file over the page size limit took the slug date and the receipt's `captured_at` from two separate clock reads, so a capture that ran across UTC midnight could print a receipt dated one day for a page slug dated the next. Both now come from one timestamp. (#7980)-- The forget test for twin inline and segmented pages froze no clock, so a run that crossed UTC midnight stamped the two pages with different dates and failed. Both halves now run under one frozen time. (#8674)-- The sync dry-run test compared request rows read in no fixed order. It now orders them by id and compares whole rows, so it also catches a dry run that edits a request. (#8416)-- The private-queue recovery test gave its orphan job a 1 ms lease and relied on it running out before reconcile looked. The test now expires the lease explicitly. (#8739)-- The reranker failure test freed a random port and assumed nothing would take it again. It now points the dead endpoint at port 1, where nothing listens. (#9616)diff --git a/changelog.d/gbra574-b5-retractions.md b/changelog.d/gbra574-b5-retractions.mddeleted file mode 100644index e774fd130a..0000000000--- a/changelog.d/gbra574-b5-retractions.md+++ /dev/null@@ -1,6 +0,0 @@-**The query facts block now shows a later retraction right after the fact it calls off.**--<!-- behavior-change: facts_block_retractions_gbra574 -->--### Added-- When the facts block shows a fact about a person or company, a later fact about the same entity that retracts it or calls it off ("retracted", "scratch that", "I was wrong", "cancelled", "called off", "fell through", "never happened", "just a rumour" and similar) follows it, with its own date header, inside the block's usual share of the token budget and row count. The later fact pairs only when it is dated after the fact, its cue is not negated ("not cancelled", "wasn't called off" and "isn't a rumour" never pair), and it carries the same slot (dimension and value) or, leaving out the entity's name and the cue words, every word it has is in the fact or it shares at least two words with it. It is read under the caller's read policy, so a retraction a remote caller or another member cannot read never appears, and a forgotten or withdrawn fact never appears. No model call; a question with no such later fact gets exactly the block it got before.diff --git a/changelog.d/owner-remote-private-facts-gst2951-more.md b/changelog.d/owner-remote-private-facts-gst2951-more.mddeleted file mode 100644index 482f59065e..0000000000--- a/changelog.d/owner-remote-private-facts-gst2951-more.md+++ /dev/null@@ -1,7 +0,0 @@-**The brain owner's own remote agents now get the owner's private facts on the entity and context_pack cards, in search's facts about an entity, in the list of facts saved without an entity and in forget's similar-facts check.**--<!-- behavior-change: owner_remote_fact_reads_more_gst2951 -->--### Fixed-- The `entity` card (recent facts and `active_fact_count`) and the `context_pack` cards built from it, the entity facts and saved facts that `search` and `query` attach, `extraction_pending`'s unattributed list and `forget`'s `similar_active` decided fact visibility from the raw remote flag, so a credential bound to the brain owner got world facts only. They now use the same owner rule as recall, think and `find_trajectory`, and the owner's reads use the owner-aware page rule, so a fact from a private page the owner reads stays visible.-- Nothing widens for anyone else: another member, a labelled-only member, an unbound token, a call with no credential and the owner speaking for an audience of several read what they read before, and a private-facts grant works where it already did. Member access still applies to the owner, and withdrawn facts stay out of every read.diff --git a/changelog.d/owner-remote-private-facts-gst2951.md b/changelog.d/owner-remote-private-facts-gst2951.mddeleted file mode 100644index ca1365a28f..0000000000--- a/changelog.d/owner-remote-private-facts-gst2951.md+++ /dev/null@@ -1,9 +0,0 @@-**The brain owner's own remote agents now get the owner's private facts from trajectories, ontology reads and write attribution, as they already did from recall, query and think.**--<!-- behavior-change: owner_remote_fact_ops_gst2951 -->--### Fixed-- `find_trajectory`, `ontology_get`, `ontology_conflicts` and `volunteer_chronicle` decided fact visibility from the raw remote flag, so a credential bound to the brain owner got world facts only and a trajectory built from private facts came back empty. They now use the same owner rule as recall and think. `get_write_attribution` finds a private fact for the owner's admin credential the same way.-- The owner also gets facts taken from a private page it can read on the ontology reads and in write attribution, as `find_trajectory` and recall already allowed.-- A newer observation from a diary page no longer hides the older value behind it on `ontology_get` and `volunteer_chronicle`, and no longer makes a false conflict on `ontology_conflicts`. Diary observations are left out before each value resolves, for every remote caller, and still never reach one.-- Nothing widens for anyone else: another member, a labelled-only member, an unbound token, a call with no credential and the owner speaking for an audience of several read no private fact they did not read before. Page rules, member access and source grants still apply to the owner, and withdrawn facts stay out of every read.diff --git a/changelog.d/vorflux-dotdot-folder-names.md b/changelog.d/vorflux-dotdot-folder-names.mddeleted file mode 100644index c3812b8204..0000000000--- a/changelog.d/vorflux-dotdot-folder-names.md+++ /dev/null@@ -1,15 +0,0 @@-**Files in a folder whose name starts with two dots, such as `..drafts` or `...`, are no longer refused or reported as outside the brain by sync, git commit-push, doctor, frontmatter, skills and the other checks listed below.**--<!-- behavior-change: dotdot_folder_names_inside -->--### Fixed-- Many path checks asked "does this path start with two dots?" to catch a path that goes up and out of a folder. That question also matched a normal folder named `..drafts`, `..x` or `...`, so a file inside the brain was refused, skipped or called "outside". All of these checks now look at the first folder name exactly, through one shared helper. Remote file uploads into such a folder are still refused; a separate fix covers that check.-- `gbrain git commit-push -- ..drafts/a.md` commits the file instead of failing with "outside the checkout", and a `gbrain.sourceRoot` of `..drafts` now scopes the commit to that folder instead of being dropped (which scoped it to the whole checkout).-- Sync markers no longer report a file that was never committed as committed when the source sits in a `..` folder of its repository.-- Skill packs and the skills catalog (`get_skill`, `list_skills`) read a `SKILL.md` that sits in, or is linked to, an in-pack `..shared` folder.-- `gbrain frontmatter` expects the slug `..drafts/note` for `..drafts/note.md`, as for any other folder, instead of reporting a false slug mismatch; its backups of two `note.md` files in different `..` folders no longer overwrite each other.-- Doctor's git-writer and foreign-writer checks, brain-repo hardening (including a `core.hooksPath` of `..hooks`), the first-turn brain rule, extract-benchmark, extract-atoms transcript labels, skillpack update bases, sync applicability, fence-write and reconcile path states, and the LongMemEval call plan treat such folders as inside.-- Real escapes stay refused with the same messages as before: `../x`, an absolute path elsewhere, a sibling folder that shares the root's name prefix, a symlinked parent that points outside, and another Windows drive.--### Added-- `bun run verify` runs `check:relative-dotdot`, which refuses a new `.startsWith('..')` containment check in `src/` and points at `relativeEscapesRoot` in `src/core/path-confine.ts`.diff --git a/changelog.d/vorflux-pg-file-size-and-disconnect.md b/changelog.d/vorflux-pg-file-size-and-disconnect.mddeleted file mode 100644index 5b12fdffbf..0000000000--- a/changelog.d/vorflux-pg-file-size-and-disconnect.md+++ /dev/null@@ -1,5 +0,0 @@-**On Postgres, file records now report their size as a plain number, and closing the engine a second time no longer runs its shutdown steps again. PGLite already worked this way.**--### Fixed-- On Postgres, `getFile` and `listFilesForPage` returned `size_bytes` as a BigInt. PGLite returned a number, and the declared type is a number. Both engines now return a number. The output of the `gbrain files` CLI and the MCP file operations does not change, because those paths already converted the value.-- On Postgres, a second `disconnect()` of an engine that was already closed ran the registered shutdown hooks again. A second `disconnect()` now does nothing, as on PGLite.diff --git a/openclaw.plugin.json b/openclaw.plugin.jsonindex bf253a7b43..97cf28fe76 100644--- a/openclaw.plugin.json+++ b/openclaw.plugin.json@@ -1,7 +1,7 @@{"id": "gbrain-context-engine","name": "gbrain",- "version": "0.60.735.0",+ "version": "0.60.736.0","description": "Personal knowledge brain with Postgres + pgvector hybrid search","family": "bundle-plugin","kind": "context-engine",diff --git a/package.json b/package.jsonindex af43ea0da4..5829b2f689 100644--- a/package.json+++ b/package.json@@ -263,7 +263,7 @@"bun": ">=1.4.4"},"license": "MIT",- "version": "0.60.735.0",+ "version": "0.60.736.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.jsonindex 6b310f26ed..f1e3c854c2 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.735.0",+ "version": "0.60.736.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.jsonindex a20ee1c598..02c99fd33d 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.735.0",+ "version": "0.60.736.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.mdindex bf650a4442..c23cca16db 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.735.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.736.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.jsonindex 2f9677d4a9..06b89dab2f 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.735.0",+ "version": "0.60.736.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.jsonindex ec3a7a3101..247e3206cb 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.735.0",+ "version": "0.60.736.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.mdindex e7e8435aea..f67588539c 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.735.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.736.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.mdindex 773cc4de1e..24406bbb84 100644--- a/plugin/README.md+++ b/plugin/README.md@@ -1,4 +1,4 @@-<!-- gbrain-plugin-tree-stamp: 0.60.735.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.736.0 --># gbrain plugin skill tree (generated — do not hand-edit)This tree is the curated skill set for the gbrain Codex and Claude Codediff --git a/src/core/behavior-changes.generated.ts b/src/core/behavior-changes.generated.tsindex 19476a7e3c..ddfca0fbd2 100644--- a/src/core/behavior-changes.generated.ts+++ b/src/core/behavior-changes.generated.ts@@ -140,6 +140,14 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin{ since: '0.60.735.0', id: 'takes_extract_dry_run_needs_yes_9547', kind: 'action', text: "`gbrain takes extract --from-pages --dry-run` without `--yes` no longer sends page content to the chat model. It lists the candidate pages and counts them, reports no claim count (`claims_extracted` is null and `dry_run` is true in `--json`), and writes nothing. A script that relied on a dry run classifying claims without `--yes` now needs `--dry-run --yes`, which classifies the candidates and still writes nothing." },{ since: '0.60.735.0', id: 'auth_list_member_status_gbra593', kind: 'add', text: "gbrain auth list --json adds a member_status field to each token: enabled, disabled or removed for the member the token is bound to, missing when that member row is gone, and null for an unbound token. The status field keeps its meaning (active or revoked). The text table prints refused for an active token whose member is disabled or removed, because the brain refuses that token at verification (access_member_disabled)." },{ since: '0.60.735.0', id: 'mirror_keep_deleted', kind: 'fix', text: "On a read-only mirror source, keeping the deletion of a page whose file the upstream edited after you deleted it now sticks. gbrain repair file-drift --held --side deleted --state tombstone_edited --prefer database lists such a page keep_deleted instead of removing a file gbrain never writes, and its apply (the user's yes on the preview hash) records the decision on the hold. The hold stays and is reported carried with reason mirror_keep_deleted, with needs_human false, in gbrain sources status, gbrain sync status and doctor, so it no longer asks again on every re-check; a re-check of the same file bytes keeps the decision. A new upstream edit of the file or gbrain restore of the page makes it ask again, and purging the deleted page moves the decision to the purged_differs hold. Nothing is deleted, restored or written into the mirror. Writable sources behave as before." },+ { since: '0.60.736.0', id: 'held_private_replies_2900', kind: 'fix', text: "A world restatement of a private fact that waits for the operator's accept is now also left out of think for remote callers who cannot read the private fact, and the reply to such a held write (remember, put_page and the other page writes, their outcome and write_request copies, get_write_request and list_write_requests) no longer carries contested.proposal_ref for those callers, so it reads like a saved write. The owner's callers, the local CLI and callers who can read the private fact still get the reference. A page write whose Facts row restates a more trusted private fact about the page's own entity kept on another page, or on none, is now held like a same-page restatement until gbrain trust confirm tp<N>; like the same-page hold, that includes the owner's own local writes and sync when the private copy is more trusted. A credential with a private_facts grant reads a held row again in get_page, search and think, as before the held-row page reads, when it can read every private copy that row restates. A remote get_page or get_versions of a page stored in segments now reports a size without the held rows." },+ { since: '0.60.736.0', id: 'held_row_page_reads_2891', kind: 'fix', text: "A world fence row restating a private fact that waits for the operator's accept (a remote put_page or remember restatement) is now left out of page, chunk, search and edit reads for remote callers who cannot read that private fact: get_page (as_of and known_as_of included), get_versions bodies and diffs, fetch, search, query, search_exact, get_chunks, the entity card and the edit_page diff. Such a caller's put_page keeps the held row it could not read, restored exactly as stored. The owner's callers, the local CLI and a member reading their own member page see the page as before. A world copy of the claim saved about another entity no longer lets a remote remember skip that hold. A held row also stays private when the page is synced or rewritten, until the operator accepts it with gbrain trust confirm tp<N>. If the lookup of held rows fails, the page read fails rather than return the page, and search drops every fence row. The page file in the brain repository still holds the world cell, and restatements that were never held stay world." },+ { since: '0.60.736.0', id: 'untrack_db_only_by_path_gst2964', kind: 'fix', text: "gbrain git commit-push --untrack in a managed canonical worktree now admits a file by its path under a storage.db_only folder that gbrain.yml declares and .gitignore ignores, whatever its extension. Before, every file was matched by its page slug, so .json, .yml and other files whose slug sync flattens refused untrack_not_db_only even though their folder was declared and ignored. A Markdown page still needs its slug under a declared folder. A code-extension file (sync's code list, .json and .yml included) is checked against the brain, because on a source whose sync strategy is code or auto it is a page with a flattened slug that a database-only folder does not cover: it is admitted only when no live page comes from it and the source's strategy does not import code, refused when it is a page whatever the strategy is now or when the strategy imports it, refused when the source's last finished sync has not seen it at its current version (run gbrain sync --source <id>, then rerun the untrack), and refused when the brain cannot be read within 10 seconds (retry when it is free). A tracked symlink out of the folder, a file reached through a symlinked folder and a sibling folder that only shares the name as a prefix now refuse. Each refusal's fix names what is missing for that file. The managed sync note about pages kept from the working tree now says that pages under a declared storage.db_only folder are database-only by declaration and need nothing, instead of telling every such page to be deleted or committed." },+ { since: '0.60.736.0', id: 'untrack_reads_brain_gst2964', kind: 'breaking', text: "In a managed checkout, gbrain git commit-push --untrack now reads the brain for every file, Markdown and CSV included, to learn which folder the source is rooted in (it used to read the checkout's top-level gbrain.yml, which refused every file of a source rooted in a folder and could admit a folder only that stray file declared, whose pages the next sync deleted), so on PGLite an untrack that worked while gbrain serve or a sync held the brain now refuses untrack_not_db_only and changes nothing until that process stops." },+ { since: '0.60.736.0', id: 'facts_block_retractions_gbra574', kind: 'add', text: "The query facts block now shows a later retraction next to the fact it answers, for every caller. When the block shows a fact about a person or company, a later fact about the same entity that retracts it or calls it off (retracted, scratch that, I was wrong, cancelled, called off, fell through, not happening, never happened, no longer planned, just a rumour and similar) comes right after it, with its own date header, inside the block's usual share of the token budget and row count. It pairs only when it is dated after the fact, its cue is not negated (\"not cancelled\", \"wasn't called off\" and \"isn't a rumour\" never pair), and it carries the same slot (the same dimension and value) or, leaving out the entity's name and the cue words, every word it has is in the fact or it shares at least two words with it. It is read under the caller's read policy, so a remote caller or another member never sees a retraction it could not already read, and a forgotten or withdrawn fact never appears. There is no setting; a question with no such later fact gets exactly the block it got before." },+ { since: '0.60.736.0', id: 'owner_remote_fact_reads_more_gst2951', kind: 'fix', text: "The brain owner's own remote agents (a credential bound to the member gbrain access owner set names, speaking for itself) now get the owner's private facts on the entity card (its recent facts and its active fact count) and the context_pack cards built from it, in the facts search and query attach about the entity a query names and the saved facts matching its words, in extraction_pending's list of facts saved without an entity, and in the similar facts forget names after a withdrawal. Before, these returned only world facts to every remote caller. Every other remote caller reads what it read before: another member, a labelled-only member, an unbound token, a call with no credential and the owner's credential speaking for an audience of several still get world facts only, and a private-facts grant admits a private fact on a world page where it already did. Page rules still apply to the owner, so a fact taken from a page whose readers leave the owner out stays hidden, and withdrawn facts stay out of every read." },+ { since: '0.60.736.0', id: 'owner_remote_fact_ops_gst2951', kind: 'fix', text: "The brain owner's own remote agents (a credential bound to the member gbrain access owner set names, speaking for itself) now read the owner's private facts through find_trajectory, ontology_get, ontology_conflicts and volunteer_chronicle, and get_write_attribution now finds a private fact for the owner's admin credential, as recall, query and think already did. Facts taken from a private page the owner can read come through too. Before, these operations returned only world facts to every remote caller, so a trajectory or ontology built from private facts came back empty for the owner. Every other remote caller reads no private fact it did not read before: another member, a labelled-only member, an unbound token, a call with no credential and the owner's credential speaking for an audience of several still get world facts only, and a private-facts grant still works on find_trajectory only. Page rules still apply to the owner, so a fact taken from a page whose readers leave the owner out stays hidden, withdrawn facts stay out of every read, and ontology from life/diary pages stays redacted for remote callers. Diary observations are now left out before each value resolves, so a newer diary note no longer hides the older value a remote caller may read." },+ { since: '0.60.736.0', id: 'dotdot_folder_names_inside', kind: 'fix', text: "Files in a folder whose name starts with two dots, such as ..drafts or ..., are now treated as inside the brain by the path checks this release fixes. Before, gbrain refused or skipped them, or called them outside, at those checks. Remote file uploads into such a folder are still refused; a separate fix covers that check. Three outputs change for such folders. First, gbrain frontmatter now expects the slug ..drafts/note for ..drafts/note.md (the same rule as any other folder) instead of note. Second, an extract-atoms transcript under meetings/..drafts/ gets the meetings label instead of corpus. Third, the LongMemEval call plan records a tracked, unchanged input under a ..inputs/ folder as a pinned INPUT line instead of a PRECONDITION. A gbrain.sourceRoot of ..drafts now scopes git commit-push to that folder instead of the whole checkout. Paths that really leave the brain are still refused." },];/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */@@ -281,4 +289,12 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {takes_extract_dry_run_needs_yes_9547: '0.60.735.0',auth_list_member_status_gbra593: '0.60.735.0',mirror_keep_deleted: '0.60.735.0',+ held_private_replies_2900: '0.60.736.0',+ held_row_page_reads_2891: '0.60.736.0',+ untrack_db_only_by_path_gst2964: '0.60.736.0',+ untrack_reads_brain_gst2964: '0.60.736.0',+ facts_block_retractions_gbra574: '0.60.736.0',+ owner_remote_fact_reads_more_gst2951: '0.60.736.0',+ owner_remote_fact_ops_gst2951: '0.60.736.0',+ dotdot_folder_names_inside: '0.60.736.0',};diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.mdindex fa8dd21c99..c474bc9f3f 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.735.0 -->+<!-- gbrain-template-stamp: 0.60.736.0 -->This repository is the **"Use this template"** distribution artifact for a[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same