Skip to content

feat(chat): Add full message reads, text edits and deletion - #1

Draft
jai wants to merge 88 commits into
mainfrom
jai/chat-rich-messages
Draft

jai wants to merge 88 commits into
mainfrom
jai/chat-rich-messages

Conversation

@jai

@jai jai commented Oct 16, 2026 •

Copy link
Copy Markdown
Owner

What Problem This Solves

Scripts reading compact Chat messages cannot inspect named hyperlink targets, cards or image metadata. People correcting or removing their own Chat messages also need native editing and deletion commands for their daily workflow.

User Impact

Opt-in --full on list and search and native message get expose SDK-modeled formatted text, CardsV2, image references and attachment metadata. Compact JSON and plain-text defaults stay compatible. Text updates use updateMask=text, and deleting threaded replies requires --delete-replies.

Full output follows the typed SDK contract. Images remain references and metadata. Read-only guards and untrusted-content wrapping apply.

Why This Change Was Made

The personal fork reuses the existing SDK and OAuth scopes for rich reads and text mutations. Append-only upstream merges keep it current while dogfooding. The latest merge changes only reviewer instructions in the PR template; application behavior, dependencies and inherited workflows are unchanged.

The PR stays open as a draft. Focused upstream proposals need Jai's scope decision.

Evidence

Validated source b22e04289aceaf030a4fd69fd6ef633e8cf45a02 includes upstream 31c4e14186e8cbbc0d9ba4514dda3c64880d1c9a and v0.48.1.

  • Independent Codex review, signed commits, hooks, local CI, pinned worker checks and all ten hosted checks passed. CI · CodeQL · Image
  • Previous and candidate Mac binaries passed 66 isolated CLI invocations and 20 loopback executions. Real Google Chat passed all 12 checks after caller-only private membership verification. Every owned message was cleaned and complete listing was empty. Wrapped existing card metadata and both full-search calls passed. Detailed evidence
  • Intended paths on four reachable hosts match validated hashes and provenance. Accessible paired reads passed, including 11 VOC entries. 6 VOC contexts have preview proof only, and one retains matched keyring errors. Raw/direct PATH and historical Mini Jai Work login coverage remain incomplete. Trusted Grokbot remains offline.

Weekly default-branch CodeQL scheduling awaits a separately authorized fork main update.

@jai jai added the agent-ignore Operator-owned changes; exclude automated maintenance label Oct 16, 2026
@jai jai changed the title feat(chat): Add rich message reads and text management feat(chat): Add full message reads, text edits and deletion Oct 16, 2026
@jai

jai commented Oct 16, 2026 •

Copy link
Copy Markdown
Owner Author

Cosmo, Jai's AI assistant.

Upstream preparation

Checked AGENTS.md, VISION.md, CI and the organization defaults. Neither repository has a PR template or CONTRIBUTING.md. This description uses the Summary and Verification structure of merged PR #1024, mention/reaction metadata.

The written merge bar is focused changes, review, regression tests, user-facing docs/changelog updates and live Google proof where behavior depends on Workspace APIs. Wider commands and API contracts need discussion first.

  • Preserve compact defaults and document the opt-in typed JSON contract.
  • Add actual-SDK HTTP regression fixtures, mutation guards and provider error coverage.
  • Update command docs, generated agent skills and changelog.
  • Run local CI and private native create/get/full list/update/delete/image/reply-deletion checks. All 12 live checks passed, with zero cleanup errors.
  • Verify existing CardsV2/image/button reads without publishing private payloads.
  • Initial implementation head 1aa6eb1e0d5c5bacdcfb0e4f662adb02f8811825 passed all six hosted checks. Claude and Grok approved the remediation. Current maintenance evidence is below.
  • Discuss the broader rich-read and mutation contracts with upstream before opening proposals.
  • Prepare focused upstream diffs that exclude the fork installer and maintenance files, and update contribution references to the eventual upstream PR numbers.

Additional dogfood evidence to collect, beyond the explicit written requirements:

  • Live full-search and provider --view full behavior: a run-owned message retained its named hyperlink and provider read state; indexing required one retry. The provider option and the output flag remain independent.
  • Repeated use under each intended agent identity, with no credential or permission changes. The Mini's existing Jai Work account and VOC's Incident Triage account passed live Chat reads after activation.
  • Complete the latest fleet update: 24aab48e remains installed at intended fork paths on four reachable named hosts. Mini Jai native processes now also select stock Homebrew; native Jai/Jai Work launcher coverage is incomplete. Trusted Grokbot and excluded canary scope remain open.

Intent

Expose rich Google Chat data through native commands and opt-in full JSON, plus text update and deletion. Keep compact defaults, scopes, read-only behavior and explicit reply deletion. Dogfood before submitting upstream.

Reviewers

  • Reviewer A: Claude Opus 5.5, nine initial findings.
  • Reviewer B: Grok 4.7 Build, two initial findings.

Act on

  • Both models: sender-controlled identifiers could bypass wrapping. The fix wraps card IDs, thread keys, client-assigned message IDs and resource paths with reserved client message IDs.
  • Grok: forwarded space references and quoted attachment names were wrapped despite valid resource syntax. The fix preserves them, with actual-SDK tests across get/list/search and projections.
  • Claude: the smoke accepted unrelated 400 failures as reply-deletion proof. It now checks stable exit codes and the exact structured provider refusal reproduced in the private fixture, then confirms both messages remain live.
  • Claude: shared docs contained fork-only wording. Feature docs now describe the commands directly; fork operation stays in the maintenance document. The changelog cites the actual personal PR until upstream PR numbers exist.

Consider

None of the remaining suggestions blocks this patch.

Noted

  • --markup changes formattedText, not plain summaries. The documentation now states that and removes the ineffective plain-output example.
  • Custom client resource names have direct classifier tests. Command-level actual-SDK tests cover the classifier paths and the other sender-defined fields. Another custom-name command fixture would add narrow coverage.

Dismissed

  • Replace the Chat classifier with a generic callback: the output package already owns Chat wrapping rules. A new extension mechanism adds indirection for one caller without removing the two distinct compact/full contracts.
  • Leave all enum-like values unwrapped: full mode deliberately wraps unknown strings conservatively. Broad uppercase/MIME patterns would create another trust rule without a demonstrated need.
  • Add a notes map to the generator or more account/confirmation helpers: these are style preferences rather than demonstrated defects. The small condition and explicit write guards remain direct.
  • Refactor every nil filter or rename upstream helpers: the patch reuses existing presentation helpers. Moving filtering into fetch could change paging behavior and increases the scope.

Agreement map

Both models independently identified the identifier trust gap. Grok alone found missing forwarded/quoted classifications; the actual SDK fixtures reproduced them. Claude alone found the loose live assertion and upstream preparation friction; both were confirmed. The remaining suggestions concern optional structure or extra coverage.

The corrected build is active on Borg Cube 04, Borg Cube 03, the Mac Mini Jai/Jai Work profiles, VOC and Grokbot through their existing command paths. Previous binaries are backed up. Gateways and stored account configuration were not changed. Borg Cube 03 was completed on October 16; Grokbot and the validated upstream update were completed on October 17.

Post-activation compatibility: the Mini Jai Work account and all six saved accounts across VOC Sysops, Incident Triage and shared FINN passed read-only Chat space reads. An initial Sysops account read returned authentication exit 4 once; the complete follow-up passed with no credential/configuration change. Its cause is unconfirmed. Binary hashes and rollback provenance are recorded privately on each host.

2026-10-17 maintenance evidence

  • Signed and pushed head 32303e618e926766c9739f7e98751fdd87fa0479 merges upstream through a6fc12ab76880c9b14e18823938abb770ac17b75: v0.45.0 release metadata, auth-email shorthand and worker dependency updates. The only conflict was the changelog; the fork feature remains under Unreleased. Chat implementation code is unchanged.
  • Independent Codex review (GPT-6 Astra, high reasoning) returned APPROVE on this exact head: no concrete correctness, security or integration regressions. It inspected the incoming diff, merge resolution and remaining fork diff. This was a source review; live/CI evidence is separate below.
  • Local make ci passed. The pinned pnpm 11.28.5 worker lint, typecheck, dry-run build and all 15 tests passed.
  • All six exact-head checks passed: CI, Docker.
  • All 12 live smoke checks passed with four synthetic messages and zero cleanup errors. A separate fifth run-owned message proved full-search/provider-full-view hyperlink and read-state behavior; it was deleted afterward. Final listing confirmed zero live messages in the private fixture.
  • Fresh read-only wrapped card proof returned one CardsV2 card, one image reference and three button links. No private payloads are published.
  • Source 32303e61 is active on every rollout host, including Grokbot. Runtime PATHs, checksums and rollback provenance were verified. Grokbot's existing global alias follows its local executable; both path variants resolve the fork. Gateways and Google account configuration were preserved.
  • Follow-up explicit-account old/new reads passed for all previously working accounts, including both Grokbot accounts and all six VOC accounts. A few initial authentication exit-4 results did not recur; the cause remains unconfirmed. Grokbot required its existing runtime keyring environment for the probe. Personal-account usage guards behave identically in both binaries.

The personal draft remains open. No upstream PR has been submitted; focused proposals still await the upstream scope discussion and Jai's decision after dogfooding.

2026-10-18 maintenance evidence

  • Signed and pushed merge head 61fe6e02f19b3453cde92e8928a0c9467c02974e incorporates upstream d48a86fb3fba9aa939fc6b4a0e9f75156add9f98: Gmail HTML forwarding notes and preserved plain-note line breaks. The merge applied cleanly; our Chat implementation and compact defaults are unchanged.
  • Independent Codex source review returned APPROVE on the exact head. A separate real-executable comparison returned PASS+NOTES: the new Gmail flags are accepted, conflict/recipient validation behaves as intended, and Chat update/delete previews and reply-deletion guards match the previous build. Gmail CLI verification was offline; MIME behavior is covered by the unit suite.
  • Local make ci, pinned-worker lint/typecheck/dry-run build/all 15 tests, and all six hosted checks passed: CI, Docker.
  • The private smoke passed all 12 checks with four owned messages and zero cleanup errors. Fresh wrapped reads returned one CardsV2 card, one image reference and three button links. Read-only full-search/provider-full-view calls succeeded with both binaries. No private payloads are published.
  • Activated 61fe6e02 on Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC. Binary hashes, source provenance and runtime resolution passed. Previous builds remain available for rollback. Gateways and Google account routing were preserved.
  • Paired old/new reads passed for all previously working stored Chat accounts on reachable hosts, including all six saved VOC accounts. Consumer-account usage guards are unchanged. A newly observed rehearsal runtime passed offline command checks; no live claim is made for its unavailable credential environment.
  • Grokbot's known address is offline. Its last verified source is 32303e61; the new validated Linux artifact is retained for deployment when it returns. Daily fleet convergence now retries a lagging fork even when upstream has no newer commit.

The personal PR stays draft. Technical Chat validation remains strong; focused upstream proposals still await the scope discussion and Jai's instruction.

2026-10-19 maintenance evidence

  • Signed and pushed head 7897017a7816540f544b094d63ee24be407f18e5 incorporates upstream 5579acdf0c21c401840560370036ade9e52c0827: Xcode 27 CI/release runners, explicit macOS 15 deployment-target checks and OIDC ClawSweeper intake. Chat implementation and defaults are unchanged. The changelog conflict preserves both entries.
  • Independent Codex source review returned APPROVE. Independent verification of the actual deployment artifact returned PASS+NOTES after 40 offline cases against each binary, covering text updates, empty text, confirmation, readonly, full-mode validation and separate reply deletion.
  • Local make ci, the pinned worker checks/all 15 tests and all six exact-head hosted checks passed: CI, Docker. Strict fork checks still match upstream. Publishing and ClawSweeper remain disabled through fork settings; inherited workflow YAML is unchanged.
  • The new minimum-OS check caught the local build default of macOS 26. The deployment artifact and native installer build now use upstream's explicit macOS 15 compiler/linker flags; Mach-O verification reports 15.0. The independent CLI comparison and live smoke were rerun on the corrected artifact. This verifies the minimum-OS metadata, not execution on a macOS 15 host.
  • All 12 live smoke checks passed on the deployment artifact, with four run-owned messages cleaned up and zero cleanup errors. Fresh wrapped card reads retained one CardsV2 card, one image reference and three button links. Old/new read-only full-search calls passed. Final complete private-fixture listing showed zero live messages and no next page.
  • Activated 7897017a on Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC. Checksums, source provenance and runtime command resolution passed; rollback builds remain available. Paired reads passed for every previously working saved Chat account on the reachable hosts, including all six VOC accounts. Item-level token checks found no errors; consumer guards are unchanged. The rehearsal profile still lacks credential environment for live proof.
  • Grokbot's trusted route remains offline; its last verified source is 32303e61. An online same-name Tailnet node has different SSH host keys, so its identity is unverified and it was left untouched. The validated Linux artifact is retained for trusted access.

The personal PR stays draft. Technical evidence supports preparing focused upstream proposals; scope discussion and Jai's instruction still precede submission.

2026-10-20 maintenance evidence

  • Signed and pushed c1a79c580bc623fcbf4fad9c1fb97ce7fa9e7dc1 merges upstream through d8917466326dc1080769711a86e717838fb7ed89: requested false Drive metadata fields, dependency updates and opt-in credential-free API relays. Chat source is unchanged; independent review confirmed the Chat SDK source is identical across the dependency versions. The changelog retains both upstream and fork entries.
  • Independent Codex source review returned APPROVE. Independent actual-binary verification returned PASS+NOTES: 40 Chat cases and ten malformed relay-origin cases per binary. The macOS arm64 artifact checksum and minimum OS 15.0 metadata were independently verified.
  • Local CI, worker frozen install/lint/typecheck/dry-run build/all 15 tests and all six hosted checks passed: CI, Docker. Worker validation matched upstream Node 26 using 26.12.0, Corepack 0.36.0 and pinned pnpm 11.28.5. Required checks and inherited CI YAML are unchanged.
  • Nine actual-binary loopback checks passed for rich get/full list, explicit empty text update, separate reply deletion, readonly rejection before any request, requested false Drive fields, original-host forwarding, no Authorization header and refused cross-origin redirects with zero target requests. This is synthetic relay proof; fleet relays remain unconfigured. Account-requiring relay commands still need an explicit label to avoid automatic account selection.
  • All 12 private live Google Chat checks passed using four owned messages, with zero cleanup errors. Fresh wrapped card reads retained one CardsV2 card, one image reference and three button links. Both old/new read-only full-search calls succeeded. Final complete listing confirmed zero live fixture messages and no next page.
  • Activated the tested artifact on Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC. Source provenance, binary checksums and intended runtime resolution passed; previous builds remain available. Paired reads passed for every previously working saved Chat account, including all six VOC accounts, with no item-level token errors. Consumer guards are unchanged. Rehearsal live proof remains unavailable without credential environment.
  • Grokbot's trusted address remains offline; its last verified build is 32303e61. Same-name nodes were not trusted as replacements. The validated Linux artifact is retained on VOC for deployment through trusted access. Gateway state, credentials, Google routing and relay configuration were preserved.

The personal PR remains draft. Technical proof supports preparing focused upstream proposals; the scope discussion and Jai's instruction still precede submission.

2026-10-21 maintenance evidence

  • Signed append-only merge and fix commits produce 83bcc6d8cf50c1c8089ee7e34a3d53a0c54bd285, incorporating upstream through e06131d2e9273130a2ed7e21f0cdc0a648888803. Upstream adds output-only file-keyring rekey/export and shared locking/backend changes. Generated command inventory retains both auth rekey and the native Chat additions. Chat source/defaults are unchanged.
  • Independent Codex review found two rekey defects. Concurrent exports could overwrite a newly published nonempty output without --force; filesystem permission loss could publish a weaker output. Both failures reproduced before repair. Publication now locks the stable output parent, rechecks replacement permission under the lock and reports the actual replaced entries. A final staged-mode check refuses publication on mismatch. Deterministic concurrency and permission tests pass, including a real macOS differing-group setgid-loss fixture. Live keyrings were never rekeyed.
  • The same independent source reviewer approved the final fix. A separate actual-artifact reviewer returned PASS+NOTES after 40 offline Chat cases per binary and 22 isolated auth checks. Synthetic source ciphertext and recorded metadata remained unchanged. Its separate setgid CLI fixture could not retain the required source bit, so that reviewer makes no setgid execution claim; the native regression test above supplies that proof. Candidate checksum and minimum macOS 15.0 metadata matched. No macOS 15 runtime claim is made.
  • Local CI, secrets race tests, current pinned-worker validation/all 15 tests and all six hosted checks passed at the exact final head: CI, Docker. Worker pins remain Node 26.12.0, Corepack 0.36.0 and pnpm 11.28.5. Required checks and inherited workflow YAML remain unchanged.
  • All 12 live Chat checks passed on the final deployment artifact using four owned messages, with zero cleanup errors. Fresh wrapped card reads retained one CardsV2 card, one image reference and three button links. Old/new read-only full-search calls succeeded. Complete fixture listing confirmed zero live messages and no next page. October 17 named-link/provider-read-state search proof remains separately dated. October 20 loopback relay proof was not rerun today; relay configuration remains unset.
  • Activated 83bcc6d8 on Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC only after all exact-head gates passed. Checksums, source provenance and intended OpenClaw command resolution passed; previous builds remain available. An expanded native-process audit found Mini Jai Work PATH variants that select stock Homebrew before the local fork. That runtime-path exception remains open; launcher/gateway configuration and Homebrew were left unchanged. The macOS artifact targets 15.0 and the native installer reuses that exact validated artifact. VOC retains the validated Linux artifact for later trusted Grokbot access.
  • Paired native read-only Chat calls passed for the currently accessible work accounts on the Macs and five saved VOC accounts, with zero item-level token errors. Consumer usage guards matched the previous build. VOC now has native agent processes with custom Gog home paths; probes used their coherent existing local environment. Initial incomplete-environment results are not evidence of a binary regression. Rehearsal still lacks credential environment for live proof. Stored identities, credentials, relays and gateway state were preserved.
  • Grokbot's trusted route remains offline, with last verified source 32303e61 from October 17. A currently online same-name node has different SSH host keys and remains unverified. It was not used as a replacement.

The personal PR stays draft. Technical Chat evidence supports focused proposals; upstream scope discussion and Jai's instruction still precede submission. Rekey integration repairs should be proposed separately if authorized.

2026-10-22 maintenance evidence

  • Signed append-only merge 6518e78137c9fc5660a188cb76d48edb51f1cf52 incorporates upstream v0.46.0 through ec34fedc23dd9d3e90f0401144cec42e06a50783. This brings Gmail Web-style forwarding headers and shared reply mailbox rendering, Go security toolchains, Google client and worker dependency updates. The changelog conflict keeps the fork Chat and rekey repairs under Unreleased and preserves upstream release notes. Chat source/defaults and the auth repairs are unchanged.
  • Independent Codex autoreview returned clean, with no actionable findings. It reviewed the incoming source, rendering/escaping, merge resolution, toolchain and worker changes. Cached generated Chat SDK source is identical between the Google client versions. This is source proof; actual-binary, CI and live Google checks are separate.
  • Independent actual-artifact verification passed its final sweep of 40 Chat cases, 21 Gmail dry-run cases and 22 isolated synthetic auth checks per binary. Candidate checksum, version, Go 1.27.3 and minimum-OS metadata matched. Earlier fixture-only expectations were corrected before the complete passing sweep; no product defect or source edit was involved. Gmail dry-runs are input proof, not MIME output or delivery proof.
  • Local CI and repository commit/push hooks passed. Worker frozen install, lint, typecheck, dry-run build and all 15 tests passed using task-local Corepack 0.36.0 and pnpm 11.28.5 under Node 26.12.0. Both artifacts record Go 1.27.3; the requested mise Go 1.27.1 wrapper selects that pinned toolchain automatically. No global tooling was activated.
  • All six exact-head hosted checks passed: CI, Docker. Current upstream CI tests minimum Go 1.26.10. The fork retains inherited CI YAML and the same strict check names.
  • All 12 live Google Chat checks passed using four owned messages, with zero cleanup errors. Fresh wrapped reads retained one CardsV2 card, one image reference and three button links. Both old/new read-only full-search calls succeeded. Complete private-fixture listing confirmed zero live messages and no next page. October 17 named-link/provider-read-state search proof and October 20 synthetic relay proof remain separately dated.
  • Activated the exact validated artifacts at the intended fork paths on Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC. Installed hashes, source provenance and current runtime resolution were audited; previous builds remain available. The native installer reused the prevalidated macOS 15 artifact. This is minimum-OS metadata verification, not execution on macOS 15. VOC retains the validated Linux artifact for later trusted Grokbot access.
  • Paired read-only Chat calls passed under all currently accessible stored work accounts on the Macs and five VOC accounts, with no item-level token errors. Consumer guards match. Rehearsal live proof remains unavailable without credential environment. An early Mini probe raced artifact staging and was killed; after copy completion, matching checksum/version verification and paired reads passed. The installed binary was not involved.
  • No currently sampled Mini native process chose stock Gog, but the previously failing Jai Work login PATH still resolves Homebrew 0.37.0. This remains an open launcher-path exception. Grokbot's trusted route is offline and its last verified source remains 32303e61; same-name nodes are not trusted replacements. Gateways, launcher configuration, credentials, account routing, Homebrew and relay configuration were preserved.

The personal PR stays draft. Technical Chat evidence supports preparing focused proposals; upstream scope discussion and Jai's instruction still precede submission.

2026-10-23 maintenance evidence

  • Signed append-only merge afece913e509f0d772f3ccea457d7298af88ea10 incorporates upstream through ea582609ec6ec4efb169d48fb7610d47e4acdca2. It pins inherited CI/Pages Node to 26.12.1 and upgrades Alpine CA packages in both Docker stages. The changelog retains upstream's security entry and the fork Chat/rekey entries under Unreleased. Native application sources, Go dependencies, compact defaults and auth repairs are unchanged.
  • Independent Codex autoreview returned clean with no actionable findings. Independent actual-binary verification passed 40 offline Chat cases per binary; unchanged Chat result/error streams matched, and candidate hash/version/Go 1.27.3/arm64/minimum macOS 15.0 metadata passed. No macOS 15 execution is claimed. Prior Gmail and synthetic auth CLI proof stays dated October 22.
  • Repository hooks and local CI passed using the requested Go wrapper with explicit Node 26.12.1. The wrapper selects Go 1.27.3 from go.mod. Worker frozen install, lint, typecheck, dry-run build and all 15 tests passed with task-local Corepack 0.36.0 and pnpm 11.28.5. No global tooling was activated.
  • All six exact-head hosted checks passed: CI, Docker. Fork CI/Pages YAML and Dockerfile match upstream. The image build verifies package/build integration; upstream's incident-chain rejection tests were not independently repeated here. Native host CA stores were not changed.
  • All 12 live Google Chat checks passed using four owned messages, with zero cleanup errors. Fresh wrapped reads retained one CardsV2 card, one image reference and three button links. Both old/new read-only full-search calls succeeded. Complete private-fixture listing confirmed zero live messages and no next page. October 17 provider-view search proof, October 20 relay proof and October 21 deterministic rekey/race proof remain separately dated.
  • Artifact transfers completed to unused staging paths. Checksum and native version checks preceded atomic publication for remote tests. After all exact-head gates passed, the exact validated artifacts reached Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC at intended fork paths. Installed hashes, provenance and runtime resolution passed; previous builds remain available. VOC retains the validated Linux artifact.
  • Paired read-only Chat calls passed for the accessible stored work accounts on the Macs and five current VOC accounts, with no item-level token errors. Consumer guards matched. VOC probes used coherent native-process environment and custom Gog home paths. Rehearsal live proof remains unavailable without credential environment. Credentials, account routing, launcher/gateway configuration, host CA stores, Homebrew and unset relay configuration were preserved.
  • Trusted Grokbot is offline. A newly online same-name node presented three different SSH host keys, with none matching trusted keys; it was left untouched. Grokbot's last verified source remains 32303e61. The historical Mini Jai Work login PATH still selects stock Homebrew 0.37.0, so that launcher exception remains open even when no sampled native process uses it.

The personal PR stays draft. Technical Chat evidence supports focused upstream proposals; scope discussion and Jai's instruction still precede submission.

2026-10-24 maintenance evidence

  • Signed append-only merge 113c53087240ceccb800649cb079a532bba90d6f incorporates upstream v0.47.0 through 563e30a205d911f7f2bd15f4504ee950e6e98cf2. Incoming changes cover OAuth diagnostic redaction, bounded 403 rate-limit retries, explicit opt-in Ads grants, selected Gmail headers and HTML alternatives, calendar settings updates, Drive false-boolean output and dependencies. Fork Chat/rekey source and compact defaults are unchanged. Changelog entries stay under Unreleased; command-index conflict resolution retains all generated pages.
  • Independent Codex autoreview returned clean with no actionable findings. Independent actual-binary verification passed 58 logical cases across 101 invocations, including the 40 prior Chat cases and new command cases. An initial verifier sweep needed fixture expectation corrections, with no product source changes. Calendar help's empty-string example renders as a typographic quote; explicit clearing passed. Gmail dry-runs prove inputs, not MIME output or delivery.
  • Hooks, local CI and pinned-worker frozen install/lint/typecheck/dry-run build/all 15 tests passed. The initial hook run inherited an account default and failed two no-account fixtures; removing GOG_ACCOUNT as prescribed made the full hooks pass. Go selected 1.27.3; Node 26.12.1, task-local Corepack 0.36.0 and pnpm 11.28.5 matched current pins. No global tooling was activated.
  • All six exact-head hosted checks passed: CI, Docker. Workflow YAML and required checks match upstream. GitHub verifies the merge signature.
  • All 12 live Chat checks passed with four owned synthetic messages and zero cleanup errors. Complete scoped listing confirmed zero live messages and no next page. Fresh wrapped CardsV2/image/button reads and both previous/candidate full-search calls passed. October 17 named-link/provider-view search and October 21 rekey/race proof remain separately dated.
  • Twelve synthetic loopback checks passed. The updated Chat SDK adds card-owner metadata and app-only ReplaceCards. The metadata survived typed full output, stayed wrapped and did not appear in compact output. Text-only updates, separate reply deletion, readonly blocking, Drive false metadata, absent Authorization, original-host forwarding and cross-origin refusal passed. Images remained references; no card actions were executed. Relays remain unset on fleet runtimes.
  • After all gates passed, the exact validated macOS arm64 and Linux amd64 artifacts were activated at intended fork paths on Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC. Both record Go 1.27.3; macOS minimum metadata is 15.0, without a macOS 15 execution claim. Installed hashes/provenance/runtime resolution passed and rollback builds remain available. Transfers completed and passed checksum/native-version checks before use.
  • Paired read-only Chat calls passed for saved Mac work accounts and five current VOC accounts without item-level token errors; consumer guards matched. VOC used coherent local native-process environments and custom Gog home paths. Rehearsal live proof lacks credential environment. Credentials, Google routing, live keyrings, launchers/gateways, Homebrew and host CA stores were preserved.
  • Trusted Grokbot remains offline at its last verified 32303e61; the current same-name nodes are also offline and remain unverified replacements. The historical Mini Jai Work login PATH still selects Homebrew 0.37.0. Intended fork paths and OpenClaw resolution are correct, but launcher repair requires separate scope.

The personal PR stays draft. Technical evidence supports focused Chat proposals; Jai's scope decision still precedes upstream submission.

2026-10-26 fleet audit

  • Upstream remains at 563e30a205d911f7f2bd15f4504ee950e6e98cf2; no integration was needed. The dogfood branch remains clean and pushed at 113c53087240ceccb800649cb079a532bba90d6f, with all six existing exact-head checks passing. Unchanged build, functional and live-write tests were not repeated.
  • Installed source provenance, checksums and command resolution passed for the named Borg Cube 04, Borg Cube 03, Mini Jai/Jai Work and VOC targets. Borg Cube 03's bare process PATH lacks Gog, but its actual login shell resolves the validated fork. The historical Mini Jai Work login PATH still selects Homebrew 0.37.0.
  • The live Mini inventory now includes an additional canary runtime. Its Gog wrapper loads local credential environment and executes Homebrew 0.37.0. It is outside the named Mini targets. The wrapper, credentials and launcher state were preserved; including this runtime requires a scope decision. No canary account access or Google writes were attempted.
  • Trusted Grokbot remains offline. An online provisional node presented three host keys with zero matches against the trusted keys; no authenticated access, trust change or installation was attempted there.

The personal PR remains draft. Existing Chat proof still supports focused upstream proposals, subject to Jai's scope decision. No upstream PR has been opened.

2026-10-27 maintenance evidence

  • Signed append-only merge 42473535b399edb50b53b90edf60ddc5fcacb09a incorporates upstream through 1d0d4d230349c2be75f94ab6d6b14027e81ab5ca. It preserves read-only Calendar grants during reauthorization, handles explicitly disabled D-Bus, retains Gmail HTML text direction and updates indirect Go and worker dependencies. The changelog keeps fork Unreleased entries and upstream notes. Fork Chat/rekey source and the direct Chat SDK are unchanged.
  • Independent Codex source review returned no actionable findings. A separate actual-artifact comparison passed 33 logical cases across 66 isolated executions. Local CI, installed hooks, worker frozen install/lint/typecheck/dry-run build/all 15 tests and all six exact-head hosted checks passed. GitHub verifies the merge signature. CI and image.
  • All 12 private Google Chat checks passed. Four run-owned messages were cleaned with zero errors; final complete listing had zero live messages and no next page. Fresh wrapped metadata retained one CardsV2 card, one image reference and three button links. Previous/candidate read-only full search both succeeded; result counts varied, so this is not parity proof. October 17 named-link/provider-view proof, October 21 rekey/race proof and October 24 synthetic relay/card-owner proof remain separately dated. Gmail dry-runs prove inputs, not MIME composition or delivery.
  • The actual Wrangler-to-Miniflare-to-workerd resolver selects workerd 1.20261021.1. Its native macOS arm64 binary SHA-256 is 44a06c31a6578f234cdf7f23219b88978c8d8d21cb8ce85795cab53614b50d64, matching the upstream TLS proof. This run did not independently repeat the 14 incident-chain handshakes. Normal worker validation passed. Native host CA stores and managed Cloudflare runtimes were unchanged.
  • Both native Linux binaries succeeded with zero accounts and token errors in an isolated home with explicitly disabled D-Bus. This command fixture does not independently reproduce the prior backend-selection defect; upstream regression tests cover backend selection and token round trips. No live keyring was rekeyed, and no existing grant was changed.
  • Both deployment artifacts record Go 1.27.3. The macOS arm64 artifact declares minimum OS 15.0; no macOS 15 execution is claimed. Its SHA-256 is 7040dc1e5b8a60d32e131c7126ce149e8a0d3db6bc5084dd91260a016d068850. Linux amd64 is 48ea69c4756d92036e6defe8825284f220d09e8de67a453dfbe9b2bfca0a95cc. Completed transfers passed checksum/native-version verification before publication for probes. The native installer reused the exact validated macOS artifact.
  • Installed hashes, provenance, intended command resolution and native/OpenClaw runtime PATH variants were audited on the four reachable named hosts. All intended fork paths now use this head. Previous artifacts remain available, including the validated Linux build on VOC. Complete paired reads passed for saved Mac work accounts and five current VOC accounts, with zero item-level token errors. Consumer guards match. Several first-pass candidate auth-exit-4 results did not recur on complete paired follow-ups. Their cause is unconfirmed, and the observations remain in private evidence. Rehearsal live proof lacks credential environment.
  • The known Mini Jai Work launcher exception remains open. Current native PATH variants and the historical login probe select stock Homebrew 0.37.0, while the intended fork path and OpenClaw resolve the validated artifact. Binary maintenance did not change launchers or Homebrew. The additional Mini canary remains outside scope and its credential-loading wrapper was preserved without reading its credentials.
  • Trusted Grokbot access still times out. Current same-name nodes are offline; their names and alias routing do not establish identity. The last verified Grokbot source remains 32303e618e926766c9739f7e98751fdd87fa0479 from October 17. No replacement node was used and no SSH trust was changed.

The personal PR stays draft. Technical evidence supports preparing focused Chat proposals; upstream scope discussion and Jai's instruction remain required before submission. Relay configuration, credentials, account routing and gateways were preserved.

2026-10-28 maintenance evidence

  • Signed append-only integration 24aab48e2899dbc78f9dbf63b2eb57844704adb8 incorporates upstream v0.47.1 and development fixes through 82e7fd6005d4ed29f8edfa2a44475e08fe3051a0. Incoming changes add ID-only Gmail search, a larger rate-limit retry ceiling, explicit Calendar clears, bounded MCP continuation and dependency updates. Fork Chat and rekey source is preserved. The changelog retains fork entries under Unreleased and all upstream release notes.
  • Independent Codex review found two incoming Calendar defects. The unfixed binary sent attendees: [] for non-empty malformed --attendees=;optional; a regression test reproduced the same destructive patch. The appended repair rejects that input before any PATCH while retaining explicit empty clears. A second review found that summary clears were lost when creating or regenerating Zoom meetings. The shared merger now honors the summary-clear marker. Combined Calendar command tests captured the stale Zoom topic before the fix and correct clear/omission behavior afterward. They use the existing provider boundary fixture; no live Zoom call was made.
  • Final independent Codex review returned no actionable findings after both repairs. Repository hooks and local CI passed on the final head. Pinned worker frozen install, lint, typecheck, dry-run build and all 15 tests passed. GitHub verifies the merge and both repair signatures. All six exact-head hosted checks passed: CI and image. Inherited CI YAML and strict required-check names are unchanged.
  • Actual-binary comparison passed 33 logical cases across 66 isolated executions. Eighteen additional synthetic loopback checks exercised both binaries, including Gmail ID-only pagination with no detail/label requests, explicit Calendar clears, malformed attendee rejection, actual stdio MCP continuation using an opaque token beginning with dashes, and bounded results. An initial expectation was corrected because the old MCP correctly rejects the unsupported page field. The corrected full sweep passed without a product change for that fixture issue.
  • MCP's existing configurable overall deadline remains authoritative over retry waits. Both binaries returned exit 124 after a one-second operator deadline during a two-second Retry-After, with no second request. The default remains 60 seconds; a longer quota-recovery window requires explicit --timeout-seconds. Documentation now states this interaction. Final review accepted the preserved contract, so no timeout increase was made.
  • All 12 final-head private Google Chat checks passed. Four run-owned messages were cleaned with zero errors; final complete listing had zero live messages and no next page. Fresh wrapped metadata retained one CardsV2 card, one image reference and three button links. Both previous/candidate read-only full-search calls succeeded. This does not re-prove result parity or the October 17 named-link/provider-view/read-state coverage. October 21 rekey/race and October 24 synthetic relay/card-owner proofs remain separately dated.
  • Google API client v0.309.0 has byte-identical generated Chat source to v0.308.0. Wrangler 4.153.0 and Miniflare 5.20261023.0-beta still resolve patched workerd 1.20261021.1 with the same native hash verified on October 27. Incident-chain TLS handshakes were not repeated. Native CA stores and managed Cloudflare runtimes were unchanged.
  • Both artifacts record Go 1.27.3. The macOS arm64 artifact declares minimum OS 15.0; no macOS 15 execution is claimed. Mac SHA-256 is da9b985bdb81087bf97fe7af19d67b4e8f96cfa29579d77679c12a06cba00139; Linux amd64 is ec3438de88f0a4a315344da7243935599bb1818c922d163e2d8338ff6df9f471. Transfers completed to unused paths, then passed checksum and native-version checks before candidate tests. The native installer reused the exact prevalidated macOS artifact.
  • The four reachable named hosts now use this source at intended fork paths, with installed hashes, provenance, command resolution and actual native/OpenClaw PATH audits verified. Complete paired reads passed for accessible Mac work accounts and all five available saved VOC account entries with zero item-level token errors. VOC inspection found two Sysops storage environments. Each is now probed separately with its coherent local environment; the bare profile lacks credential environment, while the custom-home profile passed. VOC Jai Work, Jai Personal and rehearsal also lack credential environment for live proof; native previews passed. These unavailable probes are not successes or confirmed regressions.
  • The historical Mini Jai Work login PATH and sampled native PATH variants still select Homebrew 0.37.0. The intended fork path and OpenClaw resolve the validated build. The excluded Mini canary's credential-loading wrapper is preserved, with the same checksum before and after deployment; its credentials were not read and it was not executed. Launcher, gateway and Homebrew configuration remain outside binary maintenance scope.
  • Trusted Grokbot access still times out. An online provisional node presented three keys with zero matches to the three trusted keys. No authenticated access, host-key trust change or credential copy was attempted. Grokbot's last verified source remains the October 17 build. Previous validated rollback artifacts remain available on reachable hosts, including the Linux artifact on VOC.

The personal PR stays draft. Technical evidence supports preparing focused Chat proposals; upstream scope discussion and Jai's instruction still precede submission. Existing grants, live keyrings, credentials, account routing and relay configuration were preserved. This was binary maintenance and synthetic local protocol testing, with no Executor migration.

2026-10-31 fleet audit

  • Upstream remains at 82e7fd6005d4ed29f8edfa2a44475e08fe3051a0, release v0.47.1. The dogfood head and intended fork installations remain 24aab48e2899dbc78f9dbf63b2eb57844704adb8. Installed versions, checksums and source provenance match on all four reachable named hosts. All six existing hosted checks remain green. No unchanged build, CI or live Chat tests were repeated.
  • The runtime PATH audit failed for a newly observed Mini Jai context. Five sampled native Codex/Claude processes select stock Homebrew Gog 0.37.0, and actual zsh login-shell probes under those PATHs select the same stock executable. Other sampled native processes, including Jai Work's OpenClaw Codex children, select the validated fork. The installed fork was not overwritten. The separate historical Jai Work login PATH still selects stock Gog.
  • Native launcher coverage is incomplete for both Mini Jai and Jai Work. Repair needs separate runtime scope; no launchers, gateways, Homebrew, credentials or account routing changed. The excluded canary wrapper has its prior checksum and was not executed. Trusted Grokbot remains offline through verified access. This is a runtime-resolution finding, not a source regression or new live-account compatibility proof.

2026-11-02 audit method correction

  • Upstream, the draft PR head and intended installations remain unchanged at the October 28 validated build. All four reachable named hosts retain matching versions, source provenance and checksums. The six existing hosted checks remain green. No unchanged build, CI or live Google Chat tests were repeated.
  • Repaired the macOS runtime auditor. Its ps text parser truncated PATH values at spaces and could mistake argument text for environment values. It now reads the native kernel process data with NUL boundaries. Real synthetic processes verified PATH spaces, rejection of a fake PATH assignment in arguments, and an absent PATH remaining unavailable. These checks passed on all three Mac hosts, including the older system Python. The affected live Mini process resolves the validated fork when read correctly. Earlier text-parser results are retained as rejected audit evidence.
  • Rechecked current Mac runtime paths and actual login shells with the corrected reader. The known historical Mini Jai Work login still selects stock Homebrew 0.37.0. Absence of the October 31 transient Mini Jai process does not establish launcher repair. Native Mini rollout remains incomplete; no success whitelist, launcher, gateway, Homebrew or credentials changed. The excluded canary wrapper is unchanged, and trusted Grokbot remains offline.

2026-11-04 security automation integration

  • Signed merge dcd57e10d7b94fe43ce7e5277e1ea383d6852d64 incorporates upstream through 80f45bbb9f89bd2945620253d7fb243f036435fa. Four files changed: CodeQL policy/workflow, the release signer trust file and changelog. Application source, dependencies, Chat defaults and the fork's Calendar/auth repairs are byte-identical to the previous validated head. The allowlist addition does not enable signed-tag enforcement.
  • Independent Codex review returned no actionable findings. The reviewed index tree matches the final commit tree. GitHub verifies the merge and both incoming signatures. Repository hooks, clean-environment make ci, actionlint, pinned worker validation/all 15 tests and 66 isolated CLI executions across 33 logical cases passed.
  • All ten checks passed on the branch head: CI, Docker, CodeQL, including the CodeQL result check. All three language analyses were processed without errors or warnings on the synthetic PR merge tree, which is identical to the source head. The fork's six strict checks remain unchanged. PR scans work; weekly default-branch scans await a separately authorized main mirror update because fork main remains pinned.
  • All 12 private live Chat checks passed. Caller-only membership and privacy were rechecked before writes. Four run-owned messages were removed without cleanup errors; the complete final listing had zero live messages and no next page. Read-only wrapped CardsV2/image/button metadata passed. Previous/candidate full searches succeeded; success is not result parity. Earlier named-link/provider-view, rekey/race and synthetic relay/card-owner proofs retain their original dates.
  • Both artifacts record Go 1.27.3. The macOS arm64 artifact declares minimum OS 15.0; no macOS 15 execution is claimed. Complete transfers passed checksum and native-version checks before candidate probes. The native installer reused the exact validated artifact. Intended fork paths on all four reachable named hosts now use this head, with matching installed hashes and provenance; previous builds remain available.
  • Paired reads passed before and after activation for accessible Mac accounts and five VOC saved-account entries, with zero item-level token errors. VOC's current accessible entries are the custom-home Sysops profile and four shared entries. Bare Sysops, Jai Work, Jai Personal, Incident Triage and rehearsal lack credential environment in the sampled contexts and have preview proof only. No account routing, grants or credentials changed.
  • Runtime coverage remains incomplete. Two Borg Cube 03 Claude processes have a raw PATH selecting Homebrew 0.13.0, and a Mini Jai raw PATH selects Homebrew 0.37.0. Actual zsh login probes resolve the validated fork before and after activation. The fleet helper retains its raw-PATH failures; no success whitelist was expanded. Historical Mini Jai Work login still selects stock 0.37.0. Launcher scope remains separate. The canary wrapper is unchanged and excluded. Trusted Grokbot remains offline; unverified same-name nodes were untouched.

Technical Chat evidence continues to support focused upstream proposals. This personal PR remains draft; no upstream submission is authorized. Launchers, gateways, Homebrew, native CA stores, Google grants and relay routing were preserved.

2026-11-05 release tag enforcement integration

  • Signed merge 237b2474303331446baa8bd72af3b6efffbcb9b8 incorporates upstream dc6bf1f3bba83da3e90b2c67a28fd8422021d5b1, the merged release-tag enforcement change. Only the release caller, release guide and changelog changed. Application source, dependencies and prior Chat/Calendar/auth repairs are unchanged. Fork publishing remains disabled, with no release dispatch, real tag creation or signing-policy change.
  • The caller enables the existing shared signature/target verifier. Parent and independent Codex review checked the actual v1 reusable workflow snapshot at 9785c9227d50832e8cf457ef158c5ab98a9054bf, blob 9d986ec6eb80fe2d35396ce34913783fb99dc322, including tagless dry-run conditions. This is source-contract proof; upstream's signature-fixture matrix was not independently repeated. Upstream separately notes SSH-format and original tag-object hardening; this integration does not claim those repairs.
  • Independent Codex review found no actionable defects and matched the final signed merge tree. GitHub verifies the merge and incoming signature. Hooks, clean-environment make ci, release-workflow actionlint, pinned worker frozen install/lint/typecheck/dry-run build/all 15 tests, and 66 isolated CLI invocations across 33 logical cases passed.
  • All ten checks passed on this head: CI, Docker, CodeQL. All three CodeQL language analyses were processed without errors/warnings on a PR merge tree identical to the source head. The six strict fork checks are unchanged. Fork main stays pinned, so weekly default-branch CodeQL scheduling remains outside this rollout.
  • All 12 private Google Chat checks passed after privacy and caller-only membership were rechecked. Four run-owned messages were removed with no cleanup errors. Complete final listing had zero live messages and no next page. Fresh wrapped card/image/button metadata and both previous/candidate read-only full searches passed. Search success is not parity; earlier provider, relay and rekey proofs retain their original dates.
  • Both artifacts record Go 1.27.3. The macOS arm64 artifact declares minimum OS 15.0 without a macOS 15 execution claim. Transfers completed and passed checksum/native-version checks before testing. The native installer reused the validated artifact. Intended fork paths on all four reachable named hosts now use this head, with matching installed hashes and provenance; rollback builds remain available.
  • Accessible Mac account pairs and five VOC saved entries passed before and after activation with zero item-level token errors. VOC live contexts remain custom-home Sysops and four shared entries. Bare Sysops, Jai Work, Jai Personal, Incident Triage and rehearsal have no credential environment in the sampled contexts and have preview proof only. Existing routing, grants, credentials and relay settings were preserved.
  • Raw/direct PATH coverage remains incomplete on Borg Cube 03 and Mini; corresponding current zsh login probes select the validated fork. Raw mismatch evidence is retained, and no fleet-helper whitelist was broadened. Historical Mini Jai Work login still selects stock Homebrew. No launchers, gateways or Homebrew were changed. Canary remains unchanged and excluded. Trusted Grokbot remains offline; unverified replacements were untouched.

The personal PR stays draft. Technical Chat evidence supports focused proposals after scope discussion; no upstream PR is authorized or opened.

2026-11-06 upstream v0.48.0 integration

  • Signed fork head 7dfb30ff0860aa79435e83cd7798d767aab7fbc7 merges upstream through e8428c36dd31db13eecba55fcef6f4ee75951188. Incoming fixes cover Calendar selection, pagination and time windows, Gmail MIME and watch configuration, reauthorization, service-account storage, local-first backups and Docs error classification. The changelog keeps all four fork entries under Unreleased.
  • Independent Codex review matched the signed source tree. GitHub verified the merge and all 14 incoming commits. Hooks, local CI, worker frozen install, lint, typecheck, dry-run build and 15 tests passed. Wrangler 4.157.0 resolves Miniflare 5.20261103.0-beta and workerd 1.20261104.1. Native worker SHA-256 is 998fc0b38722c50ba869e9fafe67c1e3932545f8c5c8fd8ea69cab7afefe774f.
  • All ten exact-head checks passed. CodeQL processed three languages without errors or warnings on PR merge c56b544832bd49e0d1e5046f85353d5541199e94, whose tree equals the reviewed source. Fork main stays pinned and release publishing remains disabled. CI · Image · CodeQL
  • Actual previous/candidate artifacts passed 66 isolated CLI invocations plus 14 paired loopback invocations. Synthetic checks confirm the new typed Chat citation metadata survives get, full list and full search, with text wrapped under --wrap-untrusted, valid URL references preserved and citation fields omitted from compact list. The fixture also confirms Docs 404 exit 5, rejection of equal Calendar bounds before event listing and redacted Gmail watch env-token dry-runs. Calendar fixture expectations were refined to distinguish timezone metadata lookup from event listing. No source change was needed.
  • All 12 live Chat checks passed after caller-only private membership verification. All four owned fixtures were cleaned and the complete final listing was empty. Read-only wrapped card, image and button metadata and both full-search calls passed. Citation proof is synthetic. The live full-search calls establish compatibility, with the October 17 named-link and read-state proof separately dated.
  • Mac arm64 SHA-256 e6dce719053c6f44390c9c5dc873312336f292fe21334371ed07821a8053b785; Linux amd64 SHA-256 18cf342eecc3b5c97b045f1b1ec1649844e080d77e5262d4bda1aa44e6e3deba. Both record Go 1.27.3 and the clean source revision. The native artifact declares macOS minimum 15.0. Transfers completed and passed checksum and native-version checks before testing.
  • Intended paths on Borg Cube 04, Borg Cube 03, Mini Jai and Jai Work, and VOC match the validated hashes and provenance. Paired reads passed before and after activation for accessible Mac accounts and five VOC entries, with zero item-level token errors and matching consumer guards. Five VOC contexts have preview proof only because credential environment was unavailable. Some Borg Cube 03 and Mini Jai raw paths select stock Gog. Corresponding login probes select the fork, while the historical Mini Jai Work login still selects stock. Trusted Grokbot is offline. The additional Mini canary remains excluded.
  • The fork's Chat behavior remains supported by live and synthetic evidence for focused upstream proposals. Scope discussion and Jai's instruction precede any submission.

2026-11-09 upstream attachment proposal

The open upstream proposal adds attachment summaries to compact JSON message lists and a separate download command that writes local files. Its metadata overlaps fields already available through the fork’s typed full reads. If it lands, check the resulting compact schema during the next integration. The existing dogfood evidence still supports focused proposals for typed full reads, formatted hyperlinks, CardsV2 and narrow text mutations. Open upstream attachment PR

2026-11-12 placeholder account documentation

  • Signed fork head 7f1ef9cbf8f8229c4b9b2f6d05a85f8837ba1f52 incorporates upstream 6f910fffac0a359c30430b71a1037f2ccf07453a and replaces the Gmail auto-reply recipient example with a synthetic address after independent review. Five documentation files changed. The changelog retains all four fork entries under Unreleased. Upstream documentation PR
  • Final independent Codex review matched the signed tree. GitHub verified both fork commits and the upstream commit. Local CI, hooks, pinned worker frozen install, lint, typecheck, dry-run build and all 15 worker tests passed.
  • All ten hosted checks passed at the signed head. Three CodeQL analyses processed without errors or warnings on PR merge a2b5ab32855b7ffe5f8ac529fc26a19fc01733eb, whose tree matches the signed source. CI · Image · CodeQL
  • Previous and candidate artifacts passed 66 isolated CLI invocations and 14 credential-free loopback invocations. All 12 live Chat checks passed after private caller-only membership verification. All four owned messages were cleaned and a complete listing confirmed an empty fixture. Wrapped card, image and button metadata and both read-only full-search calls passed.
  • Intended paths on Borg Cube 04, Borg Cube 03, Mini Jai and Jai Work, and VOC match the validated source, hashes and provenance. Mac arm64 SHA-256 is 5ed47ab4b4d0ad0aab8a79b9d4d974d14fea4c1bce80e48acf5cf7c4ffb81533. Linux amd64 SHA-256 is 330a0d0538c48568f5c879b6d76161734b4c3d4f15ab5b90f006081214b163e8. Both record Go 1.27.3. The Mac artifact declares minimum OS 15.0.
  • Paired reads passed before and after activation for accessible Mac accounts and 11 VOC entries. Item-level token errors were zero for accessible contexts. 5 VOC contexts have preview proof only because credential environment was unavailable. A sampled Borg Cube 03 raw PATH selected stock Gog 0.13.0. Its zsh login probe resolved the fork. The historical Mini Jai Work login still selected stock Gog 0.37.0. Native launcher coverage remains incomplete. Trusted Grokbot was unreachable. The extra Mini canary stays excluded.
  • Existing live and synthetic evidence supports focused rich-read and text mutation proposals. The upstream attachment proposal is still open and needs a compact-output comparison if it lands. Jai defines scope before submission. Upstream attachment proposal

2026-11-15 Workspace contract fixes and dependency refresh

  • Signed source ecf6bf0173e0f690c180f95e8d0d682a932fc06f through upstream 6d97417eade925947d721b4bb898815624310e44. Upstream fixes preserve Calendar event pagination and future-series updates, Gmail alias and watch-history handling, Drive shortcut downloads, Sheets numbers and output, and explicit Tasks clears. The merge kept a single malformed-attendee guard, preserving the existing diagnostic, plus the fork’s Zoom summary-clear and Chat behavior. Workspace fixes
  • Independent Codex review, hooks, local CI, pinned worker checks and all 15 worker tests passed. GitHub verified the merge and both upstream commits. All ten exact-head hosted checks passed. CodeQL processed three languages against the signed tree. CI · Image · CodeQL
  • Previous and candidate builds passed 66 isolated CLI invocations and 20 loopback invocations. Loopback covered typed Chat citations, compact omission, Calendar pagination and Tasks request clears. All 12 live Chat checks passed after private caller-only verification. Cleanup removed all four owned messages and the complete listing was empty. Wrapped existing card metadata and both read-only full-search calls passed.
  • Go 1.27.4 built both artifacts. The macOS arm64 artifact declares minimum OS 15.0. SHA-256 macOS 82ce202af5f1ebdbefb858b3c5432c4e80dfbb123a5927f959b512b6ff107214, Linux amd64 d3391fb1aae1eff102c8772bfeee2e18d14992468e4b06f881a4a9f1e57206b5. Installed paths, versions, provenance and checksums match on Borg Cube 04 and Borg Cube 03. The accessible account pairs passed before and after activation with zero item-level token errors and matching consumer guards. Native launcher coverage remains incomplete. The Mac Mini was offline and VOC was online in Tailnet but inaccessible through the authorized Mini route. Their current binaries could not be reverified. Trusted Grokbot remained offline.
  • Existing evidence supports focused rich-read and text mutation proposals. The upstream attachment proposal remains open. Compare compact output if it lands. Jai defines scope before submission. Upstream attachment proposal

2026-11-16 Mac Mini and VOC rollout

  • The trusted Mini route returned. Mini Jai, Mini Jai Work and VOC moved from the November 12 build to validated source ecf6bf0173e0f690c180f95e8d0d682a932fc06f. Native versions, installed SHA-256 checksums, provenance and rollback copies were verified. The two Borg hosts also matched. Upstream was unchanged, and all ten hosted checks still passed at this exact head.
  • Paired Chat reads passed before and after activation for the accessible Mini accounts and 11 VOC entries. 6 VOC profiles had preview proof only because credential environment was unavailable. One VOC runtime had identical keyring permission errors with both builds, so its live account proof remains unavailable. The strict account audit records that failure.
  • A sampled Mini Jai Work raw PATH had no Gog. Its tool login and the historical Jai Work login selected Homebrew Gog 0.37.0. The canary was excluded and its wrapper hash matched. Trusted Grokbot remained offline. Launcher coverage remains open.

2026-11-17 v0.48.1 release sync

Verified fork head 09d04726dc966911d011c365853d662d5a1cc81f through upstream 9efe5ff47b7d58a8efa545d4169809387a2686b9. Only version and changelog changed. Four fork notes moved under v0.48.2 Unreleased. GitHub verified the release tag and signed commits. Release

Independent review, local CI, hooks, 15 pinned worker tests, 66 isolated CLI invocations, 20 loopback executions, 12 live Chat checks and all ten exact-head checks passed. All four owned Chat fixtures were removed. The complete listing was empty. CI

Both Borg hosts, Mini Jai and Jai Work, and VOC match the validated source and artifact hashes. Accessible accounts passed paired reads, including 11 VOC entries. 6 VOC profiles have preview proof only. One retained the same keyring permission failure on both builds. Mini Jai Work's historical login still selects stock Gog. Trusted Grokbot remains offline.

2026-11-19 contributor guidance sync

Validated signed source 96ac23a4427991d7e73a63ec0ac34ff5776c2f52. Contributor guidance was integrated, disabled validation workflows restored, and the push-hook Git override corrected. All checks passed and four intended hosts matched. Existing coverage gaps persisted. CI

2026-11-21 dependency refresh

Validated signed source 2c21c2e0f4633fcbb6b40eb6662939a19498d4b7. Dependency updates passed independent review, local and hosted gates, live Chat cleanup and fleet rollout. Extra synthetic checks verified MCP continuation and operator deadlines; Chat SDK changes were comment-only. Four reachable intended hosts matched; existing coverage gaps persisted. CI

2026-11-22 problem-first PR guidance

Cosmo, Jai's AI assistant.

Validated signed head b22e04289aceaf030a4fd69fd6ef633e8cf45a02 through upstream 31c4e14186e8cbbc0d9ba4514dda3c64880d1c9a. Only PR template comments changed; application code, dependencies, workflows and fork notes are unchanged.

Independent Codex review, hooks, local CI, pinned worker checks/all 15 tests, 66 isolated CLI invocations, 20 loopback executions, all 12 live Chat checks and all ten hosted checks passed. CodeQL analyzed the matching tree. Caller-only privacy was proved before writes; four owned messages were cleaned and final listing was empty. CI

Four reachable hosts match intended source, hashes and provenance. Accessible paired reads passed, including 11 VOC entries; 6 VOC contexts remain preview-only. Known raw/login PATH and matching keyring failures persist. Trusted Grokbot remains offline.

github-actions Bot and others added 22 commits October 15, 2026 21:19
* chore: open next unreleased section

* chore: restore development metadata after v0.45.0

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Peter Steinberger <steipete@gmail.com>
…aw#1221)

Rewrite `gog auth <email>` to `gog auth add <email>` when the first token after the top-level auth command contains an @ and is not an auth subcommand. Bare `gog auth` and mistyped subcommands keep their existing Kong errors.
Update Vitest to 5.0.5 and Cloudflare Workers types to 5.20261015.1 with matching lockfile entries. Preserve the worker's 24-hour release cooldown, pinned pnpm 11.28.5, security overrides, and Go requirements.

Validated with the frozen lockfile, full worker gate, independent Codex review, and exact-head CI. No production configuration or deployment changes.
…nclaw#1215)

Preserve paragraph breaks in forward notes and add opt-in HTML-note inputs to both send and draft forwarding. Share existing reply conversion rules without changing ordinary forward defaults or reply behavior. Document image-only alternatives and preserve signature placement.

Closes openclaw#1215. Maintainer product direction approved. Validation: base-failing/head-passing send and draft regression; focused composition tests; full make ci; govulncheck with no reachable vulnerabilities; independent review with no actionable P0-P2 findings; exact-head cross-platform CI.

Co-authored-by: Malo Bourgon <mbourgon@gmail.com>
Migrate repository-local macOS CI and release preflight from macos-15 to xcode-27 while preserving macOS 15.0 and Go 1.26.0 support.

Make the Darwin deployment target explicit in cgo compiler/linker flags, preventing reuse of cached macOS 27 objects, and verify the built binary's minimum OS. Keep the shared release workflow at v1 for the centrally managed migration. Update actionlint, the release guide, and changelog.

Validation: actionlint, independent Codex review through P2, warning-free native build and minos 15.0 verification. Remote make ci, govulncheck, and exact-head GitHub CI are recorded in the task report.
Replace the App-key dispatcher with OIDC-only Worker intake. No App key and no token mints remain in this workflow. The App webhook remains the independent route; the Worker owns eligibility and best-effort acknowledgements.

Canonical migration: openclaw/clawsweeper#2062

Validated with actionlint, zizmor --offline (zero template-injection findings), no secrets. references, and independent autoreview.
The Google Drive SDK dropped requested false booleans during JSON encoding. Preserve requested top-level flags, including default starred and hasThumbnail, while retaining omission for conditionally absent fields and nested booleans. Document the exact-response alternative.

The regression fails on the previous main and passes with the fix. Focused tests, make ci, and independent Codex review passed; govulncheck found no reachable vulnerabilities.

Co-authored-by: postoso <postoso@users.noreply.github.com>
Refresh the Google API client and golangci-lint, along with eligible worker types, Wrangler, PostCSS and Undici updates. Regenerate the lockfile using pnpm 11.28.5 and retain the Go 1.26 minimum, Node 26, pnpm 11, and 24-hour worker cooldown.

Validation: Linux make ci, worker frozen install/lint/typecheck and 15 tests, and independent Codex review passed. govulncheck found no reachable vulnerabilities; only the unimported OpenPGP advisory remains with no fixed version.
Add GOG_GOOGLE_API_BASE_URL for mocks, emulators, and relays that attach credentials outside gog. Use a plain transport without resolving local credential providers, preserve the request path/query and original host, and refuse cross-origin redirects while retaining command and read-only policies.

Full Linux make ci and independent review passed. The built CLI reached a synthetic relay without Authorization and refused a cross-origin redirect with zero requests to the target. Exact-head Linux, Windows, macOS, minimum-Go, worker, and Docker CI are green.

Closes openclaw#1225

Co-authored-by: km-tr <kumagai@bear.tokyo>
Peter explicitly accepted PR openclaw#1224 on 2026-10-20. The secrets code was reviewed in-session without uploading it to the review service; Peter's external-review exception applies only to this PR. Isolated Codex review of CLI/documentation found no actionable P0–P2 issue.

Fixed source-lock bypass and destructive output replacement found during review. Hold the shared store lock through reading, staging, verification and publication; independently verify every item and its metadata; fsync before atomic Linux/macOS directory exchange; roll back publication failures and retain recovery paths if rollback also fails. Clear decrypted byte buffers where practical. Preserve legacy and encoded formats and keep live credential files unchanged. Windows uses a fresh output path, flushed ciphertext and a write-through rename; existing output is refused safely where atomic directory exchange is unavailable.

Validation: full `make ci` passed on an isolated Linux runner; focused rekey/CLI tests and secrets race tests passed. `govulncheck ./...` found no reachable vulnerability; GO-2026-5932 affects the unimported OpenPGP package only. All exact-head GitHub CI checks passed: [run 39474735303](https://github.com/openclaw/gogcli/actions/runs/39474735303). No release is part of this landing.

Co-authored-by: Søren L. Hansen <sorenisanerd@gmail.com>
Align forwarded headers in both MIME parts with Gmail's formatting: linked sender/recipient addresses, plain labels, and two blank lines before the original body. Reuse the mailbox rendering helpers without changing reply attribution behavior.

Validated the baseline mismatch on synthetic headers; focused forward tests and the full make ci gate pass. Independent Codex review found no actionable P0–P2 findings. The contributor supplied live Gmail draft/readback evidence. Closes openclaw#1236.

Co-authored-by: Malo Bourgon <mbourgon@gmail.com>
Build release and Docker binaries with Go 1.27.3 and run minimum-series CI with Go 1.26.10, addressing GO-2026-6809 while retaining the Go 1.26.0 minimum. Pin the matching official Docker image digest and refresh the Google API client and generated definitions.

Validation: Docker consistency regressions, independent Codex P0–P2 review, full remote make ci, zero reachable govulncheck findings, and exact-head cross-platform CI. Worker updates inside the 24-hour release cooldown remain deferred.
Prepare the 0.46.0 minor release for new auth commands, Google API relay support, Gmail forwarding improvements, and the Go security update. Preserve all 11 Unreleased entries verbatim, reorder them by user impact, add a one-line highlight, and set the embedded version to v0.46.0.

Validation: unchanged bullet multiset, independent Codex P0–P2 review, full remote make ci, and exact-head cross-platform CI. The prior merged-toolchain release dry run passed. Publication requires a separate successful 0.46.0 dry run on this release-prep merge.
Update Wrangler, Workers types, Oxlint, and Oxfmt within the tracking worker's 24-hour release cooldown. Preserve runtime floors and supply-chain policy; include the update in the unpublished 0.46.0 notes.

Validation: make worker-ci on Node 26.12.0 and pnpm 11.28.5, independent review, and exact-head GitHub Actions.
Restore the versioned Unreleased heading and development source version after the verified 0.46.0 publication. Preserve all published release notes.

Validation: focused documentation/version checks, independent review, and exact-head CI.
mmaps and others added 24 commits November 4, 2026 20:38
Read push and webhook tokens from named environment variables while preserving literal flags, stored-hook defaults, validation, and secret-free previews.

Refs openclaw#1292.

Co-authored-by: Michael Appel <mappel@nvidia.com>
Keep the friendly missing-document message while retaining the API error cause so affected Docs commands use the documented not_found exit code 5.

Fixes openclaw#1288. Verified through built CLI before/after comparisons, regression tests, independent review, and exact-head CI.

Co-authored-by: HardMax71 <maxymazatyan@gmail.com>
build(deps): refresh Go clients and worker tooling

Retain the Go 1.26 minimum, patched build toolchain, pnpm version, release
cooldown, and security overrides while advancing tested patch/minor updates.
New backups no longer select a maintainer-owned repository. They commit locally until the user configures a remote, and the CLI explains local-only operation. Explicit saved remotes and existing Git origins continue to work without rewrites; checkpoint uploads follow the same rule.

Closes openclaw#1287.

Validation: the default-remote regression fails on the previous implementation. Synthetic tests pass for local initialization, snapshot/checkpoint commits without a remote, and pushing to a temporary bare Git origin. No real backup or Google-account access was performed. The backup guide documents explicit remote setup. Independent Codex P0–P2 review is clean.

Full gate: `make ci` and `govulncheck ./...` passed on the dedicated Linux Crabbox lease (run `run_8ec2e0593acf4e96b1e01faab914ef5a`). Govulncheck found no reachable vulnerabilities.
…arches

Reject equal or reversed Calendar windows with a usage error before requesting events, and make a far-future search with only --from usable by ending it 90 days after that start. Successful historical --from-only searches retain their existing end at now + 90 days. Explicit time ranges and historical timezone offsets keep their intended instants.

Closes openclaw#1280.

Validation: synthetic Calendar HTTP regressions fail on the old implementation for far-future searches, invalid ranges, and historical offset seconds. The focused Calendar suite passes, including a compatibility regression for historical open-ended searches. No live Google Calendar data was used.

Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_5b7894aafd5fe2d0f467bb6b930a7f50`). Independent Codex P0–P2 final review is clean.

Co-authored-by: Steven Huang <134844631+remote-controlled-man@users.noreply.github.com>
Add optional --keyring storage to auth service-account set. Existing JSON key files remain the default and continue to work. Keyring-backed files contain only a reference, resolved consistently by status, authentication, and Keep.

Each saved reference gets its own keyring entry so separate configurations cannot overwrite each other's credentials. A failed reference write preserves the old credential and removes the new entry. The auth guide documents migration into keyring storage, returning to files, recovery copies, and older-version compatibility. Generic legacy managed key files are removed after a successful migration; caller-owned input files and separate Keep-specific files remain untouched.

Validation uses synthetic keys and injected stores: file/keyring round trips, legacy migration, independent layouts, failed reference writes, cleanup, CLI status, and Keep resolution. No live account consent or real key migration was performed.

Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_eda6c371372b6e4a77c433a9bfe59c78`). Independent Codex P0–P2 final review is clean.

Co-authored-by: Tommy Joseph <64457309+tommyjoseph@users.noreply.github.com>
Automatic reauthorization now carries the command runtime and OAuth client dependencies into the callback. Expired-token recovery can reach the normal authorization path and retry the original request while retaining cancellation, the selected client, and the stored grant.

Closes openclaw#1277.

Synthetic proof reproduces the former missing-runtime error and verifies the runtime, credentials reader, token store, client resolver, cancellation, and original service/scope set. Existing retry-transport tests cover retrying with the refreshed token. No live consent run happened.

Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_dd52ab96aef020f29094b43ae82ea568`). Independent Codex P0–P2 final review is clean.

Co-authored-by: Vitor Cepeda Lopes <vitor@vitorcepedalopes.com>
Give every regular attachment and inline part a unique X-Attachment-Id. IDs combine the original attachment index and a content digest, remaining stable when the same attachments are rebuilt while distinguishing duplicate files. Regular attachment Content-IDs match their attachment IDs; quoted inline images retain their original Content-IDs.

Closes openclaw#1299.

Generated-MIME proof parses nested multipart parts, verifies uniqueness and matching Content-IDs, preserves the original inline CID, and checks stable IDs across independent builds with duplicate attachment bytes. The regressions fail on the old implementation. Draft composition parity and inline attachment tests pass. Delivered-Gmail behavior is contributor-reported; no live Gmail send, delivery, or draft-edit test was performed.

Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_8ffa60b899555b831ea3472d711aa5c7`). Independent Codex P0–P2 final review is clean.

Co-authored-by: Mattia Trapani <mattia.trapani@gmail.com>
Allow a local backup repository to acquire its first configured origin. After `gog backup init` without a remote, `gog backup init --remote URL` now adds the missing origin so subsequent pushes use it. Existing origins are never replaced, even when a different remote is supplied in configuration.

Follow-up to openclaw#1303 and openclaw#1287. Synthetic proof first reproduced the missing-origin failure, then verified initialization, a push to a temporary local bare repository, and preservation of the existing origin. No real backup was run or personal configuration changed.

Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_1fd82869a516d40c0c3e78f16c0b3efc`). Independent Codex P0–P2 final review is clean.
Finalize the 0.48.0 minor release notes and version for local-by-default backups, optional service-account keyring storage, ID-only Gmail search, and environment-backed watch tokens. Preserve all 21 existing release-note bullets and contributor credit, and explicitly disclose the delivered-Gmail and OAuth consent validation limits.

Validation: exact-head CI green; independent P0–P2 review clean; full make ci and govulncheck passed on the dedicated Linux lease. No reachable vulnerabilities and no real backup performed.
Give the complete command-package test suite a finite twenty-minute timeout in make test and minimum-Go CI. Preserve every test and existing toolchain.

The main minimum-Go failure exhausted Go's default ten-minute package budget during normal schema work. The named test passes in 1.53s on Go 1.26.10; independent P0–P2 review and all exact-head CI checks pass.
Restore the next development cycle after v0.48.0: one 0.48.1 Unreleased section and v0.48.0-dev version metadata, preserving the published release notes.

Release-closeout tests, independent P0–P2 review, and all exact-head CI checks pass. The published release and its channels have been independently verified.
Replace the four Clawdbot account examples with generic placeholders and clarify which authenticated account to supply. Record the documentation update in the changelog.

Validation: Codex review, five documentation-checker tests, all five repository CI jobs, and CodeQL passed.
Consolidate reproduced command bugs from openclaw#1308, openclaw#1311-openclaw#1319, openclaw#1321-openclaw#1326 and issues openclaw#1328, openclaw#1329, openclaw#1330, openclaw#1331, openclaw#1335.

Co-authored-by: Bobby Bones <159389674+saariuslystoned@users.noreply.github.com>
Co-authored-by: Sebastien Tardif <sebtardif@ncf.ca>
Patch the Go build toolchain for reachable GO-2026-6859 while preserving the Go 1.26.0 source minimum. Refresh Google clients, networking dependencies, and tracking-worker tooling without weakening the release cooldown or security overrides.

Validated with the full Go and worker gates, govulncheck, independent P0–P2 review, and exact-head CI.
Finalize the v0.48.1 patch release changelog and embedded version. Preserve all existing release notes and contributor credits; include highlights for safer Gmail replies, Calendar fixes, and Go security updates.

Validation: make ci and govulncheck ./... passed on AWS Crabbox; independent Codex autoreview scoped-clean through P2; all PR checks passed at 0ec5513.
Restore the versioned 0.48.2 Unreleased section and v0.48.1-dev embedded version after the verified v0.48.1 release. Preserve all published notes and contributor credits.

Validation: changelog preservation and heading uniqueness checks passed; independent Codex autoreview is scoped-clean through P2; exact-head CI 43818414106, CodeQL, and Docker passed at 7cd0bcd.
Co-authored-by: hannesrudolph <49103247+hannesrudolph@users.noreply.github.com>
@jai jai closed this Nov 19, 2026
@jai jai reopened this Nov 19, 2026
steipete and others added 4 commits November 20, 2026 17:22
)

Refresh MCP, Google API and protocol modules, Go networking, OpenTelemetry auto SDK, and tracking-worker dependencies while retaining runtime floors, the 24-hour worker cooldown, and security overrides.

Verified with make ci, worker checks, govulncheck, dependency audit, independent P0–P2 review, and exact-head cross-platform CI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent-ignore Operator-owned changes; exclude automated maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.