comparison AGENTS.md @ 279:b3b547563ec7

Add Google connector service and agent wiki Implement the C/Seobeo Google Drive and Gmail connector with encrypted OAuth storage, Zenbu authentication, browser testing, AI tool discovery, chunked HTTP decoding, and Bazel coverage. Consolidate repository guidance into progressive wiki documentation and enforce arena-first allocation for new first-party C code. Co-authored-by: Copilot <[email protected]> Copilot-Session: 84c338fd-0939-4bb3-b7f3-1062eb213e5d
author MrJuneJune <me@mrjunejune.com>
date Mon, 17 Aug 2026 22:22:36 -0700
parents
children
comparison
equal deleted inserted replaced
278:8d560f50ed4c 279:b3b547563ec7
1 # Zenbu agent instructions
2
3 Use progressive disclosure. Do not recursively read every README, skill, or
4 wiki page in this monorepo.
5
6 1. Read [`wiki/README.md`](wiki/README.md).
7 2. Identify the package paths involved in the task.
8 3. Follow only the documentation links that the repository wiki assigns to
9 those paths.
10 4. Read `BUILD` files before broad source searches when work crosses packages.
11 5. Use Mercurial commands (`hg status`, `hg diff`), not Git workflows.
12 6. This is a Bazel-only repository. Build, test, run, bundle, generate, and
13 fetch toolchains through Bazel targets; do not introduce Make, CMake, ad-hoc
14 compiler commands, or package-manager run workflows.
15 7. Prefer first-party Zenbu libraries over new dependencies.
16 8. Depend on third-party code through its Bazel label or `MODULE.bazel`, never
17 through an untracked system installation or a direct source-path include.
18 9. Use `Dowa_Arena` for first-party allocation. Do not add raw
19 `malloc/calloc/realloc/free`; arena-owned pointers are released only by
20 `Dowa_Arena_Free`.
21 10. Update the relevant canonical wiki when behavior, configuration, routes,
22 architecture, or agent workflows change.
23
24 For a single-package task, the expected documentation set is:
25
26 ```text
27 AGENTS.md -> wiki/README.md -> one package wiki/README
28 ```
29
30 Read multiple package wikis only when the dependency graph proves the task is
31 cross-cutting. Source code and tests remain the final authority when a wiki is
32 stale or incomplete; fix the wiki as part of the same change.