Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

Release v0.60.722.0

garrytan4be849414f69
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 4ece943867..eaf53a417a 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.721.0",
+ "version": "0.60.722.0",
"description": "Personal knowledge brain for your coding agent — hybrid search, synthesis, graph traversal, and durable cross-session memory over Postgres/PGLite with pgvector, plus a curated brain-first skill set.",
"author": {
"name": "Garry Tan",
diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json
index 31124edbba..cb38df2ab0 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "gbrain",
- "version": "0.60.721.0",
+ "version": "0.60.722.0",
"description": "Personal knowledge brain for your coding agent — hybrid search, synthesis, graph traversal, and durable cross-session memory over Postgres/PGLite with pgvector, plus a curated brain-first skill set.",
"author": {
"name": "Garry Tan",
diff --git a/BOOTSTRAP_FOR_AGENTS.md b/BOOTSTRAP_FOR_AGENTS.md
index 5d394c0818..7b1be3a8be 100644
--- a/BOOTSTRAP_FOR_AGENTS.md
+++ b/BOOTSTRAP_FOR_AGENTS.md
@@ -1,4 +1,4 @@
-<!-- gbrain-runbook-stamp: 0.60.721.0 -->
+<!-- gbrain-runbook-stamp: 0.60.722.0 -->
<!-- This stamp must equal the VERSION file at every release; CI enforces it
(scripts/check-bootstrap-tag.sh). `gbrain bootstrap status` compares it to
the installed binary and warns on skew. -->
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 420d41482c..0cabeb8208 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,59 @@ credits are retained; no result has been reassigned to another provider. Origina
identifiers and attribution are available in the pre-removal Git revision
`6040075c6cb95be5881cc2e1b76ef7d71f4e5d29` (retained on 2026-09-23).
+## [0.60.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.**
+
+### Changed
+
+- A credential bound to the brain owner, with write scope and speaking for itself, may change a `visibility: private` page it reads with `put_page`, `edit_page` or `append_page`, or with `put_pages` and staged uploads (`begin_page_upload` and `commit_page_upload`), and relabel it (for example to `visibility: world`). 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` (keeping its `pinned_question`) by any of these writes that states no visibility; the page revision and the journaled request name the owner's credential. Other members, unbound tokens and OAuth clients, attested calls, the owner's credential without write scope and writes to pages whose readers or folder rule leave the owner out get `page_not_found` (or their earlier refusal) as before, on repo-less and repo brains alike, and so does any write to a soft-deleted private page and a credential fenced to slug prefixes. A staged upload over the single-string ceiling is now held to the same `readable_by` check as a smaller one.
+
+### Fixed
+
+- Purging a private page now also labels a life-chronicle event private when the event's own `derived_from` names that page; if the label can't be written, the page stays soft-deleted instead of being purged.
+- The purge's in-transaction check for derived pages reads only the pages that name the purged page instead of scanning the whole source, so single purges on large brains are much faster.
+- `gbrain pages purge-deleted --dry-run` now lists exactly what `--yes` would purge, including parked pages a consented run would release, and nothing is written before consent.
+- A purge held to keep derived pages private now tells the owner to finish it with `gbrain delete <slug> --purge --source-id <id>` as a new request, which writes the purge tombstones.
+
+<!-- behavior-change: owner_remote_private_writes_gst2091 -->
+
+**CI runs the unit suite in 34 shards instead of 30, so every shard fits its 600-second budget again.**
+
+### Changed
+- Shard timing weights are refreshed from the median of five recent nightly Test runs (unit and serial) and the latest full E2E nightly. With those weights the heaviest of 30 shards packed to just over 600 seconds; with 34 shards each packs to about 529 seconds.
+- The `test` job in test.yml and the `coverage-full-unit` job in e2e.yml both run 34 shards, and their coverage manifests expect all 34. A full run starts four more unit jobs than before.
+
+### Fixed
+- `bun run release:unstamp` no longer refuses a branch because master edited a published migration after the branch was cut. An edit the branch itself made to a published migration is still refused.
+
+**Guest notes: a group member's note is saved, marked as a guest's, warned about on every read, and becomes your own page only when you say so.** People in a group chat with your agent sometimes say things worth keeping. A guest source keeps those notes apart from your own pages, with a record of who said them. 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.
+
+A guest source has four rules the database enforces, whatever program writes. Only writers on the source's list (an OAuth client or legacy token, for example the broker your agent's host runs) may create a page there or change its text, and only as a new page; your own CLI, `gbrain import`, sync, `remember`, `add_link` and `put_raw_data` are refused `source_writer_restricted`, while delete, restore and purge from your CLI still work. No page there is ever stored above the `external_untrusted` trust tier, even after an owner rewrite or a trust confirmation. Guest notes feed no facts, takes, timeline entries or links (`guest_page_immutable`). And a guest source is database-only, so attaching a local path is refused. `gbrain guests init` also refuses an existing source that already holds pages, deleted pages not yet purged included, so your own pages never turn into guest notes.
+
+When the writer saves a note, gbrain records who it was saved for, which group, when and which client sent it, in its own table that no later write can edit and that never comes from the page text. Every read that returns a guest note (search, query, get, list, find, backlinks, timeline, think and the rest) marks it as an outside guest's words: `origin: "guest"` and a `guest` object in JSON, and a warning line plus the external-data envelope in text. A contract test fails if any operation, present or future, returns a guest row without the mark.
+
+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`), which writes a normal page and records the link; the broker can no longer delete a promoted note (`guest_page_promoted`). Promotion reads the note through the caller's normal read scope, and promoting again finishes a promotion whose link was not recorded (an interrupted run or a write still pending) without writing the page twice. 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. `gbrain doctor --only guest_source` checks the whole setup, including that the source's two records agree.
+
+### Added
+- `gbrain guests init --writer <principal>` (preview, then `--yes`) creates or marks the `guests` source; `gbrain sources writers <id> [--add|--remove|--clear]` changes who may write.
+- `gbrain guests promote <slug>` and MCP `promote_guest_note`: the owner keeps a guest note as their own page.
+- `gbrain guests grant-owner-clients`: adds the guest source to the owner's own clients' read lists, preview first.
+- Doctor check `guest_source`.
+- Error codes `source_writer_restricted`, `guest_page_immutable`, `guest_promotion_owner_only`, `guest_page_promoted` and their recovery paths (docs/guides/error-codes.md, docs/guides/write-refusals.md).
+- Guide: docs/guides/guest-notes.md.
+
+### Itemized changes
+- The guest-notes schema migration (`src/core/schema-migrations/v<NNN>-guest-notes.ts`; `GUEST_NOTES_MIGRATION` in `src/core/guests/migration.ts` names its number): the `guest_sources`, `guest_marks` and `guest_promotions` tables under row-level security, the per-source trust ceiling in the trust trigger, and the writer backstop trigger.
+- `src/core/guests/`: admission (writer list, new-page-only, allowed frontmatter and readers), the mark and its warning, derived-row refusals, promotion, owner credentials and source setup.
+- Read paths (`src/cli/page-render.ts`, `src/cli/search-row-format.ts`, `src/cli/guest-lines.ts`, `src/core/access/page-items.ts`, `src/core/think/index.ts`, `src/core/search/transcript-quote.ts`) carry the guest mark and warning.
+- A guest writer can delete only the guest notes it saved itself; deleting a note another writer saved is refused `permission_denied`.
+- Stale extraction, `propose_takes` (scoped or not) and the cycle's fact, atom and enrichment phases leave guest pages out.
+- Reads on a brain whose schema is still behind that migration keep working, because the guest check falls back to the source config when the `guest_sources` table is missing.
+- Goldens regenerated: `test/fixtures/goldens/sql-text/pages.json` (stale-extraction query excludes guest pages), `test/fixtures/goldens/exports/types.json` (guest types and error codes), the doctor goldens (the `guest_source` row and the three new tables under row-level security) and `test/fixtures/goldens/cli/tools-json.json` (the new operation).
+
+<!-- behavior-change: guest_notes_gbra504 -->
+
## [0.60.721.0] - 2026-11-14
**Deleting a private page no longer opens the pages derived from it: each page that was private only because of the deleted page now gets its own `visibility: private` label before the deleted page's row goes.**
diff --git a/VERSION b/VERSION
index b9897e5044..91aacd527e 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.60.721.0
+0.60.722.0
diff --git a/changelog.d/capy-owner-remote-private-writes.md b/changelog.d/capy-owner-remote-private-writes.md
deleted file mode 100644
index ac7f2201e3..0000000000
--- a/changelog.d/capy-owner-remote-private-writes.md
+++ /dev/null
@@ -1,14 +0,0 @@
-**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.**
-
-### Changed
-
-- A credential bound to the brain owner, with write scope and speaking for itself, may change a `visibility: private` page it reads with `put_page`, `edit_page` or `append_page`, or with `put_pages` and staged uploads (`begin_page_upload` and `commit_page_upload`), and relabel it (for example to `visibility: world`). 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` (keeping its `pinned_question`) by any of these writes that states no visibility; the page revision and the journaled request name the owner's credential. Other members, unbound tokens and OAuth clients, attested calls, the owner's credential without write scope and writes to pages whose readers or folder rule leave the owner out get `page_not_found` (or their earlier refusal) as before, on repo-less and repo brains alike, and so does any write to a soft-deleted private page and a credential fenced to slug prefixes. A staged upload over the single-string ceiling is now held to the same `readable_by` check as a smaller one.
-
-### Fixed
-
-- Purging a private page now also labels a life-chronicle event private when the event's own `derived_from` names that page; if the label can't be written, the page stays soft-deleted instead of being purged.
-- The purge's in-transaction check for derived pages reads only the pages that name the purged page instead of scanning the whole source, so single purges on large brains are much faster.
-- `gbrain pages purge-deleted --dry-run` now lists exactly what `--yes` would purge, including parked pages a consented run would release, and nothing is written before consent.
-- A purge held to keep derived pages private now tells the owner to finish it with `gbrain delete <slug> --purge --source-id <id>` as a new request, which writes the purge tombstones.
-
-<!-- behavior-change: owner_remote_private_writes_gst2091 -->
diff --git a/changelog.d/capy-unit-shards-34.md b/changelog.d/capy-unit-shards-34.md
deleted file mode 100644
index ac15d3f6d4..0000000000
--- a/changelog.d/capy-unit-shards-34.md
+++ /dev/null
@@ -1,8 +0,0 @@
-**CI runs the unit suite in 34 shards instead of 30, so every shard fits its 600-second budget again.**
-
-### Changed
-- Shard timing weights are refreshed from the median of five recent nightly Test runs (unit and serial) and the latest full E2E nightly. With those weights the heaviest of 30 shards packed to just over 600 seconds; with 34 shards each packs to about 529 seconds.
-- The `test` job in test.yml and the `coverage-full-unit` job in e2e.yml both run 34 shards, and their coverage manifests expect all 34. A full run starts four more unit jobs than before.
-
-### Fixed
-- `bun run release:unstamp` no longer refuses a branch because master edited a published migration after the branch was cut. An edit the branch itself made to a published migration is still refused.
diff --git a/changelog.d/gbra504-guest-notes-4-promotion.md b/changelog.d/gbra504-guest-notes-4-promotion.md
deleted file mode 100644
index 2330b279b7..0000000000
--- a/changelog.d/gbra504-guest-notes-4-promotion.md
+++ /dev/null
@@ -1,26 +0,0 @@
-**Guest notes: a group member's note is saved, marked as a guest's, warned about on every read, and becomes your own page only when you say so.** People in a group chat with your agent sometimes say things worth keeping. A guest source keeps those notes apart from your own pages, with a record of who said them. 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.
-
-A guest source has four rules the database enforces, whatever program writes. Only writers on the source's list (an OAuth client or legacy token, for example the broker your agent's host runs) may create a page there or change its text, and only as a new page; your own CLI, `gbrain import`, sync, `remember`, `add_link` and `put_raw_data` are refused `source_writer_restricted`, while delete, restore and purge from your CLI still work. No page there is ever stored above the `external_untrusted` trust tier, even after an owner rewrite or a trust confirmation. Guest notes feed no facts, takes, timeline entries or links (`guest_page_immutable`). And a guest source is database-only, so attaching a local path is refused. `gbrain guests init` also refuses an existing source that already holds pages, deleted pages not yet purged included, so your own pages never turn into guest notes.
-
-When the writer saves a note, gbrain records who it was saved for, which group, when and which client sent it, in its own table that no later write can edit and that never comes from the page text. Every read that returns a guest note (search, query, get, list, find, backlinks, timeline, think and the rest) marks it as an outside guest's words: `origin: "guest"` and a `guest` object in JSON, and a warning line plus the external-data envelope in text. A contract test fails if any operation, present or future, returns a guest row without the mark.
-
-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`), which writes a normal page and records the link; the broker can no longer delete a promoted note (`guest_page_promoted`). Promotion reads the note through the caller's normal read scope, and promoting again finishes a promotion whose link was not recorded (an interrupted run or a write still pending) without writing the page twice. 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. `gbrain doctor --only guest_source` checks the whole setup, including that the source's two records agree.
-
-### Added
-- `gbrain guests init --writer <principal>` (preview, then `--yes`) creates or marks the `guests` source; `gbrain sources writers <id> [--add|--remove|--clear]` changes who may write.
-- `gbrain guests promote <slug>` and MCP `promote_guest_note`: the owner keeps a guest note as their own page.
-- `gbrain guests grant-owner-clients`: adds the guest source to the owner's own clients' read lists, preview first.
-- Doctor check `guest_source`.
-- Error codes `source_writer_restricted`, `guest_page_immutable`, `guest_promotion_owner_only`, `guest_page_promoted` and their recovery paths (docs/guides/error-codes.md, docs/guides/write-refusals.md).
-- Guide: docs/guides/guest-notes.md.
-
-### Itemized changes
-- The guest-notes schema migration (`src/core/schema-migrations/v<NNN>-guest-notes.ts`; `GUEST_NOTES_MIGRATION` in `src/core/guests/migration.ts` names its number): the `guest_sources`, `guest_marks` and `guest_promotions` tables under row-level security, the per-source trust ceiling in the trust trigger, and the writer backstop trigger.
-- `src/core/guests/`: admission (writer list, new-page-only, allowed frontmatter and readers), the mark and its warning, derived-row refusals, promotion, owner credentials and source setup.
-- Read paths (`src/cli/page-render.ts`, `src/cli/search-row-format.ts`, `src/cli/guest-lines.ts`, `src/core/access/page-items.ts`, `src/core/think/index.ts`, `src/core/search/transcript-quote.ts`) carry the guest mark and warning.
-- A guest writer can delete only the guest notes it saved itself; deleting a note another writer saved is refused `permission_denied`.
-- Stale extraction, `propose_takes` (scoped or not) and the cycle's fact, atom and enrichment phases leave guest pages out.
-- Reads on a brain whose schema is still behind that migration keep working, because the guest check falls back to the source config when the `guest_sources` table is missing.
-- Goldens regenerated: `test/fixtures/goldens/sql-text/pages.json` (stale-extraction query excludes guest pages), `test/fixtures/goldens/exports/types.json` (guest types and error codes), the doctor goldens (the `guest_source` row and the three new tables under row-level security) and `test/fixtures/goldens/cli/tools-json.json` (the new operation).
-
-<!-- behavior-change: guest_notes_gbra504 -->
diff --git a/openclaw.plugin.json b/openclaw.plugin.json
index c9efbd1df6..8dc41776cf 100644
--- a/openclaw.plugin.json
+++ b/openclaw.plugin.json
@@ -1,7 +1,7 @@
{
"id": "gbrain-context-engine",
"name": "gbrain",
- "version": "0.60.721.0",
+ "version": "0.60.722.0",
"description": "Personal knowledge brain with Postgres + pgvector hybrid search",
"family": "bundle-plugin",
"kind": "context-engine",
diff --git a/package.json b/package.json
index e7f85fa2ac..c3929c00d3 100644
--- a/package.json
+++ b/package.json
@@ -260,7 +260,7 @@
"bun": ">=1.4.4"
},
"license": "MIT",
- "version": "0.60.721.0",
+ "version": "0.60.722.0",
"overrides": {
"@aws-sdk/util-format-url": "3.972.9",
"@ai-sdk/provider-utils": "4.0.56",
diff --git a/plugin-variants/gbrain-coding/.claude-plugin/plugin.json b/plugin-variants/gbrain-coding/.claude-plugin/plugin.json
index c8e27862fc..c0c5134786 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.721.0",
+ "version": "0.60.722.0",
"description": "Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant. (persona variant of the gbrain plugin — 21 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-coding/.codex-plugin/plugin.json b/plugin-variants/gbrain-coding/.codex-plugin/plugin.json
index 44809636aa..561decfd3a 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.721.0",
+ "version": "0.60.722.0",
"description": "Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant. (persona variant of the gbrain plugin — 21 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-coding/README.md b/plugin-variants/gbrain-coding/README.md
index d24d0290f7..ff1b4043c1 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.721.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.722.0 -->
# gbrain-coding (generated persona variant — do not hand-edit)
Brain-first coding agent working inside a repo: retrieval, routing, ingest discipline, correction hygiene. Default persona for the claude-code harness bridge; also published as the gbrain-coding marketplace variant.
diff --git a/plugin-variants/gbrain-daily/.claude-plugin/plugin.json b/plugin-variants/gbrain-daily/.claude-plugin/plugin.json
index bfb6e674a0..bba50ca6bf 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.721.0",
+ "version": "0.60.722.0",
"description": "Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant. (persona variant of the gbrain plugin — 20 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-daily/.codex-plugin/plugin.json b/plugin-variants/gbrain-daily/.codex-plugin/plugin.json
index 98f0ac49b6..8ef06cd8bd 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.721.0",
+ "version": "0.60.722.0",
"description": "Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant. (persona variant of the gbrain plugin — 20 skills)",
"author": {
"name": "Garry Tan",
diff --git a/plugin-variants/gbrain-daily/README.md b/plugin-variants/gbrain-daily/README.md
index 4085b37a4c..27d7bb19a7 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.721.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.722.0 -->
# gbrain-daily (generated persona variant — do not hand-edit)
Personal knowledge-brain daily use: meetings, tasks, briefings, reading, research. Published as the gbrain-daily marketplace variant.
diff --git a/plugin/README.md b/plugin/README.md
index e8e3cb3690..752c272f3c 100644
--- a/plugin/README.md
+++ b/plugin/README.md
@@ -1,4 +1,4 @@
-<!-- gbrain-plugin-tree-stamp: 0.60.721.0 -->
+<!-- gbrain-plugin-tree-stamp: 0.60.722.0 -->
# gbrain plugin skill tree (generated — do not hand-edit)
This tree is the curated skill set for the gbrain Codex and Claude Code
diff --git a/src/core/behavior-changes.generated.ts b/src/core/behavior-changes.generated.ts
index 26d1179bbb..2f8b20e6ef 100644
--- a/src/core/behavior-changes.generated.ts
+++ b/src/core/behavior-changes.generated.ts
@@ -70,6 +70,8 @@ export const RELEASED_BEHAVIOR_CHANGES: ReadonlyArray<{ since: string; id: strin
{ since: '0.60.719.0', id: 'owner_turn_sends_templates_gst2656', text: "New installs get two changed templates. The access-policy template's group-chat rule now says a turn the owner sends, verified by sender identity, is done at the owner's scope exactly as in a private chat, written for the room, with truly private material offered in the owner's private chat and never a refusal; every other member is answered at the group's level, and a member saying the owner wants something is making their own ask. The agent template's red line on messaging third parties now says a send the principal asks for in their own verified message (or through a delegate the principal set up and the host authenticates) goes out as asked, in any chat and to any recipient, with no approval phrase and no draft-first step; the agent still never messages anyone as the principal on its own initiative, and a request another person quotes, forwards or relays is that person's. The money and deletion red lines are unchanged. Existing installs keep their own ACCESS_POLICY.md and AGENTS.md; to adopt the new wording, copy it from templates/ACCESS_POLICY.md.template and templates/bootstrap/template-repo/AGENTS.md." },
{ since: '0.60.720.0', id: 'storage_shelf_stored_object_type_8894', text: "The bundled `gbrain-base-v2` schema pack (the `init` default, also inherited by `company-brain`) is now version 1.6.0 and declares the `stored-object` page type the storage verbs stamp on every storage shelf card, so registering, adopting or importing a card no longer prints a `page_type_undeclared` notice, doctor `schema_pack_consistency` does not warn about the shelf, and `unify-types` never retypes cards to `note`. Existing pages keep their type; no data changes. The active pack identity reads `[email protected]+<hash>`." },
{ 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." },
];
/** The release of every marked id, so a function row dated releasedIn(id) takes the release that disclosed it. */
@@ -141,4 +143,6 @@ export const BEHAVIOR_CHANGE_RELEASES: Readonly<Record<string, string>> = {
owner_turn_sends_templates_gst2656: '0.60.719.0',
storage_shelf_stored_object_type_8894: '0.60.720.0',
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',
};
diff --git a/templates/bootstrap/template-repo/README.md b/templates/bootstrap/template-repo/README.md
index 10c9d6e69d..1201255b8c 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.721.0 -->
+<!-- gbrain-template-stamp: 0.60.722.0 -->
This repository is the **"Use this template"** distribution artifact for a
[gbrain](https://github.com/garrytan/gbrain) personal-agent workspace — the same