docs: point AGENTS.md at the vault hub #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/vault-hub"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a
## Documentationpointer to the vault hub (Engineering/Projects/safe-ai-tools/00 Overview.md), as the vault conventions ask for a new repo. Outside the Esper-managed block so a regenerate keeps it. Docs only, no version bump.🤖 Generated with Claude Code
🤖 Auto-review status ·
jonah/safe-ai-toolsPR #5✅ PR is clean — no fixes required.
Last updated: 2026-10-06T12:35:32.163Z
[STATUS: CLEAN]
Review scope:
origin/main...HEAD— 1 commit (51746c3 docs: point AGENTS.md at the vault hub), 1 file changed, +5 lines (AGENTS.md:54-57).Findings:
## Documentationsection sits after<!-- esper:project-context:end -->, soesper-cli initwon't overwrite it (AGENTS.md:52-57).git diff --checkclean, trailing newline present, file at 57/500 lines, no secrets,gitleaks/end-of-file-fixerunaffected.CLAUDE.md→@AGENTS.md.Non-blocking notes (no action required):
AGENTS.md:56— the vault pointer depends on theobsidianMCP with no fallback, unlike the Esper section (AGENTS.md:15-17) which explicitly degrades when its MCP is down. Harmless today; add a plain-path fallback only if agents actually stall on missing docs.AGENTS.md:55— "plans ... live in the vault, not here" is loosely contradicted byBRIEF.mdliving in-repo. Wording nit only; product docs (README, CHANGELOG) are clearly out of scope of the sentence.