Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
v0.60.734.0 release (#9580)
Garry Tana278ddf45887
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex e3d875e130..c695fa354e 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "gbrain",- "version": "0.60.733.0",+ "version": "0.60.734.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 40db1ada2d..459018b5fc 100644--- a/.codex-plugin/plugin.json+++ b/.codex-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "gbrain",- "version": "0.60.733.0",+ "version": "0.60.734.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 2edf63c943..dfae426a23 100644--- a/BOOTSTRAP_FOR_AGENTS.md+++ b/BOOTSTRAP_FOR_AGENTS.md@@ -1,4 +1,4 @@-<!-- gbrain-runbook-stamp: 0.60.733.0 -->+<!-- gbrain-runbook-stamp: 0.60.734.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 8763100c81..d6f23ae204 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,6 +10,133 @@ 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.734.0] - 2026-11-17++**Repairs keep a page's safety flag or quarantine, `gbrain facts relink` keeps a fact's origin and exact dates, and consolidate no longer ends a fact because it was said again.**++### Fixed+- `gbrain repair rows-behind` and the other managed file repairs no longer strip the write gate's `instruction_like` flag or quarantine from a page. A repair now publishes through the same write gate a sync of those bytes runs, with the file's path, so an owner allow rule scoped to that path holds during a repair as it does during sync. Rows-behind and overwritten-edits comparisons ignore those database-only markers, so a flagged page is no longer reported behind its own file. Under `write_gate.external_mode=reject`, a repair of external instruction-like content now refuses with `write_gate_rejected`, as sync already holds that file, and the refusal names `gbrain trust allow --source <id> --uri-prefix <path>` (#9511).+- `gbrain facts relink` no longer re-stamps a fact's trust tier and write origin with the relink request, and no longer rounds its `valid_from` and `valid_until` to the second. The page's facts table carries the stored instant to the millisecond, so the page projection writes the same instant back. A fact stored finer than a millisecond is left unlinked and counted `claim_unfenceable` instead of being rounded (#9260).+- The upkeep consolidate step no longer ends a fact at the next copy of the same claim. A fact now ends at the next fact in its cluster that says something else, by claim text and typed value, so a restated value stays active from the date it was first stated, every copy ends together when the value changes, and a typed metric whose value changed under the same wording still ends the older value. Facts consolidated before this release keep the dates they have.++<!-- behavior-change: repair_write_gate_markers_9511 -->+<!-- behavior-change: relink_keeps_fact_instant_9260 -->+<!-- behavior-change: consolidate_restatement_stays_open -->++**New `gbrain repair open-facts` lets the operator open facts saved private before the world default, after a preview, with an undo.**++<!-- behavior-change: open_facts_repair_8194 -->++### Added+- `gbrain repair open-facts --source <id> --created-before <ISO-8601>` previews the active private facts saved before that instant, counts every fact it leaves private by reason (private, missing or quarantined pages, member pages, withdrawn, contested, expired, superseded), and `--apply --expect <hash>` opens exactly that window in place, keeping ids and trust tiers (Discussion #8194).+- Facts with no page and transcript-lane facts are listed apart and open only with `--class unpaged:<lane>`; `--ids-file` narrows the set; `--undo <ledger>` re-privates what a run opened.+- The command runs only from the CLI on the brain host: remote callers, member mode (`GBRAIN_ENFORCED_MEMBER`), `repair --all`, doctor and the remediation plan never run it. Nothing changes until an operator runs it.+- A fact made private on purpose before the cutoff is opened with the legacy ones, so read the preview or narrow the run with `--ids-file`.+- A fact with an end date (`valid_until`) in the past that was never expired or superseded is opened like a current one; a follow-up leaves it private.+- A fact whose table sits in a page's timeline is left private; a follow-up opens it.++**A remote `remember` that restates a confirmed private fact as world is now stored private until the brain's operator accepts it, as page writes to that fact's own page already were.**++<!-- behavior-change: remember_restated_private_hold_2875 -->++### Fixed+- A remote caller that remembered the exact claim of a private fact on the same entity, more trusted than itself, got a new world copy that every other connected client could read, so an agent that knew a private claim could publish it. The new fact is now stored private with a trust proposal that carries the widening; `gbrain trust review` lists it and `gbrain trust confirm tp<N>` makes it world. Remembers with no private copy on that entity, with a world copy already present, or with an explicit private visibility are unchanged.+- Two gaps remain until #9574 lands: the page that carries a held fact still shows its text to remote `get_page` and search, and a writer who first saves the same claim about a different entity is not held.++**Ten small fixes from outside reports: agent-session repair, doctor, the prompt hook, sync, transcript ingest and enrich.**++### Fixed+- `gbrain repair agent-session-facts` no longer counts sessions that already carry a speaker sidecar toward another session's repeated opening, so an owner session whose prompt was replayed by marked workers is no longer listed as ambiguous (#9521, reported and first fixed by @Masashi-Ono0611).+- `gbrain doctor --only memory_writeback` connects the database instead of reporting it unreachable (#9513, reported and first fixed by @Masashi-Ono0611).+- The Retrieval Reflex recipe's health check and setup steps run only its own doctor check, so an unrelated failing check no longer fails the integration (#9228, reported and first fixed by @johnerik).+- A facts-absorb job that finished by skipping (superseded, page missing, extraction off) no longer counts as proof the page was extracted, so a later rewrite that keeps the body still queues extraction (#9248, reported and first fixed by @Masashi-Ono0611).+- Task notifications and teammate messages no longer get the brain-first nudge, in the main prompt hook and in the turn-rule hook; prompts a person types are unchanged (#9163, reported and first fixed by @Masashi-Ono0611).+- A failed commit-ledger location lookup is retried on the next call instead of being remembered for the life of the process (#8870, reported and first fixed by @sx4im).+- `gbrain sync --all --parallel N` caps how many sources run at once, as its help says, and `--max-sources` still wins when both are given (#8951, reported and first fixed by @Masashi-Ono0611).+- `gbrain transcripts ingest` skips Claude Code's per-project `sessions-index.json` instead of reporting an unknown format on every run (#9115, reported and first fixed by @Masashi-Ono0611).+- The autopilot-install doctor test names its installer target, so on macOS it can no longer load a real LaunchAgent (#9545, reported and first fixed by @Kkkkkuro).+- `gbrain enrich` stops asking the provider for a prompt cache, because its system prompt is below the smallest cacheable prefix and the cache was written on every call but never read (#9541, reported and first fixed by @mattverlaque).++**`gbrain repair agent-session-facts` finishes its preview on brains with tens of thousands of saved facts, and `gbrain setup claude-code` no longer fails its re-run after Claude Code rewrites its settings file.**++### Fixed+- `gbrain repair agent-session-facts` (and doctor's `agent_session_facts` check) no longer times out on a large brain. The preview fingerprinted the source's facts once for every user-attributed fact saved from a session, before it knew whether that session was an agent's; it now looks for the owner's own copy only for facts whose session it already judged evidenced or ambiguous, using the existing fingerprint index, and it reads each take's contributing facts in one pass instead of one lookup per take. On a generated brain with 143,640 facts and 7,045 sessions the preview went from a statement timeout to about 1.5 seconds (#9503).+- `gbrain setup claude-code` re-run no longer exits 1 with `turn_hook_not_loaded` (and doctor's `harness_wiring` no longer warns) when Claude Code has rewritten `~/.claude/settings.json` without the `_gbrain` key on gbrain's hook entries. The per-turn hook check now recognises an entry the setup receipt owns, the same way setup itself does (#9505).+- `gbrain errors migration_host_work_owed` explains the doctor warning instead of printing "Unknown error code".+- `gbrain sources git-reconcile` treats a git command that ran past its time limit or was killed from outside (`git_command_stopped`) as a retryable failure (exit 4) instead of asking the user (exit 1). A git command stopped by its output limit or by a git crash still asks the user, since a retry stops the same way.+- `gbrain git commit-push` refuses with `git_unavailable` when it cannot list conflicted files, instead of reading a failed listing as "no conflicts". A write-through file refused for unresolved conflicts is kept in the pending ledger, so doctor reports it and `--pending` retries it, while later write-throughs still commit the ledger's other files, and the advice now says to keep the changes from both sides rather than to pick one side, since one side may be a write gbrain made.+- A git child that crashes (SIGSEGV, SIGBUS, SIGILL, SIGFPE or SIGABRT) is reported as a crash with a `git fsck` suggestion, not as a kill from outside gbrain, and output too large for one string is reported as `git_command_stopped` (`output_limit`) instead of an empty listing.++### Tests and CI+- The unit suite runs on 36 shards instead of 34, with refreshed shard weights, which brings the predicted time per shard from about 595 s to about 562 s.+- A test now covers `scripts/check-migration-projection.ts` and its baseline, and macOS 26 validation records the tree it tested so a passed run can stand as evidence for the same tree.++<!-- behavior-change: setup_turn_hook_unmarked_9505 -->+<!-- behavior-change: git_reconcile_stopped_retryable -->++**`gbrain frontmatter validate` checks every path you give it, and doctor, `gbrain serve --http`, the update check and the agent-session repair each get a small fix.**++### Fixed+- `gbrain frontmatter validate a.md b.md` validated only the last path and could report ok for a bad file named earlier. It now checks every path, walks each directory, checks a file named twice once, refuses before checking anything when a path is missing, and lists the paths as `targets` in `--json` when there is more than one.+- Doctor no longer tells you to run `gbrain sync` for a gbrain-owned content folder on a brain with persistence off, which sync refuses. The check still fails, and it now names the `gbrain import` command that works for that folder.+- `gbrain transcripts archive status` says when `maintenance.auto` is false, because free upkeep then doesn't archive conversations by itself (an installed autopilot still does). The line names `gbrain transcripts archive run`.+- `gbrain serve --http` no longer treats a request refused for a missing or wrong token as activity, so unauthenticated traffic can't keep idle upkeep from running (#9484).+- If your computer's clock moved backwards, the update check no longer goes quiet. A saved answer stamped more than 5 minutes in the future counts as stale and is replaced, so a notice that your version was withdrawn still reaches you (#8795, also reported in #9157).+- `gbrain repair agent-session-facts` reads only the listed sources' facts when it looks up takes, so its cost follows the source instead of the whole brain.++<!-- behavior-change: frontmatter_validate_every_path -->+<!-- behavior-change: serve_http_refused_not_activity_9484 -->+<!-- behavior-change: update_cache_future_stamp_8795 -->++**Local searches on a very common word no longer spend the keyword time limit in the title step.**++### Fixed+- The title step of hybrid search now ranks at most 5,000 matching pages for local callers, the ones with the lowest page ids, so the cut keeps the same pages on every call. A word that sits in many page timelines used to make it rank every matching page and run into the 8 s keyword statement limit on a large brain, a second time after the keyword step (#7082). When the cut applies, pages whose title holds the words come first and hybrid search reports `keyword_candidates_incomplete`. A query that matches 5,000 pages or fewer keeps its exact result, including a page found only through a timeline row that no chunk holds. Remote callers' results do not change.++<!-- behavior-change: title_arm_candidate_cap_7082 -->++**A restricted Postgres write role can no longer save purged or withdrawn content again by lacking a read policy on the purge and withdrawal ledgers: the guard now refuses the write with a message naming the policy to add.**++<!-- behavior-change: guard_ledgers_fail_closed_7632 -->++### Fixed+- The seven purge and withdrawal guard triggers (facts, takes, pages, segment derivations and the derivation sweep's scope note) read their ledgers as the writing role. A role with write policies on the guarded table but no policy on the ledger read it as empty, so a purged claim, take, page or derivation could be stored again while the purge reported done, and a withdrawn fact could be saved or set active again. Each guard now refuses such a role with `writer_coordinator_required` (`unreadable_state`), the same refusal the writer fences and derived-state maintainers use, and its hint names the table and the docs/ENGINES.md recipe. The guards keep running with the writer's own rights (no SECURITY DEFINER). Migration v318 applies it to existing brains. Owners, roles that bypass row-level security and PGLite see no change. (#7632, #7659)+- After upgrading on Postgres, check the guards. v318 can only replace a guard function the migrating role owns. One owned by another role stays fail-open, and v318 names it in a single stderr line starting `guards:`. docs/ENGINES.md ("Purge and withdrawal guards") has a query that lists the seven guards and whether each now fails closed. For any that doesn't, its owner runs `ALTER FUNCTION public.<name>() OWNER TO <the role gbrain migrates as>`, then `gbrain apply-migrations --yes` (or the next gbrain start) replaces it.++**A purged claim no longer comes back as a page's change reason when a sync publishes after the purge.**++### Fixed+- A sync reads each page's change reason from its `gbrain-reason` commit trailer before it saves the page. If a fact purge committed in between, the saved page history still stored the purged text as that page's reason. The save now checks the purge's tombstone for the exact commit and file when it writes the history row, so the reason is stored empty, while the page content still imports and other files' reasons from the same commit are kept. This applies to classic and managed sync (#8635, #8591).++<!-- behavior-change: purged_change_reason_8635 -->++**A large read-only mirror source whose sync passes only re-check old holds no longer parks as `pass_abandoned` with nothing settled, and its status and repair output now say what is actually held.**++### Fixed+- A sync pass that stopped while it re-checked old holds now counts as progress when it cleared a hold's re-check trigger, so a few such passes no longer build the abandoned streak. Passes that re-check the same holds every time (slug conflicts) still end `pass_abandoned`, and so do passes that only re-hold a page edited again before each of them: once that hold has been held three times, `gbrain sync status` reports `needs_human: true` with that page's own decision.+- A pass now reads the earlier Git versions of the held pages it re-checks one batch at a time, just before that batch commits, instead of for the whole round before its first commit. On a source with many such holds the first commit came only after the whole history read.+- `gbrain sync status` leads with the pass's own next step when the holds are not what stops the source, and `next.why` for `pass_interrupted` and `pass_abandoned` names the step the stopped pass was last seen in (the level read, or the history read with how far it got).+- On a read-only mirror, `gbrain repair file-drift --held` compares each held page with its file. A differing page reads `prefer_file` or `needs_human` with its evidence, a matching one `release_hold`, and only a page whose file is gone reads `no_drift` with `database_only`. The comparison still writes nothing.+- A windowed held dry run reports `complete: false` while held pages remain past its window, and `details.window.next_command` names the next window.+- `gbrain sources status --json` counts `git_holds.by_code` over every hold of the source, not only the listed ones.++Larger sources still need a per-class decision flow for their held pages; this change only makes the counts and the comparison true.++<!-- behavior-change: mirror_compare_reads_file_gst2843 -->+<!-- behavior-change: held_compare_complete_window_gst2843 -->+<!-- behavior-change: hold_by_code_counts_all_gst2843 -->++**Saved facts in query results now say when they were said, collapse their copies, match on word stems, and end at the right date when replaced.**++<!-- behavior-change: fact_rows_observed_date_gbra574 -->+<!-- behavior-change: superseded_fact_valid_until_gbra574 -->++### Fixed+- The facts block, temporal fact reserve, facts arm and recall date headers print the observed date of the page each fact came from, read under the caller's page access; a failed read reports `fact_observed_date_unavailable` instead of a silent `observed unknown`.+- Copies of one claim take one row in the facts block (dated as first stated, `(stated N times, last DATE)`), so restated facts stop crowding out older values; facts that differ by one word keep their rows.+- Question ranking of saved facts matches on stems under the brain's full-text config (an exact word still ranks above a stem-only match) and ignores dates, years and auxiliary verbs, so an as-of question admits the facts it names and a fact sharing only a year with the question is not admitted.+- Every supersession writer ends the replaced fact by one rule. It ends on the newer fact's `valid_from` when it falls inside the older fact's window, else at the older fact's own earlier end or now, and never before the older fact began. New writes only.+## [0.60.733.0] - 2026-11-16**`gbrain transcripts archive` no longer has a day page refused by the write gate over its name, and a run exits 1 exactly when its `errors` list is not empty.**diff --git a/VERSION b/VERSIONindex 18acb48e59..62f5def954 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-0.60.733.0+0.60.734.0diff --git a/changelog.d/capy-data-integrity-9511-9260-consolidate.md b/changelog.d/capy-data-integrity-9511-9260-consolidate.mddeleted file mode 100644index c3a75420a7..0000000000--- a/changelog.d/capy-data-integrity-9511-9260-consolidate.md+++ /dev/null@@ -1,13 +0,0 @@-----important: data-loss-----**Repairs keep a page's safety flag or quarantine, `gbrain facts relink` keeps a fact's origin and exact dates, and consolidate no longer ends a fact because it was said again.**--### Fixed-- `gbrain repair rows-behind` and the other managed file repairs no longer strip the write gate's `instruction_like` flag or quarantine from a page. A repair now publishes through the same write gate a sync of those bytes runs, with the file's path, so an owner allow rule scoped to that path holds during a repair as it does during sync. Rows-behind and overwritten-edits comparisons ignore those database-only markers, so a flagged page is no longer reported behind its own file. Under `write_gate.external_mode=reject`, a repair of external instruction-like content now refuses with `write_gate_rejected`, as sync already holds that file, and the refusal names `gbrain trust allow --source <id> --uri-prefix <path>` (#9511).-- `gbrain facts relink` no longer re-stamps a fact's trust tier and write origin with the relink request, and no longer rounds its `valid_from` and `valid_until` to the second. The page's facts table carries the stored instant to the millisecond, so the page projection writes the same instant back. A fact stored finer than a millisecond is left unlinked and counted `claim_unfenceable` instead of being rounded (#9260).-- The upkeep consolidate step no longer ends a fact at the next copy of the same claim. A fact now ends at the next fact in its cluster that says something else, by claim text and typed value, so a restated value stays active from the date it was first stated, every copy ends together when the value changes, and a typed metric whose value changed under the same wording still ends the older value. Facts consolidated before this release keep the dates they have.--<!-- behavior-change: repair_write_gate_markers_9511 -->-<!-- behavior-change: relink_keeps_fact_instant_9260 -->-<!-- behavior-change: consolidate_restatement_stays_open -->diff --git a/changelog.d/capy-open-legacy-private-facts.md b/changelog.d/capy-open-legacy-private-facts.mddeleted file mode 100644index 88d9363d19..0000000000--- a/changelog.d/capy-open-legacy-private-facts.md+++ /dev/null@@ -1,11 +0,0 @@-**New `gbrain repair open-facts` lets the operator open facts saved private before the world default, after a preview, with an undo.**--<!-- behavior-change: open_facts_repair_8194 -->--### Added-- `gbrain repair open-facts --source <id> --created-before <ISO-8601>` previews the active private facts saved before that instant, counts every fact it leaves private by reason (private, missing or quarantined pages, member pages, withdrawn, contested, expired, superseded), and `--apply --expect <hash>` opens exactly that window in place, keeping ids and trust tiers (Discussion #8194).-- Facts with no page and transcript-lane facts are listed apart and open only with `--class unpaged:<lane>`; `--ids-file` narrows the set; `--undo <ledger>` re-privates what a run opened.-- The command runs only from the CLI on the brain host: remote callers, member mode (`GBRAIN_ENFORCED_MEMBER`), `repair --all`, doctor and the remediation plan never run it. Nothing changes until an operator runs it.-- A fact made private on purpose before the cutoff is opened with the legacy ones, so read the preview or narrow the run with `--ids-file`.-- A fact with an end date (`valid_until`) in the past that was never expired or superseded is opened like a current one; a follow-up leaves it private.-- A fact whose table sits in a page's timeline is left private; a follow-up opens it.diff --git a/changelog.d/capy-remote-remember-private-restate-hold.md b/changelog.d/capy-remote-remember-private-restate-hold.mddeleted file mode 100644index ffda02485b..0000000000--- a/changelog.d/capy-remote-remember-private-restate-hold.md+++ /dev/null@@ -1,10 +0,0 @@-----important: security-----**A remote `remember` that restates a confirmed private fact as world is now stored private until the brain's operator accepts it, as page writes to that fact's own page already were.**--<!-- behavior-change: remember_restated_private_hold_2875 -->--### Fixed-- A remote caller that remembered the exact claim of a private fact on the same entity, more trusted than itself, got a new world copy that every other connected client could read, so an agent that knew a private claim could publish it. The new fact is now stored private with a trust proposal that carries the widening; `gbrain trust review` lists it and `gbrain trust confirm tp<N>` makes it world. Remembers with no private copy on that entity, with a world copy already present, or with an explicit private visibility are unchanged.-- Two gaps remain until #9574 lands: the page that carries a held fact still shows its text to remote `get_page` and search, and a writer who first saves the same claim about a different entity is not held.diff --git a/changelog.d/capy-small-fix-wave-1.md b/changelog.d/capy-small-fix-wave-1.mddeleted file mode 100644index 1400bc6798..0000000000--- a/changelog.d/capy-small-fix-wave-1.md+++ /dev/null@@ -1,13 +0,0 @@-**Ten small fixes from outside reports: agent-session repair, doctor, the prompt hook, sync, transcript ingest and enrich.**--### Fixed-- `gbrain repair agent-session-facts` no longer counts sessions that already carry a speaker sidecar toward another session's repeated opening, so an owner session whose prompt was replayed by marked workers is no longer listed as ambiguous (#9521, reported and first fixed by @Masashi-Ono0611).-- `gbrain doctor --only memory_writeback` connects the database instead of reporting it unreachable (#9513, reported and first fixed by @Masashi-Ono0611).-- The Retrieval Reflex recipe's health check and setup steps run only its own doctor check, so an unrelated failing check no longer fails the integration (#9228, reported and first fixed by @johnerik).-- A facts-absorb job that finished by skipping (superseded, page missing, extraction off) no longer counts as proof the page was extracted, so a later rewrite that keeps the body still queues extraction (#9248, reported and first fixed by @Masashi-Ono0611).-- Task notifications and teammate messages no longer get the brain-first nudge, in the main prompt hook and in the turn-rule hook; prompts a person types are unchanged (#9163, reported and first fixed by @Masashi-Ono0611).-- A failed commit-ledger location lookup is retried on the next call instead of being remembered for the life of the process (#8870, reported and first fixed by @sx4im).-- `gbrain sync --all --parallel N` caps how many sources run at once, as its help says, and `--max-sources` still wins when both are given (#8951, reported and first fixed by @Masashi-Ono0611).-- `gbrain transcripts ingest` skips Claude Code's per-project `sessions-index.json` instead of reporting an unknown format on every run (#9115, reported and first fixed by @Masashi-Ono0611).-- The autopilot-install doctor test names its installer target, so on macOS it can no longer load a real LaunchAgent (#9545, reported and first fixed by @Kkkkkuro).-- `gbrain enrich` stops asking the provider for a prompt cache, because its system prompt is below the smallest cacheable prefix and the cache was written on every call but never read (#9541, reported and first fixed by @mattverlaque).diff --git a/changelog.d/capy-small-fix-wave-5.md b/changelog.d/capy-small-fix-wave-5.mddeleted file mode 100644index ecdd67eeed..0000000000--- a/changelog.d/capy-small-fix-wave-5.md+++ /dev/null@@ -1,16 +0,0 @@-**`gbrain repair agent-session-facts` finishes its preview on brains with tens of thousands of saved facts, and `gbrain setup claude-code` no longer fails its re-run after Claude Code rewrites its settings file.**--### Fixed-- `gbrain repair agent-session-facts` (and doctor's `agent_session_facts` check) no longer times out on a large brain. The preview fingerprinted the source's facts once for every user-attributed fact saved from a session, before it knew whether that session was an agent's; it now looks for the owner's own copy only for facts whose session it already judged evidenced or ambiguous, using the existing fingerprint index, and it reads each take's contributing facts in one pass instead of one lookup per take. On a generated brain with 143,640 facts and 7,045 sessions the preview went from a statement timeout to about 1.5 seconds (#9503).-- `gbrain setup claude-code` re-run no longer exits 1 with `turn_hook_not_loaded` (and doctor's `harness_wiring` no longer warns) when Claude Code has rewritten `~/.claude/settings.json` without the `_gbrain` key on gbrain's hook entries. The per-turn hook check now recognises an entry the setup receipt owns, the same way setup itself does (#9505).-- `gbrain errors migration_host_work_owed` explains the doctor warning instead of printing "Unknown error code".-- `gbrain sources git-reconcile` treats a git command that ran past its time limit or was killed from outside (`git_command_stopped`) as a retryable failure (exit 4) instead of asking the user (exit 1). A git command stopped by its output limit or by a git crash still asks the user, since a retry stops the same way.-- `gbrain git commit-push` refuses with `git_unavailable` when it cannot list conflicted files, instead of reading a failed listing as "no conflicts". A write-through file refused for unresolved conflicts is kept in the pending ledger, so doctor reports it and `--pending` retries it, while later write-throughs still commit the ledger's other files, and the advice now says to keep the changes from both sides rather than to pick one side, since one side may be a write gbrain made.-- A git child that crashes (SIGSEGV, SIGBUS, SIGILL, SIGFPE or SIGABRT) is reported as a crash with a `git fsck` suggestion, not as a kill from outside gbrain, and output too large for one string is reported as `git_command_stopped` (`output_limit`) instead of an empty listing.--### Tests and CI-- The unit suite runs on 36 shards instead of 34, with refreshed shard weights, which brings the predicted time per shard from about 595 s to about 562 s.-- A test now covers `scripts/check-migration-projection.ts` and its baseline, and macOS 26 validation records the tree it tested so a passed run can stand as evidence for the same tree.--<!-- behavior-change: setup_turn_hook_unmarked_9505 -->-<!-- behavior-change: git_reconcile_stopped_retryable -->diff --git a/changelog.d/capy-small-fix-wave-6.md b/changelog.d/capy-small-fix-wave-6.mddeleted file mode 100644index 9f499da605..0000000000--- a/changelog.d/capy-small-fix-wave-6.md+++ /dev/null@@ -1,13 +0,0 @@-**`gbrain frontmatter validate` checks every path you give it, and doctor, `gbrain serve --http`, the update check and the agent-session repair each get a small fix.**--### Fixed-- `gbrain frontmatter validate a.md b.md` validated only the last path and could report ok for a bad file named earlier. It now checks every path, walks each directory, checks a file named twice once, refuses before checking anything when a path is missing, and lists the paths as `targets` in `--json` when there is more than one.-- Doctor no longer tells you to run `gbrain sync` for a gbrain-owned content folder on a brain with persistence off, which sync refuses. The check still fails, and it now names the `gbrain import` command that works for that folder.-- `gbrain transcripts archive status` says when `maintenance.auto` is false, because free upkeep then doesn't archive conversations by itself (an installed autopilot still does). The line names `gbrain transcripts archive run`.-- `gbrain serve --http` no longer treats a request refused for a missing or wrong token as activity, so unauthenticated traffic can't keep idle upkeep from running (#9484).-- If your computer's clock moved backwards, the update check no longer goes quiet. A saved answer stamped more than 5 minutes in the future counts as stale and is replaced, so a notice that your version was withdrawn still reaches you (#8795, also reported in #9157).-- `gbrain repair agent-session-facts` reads only the listed sources' facts when it looks up takes, so its cost follows the source instead of the whole brain.--<!-- behavior-change: frontmatter_validate_every_path -->-<!-- behavior-change: serve_http_refused_not_activity_9484 -->-<!-- behavior-change: update_cache_future_stamp_8795 -->diff --git a/changelog.d/capy-title-arm-candidate-cap.md b/changelog.d/capy-title-arm-candidate-cap.mddeleted file mode 100644index 5b4bf2c868..0000000000--- a/changelog.d/capy-title-arm-candidate-cap.md+++ /dev/null@@ -1,6 +0,0 @@-**Local searches on a very common word no longer spend the keyword time limit in the title step.**--### Fixed-- The title step of hybrid search now ranks at most 5,000 matching pages for local callers, the ones with the lowest page ids, so the cut keeps the same pages on every call. A word that sits in many page timelines used to make it rank every matching page and run into the 8 s keyword statement limit on a large brain, a second time after the keyword step (#7082). When the cut applies, pages whose title holds the words come first and hybrid search reports `keyword_candidates_incomplete`. A query that matches 5,000 pages or fewer keeps its exact result, including a page found only through a timeline row that no chunk holds. Remote callers' results do not change.--<!-- behavior-change: title_arm_candidate_cap_7082 -->diff --git a/changelog.d/fix-guard-ledgers-fail-closed-7632.md b/changelog.d/fix-guard-ledgers-fail-closed-7632.mddeleted file mode 100644index 85efa046cd..0000000000--- a/changelog.d/fix-guard-ledgers-fail-closed-7632.md+++ /dev/null@@ -1,10 +0,0 @@-----important: security-----**A restricted Postgres write role can no longer save purged or withdrawn content again by lacking a read policy on the purge and withdrawal ledgers: the guard now refuses the write with a message naming the policy to add.**--<!-- behavior-change: guard_ledgers_fail_closed_7632 -->--### Fixed-- The seven purge and withdrawal guard triggers (facts, takes, pages, segment derivations and the derivation sweep's scope note) read their ledgers as the writing role. A role with write policies on the guarded table but no policy on the ledger read it as empty, so a purged claim, take, page or derivation could be stored again while the purge reported done, and a withdrawn fact could be saved or set active again. Each guard now refuses such a role with `writer_coordinator_required` (`unreadable_state`), the same refusal the writer fences and derived-state maintainers use, and its hint names the table and the docs/ENGINES.md recipe. The guards keep running with the writer's own rights (no SECURITY DEFINER). Migration v318 applies it to existing brains. Owners, roles that bypass row-level security and PGLite see no change. (#7632, #7659)-- After upgrading on Postgres, check the guards. v318 can only replace a guard function the migrating role owns. One owned by another role stays fail-open, and v318 names it in a single stderr line starting `guards:`. docs/ENGINES.md ("Purge and withdrawal guards") has a query that lists the seven guards and whether each now fails closed. For any that doesn't, its owner runs `ALTER FUNCTION public.<name>() OWNER TO <the role gbrain migrates as>`, then `gbrain apply-migrations --yes` (or the next gbrain start) replaces it.diff --git a/changelog.d/fix-purged-change-reason-8635.md b/changelog.d/fix-purged-change-reason-8635.mddeleted file mode 100644index 937a4c4fc5..0000000000--- a/changelog.d/fix-purged-change-reason-8635.md+++ /dev/null@@ -1,9 +0,0 @@-----important: security-----**A purged claim no longer comes back as a page's change reason when a sync publishes after the purge.**--### Fixed-- A sync reads each page's change reason from its `gbrain-reason` commit trailer before it saves the page. If a fact purge committed in between, the saved page history still stored the purged text as that page's reason. The save now checks the purge's tombstone for the exact commit and file when it writes the history row, so the reason is stored empty, while the page content still imports and other files' reasons from the same commit are kept. This applies to classic and managed sync (#8635, #8591).--<!-- behavior-change: purged_change_reason_8635 -->diff --git a/changelog.d/gbra-568-mirror-parked.md b/changelog.d/gbra-568-mirror-parked.mddeleted file mode 100644index 136aefdebc..0000000000--- a/changelog.d/gbra-568-mirror-parked.md+++ /dev/null@@ -1,15 +0,0 @@-**A large read-only mirror source whose sync passes only re-check old holds no longer parks as `pass_abandoned` with nothing settled, and its status and repair output now say what is actually held.**--### Fixed-- A sync pass that stopped while it re-checked old holds now counts as progress when it cleared a hold's re-check trigger, so a few such passes no longer build the abandoned streak. Passes that re-check the same holds every time (slug conflicts) still end `pass_abandoned`, and so do passes that only re-hold a page edited again before each of them: once that hold has been held three times, `gbrain sync status` reports `needs_human: true` with that page's own decision.-- A pass now reads the earlier Git versions of the held pages it re-checks one batch at a time, just before that batch commits, instead of for the whole round before its first commit. On a source with many such holds the first commit came only after the whole history read.-- `gbrain sync status` leads with the pass's own next step when the holds are not what stops the source, and `next.why` for `pass_interrupted` and `pass_abandoned` names the step the stopped pass was last seen in (the level read, or the history read with how far it got).-- On a read-only mirror, `gbrain repair file-drift --held` compares each held page with its file. A differing page reads `prefer_file` or `needs_human` with its evidence, a matching one `release_hold`, and only a page whose file is gone reads `no_drift` with `database_only`. The comparison still writes nothing.-- A windowed held dry run reports `complete: false` while held pages remain past its window, and `details.window.next_command` names the next window.-- `gbrain sources status --json` counts `git_holds.by_code` over every hold of the source, not only the listed ones.--Larger sources still need a per-class decision flow for their held pages; this change only makes the counts and the comparison true.--<!-- behavior-change: mirror_compare_reads_file_gst2843 -->-<!-- behavior-change: held_compare_complete_window_gst2843 -->-<!-- behavior-change: hold_by_code_counts_all_gst2843 -->diff --git a/changelog.d/gbra574-dated-facts-wave-a.md b/changelog.d/gbra574-dated-facts-wave-a.mddeleted file mode 100644index acbe5d469e..0000000000--- a/changelog.d/gbra574-dated-facts-wave-a.md+++ /dev/null@@ -1,10 +0,0 @@-**Saved facts in query results now say when they were said, collapse their copies, match on word stems, and end at the right date when replaced.**--<!-- behavior-change: fact_rows_observed_date_gbra574 -->-<!-- behavior-change: superseded_fact_valid_until_gbra574 -->--### Fixed-- The facts block, temporal fact reserve, facts arm and recall date headers print the observed date of the page each fact came from, read under the caller's page access; a failed read reports `fact_observed_date_unavailable` instead of a silent `observed unknown`.-- Copies of one claim take one row in the facts block (dated as first stated, `(stated N times, last DATE)`), so restated facts stop crowding out older values; facts that differ by one word keep their rows.-- Question ranking of saved facts matches on stems under the brain's full-text config (an exact word still ranks above a stem-only match) and ignores dates, years and auxiliary verbs, so an as-of question admits the facts it names and a fact sharing only a year with the question is not admitted.-- Every supersession writer ends the replaced fact by one rule. It ends on the newer fact's `valid_from` when it falls inside the older fact's window, else at the older fact's own earlier end or now, and never before the older fact began. New writes only.diff --git a/openclaw.plugin.json b/openclaw.plugin.jsonindex 7c843d745e..c904163fbe 100644--- a/openclaw.plugin.json+++ b/openclaw.plugin.json@@ -1,7 +1,7 @@{"id": "gbrain-context-engine","name": "gbrain",- "version": "0.60.733.0",+ "version": "0.60.734.0","description": "Personal knowledge brain with Postgres + pgvector hybrid search","family": "bundle-plugin","kind": "context-engine",diff --git a/package.json b/package.jsonindex ca90cef6c9..3ed8667097 100644--- a/package.json+++ b/package.json@@ -262,7 +262,7 @@"bun": ">=1.4.4"},"license": "MIT",- "version": "0.60.733.0",+ "version": "0.60.734.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 1a00ae9686..fd17b12c0b 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.733.0",+ "version": "0.60.734.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 5f8d7cff1b..70bef5654f 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.733.0",+ "version": "0.60.734.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 14acdd9525..8f29e4d302 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.733.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.734.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 354d6a671a..68d4351196 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.733.0",+ "version": "0.60.734.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 a5359fae25..b87e0bac24 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.733.0",+ "version": "0.60.734.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 0a7f4065ea..98c24c6dd8 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.733.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.734.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 324650b7ed..f392c1a46b 100644--- a/plugin/README.md+++ b/plugin/README.md@@ -1,4 +1,4 @@-<!-- gbrain-plugin-tree-stamp: 0.60.733.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.734.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 c90593c76e..bc41bd26bd 100644--- a/src/core/behavior-changes.generated.ts+++ b/src/core/behavior-changes.generated.ts@@ -98,6 +98,24 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin{ since: '0.60.733.0', id: 'atom_retirement_keeps_tier_9456', kind: 'fix', text: "An atom a re-extraction retires now keeps the trust tier and write origin its extraction gave it, and an atom a later extraction produces again comes back at that tier. The retirement used to store the atom as unknown with no origin, so a revived atom stayed unknown. The same holds for every page a derived writer retires (chronicle events, synthesis outputs, gbrain repair stale-atoms). Atoms retired before this release keep the tier they were stored with." },{ since: '0.60.733.0', id: 'provider_response_unparseable_9466', kind: 'fix', text: "A model provider that answers with a success status and a body that is not one JSON document (a route that streams when a request omits stream is the common cause) now fails with the non-retryable code provider_response_unparseable instead of a transient error. A facts job that hits it ends on its first attempt instead of retrying the same paid call, gbrain facts retry-dead does not resubmit it, and its recorded error reads cause=AIConfigError provider_response_unparseable. No response text is kept. Fix the route, for example with gbrain config set provider_chat_options.<provider>:<model> '{\"stream\": false}', then retry the job." },{ since: '0.60.733.0', id: 'sync_freshness_content_directory_9471', kind: 'fix', text: "gbrain doctor's sync_freshness no longer fails a source whose folder sits inside gbrain's own content directory (for example one added beside the default source with gbrain sources add) and no longer tells you to run gbrain sync for it, a command that refuses such a source with sync_not_applicable. It counts the source as a content directory where sync does not apply and names gbrain import <dir> --source <id> for adding files instead." },+ { since: '0.60.734.0', id: 'repair_write_gate_markers_9511', kind: 'breaking', text: "Managed file repairs (gbrain repair rows-behind, file-drift, frontmatter, slug-conflicts, fence repair and local-edit adoption) now run the write gate a sync of the same file runs, with the file's path, so they keep a page's instruction_like flag or quarantine instead of stripping it, and an owner allow rule scoped to that path holds during the repair. Under write_gate.external_mode=reject, a repair of external instruction-like content now refuses with write_gate_rejected, the way sync already holds that file, instead of publishing it. If a repair refuses this way and you trust the file, allow it with gbrain trust allow --source <id> --uri-prefix <path>, or edit the file, then preview and apply the repair again; nothing was written." },+ { since: '0.60.734.0', id: 'relink_keeps_fact_instant_9260', kind: 'fix', text: "gbrain facts relink no longer changes a linked fact's trust tier or write origin, and no longer rounds its valid_from and valid_until to the second; the entity page's facts table keeps the stored instant to the millisecond. A fact whose stored instant is finer than a millisecond (only raw SQL or a database clock default writes one) is now left unlinked and counted claim_unfenceable instead of being linked with rounded dates. Facts linked before this release keep the dates they have." },+ { since: '0.60.734.0', id: 'consolidate_restatement_stays_open', kind: 'fix', text: "The consolidate upkeep step now ends a fact only at the next fact in its cluster that says something else, by claim text and typed value. A value restated on a later date stays active from the date it was first stated, and every restated copy ends together when the value changes. Before, each copy ended at the next copy's date, so the date a value was first stated was no longer on any active row. Facts consolidated before this release keep the dates they have." },+ { since: '0.60.734.0', id: 'open_facts_repair_8194', kind: 'add', text: "New command: gbrain repair open-facts opens facts that were saved private before facts.default_visibility became world, so remote callers that are not the brain owner can recall them. Nothing changes until the operator runs it on the brain host: preview with gbrain repair open-facts --source <id> --created-before <ISO-8601>, then apply exactly that preview with --apply --expect <hash>. Facts on private, member or quarantined pages, withdrawn, contested, expired or superseded facts stay private and are counted by reason. Each change is recorded in ~/.gbrain/repair/open-facts/, and --undo <ledger> makes the opened facts private again (what was already read stays read)." },+ { since: '0.60.734.0', id: 'remember_restated_private_hold_2875', kind: 'fix', text: "A remote remember of the exact claim of a private fact on the same entity that is more trusted than the caller is now stored private with a trust proposal, instead of as a world copy other connected clients could read. The operator lists it with gbrain trust review and makes it world with gbrain trust confirm tp<N>. Other remembers are unchanged." },+ { since: '0.60.734.0', id: 'setup_turn_hook_unmarked_9505', kind: 'fix', text: "gbrain setup claude-code no longer exits 1 with turn_hook_not_loaded on a re-run, and doctor's harness_wiring no longer warns that the per-turn hook is missing, when Claude Code has rewritten ~/.claude/settings.json and dropped the _gbrain key from gbrain's hook entries. The check now recognises a hook entry that gbrain setup wrote (its setup receipt owns the entry) with or without that key. Nothing to do after upgrading; if you saw the warning, your hook was already working." },+ { since: '0.60.734.0', id: 'git_reconcile_stopped_retryable', kind: 'fix', text: "gbrain sources git-reconcile now reports a source whose commit-push stopped with git_command_stopped because a git command ran past its time limit or was killed from outside as failed and retryable, exit 4, instead of needs_user, exit 1. A script that retries on exit 4 now retries it. A git command stopped by its output limit, or one that crashed (SIGSEGV, SIGBUS, SIGILL, SIGFPE or SIGABRT), still reports needs_user, exit 1, because a retry stops the same way." },+ { since: '0.60.734.0', id: 'frontmatter_validate_every_path', kind: 'fix', text: "gbrain frontmatter validate now checks every path it is given. With several paths it used to check only the last one, so a bad file named earlier could pass with exit 0. It now checks all of them, exits 1 if any fails, and refuses before checking anything when a path does not exist. With --json and more than one path, the output adds a targets list." },+ { since: '0.60.734.0', id: 'serve_http_refused_not_activity_9484', kind: 'fix', text: "gbrain serve --http no longer counts a request refused for a missing or wrong bearer token as activity. Idle upkeep waits for a quiet interval, and requests anyone could send without a token used to reset that interval, so upkeep might never run. Authenticated requests, including pings, still count as before." },+ { since: '0.60.734.0', id: 'update_cache_future_stamp_8795', kind: 'fix', text: "The update check no longer trusts a saved answer stamped in the future. After a computer's clock moved backwards, the saved answer could stay \"fresh\" and block every refresh, which hid newer releases and a withdrawn-release notice. A saved answer more than 5 minutes ahead of the clock is now stale and is replaced on the next check." },+ { since: '0.60.734.0', id: 'title_arm_candidate_cap_7082', kind: 'fix', text: "On a local search (the CLI and gbrain serve's local callers), the title step now ranks at most 5,000 of the pages that match the query in their title or timeline: the 5,000 with the lowest page ids, so the same pages on every call for the same data. Before, a very common word made it rank every matching page and read every matching timeline until the keyword time limit. A query that matches 5,000 pages or fewer gets the same result as before, timeline-only matches included. When the cut applies, the pages whose title holds the words come first (the rows remote callers get), then the other matching pages among the 5,000 kept, and hybrid search reports `keyword_candidates_incomplete`. A query of several words is cut on the pages that match the whole query, not word by word. Remote callers' results do not change." },+ { since: '0.60.734.0', id: 'guard_ledgers_fail_closed_7632', kind: 'fix', text: "On Postgres, a database write role that neither owns gbrain's purge and withdrawal ledgers (`fact_purges`, `fact_withdrawals`, `take_purges`, `page_purges`, `page_segment_derivation_purges`, `page_segment_derivation_purge_pages`) nor bypasses row-level security, and holds no policy that lets it read one, now gets a refusal on the writes that ledger's guard checks, where before the guard read the ledger as empty and let the write through: a purged claim, take, page or derivation could be stored again and a withdrawn fact saved active. The refusal is `writer_coordinator_required: writer state is unreadable to this database role` (P0001, `unreadable_state`); its hint names the table and the policy to add, and docs/ENGINES.md (\"Purge and withdrawal guards\") lists the policies a scoped write role needs. The guards stay SECURITY INVOKER: no trigger runs with different rights. The owner, a role that bypasses RLS, a ledger without row-level security and PGLite are unaffected. Where the role running migrations does not own a guard function, the upgrade leaves that function, names it on stderr and finishes; the next migration run by a role that owns it fixes it (#7632, #7659)." },+ { since: '0.60.734.0', id: 'purged_change_reason_8635', kind: 'fix', text: "A sync that read a page's change reason from a gbrain-reason commit trailer, then saved the page after a fact purge removed that text, used to store the purged text in the page's history as the reason for the change. The save now checks for the purge when it writes the history row and stores no reason instead; the page content still imports, and other files' reasons from the same commit are kept. Nothing to do. Reasons already stored before this release are not changed." },+ { since: '0.60.734.0', id: 'mirror_compare_reads_file_gst2843', kind: 'fix', text: "On a read-only mirror source, gbrain repair file-drift --held without --prefer now compares each held page with its file. A page that differs from its file reads prefer_file or needs_human with its evidence (what differs and which side is newer), and one that matches reads release_hold. Only a page whose file is gone reads no_drift with database_only. Before, every held page on a mirror read no_drift with database_only, whether or not it matched its file. Every compared page in details.pages now carries an evidence field, null when nothing was read. The comparison still writes nothing, and sync holds the same pages as before." },+ { since: '0.60.734.0', id: 'held_compare_complete_window_gst2843', kind: 'fix', text: "A gbrain repair file-drift --held dry run (a comparison, or a --prefer preview) now reports complete: false while held pages remain past its window, and details.window.next_command names the command for the next window. Before, complete was true after every window, even with thousands of held pages left. Applies keep the old meaning: every item of the approved window was attempted." },+ { since: '0.60.734.0', id: 'hold_by_code_counts_all_gst2843', kind: 'fix', text: "gbrain sources status --json now counts git_holds.by_code over every hold of the source. Before, the counts came only from the held files the listing read (at most 500), so a source with more holds under-counted each code. A code with no held file in the listing has no example. If the per-code count cannot be read, by_code falls back to the listed files and by_code_complete is false." },+ { since: '0.60.734.0', id: 'fact_rows_observed_date_gbra574', kind: 'fix', text: "Saved facts in query results now say when they were said. The facts block (on by default for a query with a token budget), the temporal fact reserve, the facts arm and recall's date headers fill the observed date in their [observed ...; valid ...] header from the page the fact was taken from, read under the caller's own page access, so a page the caller may not read dates nothing. If that read fails the header shows observed unknown and the response reports the degraded stage fact_observed_date_unavailable (recall: facts_degraded reason fact_observed_date_unavailable). Copies of one claim take one row in the facts block, dated as first stated and followed by (stated N times, last DATE); facts that differ by even one word keep their own rows. Question ranking of saved facts now matches words on their stems, with a word matched only through its stem ranking a little below an exact match (a question naming Roger puts a Roger fact above a Rogers fact), and dates, years and auxiliary verbs such as had or been no longer count toward the match, so a question phrased as of a date admits the facts it names and a fact sharing only a year with the question is no longer admitted. A fact about another person who shares the named person's surname can still be admitted when it also shares a verb with the question; its row names that person." },+ { since: '0.60.734.0', id: 'superseded_fact_valid_until_gbra574', kind: 'fix', text: "When a newer fact replaces an older one, every writer now ends the older fact's validity by one rule. It ends on the newer fact's valid_from when that date falls after the older fact began and before the older fact's own end (or now, if it had none); otherwise it ends at its own earlier end or now, and never before its own valid_from (a fact dated in the future ends where it begins). Per writer: remember with replaces (managed or not) and the engine supersede path used to leave the older fact open-ended when the newer fact was backdated, and now end it at the time of the write; the unmanaged remember that strikes the row in a page's facts table used to end it on today's date and now ends it at the newer fact's valid_from, which for remember is the time of the write; an accepted gbrain decide proposal used to end it at the time of acceptance and now ends it on the newer fact's valid_from when that falls inside the older fact's window; expireFact takes an optional successor date and applies the same rule. Extraction already used the rule and only gains the backdated case. A backdated replacement is one dated on or before the day the older fact began. For one of those, the older fact's end date is the day gbrain learned of the replacement (the time of the write), not a date taken from the source, unless the older fact already had an earlier end, which it keeps. Only future writes change. No stored row is rewritten, and forgetting or withdrawing a fact works exactly as before." },];/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */@@ -197,4 +215,22 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {atom_retirement_keeps_tier_9456: '0.60.733.0',provider_response_unparseable_9466: '0.60.733.0',sync_freshness_content_directory_9471: '0.60.733.0',+ repair_write_gate_markers_9511: '0.60.734.0',+ relink_keeps_fact_instant_9260: '0.60.734.0',+ consolidate_restatement_stays_open: '0.60.734.0',+ open_facts_repair_8194: '0.60.734.0',+ remember_restated_private_hold_2875: '0.60.734.0',+ setup_turn_hook_unmarked_9505: '0.60.734.0',+ git_reconcile_stopped_retryable: '0.60.734.0',+ frontmatter_validate_every_path: '0.60.734.0',+ serve_http_refused_not_activity_9484: '0.60.734.0',+ update_cache_future_stamp_8795: '0.60.734.0',+ title_arm_candidate_cap_7082: '0.60.734.0',+ guard_ledgers_fail_closed_7632: '0.60.734.0',+ purged_change_reason_8635: '0.60.734.0',+ mirror_compare_reads_file_gst2843: '0.60.734.0',+ held_compare_complete_window_gst2843: '0.60.734.0',+ hold_by_code_counts_all_gst2843: '0.60.734.0',+ fact_rows_observed_date_gbra574: '0.60.734.0',+ superseded_fact_valid_until_gbra574: '0.60.734.0',};diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.mdindex 1eb6aabc7a..61f966b807 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.733.0 -->+<!-- gbrain-template-stamp: 0.60.734.0 -->This repository is the **"Use this template"** distribution artifact for a[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same