Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
v0.60.723.0 release (#9404)
Garry Tan894ba65d8f32
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex eaf53a417a..78429b58e4 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "gbrain",- "version": "0.60.722.0",+ "version": "0.60.723.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 cb38df2ab0..41d32347fb 100644--- a/.codex-plugin/plugin.json+++ b/.codex-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "gbrain",- "version": "0.60.722.0",+ "version": "0.60.723.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 7b1be3a8be..ae23e67aba 100644--- a/BOOTSTRAP_FOR_AGENTS.md+++ b/BOOTSTRAP_FOR_AGENTS.md@@ -1,4 +1,4 @@-<!-- gbrain-runbook-stamp: 0.60.722.0 -->+<!-- gbrain-runbook-stamp: 0.60.723.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 4f27f9421c..a65da8b935 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,6 +10,208 @@ 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.723.0] - 2026-11-15++**`gbrain access rule add` no longer lets a hand-typed reader list lock the brain owner out of a folder.** When an owner is set, a rule whose `--readers` leaves the owner out is refused with `readers_omit_owner`, the same check and message `gbrain repair visibility --readers` already uses, and nothing is written. Pass `--allow-without-owner` when the owner really should not read it. A brain with no owner set is unchanged, and it works the same on a repo-less source (rules in the database) and a git source (`.gbrain/access.yml`).++<!-- behavior-change: access_rule_keeps_owner_gst2698 -->++### Itemized changes++- `src/commands/access-rules.ts`: `rule add` checks the owner before previewing or writing; new `--allow-without-owner` flag, named in `gbrain access --help`.+- `src/core/access/owner.ts`: the owner lookup and the `readers_omit_owner` error now live here and are shared with `src/core/repair/readers.ts`.+- Docs: `docs/guides/access-designations.md` and the setup skill name the flag.+- Tests: new `test/access-rule-owner-gst2698.test.ts` (refusal, override and no-owner case on a repo-less and a git source, PGLite and Postgres); two existing tests that rule a page away from the owner on purpose now pass `--allow-without-owner`.++**A squashed landing on master reuses the pull request's passed full test run instead of running the whole suite again.**++### Changed++- `scripts/ci-reuse.ts`: a one-parent push to master (a pull request landed as one squashed commit) now reuses the landed pull request's own run: the complete, passed full run of Test or E2E on a head GitHub names for the commit with the same tree, under the same artifact, job and repository checks a merge commit gets. Every run on those heads is read and the newest one decides: if it failed or is still running, the push runs in full, and a cancelled run or one that skipped its full job is passed over. A one-parent push no pull request names (a hand revert, a direct push), one whose lookup fails, one whose tree matches no full run, and a root commit still run in full. docs/ci-event-parity.md, "Master-push reuse", says so.++**Outside contributors now get an accurate picture of what happens to their pull requests, and issues our own automation files are labelled so community reports are easy to find.** The comment posted on an outside pull request and the new "How an outside pull request is handled" section of CONTRIBUTING.md describe what really happens: docs-only changes can be merged as they are after a read, small plainly correct fixes are rebuilt with credit to the author, every PR lands as one squashed commit with outside authors credited by a `Co-authored-by:` trailer, and the three-open-PR limit never applies to anyone who had a PR taken in the last 90 days. Every issue the repo's scripts and CI open now carries the `agent-filed` label, and the new-issue page links to a "Community issues" search that leaves those out.++### Itemized changes++- `scripts/fix-wave-gate.ts`, `scripts/fix-wave-closeout.ts`: the gate and close-out comments describe the current rules and link to the new CONTRIBUTING section.+- `scripts/lib/gh-issue.ts`: `createIssue` always adds `agent-filed`; `scripts/upgrade-matrix.ts` and `scripts/lib/master-red.ts` keep it on every issue they open.+- `.github/ISSUE_TEMPLATE/config.yml`: a "Community issues" contact link.+- Docs: CONTRIBUTING.md, README.md, docs/RELEASING.md and the CI key-files page.+- Tests: new `test/scripts/gh-issue-agent-filed.test.ts`; the nightly-issue, fix-wave-gate and fix-wave-closeout tests updated.++**A second folder of notes (say, your company's beside your own) shows up in search without Git and without guessing why it doesn't.**++### Changed+- On a brain only you use, a source you add without `--federated` or `--no-federated` joins default search, so `gbrain query` finds its pages right away. On a shared brain it stays out, and `gbrain sources add` and `gbrain sync --source <id>` say so with a `source_not_in_default_search` notice whose fix is `gbrain sources federate <id>` (also under `notices` in `--json`). Sources you already have keep their setting.+- `gbrain sources add <id> --path <folder>` accepts a plain folder that is not in a git repository, without `--force`, and says that git history is off for it. A git repository with nothing committed is still refused. `gbrain sources inspect` on a plain folder now points at `sources add`.+- `gbrain setup codex` lists the provider key names (`OPENAI_API_KEY`, `VOYAGE_API_KEY` and the rest) under `env_vars`, so Codex passes keys you already exported to gbrain and search stays semantic. Only names are written.+- The "sole non-default source ... routing to 'default'" line no longer prints on every command when that source is already in default search.+- `gbrain sources federate` on a keyless brain says embedding is off instead of telling you to run `gbrain embed --stale`, and `sources --help` and `pages --help` no longer show an old version in their header.+- README: the voice line points at agent-voice (the Twilio recipe is deprecated), says how voice notes and chat transcripts get in today, and shows how to add a second folder.++<!-- behavior-change: new_sources_join_default_search_gst2732 -->+<!-- behavior-change: plain_folder_sources_gst2732 -->++**Two tests that failed CI runs on unrelated changes now pass on a busy runner.** Neither changed what it checks.++### Tests++- `test/proactive-brief.test.ts`: the two tests that check a delivered brief writes its `context_volunteer_events` rows went through `turnContextWithBrief`, which gives the brief only 300 ms of wall clock from the start of the request. On a slow runner the base assembly used up that time, the brief came back empty, nothing was delivered or logged, and the row check saw `[]`. `turnContextWithBrief` now takes an optional clock (it still defaults to the 300 ms cutoff), and those two tests pass the same wide test clock the file's other brief tests already use. A probe that slows every query by 60 ms fails the old test and passes the new one.+- `test/skill-resolver-hook-lane.test.ts`: the 5 MB Hermes history test compared one timed run of a small turn with one timed run of the 5 MB turn against the 50 ms lane deadline. Each run varies by 20 to 30 ms on an idle machine and more on a loaded one, so one descheduled turn could fail it (it failed 1 run in 5 under load locally). It now times three runs of each and compares the fastest of each, with the same 50 ms bar.++- A member's connection can no longer use `sources_resolve_path` to learn that a page it may not read exists. A guessed path for a restricted or owner-private page now gets the same answer as a path with no file and no page, even when an older readable copy of that path was deleted. The brain owner's own connections read exactly what they read before. (#8761)+- The `gbrain access rule add` commands printed by `gbrain doctor`, the labelled-only create refusal, `gbrain access serves` and the federation exposure check now include the owner in `--readers`, so they are accepted on a brain with an owner set. Re-running `gbrain access serves` after applying its printed fix now reports the rule as already in place.+- `sources_resolve_path` on a plain directory with no Git history now refuses with `sync_not_applicable` (reason `plain_directory`) and a next step, instead of a raw Git error. Contributed by @Kkkkkuro.++**A first install prints no Bun error and ends with memory connected, on every agent harness.**++### Changed+- gbrain no longer ships a postinstall script, so `bun install -g github:garrytan/gbrain#stable` no longer ends with "Blocked 1 postinstall", and a clone's `bun install` no longer prints "postinstall skipped". The script did nothing on a fresh install; migrations already run in `gbrain setup`, `gbrain upgrade` and on the first command.+- After reinstalling over an older brain, commands print a `migrations_pending` notice naming the upgrade migrations still to run, with `gbrain apply-migrations --yes` as the fix.+- `gbrain init` treats connecting the agent as an install step (its own `harness_wiring` notice), not a setting awaiting approval. The first-run settings are reported as in effect, with how to change them, and no "Reply 'defaults'" question; automatic saving shows as off (recommended salient) instead of "default: salient".+- The install docs no longer tell agents to stop and ask about search mode: connect first, then report the settings and the cost matrix in the install reply.++<!-- behavior-change: install_no_postinstall_gst2732 -->+<!-- behavior-change: first_run_connects_then_reports_gst2732 -->++**A test of the OpenClaw skill plugin's daily log no longer fails on a slow runner.** It didn't change what it checks.++### Tests++- `test/openclaw-skill-plugin.test.ts`: the plugin writes each daily-log line through a chain of awaited appends, and the test's Node driver exited a fixed 300 ms after its last step. On a slow runner, the 164 appends in "the daily log keeps event order when a skill read follows a turn at once" were still queued when the driver exited, so the tail of the log was lost and the check failed. The driver now waits, for at most 30 s, until the log holds the number of lines the test expects, and then exits as before. The other test that reads this log (six lines) waits the same way. A probe that slows every append by 5 ms fails the old test (109 lines lost) and passes the new one.++**The README now opens on one brain for you and your company.**++### Changed+- The first screen says who GBrain is for, what you have a few minutes after installing, and how to add your own notes and your company's docs (a facts page, a decisions log, call transcripts) as two searchable folders with three commands.+- It says plainly that GBrain is not a data warehouse or analytics store.+- The install block and the hosted option are unchanged; the sections that used to sit above the install now follow it.++**`gbrain repair redacted-facts` now restores facts the conversation extractor wrote, which keep a row number on a page with no Facts fence (#8820).**++### Fixed+- `src/core/repair/redacted-facts.ts`: a fact with a row number is treated as a Facts-fence row only while its page's fence holds an active row with its text at that number. A conversation-extractor fact with no such fence row is now restored in place, keeping its row number, by the same row-exact rewrite as a database-only fact; its page is not changed. Before, the preview listed these facts as `evidenced` and the apply left them damaged with `changed_since_preview`. Any other fact whose fence row is gone is now listed as `unproven` (`fence_row_missing`) instead of `evidenced`, so the preview no longer promises a restore the apply cannot make. The repair is still preview-first: `--apply --expect <hash>` restores only the previewed set. Reported by @tarush1989.+- Docs: `docs/guides/repair.md` (redacted facts class table and apply paragraph).+- Tests: `test/repair-redacted-facts.test.ts` (PGLite, and Postgres through `test/e2e/repair-redacted-facts-postgres.test.ts`): a managed brain restores an extractor fact and leaves its page revision unchanged; an unmanaged brain restores an extractor fact and keeps a non-extractor fact whose fence row is gone. Both failed before the fix on both engines.++**`gbrain repair visibility --propose` drafts who should read each open page, so a brain shared by several people can be labelled without typing every reader list by hand.** It reads the participants, attendees and to, from and cc addresses already on open pages, matches each address to an enabled member's declared email, and groups the pages by reader set with the owner always first. For each set it writes a private slugs file (mode 0600) and prints the existing `gbrain repair visibility --slugs-file ... --readers ...` command, so you preview and apply with the tools you already have. It labels nothing itself. A page with an address that matches no member, or a slug a slugs file cannot carry (one starting with `#`, padded with spaces or holding a line break), is listed as unmatched instead of guessed. DM, chat and mail folders with no address list get an `access rule add` command to fill in. On a brain that serves one person it says there is nothing to propose and reads no pages. It works the same on a repo-less brain and a git brain, and refuses to write its files inside a git work tree.++### Itemized changes++- `src/commands/repair-propose.ts` (new): builds the proposal, writes each slugs file through an exclusive temp file and a rename, and shell-quotes every printed command.+- `src/commands/repair.ts`: new `--propose` and `--out` flags on `gbrain repair visibility`.+- `src/core/access/open-pages.ts`, `src/commands/access-serves.ts`: share the open-page query and git-root lookup with the new command.+- New error code `repair_propose_dir_in_git`, listed in `docs/guides/error-codes.md`.+- Docs: `docs/guides/repair.md` (proposing readers) and `docs/architecture/key-files/access.md`.+- Tests: new `test/repair-visibility-propose-gst2670.test.ts` (PGLite and Postgres).++**Purging a page retires the facts extracted from it, `gbrain migrate embeddings` stops refusing on some databases, a growing transcript is no longer re-synthesized on every dream pass, legacy embedding labels no longer wipe valid vectors, and search says how far an upgrade's index rebuild has got.**++<!-- behavior-change: resynthesis_hold_6753 -->++### Fixed++- **Facts extracted from a purged page are retired with it** (#8859, reported by @ocscdsa). Facts the extractor filed on no page and that name the page only in their context stayed active after the page was retired or purged. Retire and purge now match them too. Facts left behind by earlier purges are not changed here.+- **`gbrain migrate embeddings` no longer always refuses with "Source census changed while acquiring locks"** on databases whose collation sorts source ids differently from code-unit order (#9307, reported by @ozabramov; first fixed by @Masashi-Ono0611 in #9310).+- **A growing transcript is re-synthesized at most twice a day** (#6753, reported by @andreineacsu). A transcript synthesized within `dream.synthesize.cooldown_hours` is held, so repeats drop from up to 24 a day to 2. The daily spend ceiling is unchanged ($120 worst case). Explicit `--input` and `--date` runs are never held.+- **Chunks stamped with a bare model label keep their vectors** (#8533, reported by @babyspectrum). The false-stamp guard, the projection preserve check and the stale-signature invalidation now share one rule: a bare label counts when its model name and width match the configured model; a different explicit provider prefix is still invalidated. Before, the last two nulled valid vectors and forced a paid re-embed.+- **Search says how far an upgrade's index rebuild has got** (#9192, reported by @jonahberg). While the rebuild runs, the partial-results notice gives pages done out of total, the measured rate and the command to watch progress, and the upgrade prints it once.++### Itemized changes++- `src/core/facts/gone-page-facts.ts`, `src/core/facts/subject-infer.ts`, `src/core/persistence/page-purge.ts`: extracted-from-page facts are expired and purged with their page.+- `src/commands/migrate-embeddings.ts`: the locked census is sorted the same way as the requested source list.+- `src/core/cycle/synthesize-completion.ts`, `src/core/cycle/synthesize.ts`: per-transcript re-synthesis hold.+- `src/core/embedding-invalidation.ts`, `src/core/engine-sql/chunks.ts`, `src/core/page-state/projections.ts`: one `chunkModelMatchesSql` rule.+- `src/core/search/retrieval-coverage.ts`, `src/core/ops/search.ts`, `src/core/interop-notices.ts`, v153's notice handler: rebuild progress.+- Tests: one new test per fix, on PGLite and Postgres where the bug is engine-specific; the #5051 test changes one assertion and its count.++**The skill resolver now leaves its skills block out when no skill fits the message, instead of showing one on every turn.**++### Fixed+- `gbrain skills resolve`, the hook lane, and the OpenClaw and Pi plugins apply `top_gate` by default (0.6): a block whose best skill only matches weakly is left out (`block_reason: weak_top_match`), and a skill named in the message still gets through. On harness-evals' public set P with its 351-skill catalog, blocks on requests that need no skill drop from 61 of 61 to 7 of 61, and the acceptable skill stays in the block for 174 of 228 skill requests (176 before). `skills.resolver.top_gate 0` restores the old behavior.+- `gbrain skills resolve` and the OpenClaw and Pi plugins now read `skills.resolver.top_gate` (and `per_harness.<harness>.top_gate`); before, only the hook lane did. `--top-gate` still wins on the command line.++<!-- behavior-change: skill_resolver_gate_default_gst2704 -->++**Two slow test files are split along their own seams, so no file comes near CI's 300-second per-file limit.** `test/enforced-member.serial.test.ts` took 185 to 191 s on a 4-vCPU machine, and CI killed it at 300 s on slow runners with no assertion failing. It is now three serial files that take at most 77 s each. `test/setup-serves-several.test.ts` took 193 to 240 s and is now three unit files that take at most 78 s each. The tests and assertions are unchanged (27 and 645, and 27 and 270), and no product code, timeout, budget or retry count changed.++### Tests++- `test/enforced-member.serial.test.ts` keeps the reads and refusals. Writes and the git commit-push suite move to `test/enforced-member-writes.serial.test.ts`, and the `access.enforced_member_writes` case moves to `test/enforced-member-writes-setting.serial.test.ts`. Each file seeds its own brain through `test/helpers/enforced-member-brain.ts`.+- The spawned `gbrain setup` cases split out of `test/setup-serves-several.test.ts` into `test/setup-serves-stdio-member.test.ts` and `test/setup-serves-upgrade.test.ts`, with the shared box in `test/helpers/setup-serves-box.ts`.+- The new serial files get rows in `scripts/serial-files.tsv`, `test/postgres-unit-arms.txt` and `scripts/postgres-arm-weights.json`. The unit and serial weight maps get no hand-added rows, because they must match the miner's metadata, so new files use the p75 estimate until the next re-mine.++**docs/RELEASING.md now says how a pull request lands on master: as one commit titled with the pull request's title and number.**++### Changed++- docs/RELEASING.md, "Releases per batch", has a "How a PR lands" paragraph: each pull request, release pull requests included, lands as one squashed commit whose subject is its title followed by `(#<number>)`, with other authors credited by `Co-authored-by:` trailers, while branches keep bringing master in with merge commits and are never rebased.+- The contributor audit's offline fixture now includes a squashed `(#<number>)` commit next to its "Merge pull request" merges, so the audit's tests cover both commit shapes it reads.++**On a thin client, `gbrain serve` now connects a stdio-only agent harness to your remote brain instead of refusing.**++Install the gbrain CLI on the agent's machine, run `gbrain init --mcp-only` with an OAuth client from the brain host, and register `gbrain serve` as the harness's stdio MCP server, the same entry a local brain uses. Every call goes to the brain host with that client's grant and comes back unchanged, refusals included; the bridge opens no local database, stores no page text and adds no access. Reported and first proposed by @jel405 (#8543).++### Itemized changes++- Bare `gbrain serve` on a thin client is a stdio bridge. It accepts `--surface`, `--advertise` and `--source-guard` (the argv gbrain's plugins register); `request_tools {surface}` widens only the session and writes nothing on the host. `serve --http`, `--access` and the other host flags still refuse with `requires_local_engine`, with a fix that keeps the flags (`--access` points at registering a narrow read-only client instead).+- Bridge failures are v1 agent envelopes with a bounded recovery and a fix that never adds a scope. A write whose answer was lost keeps its `request_id` (`write_outcome_unknown`) so it can be checked or resent without writing twice. URLs in envelopes and stderr lose their userinfo, query and fragment.+- A call that names an audience (`_meta.on_behalf_of`) is relayed only to a host that enforces it (gbrain 0.60.543.0 or newer); otherwise the bridge answers `host_upgrade_required`.+- `gbrain doctor` on a read or read+write thin client reports the missing admin scope as expected instead of advising a re-register with admin.+- `gbrain agent register --harness openclaw` prints the lines to run on the OpenClaw machine: `gbrain init --mcp-only …` then `openclaw mcp add gbrain --command "$(command -v gbrain)" --arg serve …`.++<!-- behavior-change: thin_client_serve_stdio_bridge_8543 -->++**`gbrain extract timeline --source db` no longer fails on a large page with many stored versions on a managed Postgres brain.**++Retraction used to read every stored version of the page in one statement inside the publication transaction. With hundreds of versions that statement ran past the 5 second statement timeout on every retry, so the page's timeline extract failed with `write_interrupted` on every maintenance run. The version scan now runs before the transaction and reads one version at a time. Inside the transaction gbrain only checks that the versions it read are still the page's, with the same text. A row whose versions changed in between stays until the next run. Reported in #9362.++### Fixed+- `gbrain extract timeline --source db` and the maintenance timeline pass no longer time out with `write_interrupted` on a page with hundreds of stored versions (#9362).++**Guest notes now refuse writes from a database role that cannot see which sources are guest sources, and several smaller guest-note gaps from the first release are closed.**++A brain whose gbrain process connects to Postgres as a scoped row-level-security role used to read the guest source list as empty, so a write into a guest source passed as if the source were ordinary. Such a role is now refused with `writer_coordinator_required` until it can read `guest_sources` (one SELECT policy, added to the maintainer recipe in docs/ENGINES.md). The owner, a role that bypasses row-level security and PGLite brains see no change.++### Fixed+- Schema migration v314 re-creates the guest guard in the trust trigger and the guest-record guard so they refuse a role that row-level security keeps from reading `guest_sources`; guest admission, `remember`, links and remote deletes refuse the same way instead of treating the source as ordinary.+- `gbrain guests promote` no longer answers `already_promoted` when the kept page was purged, so promoting again writes the page and keeps one link. v314 adds a unique index on the promotion link (a brain that already holds duplicate links keeps them, gets no index and a warning), and two promotions of the same note to the same page that race each other both succeed with one link.+- A guest note whose mark writes no row now fails the save instead of committing a guest page with no mark.+- `gbrain guests init` counts the source's pages under the source row's lock, so no page can land between the check and the change.+- The repair `gbrain doctor` suggests for a source whose config says guest but has no guest record, `gbrain guests init --source <id> --yes`, now works when the source holds pages.+- A cycle phase skipped because the guest-source lookup failed now says the lookup failed (`reason: guest_source_lookup_failed`, with the error), instead of reporting a plain guest-source skip.+- A read the guest-note stamp cannot copy is refused, instead of marking the handler's own object.+- A page write on a brain whose schema is behind the guest-notes migration is refused `migrations_pending` instead of failing with a missing-table error.+- The owner-credential read behind `gbrain guests grant-owner-clients` and doctor's `guest_source` check no longer loads token hashes.+- `gbrain auth rescope --client <id>` with no grant flag now prints the client's operations and slug prefixes, and `gbrain delete --help` says `--expected-revision` is required unless `--force`.+- docs/guides/guest-notes.md gives the setup order that works (init, register the broker client, rescope its operations, then add it as a writer), and says that deletes need a revision or `--force` and that a put with attribution but no audience is refused `readable_by_invalid`.++<!-- behavior-change: guest_sources_scoped_role_fail_closed_9354 -->++**On a PGLite brain held by `gbrain serve` or the job worker, `gbrain wakeshift emit cron.finished` now records the run instead of dropping it, and revoking a credential always ends its watches.**++### Fixed++- A cron run that finished while `gbrain serve` or `gbrain jobs work` held the PGLite brain was lost. Emit now saves it as a small private file (0600) under the brain's own gbrain home, and the process holding the brain records it within seconds with its original finish time, so a watcher still wakes. Two processes reading the folder at once never record a run twice. A file that is malformed, oversized or has an impossible time goes to `rejected/` with one stderr line and never holds back the runs after it. At most 1,000 runs wait per brain. Postgres brains and brains with reporting back off never use the folder.+- The next direct `emit` also records any leftover runs, and it records its own run even when the leftovers can't be read.+- `gbrain auth revoke --id <id>` with a legacy token id written in uppercase now ends that token's watches and asks Wakeshift to forget its user.+- When removing an access member failed to ask Wakeshift to forget that member's user, the wake drainer now asks again. A member who is still active keeps their Wakeshift user.++**gbrain can now report back when a pending write settles or a cron run finishes, on brains shared with access members, and to OpenClaw and thin-client agents. Reporting back stays off until the brain owner turns it on.**++Two new events join job completion. `watch_write_request` wakes the conversation when a `write_pending` write commits, fails, conflicts or is cancelled. It uses the same check as `get_write_request`, so someone else's request reads as not found. `watch_cron` wakes it after the next run of a cron the owner registered with `gbrain wakeshift cron add <name>`. The cron's own script ends with `gbrain wakeshift emit cron.finished --name <name> --status ok|failed`, which records the run and never blocks or fails the script, even when it can't open the brain. On a PGLite brain, a run that finishes while `gbrain serve` or a job worker holds the brain isn't recorded. Every wake is still a pointer (ids, status and times), never page text or cron output. A brain with access members can now report back too. The owner gives their terms and privacy links to `gbrain wakeshift enable`, and each member's agent shows the agreement step and records acceptance before its first watch. Removing a member, revoking a token or deleting an OAuth client ends that principal's watches and asks Wakeshift to forget its user. Guide: docs/guides/wakeshift.md.++### Itemized changes++- New MCP tools `watch_write_request`, `watch_cron` and `accept_wakeshift_terms`, listed only while reporting back is on. `list_watches` and `unwatch` now cover every kind of watch.+- New `gbrain wakeshift cron add | remove | list` and `gbrain wakeshift emit cron.finished`. `enable` takes `--terms-url` and `--privacy-url` (https), which a brain with access members needs. `status` and doctor say when gbrain's published events are older than the installed gbrain; run `gbrain wakeshift enable` again to publish the new ones.+- New `gbrain wakeshift watch job <id> | write <request_id> | cron <name>`, which runs on a thin client (`gbrain init --mcp-only`). It prints Wakeshift's instructions as the last line and never saves a session key.+- New `gbrain setup openclaw --wakeshift`. After consent, it installs and enables Wakeshift's OpenClaw plugin, pinned at `@wakeshift/[email protected]`. On a gateway that listens beyond the machine, it prints Wakeshift's question about the hooks endpoint and never answers it. A new doctor check `wakeshift_openclaw` warns when the installed plugin differs from the pin.+- `gbrain setup claude-code` and `gbrain setup codex` show a "Report back (Wakeshift)" row in the first-run settings. After a remote `submit_job` or `submit_agent`, a once-per-session notice (`wakeshift_report_back`, muteable) says how to have the conversation woken. With reporting back on, the MCP instructions gain one sentence about it. With it off, the instructions are unchanged.+- Fixed: Wakeshift's instructions in a watch result were cut at 2,000 characters, which dropped the step that starts Claude Code's listener. They now pass through whole, up to 16,000.+- Schema migration v313 adds `wake_crons`, `wake_cron_runs`, `wake_terms_acceptances`, `wake_forgets` and `wake_subscriptions.target_ref`. All are empty unless reporting back is on, and repo-less brains get them unchanged.+## [0.60.722.0] - 2026-11-14**The brain owner's own remote agents can now edit, append to and relabel the private pages they already read, and everyone else is still refused.**diff --git a/VERSION b/VERSIONindex 91aacd527e..7f4891b445 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-0.60.722.0+0.60.723.0diff --git a/changelog.d/capy-access-rule-owner-check.md b/changelog.d/capy-access-rule-owner-check.mddeleted file mode 100644index 7b8861d234..0000000000--- a/changelog.d/capy-access-rule-owner-check.md+++ /dev/null@@ -1,10 +0,0 @@-**`gbrain access rule add` no longer lets a hand-typed reader list lock the brain owner out of a folder.** When an owner is set, a rule whose `--readers` leaves the owner out is refused with `readers_omit_owner`, the same check and message `gbrain repair visibility --readers` already uses, and nothing is written. Pass `--allow-without-owner` when the owner really should not read it. A brain with no owner set is unchanged, and it works the same on a repo-less source (rules in the database) and a git source (`.gbrain/access.yml`).--<!-- behavior-change: access_rule_keeps_owner_gst2698 -->--### Itemized changes--- `src/commands/access-rules.ts`: `rule add` checks the owner before previewing or writing; new `--allow-without-owner` flag, named in `gbrain access --help`.-- `src/core/access/owner.ts`: the owner lookup and the `readers_omit_owner` error now live here and are shared with `src/core/repair/readers.ts`.-- Docs: `docs/guides/access-designations.md` and the setup skill name the flag.-- Tests: new `test/access-rule-owner-gst2698.test.ts` (refusal, override and no-owner case on a repo-less and a git source, PGLite and Postgres); two existing tests that rule a page away from the owner on purpose now pass `--allow-without-owner`.diff --git a/changelog.d/capy-ci-reuse-squash.md b/changelog.d/capy-ci-reuse-squash.mddeleted file mode 100644index ba4471f4bb..0000000000--- a/changelog.d/capy-ci-reuse-squash.md+++ /dev/null@@ -1,5 +0,0 @@-**A squashed landing on master reuses the pull request's passed full test run instead of running the whole suite again.**--### Changed--- `scripts/ci-reuse.ts`: a one-parent push to master (a pull request landed as one squashed commit) now reuses the landed pull request's own run: the complete, passed full run of Test or E2E on a head GitHub names for the commit with the same tree, under the same artifact, job and repository checks a merge commit gets. Every run on those heads is read and the newest one decides: if it failed or is still running, the push runs in full, and a cancelled run or one that skipped its full job is passed over. A one-parent push no pull request names (a hand revert, a direct push), one whose lookup fails, one whose tree matches no full run, and a root commit still run in full. docs/ci-event-parity.md, "Master-push reuse", says so.diff --git a/changelog.d/capy-contributor-gate-wording-agent-filed-label.md b/changelog.d/capy-contributor-gate-wording-agent-filed-label.mddeleted file mode 100644index 56fc314438..0000000000--- a/changelog.d/capy-contributor-gate-wording-agent-filed-label.md+++ /dev/null@@ -1,9 +0,0 @@-**Outside contributors now get an accurate picture of what happens to their pull requests, and issues our own automation files are labelled so community reports are easy to find.** The comment posted on an outside pull request and the new "How an outside pull request is handled" section of CONTRIBUTING.md describe what really happens: docs-only changes can be merged as they are after a read, small plainly correct fixes are rebuilt with credit to the author, every PR lands as one squashed commit with outside authors credited by a `Co-authored-by:` trailer, and the three-open-PR limit never applies to anyone who had a PR taken in the last 90 days. Every issue the repo's scripts and CI open now carries the `agent-filed` label, and the new-issue page links to a "Community issues" search that leaves those out.--### Itemized changes--- `scripts/fix-wave-gate.ts`, `scripts/fix-wave-closeout.ts`: the gate and close-out comments describe the current rules and link to the new CONTRIBUTING section.-- `scripts/lib/gh-issue.ts`: `createIssue` always adds `agent-filed`; `scripts/upgrade-matrix.ts` and `scripts/lib/master-red.ts` keep it on every issue they open.-- `.github/ISSUE_TEMPLATE/config.yml`: a "Community issues" contact link.-- Docs: CONTRIBUTING.md, README.md, docs/RELEASING.md and the CI key-files page.-- Tests: new `test/scripts/gh-issue-agent-filed.test.ts`; the nightly-issue, fix-wave-gate and fix-wave-closeout tests updated.diff --git a/changelog.d/capy-first-run-sources-codex.md b/changelog.d/capy-first-run-sources-codex.mddeleted file mode 100644index d146a0f6c5..0000000000--- a/changelog.d/capy-first-run-sources-codex.md+++ /dev/null@@ -1,12 +0,0 @@-**A second folder of notes (say, your company's beside your own) shows up in search without Git and without guessing why it doesn't.**--### Changed-- On a brain only you use, a source you add without `--federated` or `--no-federated` joins default search, so `gbrain query` finds its pages right away. On a shared brain it stays out, and `gbrain sources add` and `gbrain sync --source <id>` say so with a `source_not_in_default_search` notice whose fix is `gbrain sources federate <id>` (also under `notices` in `--json`). Sources you already have keep their setting.-- `gbrain sources add <id> --path <folder>` accepts a plain folder that is not in a git repository, without `--force`, and says that git history is off for it. A git repository with nothing committed is still refused. `gbrain sources inspect` on a plain folder now points at `sources add`.-- `gbrain setup codex` lists the provider key names (`OPENAI_API_KEY`, `VOYAGE_API_KEY` and the rest) under `env_vars`, so Codex passes keys you already exported to gbrain and search stays semantic. Only names are written.-- The "sole non-default source ... routing to 'default'" line no longer prints on every command when that source is already in default search.-- `gbrain sources federate` on a keyless brain says embedding is off instead of telling you to run `gbrain embed --stale`, and `sources --help` and `pages --help` no longer show an old version in their header.-- README: the voice line points at agent-voice (the Twilio recipe is deprecated), says how voice notes and chat transcripts get in today, and shows how to add a second folder.--<!-- behavior-change: new_sources_join_default_search_gst2732 -->-<!-- behavior-change: plain_folder_sources_gst2732 -->diff --git a/changelog.d/capy-fix-proactive-brief-and-hook-lane-flakes.md b/changelog.d/capy-fix-proactive-brief-and-hook-lane-flakes.mddeleted file mode 100644index 74e56c8a83..0000000000--- a/changelog.d/capy-fix-proactive-brief-and-hook-lane-flakes.md+++ /dev/null@@ -1,6 +0,0 @@-**Two tests that failed CI runs on unrelated changes now pass on a busy runner.** Neither changed what it checks.--### Tests--- `test/proactive-brief.test.ts`: the two tests that check a delivered brief writes its `context_volunteer_events` rows went through `turnContextWithBrief`, which gives the brief only 300 ms of wall clock from the start of the request. On a slow runner the base assembly used up that time, the brief came back empty, nothing was delivered or logged, and the row check saw `[]`. `turnContextWithBrief` now takes an optional clock (it still defaults to the 300 ms cutoff), and those two tests pass the same wide test clock the file's other brief tests already use. A probe that slows every query by 60 ms fails the old test and passes the new one.-- `test/skill-resolver-hook-lane.test.ts`: the 5 MB Hermes history test compared one timed run of a small turn with one timed run of the 5 MB turn against the 50 ms lane deadline. Each run varies by 20 to 30 ms on an idle machine and more on a loaded one, so one descheduled turn could fail it (it failed 1 run in 5 under load locally). It now times three runs of each and compares the fastest of each, with the same 50 ms bar.diff --git a/changelog.d/capy-gst-2128-access-hints-resolve-path.md b/changelog.d/capy-gst-2128-access-hints-resolve-path.mddeleted file mode 100644index d59de49069..0000000000--- a/changelog.d/capy-gst-2128-access-hints-resolve-path.md+++ /dev/null@@ -1,6 +0,0 @@-----important: security------ A member's connection can no longer use `sources_resolve_path` to learn that a page it may not read exists. A guessed path for a restricted or owner-private page now gets the same answer as a path with no file and no page, even when an older readable copy of that path was deleted. The brain owner's own connections read exactly what they read before. (#8761)-- The `gbrain access rule add` commands printed by `gbrain doctor`, the labelled-only create refusal, `gbrain access serves` and the federation exposure check now include the owner in `--readers`, so they are accepted on a brain with an owner set. Re-running `gbrain access serves` after applying its printed fix now reports the rule as already in place.-- `sources_resolve_path` on a plain directory with no Git history now refuses with `sync_not_applicable` (reason `plain_directory`) and a next step, instead of a raw Git error. Contributed by @Kkkkkuro.diff --git a/changelog.d/capy-install-no-postinstall.md b/changelog.d/capy-install-no-postinstall.mddeleted file mode 100644index aeff89254d..0000000000--- a/changelog.d/capy-install-no-postinstall.md+++ /dev/null@@ -1,10 +0,0 @@-**A first install prints no Bun error and ends with memory connected, on every agent harness.**--### Changed-- gbrain no longer ships a postinstall script, so `bun install -g github:garrytan/gbrain#stable` no longer ends with "Blocked 1 postinstall", and a clone's `bun install` no longer prints "postinstall skipped". The script did nothing on a fresh install; migrations already run in `gbrain setup`, `gbrain upgrade` and on the first command.-- After reinstalling over an older brain, commands print a `migrations_pending` notice naming the upgrade migrations still to run, with `gbrain apply-migrations --yes` as the fix.-- `gbrain init` treats connecting the agent as an install step (its own `harness_wiring` notice), not a setting awaiting approval. The first-run settings are reported as in effect, with how to change them, and no "Reply 'defaults'" question; automatic saving shows as off (recommended salient) instead of "default: salient".-- The install docs no longer tell agents to stop and ask about search mode: connect first, then report the settings and the cost matrix in the install reply.--<!-- behavior-change: install_no_postinstall_gst2732 -->-<!-- behavior-change: first_run_connects_then_reports_gst2732 -->diff --git a/changelog.d/capy-openclaw-plugin-log-flake.md b/changelog.d/capy-openclaw-plugin-log-flake.mddeleted file mode 100644index 1cdbd641af..0000000000--- a/changelog.d/capy-openclaw-plugin-log-flake.md+++ /dev/null@@ -1,5 +0,0 @@-**A test of the OpenClaw skill plugin's daily log no longer fails on a slow runner.** It didn't change what it checks.--### Tests--- `test/openclaw-skill-plugin.test.ts`: the plugin writes each daily-log line through a chain of awaited appends, and the test's Node driver exited a fixed 300 ms after its last step. On a slow runner, the 164 appends in "the daily log keeps event order when a skill read follows a turn at once" were still queued when the driver exited, so the tail of the log was lost and the check failed. The driver now waits, for at most 30 s, until the log holds the number of lines the test expects, and then exits as before. The other test that reads this log (six lines) waits the same way. A probe that slows every append by 5 ms fails the old test (109 lines lost) and passes the new one.diff --git a/changelog.d/capy-readme-first-screen.md b/changelog.d/capy-readme-first-screen.mddeleted file mode 100644index d9081267ab..0000000000--- a/changelog.d/capy-readme-first-screen.md+++ /dev/null@@ -1,6 +0,0 @@-**The README now opens on one brain for you and your company.**--### Changed-- The first screen says who GBrain is for, what you have a few minutes after installing, and how to add your own notes and your company's docs (a facts page, a decisions log, call transcripts) as two searchable folders with three commands.-- It says plainly that GBrain is not a data warehouse or analytics store.-- The install block and the hosted option are unchanged; the sections that used to sit above the install now follow it.diff --git a/changelog.d/capy-redacted-facts-legacy-rows.md b/changelog.d/capy-redacted-facts-legacy-rows.mddeleted file mode 100644index 5676c83762..0000000000--- a/changelog.d/capy-redacted-facts-legacy-rows.md+++ /dev/null@@ -1,6 +0,0 @@-**`gbrain repair redacted-facts` now restores facts the conversation extractor wrote, which keep a row number on a page with no Facts fence (#8820).**--### Fixed-- `src/core/repair/redacted-facts.ts`: a fact with a row number is treated as a Facts-fence row only while its page's fence holds an active row with its text at that number. A conversation-extractor fact with no such fence row is now restored in place, keeping its row number, by the same row-exact rewrite as a database-only fact; its page is not changed. Before, the preview listed these facts as `evidenced` and the apply left them damaged with `changed_since_preview`. Any other fact whose fence row is gone is now listed as `unproven` (`fence_row_missing`) instead of `evidenced`, so the preview no longer promises a restore the apply cannot make. The repair is still preview-first: `--apply --expect <hash>` restores only the previewed set. Reported by @tarush1989.-- Docs: `docs/guides/repair.md` (redacted facts class table and apply paragraph).-- Tests: `test/repair-redacted-facts.test.ts` (PGLite, and Postgres through `test/e2e/repair-redacted-facts-postgres.test.ts`): a managed brain restores an extractor fact and leaves its page revision unchanged; an unmanaged brain restores an extractor fact and keeps a non-extractor fact whose fence row is gone. Both failed before the fix on both engines.diff --git a/changelog.d/capy-repair-visibility-propose.md b/changelog.d/capy-repair-visibility-propose.mddeleted file mode 100644index 04e464f1ab..0000000000--- a/changelog.d/capy-repair-visibility-propose.md+++ /dev/null@@ -1,10 +0,0 @@-**`gbrain repair visibility --propose` drafts who should read each open page, so a brain shared by several people can be labelled without typing every reader list by hand.** It reads the participants, attendees and to, from and cc addresses already on open pages, matches each address to an enabled member's declared email, and groups the pages by reader set with the owner always first. For each set it writes a private slugs file (mode 0600) and prints the existing `gbrain repair visibility --slugs-file ... --readers ...` command, so you preview and apply with the tools you already have. It labels nothing itself. A page with an address that matches no member, or a slug a slugs file cannot carry (one starting with `#`, padded with spaces or holding a line break), is listed as unmatched instead of guessed. DM, chat and mail folders with no address list get an `access rule add` command to fill in. On a brain that serves one person it says there is nothing to propose and reads no pages. It works the same on a repo-less brain and a git brain, and refuses to write its files inside a git work tree.--### Itemized changes--- `src/commands/repair-propose.ts` (new): builds the proposal, writes each slugs file through an exclusive temp file and a rename, and shell-quotes every printed command.-- `src/commands/repair.ts`: new `--propose` and `--out` flags on `gbrain repair visibility`.-- `src/core/access/open-pages.ts`, `src/commands/access-serves.ts`: share the open-page query and git-root lookup with the new command.-- New error code `repair_propose_dir_in_git`, listed in `docs/guides/error-codes.md`.-- Docs: `docs/guides/repair.md` (proposing readers) and `docs/architecture/key-files/access.md`.-- Tests: new `test/repair-visibility-propose-gst2670.test.ts` (PGLite and Postgres).diff --git a/changelog.d/capy-severe-five.md b/changelog.d/capy-severe-five.mddeleted file mode 100644index b01c7c93a5..0000000000--- a/changelog.d/capy-severe-five.md+++ /dev/null@@ -1,23 +0,0 @@-----important: data-loss-----**Purging a page retires the facts extracted from it, `gbrain migrate embeddings` stops refusing on some databases, a growing transcript is no longer re-synthesized on every dream pass, legacy embedding labels no longer wipe valid vectors, and search says how far an upgrade's index rebuild has got.**--<!-- behavior-change: resynthesis_hold_6753 -->--### Fixed--- **Facts extracted from a purged page are retired with it** (#8859, reported by @ocscdsa). Facts the extractor filed on no page and that name the page only in their context stayed active after the page was retired or purged. Retire and purge now match them too. Facts left behind by earlier purges are not changed here.-- **`gbrain migrate embeddings` no longer always refuses with "Source census changed while acquiring locks"** on databases whose collation sorts source ids differently from code-unit order (#9307, reported by @ozabramov; first fixed by @Masashi-Ono0611 in #9310).-- **A growing transcript is re-synthesized at most twice a day** (#6753, reported by @andreineacsu). A transcript synthesized within `dream.synthesize.cooldown_hours` is held, so repeats drop from up to 24 a day to 2. The daily spend ceiling is unchanged ($120 worst case). Explicit `--input` and `--date` runs are never held.-- **Chunks stamped with a bare model label keep their vectors** (#8533, reported by @babyspectrum). The false-stamp guard, the projection preserve check and the stale-signature invalidation now share one rule: a bare label counts when its model name and width match the configured model; a different explicit provider prefix is still invalidated. Before, the last two nulled valid vectors and forced a paid re-embed.-- **Search says how far an upgrade's index rebuild has got** (#9192, reported by @jonahberg). While the rebuild runs, the partial-results notice gives pages done out of total, the measured rate and the command to watch progress, and the upgrade prints it once.--### Itemized changes--- `src/core/facts/gone-page-facts.ts`, `src/core/facts/subject-infer.ts`, `src/core/persistence/page-purge.ts`: extracted-from-page facts are expired and purged with their page.-- `src/commands/migrate-embeddings.ts`: the locked census is sorted the same way as the requested source list.-- `src/core/cycle/synthesize-completion.ts`, `src/core/cycle/synthesize.ts`: per-transcript re-synthesis hold.-- `src/core/embedding-invalidation.ts`, `src/core/engine-sql/chunks.ts`, `src/core/page-state/projections.ts`: one `chunkModelMatchesSql` rule.-- `src/core/search/retrieval-coverage.ts`, `src/core/ops/search.ts`, `src/core/interop-notices.ts`, v153's notice handler: rebuild progress.-- Tests: one new test per fix, on PGLite and Postgres where the bug is engine-specific; the #5051 test changes one assertion and its count.diff --git a/changelog.d/capy-skill-resolver-no-skill-gate-gst2704.md b/changelog.d/capy-skill-resolver-no-skill-gate-gst2704.mddeleted file mode 100644index 2df978ff1f..0000000000--- a/changelog.d/capy-skill-resolver-no-skill-gate-gst2704.md+++ /dev/null@@ -1,7 +0,0 @@-**The skill resolver now leaves its skills block out when no skill fits the message, instead of showing one on every turn.**--### Fixed-- `gbrain skills resolve`, the hook lane, and the OpenClaw and Pi plugins apply `top_gate` by default (0.6): a block whose best skill only matches weakly is left out (`block_reason: weak_top_match`), and a skill named in the message still gets through. On harness-evals' public set P with its 351-skill catalog, blocks on requests that need no skill drop from 61 of 61 to 7 of 61, and the acceptable skill stays in the block for 174 of 228 skill requests (176 before). `skills.resolver.top_gate 0` restores the old behavior.-- `gbrain skills resolve` and the OpenClaw and Pi plugins now read `skills.resolver.top_gate` (and `per_harness.<harness>.top_gate`); before, only the hook lane did. `--top-gate` still wins on the command line.--<!-- behavior-change: skill_resolver_gate_default_gst2704 -->diff --git a/changelog.d/capy-split-slow-enforced-member-tests.md b/changelog.d/capy-split-slow-enforced-member-tests.mddeleted file mode 100644index 45f1d4ee14..0000000000--- a/changelog.d/capy-split-slow-enforced-member-tests.md+++ /dev/null@@ -1,7 +0,0 @@-**Two slow test files are split along their own seams, so no file comes near CI's 300-second per-file limit.** `test/enforced-member.serial.test.ts` took 185 to 191 s on a 4-vCPU machine, and CI killed it at 300 s on slow runners with no assertion failing. It is now three serial files that take at most 77 s each. `test/setup-serves-several.test.ts` took 193 to 240 s and is now three unit files that take at most 78 s each. The tests and assertions are unchanged (27 and 645, and 27 and 270), and no product code, timeout, budget or retry count changed.--### Tests--- `test/enforced-member.serial.test.ts` keeps the reads and refusals. Writes and the git commit-push suite move to `test/enforced-member-writes.serial.test.ts`, and the `access.enforced_member_writes` case moves to `test/enforced-member-writes-setting.serial.test.ts`. Each file seeds its own brain through `test/helpers/enforced-member-brain.ts`.-- The spawned `gbrain setup` cases split out of `test/setup-serves-several.test.ts` into `test/setup-serves-stdio-member.test.ts` and `test/setup-serves-upgrade.test.ts`, with the shared box in `test/helpers/setup-serves-box.ts`.-- The new serial files get rows in `scripts/serial-files.tsv`, `test/postgres-unit-arms.txt` and `scripts/postgres-arm-weights.json`. The unit and serial weight maps get no hand-added rows, because they must match the miner's metadata, so new files use the p75 estimate until the next re-mine.diff --git a/changelog.d/capy-squash-landing.md b/changelog.d/capy-squash-landing.mddeleted file mode 100644index 8428fd9696..0000000000--- a/changelog.d/capy-squash-landing.md+++ /dev/null@@ -1,6 +0,0 @@-**docs/RELEASING.md now says how a pull request lands on master: as one commit titled with the pull request's title and number.**--### Changed--- docs/RELEASING.md, "Releases per batch", has a "How a PR lands" paragraph: each pull request, release pull requests included, lands as one squashed commit whose subject is its title followed by `(#<number>)`, with other authors credited by `Co-authored-by:` trailers, while branches keep bringing master in with merge commits and are never rebased.-- The contributor audit's offline fixture now includes a squashed `(#<number>)` commit next to its "Merge pull request" merges, so the audit's tests cover both commit shapes it reads.diff --git a/changelog.d/capy-thin-client-serve-stdio-bridge.md b/changelog.d/capy-thin-client-serve-stdio-bridge.mddeleted file mode 100644index 7b8c4d930c..0000000000--- a/changelog.d/capy-thin-client-serve-stdio-bridge.md+++ /dev/null@@ -1,13 +0,0 @@-**On a thin client, `gbrain serve` now connects a stdio-only agent harness to your remote brain instead of refusing.**--Install the gbrain CLI on the agent's machine, run `gbrain init --mcp-only` with an OAuth client from the brain host, and register `gbrain serve` as the harness's stdio MCP server, the same entry a local brain uses. Every call goes to the brain host with that client's grant and comes back unchanged, refusals included; the bridge opens no local database, stores no page text and adds no access. Reported and first proposed by @jel405 (#8543).--### Itemized changes--- Bare `gbrain serve` on a thin client is a stdio bridge. It accepts `--surface`, `--advertise` and `--source-guard` (the argv gbrain's plugins register); `request_tools {surface}` widens only the session and writes nothing on the host. `serve --http`, `--access` and the other host flags still refuse with `requires_local_engine`, with a fix that keeps the flags (`--access` points at registering a narrow read-only client instead).-- Bridge failures are v1 agent envelopes with a bounded recovery and a fix that never adds a scope. A write whose answer was lost keeps its `request_id` (`write_outcome_unknown`) so it can be checked or resent without writing twice. URLs in envelopes and stderr lose their userinfo, query and fragment.-- A call that names an audience (`_meta.on_behalf_of`) is relayed only to a host that enforces it (gbrain 0.60.543.0 or newer); otherwise the bridge answers `host_upgrade_required`.-- `gbrain doctor` on a read or read+write thin client reports the missing admin scope as expected instead of advising a re-register with admin.-- `gbrain agent register --harness openclaw` prints the lines to run on the OpenClaw machine: `gbrain init --mcp-only …` then `openclaw mcp add gbrain --command "$(command -v gbrain)" --arg serve …`.--<!-- behavior-change: thin_client_serve_stdio_bridge_8543 -->diff --git a/changelog.d/fix-timeline-retract-version-scan.md b/changelog.d/fix-timeline-retract-version-scan.mddeleted file mode 100644index 43fc9eea5c..0000000000--- a/changelog.d/fix-timeline-retract-version-scan.md+++ /dev/null@@ -1,6 +0,0 @@-**`gbrain extract timeline --source db` no longer fails on a large page with many stored versions on a managed Postgres brain.**--Retraction used to read every stored version of the page in one statement inside the publication transaction. With hundreds of versions that statement ran past the 5 second statement timeout on every retry, so the page's timeline extract failed with `write_interrupted` on every maintenance run. The version scan now runs before the transaction and reads one version at a time. Inside the transaction gbrain only checks that the versions it read are still the page's, with the same text. A row whose versions changed in between stays until the next run. Reported in #9362.--### Fixed-- `gbrain extract timeline --source db` and the maintenance timeline pass no longer time out with `write_interrupted` on a page with hundreds of stored versions (#9362).diff --git a/changelog.d/garrytan-guest-notes-follow-ups.md b/changelog.d/garrytan-guest-notes-follow-ups.mddeleted file mode 100644index 18b67f03e6..0000000000--- a/changelog.d/garrytan-guest-notes-follow-ups.md+++ /dev/null@@ -1,18 +0,0 @@-**Guest notes now refuse writes from a database role that cannot see which sources are guest sources, and several smaller guest-note gaps from the first release are closed.**--A brain whose gbrain process connects to Postgres as a scoped row-level-security role used to read the guest source list as empty, so a write into a guest source passed as if the source were ordinary. Such a role is now refused with `writer_coordinator_required` until it can read `guest_sources` (one SELECT policy, added to the maintainer recipe in docs/ENGINES.md). The owner, a role that bypasses row-level security and PGLite brains see no change.--### Fixed-- Schema migration v314 re-creates the guest guard in the trust trigger and the guest-record guard so they refuse a role that row-level security keeps from reading `guest_sources`; guest admission, `remember`, links and remote deletes refuse the same way instead of treating the source as ordinary.-- `gbrain guests promote` no longer answers `already_promoted` when the kept page was purged, so promoting again writes the page and keeps one link. v314 adds a unique index on the promotion link (a brain that already holds duplicate links keeps them, gets no index and a warning), and two promotions of the same note to the same page that race each other both succeed with one link.-- A guest note whose mark writes no row now fails the save instead of committing a guest page with no mark.-- `gbrain guests init` counts the source's pages under the source row's lock, so no page can land between the check and the change.-- The repair `gbrain doctor` suggests for a source whose config says guest but has no guest record, `gbrain guests init --source <id> --yes`, now works when the source holds pages.-- A cycle phase skipped because the guest-source lookup failed now says the lookup failed (`reason: guest_source_lookup_failed`, with the error), instead of reporting a plain guest-source skip.-- A read the guest-note stamp cannot copy is refused, instead of marking the handler's own object.-- A page write on a brain whose schema is behind the guest-notes migration is refused `migrations_pending` instead of failing with a missing-table error.-- The owner-credential read behind `gbrain guests grant-owner-clients` and doctor's `guest_source` check no longer loads token hashes.-- `gbrain auth rescope --client <id>` with no grant flag now prints the client's operations and slug prefixes, and `gbrain delete --help` says `--expected-revision` is required unless `--force`.-- docs/guides/guest-notes.md gives the setup order that works (init, register the broker client, rescope its operations, then add it as a writer), and says that deletes need a revision or `--force` and that a put with attribution but no audience is refused `readable_by_invalid`.--<!-- behavior-change: guest_sources_scoped_role_fail_closed_9354 -->diff --git a/changelog.d/garrytan-wakeshift-emit-spool.md b/changelog.d/garrytan-wakeshift-emit-spool.mddeleted file mode 100644index 5a55bca0ea..0000000000--- a/changelog.d/garrytan-wakeshift-emit-spool.md+++ /dev/null@@ -1,8 +0,0 @@-**On a PGLite brain held by `gbrain serve` or the job worker, `gbrain wakeshift emit cron.finished` now records the run instead of dropping it, and revoking a credential always ends its watches.**--### Fixed--- A cron run that finished while `gbrain serve` or `gbrain jobs work` held the PGLite brain was lost. Emit now saves it as a small private file (0600) under the brain's own gbrain home, and the process holding the brain records it within seconds with its original finish time, so a watcher still wakes. Two processes reading the folder at once never record a run twice. A file that is malformed, oversized or has an impossible time goes to `rejected/` with one stderr line and never holds back the runs after it. At most 1,000 runs wait per brain. Postgres brains and brains with reporting back off never use the folder.-- The next direct `emit` also records any leftover runs, and it records its own run even when the leftovers can't be read.-- `gbrain auth revoke --id <id>` with a legacy token id written in uppercase now ends that token's watches and asks Wakeshift to forget its user.-- When removing an access member failed to ask Wakeshift to forget that member's user, the wake drainer now asks again. A member who is still active keeps their Wakeshift user.diff --git a/changelog.d/garrytan-wakeshift-rest.md b/changelog.d/garrytan-wakeshift-rest.mddeleted file mode 100644index d4cc5ad3f9..0000000000--- a/changelog.d/garrytan-wakeshift-rest.md+++ /dev/null@@ -1,13 +0,0 @@-**gbrain can now report back when a pending write settles or a cron run finishes, on brains shared with access members, and to OpenClaw and thin-client agents. Reporting back stays off until the brain owner turns it on.**--Two new events join job completion. `watch_write_request` wakes the conversation when a `write_pending` write commits, fails, conflicts or is cancelled. It uses the same check as `get_write_request`, so someone else's request reads as not found. `watch_cron` wakes it after the next run of a cron the owner registered with `gbrain wakeshift cron add <name>`. The cron's own script ends with `gbrain wakeshift emit cron.finished --name <name> --status ok|failed`, which records the run and never blocks or fails the script, even when it can't open the brain. On a PGLite brain, a run that finishes while `gbrain serve` or a job worker holds the brain isn't recorded. Every wake is still a pointer (ids, status and times), never page text or cron output. A brain with access members can now report back too. The owner gives their terms and privacy links to `gbrain wakeshift enable`, and each member's agent shows the agreement step and records acceptance before its first watch. Removing a member, revoking a token or deleting an OAuth client ends that principal's watches and asks Wakeshift to forget its user. Guide: docs/guides/wakeshift.md.--### Itemized changes--- New MCP tools `watch_write_request`, `watch_cron` and `accept_wakeshift_terms`, listed only while reporting back is on. `list_watches` and `unwatch` now cover every kind of watch.-- New `gbrain wakeshift cron add | remove | list` and `gbrain wakeshift emit cron.finished`. `enable` takes `--terms-url` and `--privacy-url` (https), which a brain with access members needs. `status` and doctor say when gbrain's published events are older than the installed gbrain; run `gbrain wakeshift enable` again to publish the new ones.-- New `gbrain wakeshift watch job <id> | write <request_id> | cron <name>`, which runs on a thin client (`gbrain init --mcp-only`). It prints Wakeshift's instructions as the last line and never saves a session key.-- New `gbrain setup openclaw --wakeshift`. After consent, it installs and enables Wakeshift's OpenClaw plugin, pinned at `@wakeshift/[email protected]`. On a gateway that listens beyond the machine, it prints Wakeshift's question about the hooks endpoint and never answers it. A new doctor check `wakeshift_openclaw` warns when the installed plugin differs from the pin.-- `gbrain setup claude-code` and `gbrain setup codex` show a "Report back (Wakeshift)" row in the first-run settings. After a remote `submit_job` or `submit_agent`, a once-per-session notice (`wakeshift_report_back`, muteable) says how to have the conversation woken. With reporting back on, the MCP instructions gain one sentence about it. With it off, the instructions are unchanged.-- Fixed: Wakeshift's instructions in a watch result were cut at 2,000 characters, which dropped the step that starts Claude Code's listener. They now pass through whole, up to 16,000.-- Schema migration v313 adds `wake_crons`, `wake_cron_runs`, `wake_terms_acceptances`, `wake_forgets` and `wake_subscriptions.target_ref`. All are empty unless reporting back is on, and repo-less brains get them unchanged.diff --git a/openclaw.plugin.json b/openclaw.plugin.jsonindex 8dc41776cf..ee20c436f9 100644--- a/openclaw.plugin.json+++ b/openclaw.plugin.json@@ -1,7 +1,7 @@{"id": "gbrain-context-engine","name": "gbrain",- "version": "0.60.722.0",+ "version": "0.60.723.0","description": "Personal knowledge brain with Postgres + pgvector hybrid search","family": "bundle-plugin","kind": "context-engine",diff --git a/package.json b/package.jsonindex 6665d53b90..c74ab59f77 100644--- a/package.json+++ b/package.json@@ -259,7 +259,7 @@"bun": ">=1.4.4"},"license": "MIT",- "version": "0.60.722.0",+ "version": "0.60.723.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 c0c5134786..275c8bf583 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.722.0",+ "version": "0.60.723.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 561decfd3a..b9de4f14d0 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.722.0",+ "version": "0.60.723.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 ff1b4043c1..1c0308a36d 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.722.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.723.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 bba50ca6bf..375ee45189 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.722.0",+ "version": "0.60.723.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 8ef06cd8bd..53d029f999 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.722.0",+ "version": "0.60.723.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 27d7bb19a7..5d0f023155 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.722.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.723.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 1624595915..12dcfd8fe0 100644--- a/plugin/README.md+++ b/plugin/README.md@@ -1,4 +1,4 @@-<!-- gbrain-plugin-tree-stamp: 0.60.722.0 -->+<!-- gbrain-plugin-tree-stamp: 0.60.723.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 2f8b20e6ef..c408df3fd1 100644--- a/src/core/behavior-changes.generated.ts+++ b/src/core/behavior-changes.generated.ts@@ -72,6 +72,15 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin{ since: '0.60.721.0', id: 'derived_origin_carry_private_gst2689', text: "Deleting a page that keeps other pages private now writes a visibility: private label on each page that was private only because of it (a summary whose derived_from names it, an atom extracted from it, a synthesized concept built from such an atom), before the deleted page's row is removed. On a brain with Git the derived page's file gains that one label line. The label stays if you restore the deleted page later. If a label cannot be written, the purge keeps the deleted page soft-deleted and gbrain doctor reports it as derived_origin_parked with the page that blocks it; an explicit gbrain delete --purge then returns purge_held instead of purging." },{ since: '0.60.722.0', id: 'owner_remote_private_writes_gst2091', text: "The brain owner's own remote agents can now change private pages. A credential bound to the brain owner (gbrain access owner set) that has write scope and speaks for itself (no audience, not an attested call, not a subagent job, no slug fence) may rewrite, edit, append to and relabel a page marked visibility: private that it already reads, through put_page, edit_page and append_page, and through put_pages and staged uploads (begin_page_upload and commit_page_upload), which write the same pages; before, these writes answered page_not_found. A put_page that leaves out visibility or readable_by keeps the stored ones, an empty visibility counts as left out, and a page private only through a privacy alias, a pinned question, a derived type or a private origin is saved as visibility: private (a pinned question keeps its marker) by any of these writes that states no visibility; the change is recorded under the owner's credential. Everyone else is refused exactly as before: other members, unbound tokens and OAuth clients, attested calls, the owner's credential asserting a shared room, the owner's credential without write scope, and any write to a page whose readable_by or folder rule leaves the owner out. delete_page on a private page, and any write to a soft-deleted private page, stays refused, and a credential fenced to slug prefixes, even after the write was submitted, gets no owner widening. An owner who does not want an agent to change private pages gives that agent a credential without write scope (gbrain auth create <name> --member <owner> --scopes read; without --scopes the token gets full access), or binds it to its own member instead of the owner." },{ since: '0.60.722.0', id: 'guest_notes_gbra504', text: "New guest notes (GBRA-504): a brain can keep what people outside it say in a group chat with your agent, in a guest source that only a listed broker credential writes, once per note. Nothing changes until you run gbrain guests init: a brain without a guest source reads, writes and costs exactly as before, and no grant, privacy label or search scope changes on upgrade. With a guest source, every read that returns a guest note marks it as an outside guest's words (origin guest, trust tier external_untrusted, a guest object in JSON and a warning line in text), guest notes feed no facts, takes, timeline entries or links, and your own CLI cannot write there. You keep a note as your own page with gbrain guests promote <slug> (MCP promote_guest_note, owner only; anyone else is refused guest_promotion_owner_only), after which the broker can no longer delete it (guest_page_promoted). A guest writer can delete only the guest notes it saved itself. Your own tokens and OAuth clients read the guest source only once it is on their read list: gbrain guests grant-owner-clients previews that and --yes applies it, and gbrain doctor --only guest_source checks the whole setup." },+ { since: '0.60.723.0', id: 'access_rule_keeps_owner_gst2698', text: "gbrain access rule add now refuses a reader list that leaves out the brain owner when one is set (gbrain access owner), the same refusal gbrain repair visibility --readers already gives (readers_omit_owner), because such a rule closes the folder or page to the owner's own keys. Add the owner to --readers, or pass --allow-without-owner when the owner should not read it. A group that holds the owner does not count. Rules already in place are not changed, and a brain with no owner set behaves as before." },+ { since: '0.60.723.0', id: 'new_sources_join_default_search_gst2732', text: "A source added with no `--federated` or `--no-federated` choice is now federated (in default search, and readable by connections with no source grant) when the brain serves one person: `access.serves` reads one, `brain.audience` classifies personal and the client is not thin. Otherwise it stays unset as before, and `sources add` and `sync --source <id>` print the `source_not_in_default_search` notice with `gbrain sources federate <id>` as the fix (asking the user first on a shared brain). Existing sources are not changed. Adds from a remote MCP caller keep the old default." },+ { since: '0.60.723.0', id: 'plain_folder_sources_gst2732', text: "`gbrain sources add <id> --path <folder>` no longer needs `--force` for a plain folder outside any git repository: it registers as a plain directory (sync imports its files without Git, a removed file keeps its page). The `not_a_git_repo` refusal now applies only to a path inside a git repository with no committed, tracked content." },+ { since: '0.60.723.0', id: 'install_no_postinstall_gst2732', text: "gbrain ships no postinstall script, so a global `bun install -g` of the stable release no longer ends with Bun's \"Blocked 1 postinstall\" line and a clone's `bun install` no longer prints \"postinstall skipped\". Nothing it did is lost: every command already refuses on a Bun below the floor, `gbrain setup` applies a new brain's setup migrations, `gbrain upgrade` runs migrations in post-upgrade, and the first command on a brain applies pending schema migrations. New: when upgrade migrations are still pending (after reinstalling over an older brain with `bun install -g`), every command except apply-migrations, upgrade, post-upgrade, doctor, init, setup and serve prints a `migrations_pending` notice naming them, with `gbrain apply-migrations --yes` as the fix." },+ { since: '0.60.723.0', id: 'first_run_connects_then_reports_gst2732', text: "`gbrain init` no longer asks the user to approve connecting gbrain to their agent. The first-run bundle (`first_run_decisions`) now lists the settings in effect and how to change them, with no \"Reply 'defaults'\" question: search mode as applied, automatic saving (`writeback`) shown as in effect `off` with `salient` recommended (it was shown as default `salient` while off), skills and upkeep. Connecting the agent moved out of the bundle into its own `harness_wiring` notice (kind info, actor agent, no consent), because it is an install step. The install docs (AGENTS.md step 3, INSTALL_FOR_AGENTS.md Step 3.5) drop the STOP for every harness: connect first, then relay the settings and the cost matrix in the reply that reports the install. Nothing paid turns on from these settings without a key the user supplied." },+ { since: '0.60.723.0', id: 'resynthesis_hold_6753', text: "gbrain dream no longer re-synthesizes a transcript that keeps growing on every pass. A transcript synthesized within dream.synthesize.cooldown_hours (12 by default) is held until that window passes, and the run reports how many grown transcripts it held (resynthesis_cooldown). A busy transcript is now re-synthesized at most twice a day instead of up to 24 times; the daily spend ceiling is unchanged. An explicit gbrain dream --input or --date run is never held. To re-synthesize sooner, lower dream.synthesize.cooldown_hours or pass --input." },+ { since: '0.60.723.0', id: 'skill_resolver_gate_default_gst2704', text: "The skill resolver now stays quiet when no skill fits. Before, it showed a skills block on almost every message, including ones that need no skill, because some skill always shared a word with the message. It now leaves the block out when its best match is weak (skills.resolver.top_gate, default 0.6), and a skill you name in the message is still suggested. On a 351-skill public test catalog this cut blocks on no-skill requests from 100% to 11.5% and kept the right skill in the block for 174 of 228 requests that needed one, against 176 before. To tune it, run gbrain config set skills.resolver.top_gate <number>; set it to 0 to get the old behavior back. OpenClaw and Pi pick up the setting on the next gbrain setup <harness> --skill-loading resolve." },+ { since: '0.60.723.0', id: 'thin_client_serve_stdio_bridge_8543', text: "On a thin client (gbrain init --mcp-only), plain `gbrain serve` no longer refuses: it is now a stdio MCP server that relays every call to the brain host with the stored OAuth client's grant, opens no local database and adds no access. A harness entry that runs `gbrain serve` on a thin client now connects to the remote brain instead of exiting with requires_local_engine. `gbrain serve --http`, `--access` and the other host flags still refuse there. `gbrain doctor` on a read or read+write client now reports the missing admin scope as expected (ok) instead of a warning that suggested re-registering with admin." },+ { since: '0.60.723.0', id: 'guest_sources_scoped_role_fail_closed_9354', text: "Brains whose gbrain process connects to Postgres as a scoped row-level-security role now need that role to read the guest_sources table. Before, such a role read it as empty, so guest-source checks passed every write as if no source were a guest source. Now a role that row-level security keeps from reading guest_sources is refused with writer_coordinator_required (unreadable_state, state guest_sources) on page, fact, take and timeline writes, because it cannot tell a guest source from an ordinary one. The table owner, a role that bypasses row-level security, and PGLite brains are unaffected. To keep writing, give the scoped writer the SELECT policy on guest_sources from the maintainer recipe in docs/ENGINES.md (derived-state maintainers)." },];/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */@@ -145,4 +154,13 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {derived_origin_carry_private_gst2689: '0.60.721.0',owner_remote_private_writes_gst2091: '0.60.722.0',guest_notes_gbra504: '0.60.722.0',+ access_rule_keeps_owner_gst2698: '0.60.723.0',+ new_sources_join_default_search_gst2732: '0.60.723.0',+ plain_folder_sources_gst2732: '0.60.723.0',+ install_no_postinstall_gst2732: '0.60.723.0',+ first_run_connects_then_reports_gst2732: '0.60.723.0',+ resynthesis_hold_6753: '0.60.723.0',+ skill_resolver_gate_default_gst2704: '0.60.723.0',+ thin_client_serve_stdio_bridge_8543: '0.60.723.0',+ guest_sources_scoped_role_fail_closed_9354: '0.60.723.0',};diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.mdindex 1201255b8c..2e778d093d 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.722.0 -->+<!-- gbrain-template-stamp: 0.60.723.0 -->This repository is the **"Use this template"** distribution artifact for a[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same