This project uses bd (beads) for issue tracking. Run bd prime for full workflow context. Architecture in one line: Issues live in a local Dolt database (.beads/dolt/); cross-machine sync uses bd dolt push/pull (a git-compatible protocol), stored under refs/dolt/data on your git remote — separate from refs/heads/* where your code lives. .beads/issues.jsonl is a passive export, not the wire protocol. See SYNC_CONCEPTS.md for the one-screen overview and anti-patterns (don't treat JSONL as the source of truth; don't bd import during…
3672mo agoReviewMountCreate a free account to mount
This project uses bd (beads) for issue tracking. Run bd prime for full workflow context. Architecture in one line: Issues live in a local Dolt database (.beads/dolt/); cross-machine sync uses…
24644d agoReviewMountCreate a free account to mount
You are a senior full-stack developer capable of working across the entire application stack. You assist developers working on TestProject. Follow these conventions: Do not commit secrets to the repository…
5710mo agoReviewMountCreate a free account to mount
Conventions for anyone, human or agent, working in this repository. The design is in docs/DESIGN.md; read docs/index.md first. One package. Follow the layout in DESIGN section 10 exactly. This project…
1948d agoReviewMountCreate a free account to mount
This project uses bd (beads) for issue tracking. Run bd prime for full workflow context. Architecture in one line: Issues live in a local Dolt database (.beads/dolt/); cross-machine sync uses…
This project uses bd (beads) for issue tracking. Run bd prime for full workflow context. Architecture in one line: Issues live in a local Dolt database (.beads/dolt/); cross-machine sync uses…
biblical-atlas-mcp is a Go MCP server for the biblical-atlas Bible atlas. It downloads the atlas's public data file (https://biblical-atlas.geiser.cloud/data.json), indexes it in memory and answers ten read-only tools. The design is in docs/design/DESIGN.md; read it before changing behaviour. User docs are in docs/. This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands. Architecture in one line: issues live in
MCP server (Go, stdio only, macOS only) for VPN Bypass. Each tool sends one request to the app's control socket and returns the app's result object unchanged. The app owns the contract. Its source of truth is in the VPN-Bypass repo: Sources/VPNBypassCore/CommandRouter.swift (Custom-mode verbs: status, mode, default, route.*, rule.*), ClassicControl.swift (the 4.9.0 domain.*, service.*, routes.*, refresh, dns.refresh and logs verbs; both hold their arguments and error codes), ControlSocketServer.swift (framing: one JSON line each way, 64 KiB per request line, 30…
GeiserXDeletes or force-pushesAGENTS.md