Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
Merge remote-tracking branch 'origin/master' into capy/gbra220-meeting-slack-sources
garrytanf9ff9c15ffa3
diff --cc CHANGELOG.mdindex 8ab254813e,a196fa35b7..79826eabbe--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -10,25 -10,45 +10,64 @@@ credits are retained; no result has beeidentifiers and attribution are available in the pre-removal Git revision`6040075c6cb95be5881cc2e1b76ef7d71f4e5d29` (retained on 2026-09-23).+## [Unreleased]++**Meeting notes now flow into the brain on a schedule, with no custom script.**++A new `meetings` source kind imports meetings from Fireflies (the first provider behind a provider interface) into one page per meeting: title, date, attendees, the provider's summary, action items and keywords, and optionally the transcript. You save the API key once on stdin with `gbrain connectors auth fireflies --token -` (probed before it is saved, 0600, never in argv, config or the database), add the source with `gbrain sources add meetings --kind meetings --provider fireflies`, and run the first sync yourself. After that, autopilot keeps it fresh every `--sync-interval-min` minutes (default 60) and waits out the provider's rate limit. Nothing syncs until you register a source and run its first sync.++It works on a brain with no Git repository: pages and the sync position are recorded in the database. On a brain with a Git checkout, `--dir` inside it records each page with a commit before its database row, and a missing checkout holds the meeting instead of writing it to the database alone. The record mode is chosen when the source is added and never re-inferred.++| Situation | What happens |+|---|---|+| The key's owner did not attend the meeting | the page is private |+| A meeting the provider is still processing | re-checked every sync; published when its summary arrives (or after 48 hours) |+| A meeting edited upstream | the page updates and facts extracted from the old version are retired |+| A meeting deleted upstream (inside the lookback) | the page is deleted and its facts are retired |+| A key for a different account | refused (`connector_account_changed`) before anything is imported |+| Summary text that looks like a facts table, citation or timeline row | made inert before it lands in the page |++Guide: [docs/guides/meeting-and-slack-sources.md](docs/guides/meeting-and-slack-sources.md).++ ## [0.60.475.0] - 2026-10-27++ **A repository's own commit checks now apply to commits gbrain makes.**++ `gbrain git commit-push` and gbrain's own page writes told Git to read every file path literally. Git passes that setting on to the repository's hooks, so a pre-commit check that picks files by pattern (all `*.json` files, say) found no files and let the commit through. A JSON file with merge-conflict markers could be committed and pushed by gbrain while a plain `git commit` of the same file was refused. Hooks that build their own path patterns, such as a post-commit step that runs `git add -- ':(literal)<file>'`, failed for the same reason.++ gbrain now marks each of its own paths as literal one at a time and no longer turns the setting on for the whole command. Its hooks, filters and helpers start without it, even when gbrain's own environment sets it. Files whose names contain `*`, `?`, `[` or a leading `:` still commit only themselves.++ ### What changed++ | Situation | Before | Now |+ |---|---|---|+ | A pre-commit hook lists staged files with a pattern (`git diff --cached --name-only -- '*.json'`) and refuses a bad one | the hook saw no files; gbrain committed and pushed | the hook refuses; `gbrain git commit-push` exits 1 with `git_unavailable` and the hook's message, leaves the file unstaged and pushes nothing |+ | A post-commit hook runs `git add -- ':(literal)<file>'` | `did not match any files` | works as after a plain `git commit` |+ | A clean filter, push helper or hook started for a gbrain commit | inherited `GIT_LITERAL_PATHSPECS=1` | sees no pathspec setting |+ | `GIT_LITERAL_PATHSPECS`, `GIT_GLOB_PATHSPECS`, `GIT_NOGLOB_PATHSPECS` or `GIT_ICASE_PATHSPECS` set in the environment gbrain runs in | passed to every Git command gbrain ran | dropped from Git commands gbrain runs |+ | A new page file whose name starts with `:` | the ignore check read it as the name without the colon | checked under its real name |++ Release 0.60.474.0 also updated the `qs` dependency to 6.16.1 for security advisory GHSA-6pq8-jhm2-2vcw.++ ## [0.60.474.0] - 2026-10-27++ **A database role that can't read the writer state is now refused instead of let through.**++ The writer guards on pages, facts, takes, tags, timeline entries, aliases, sources and the segment tables check `persistence_brain` before deciding whether a write needs the coordinator. A non-owner Postgres role without BYPASSRLS, with write policies on those tables but none on the state tables, read no state row, so the guard treated the brain as unmanaged and allowed the write. The Git-canonical fence, the persistence protocol floor, protocol activation and the Git-canonical source count had the same gap. Each of them now refuses with `writer_coordinator_required` ("writer state is unreadable to this database role") when row-level security hides the state it reads. The owner and roles that bypass RLS behave as before. So do roles that can read the state, on managed and unmanaged brains alike, except at protocol activation and the Git-canonical source count, which refuse any role that row-level security filters (a hidden row there can't be told from an absent one). A role that can't see `persistence_brain` is now refused even on an unmanaged brain, since the guard can't tell which kind it is. One case now refuses every caller: a managed brain whose `persistence_brain` or `git_canonical_brain` row is missing, which `gbrain init` never leaves.++ ### What changed++ | Situation | Before | Now |+ |---|---|---|+ | A scoped role writes a page on a managed brain without seeing `persistence_brain` | the write passed as if the brain were unmanaged | refused: `writer_coordinator_required`, `relationship: unreadable_state` |+ | The same role writes to a Git-canonical source without seeing `git_canonical_brain` or the source row | the Git-protocol fence was skipped | refused the same way (a writer that declares the Git protocol still passes) |+ | A role deletes a tag or timeline row whose page RLS hides | treated as a cascade and allowed | refused |+ | A role updates a request or effect without seeing the protocol floor | no floor applied | refused |+ | Protocol activation by a role that RLS filters on the persistence tables | pending work could read as quiesced | refused |+ | A Git-canonical flag change by a role that RLS filters on `sources` | the strict-source count could drop to zero | refused |++ The migration replaces five function bodies. It changes no privileges and rewrites no data. Function owners and `search_path` settings stay the same.+## [0.60.473.0] - 2026-10-27**A change you stage while a write is finishing is no longer overwritten.**