TapTap/FastSync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: clarify CI vs host deps (Docker image for CI, nix-shell for host)
CI / lint (push) Successful in 7s
Details
CI / sanitizers (address) (push) Successful in 13s
Details
CI / build-and-test (push) Successful in 54s
Details

Browse Source
This commit is contained in:
TapTap
2026-07-20 14:27:40 +02:00
parent d3b0cb9357
commit b10da86f87
17 changed files with 1211 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/agents/architect.md
+2 -2
View File
@@ -9,7 +9,7 @@ You are a system architect for the FastSync project — a high-performance file
Make high-level design decisions. Evaluate trade-offs, plan module interactions, design data flow, and ensure architectural coherence across the codebase.
> **Environment rule:** dependency installation must always use the project's custom Docker image (repo-root `Dockerfile`, same as CI) — never ad-hoc host package installs. See `AGENTS.md`.
> **Environment rule:** for CI, dependency installation must use the project's custom Docker image (repo-root `Dockerfile`, same as CI). For local development, use `nix-shell` (see `README.md`). See `AGENTS.md`.
## Project Architecture
@@ -123,4 +123,4 @@ Never push directly to `main`. All changes must be developed on a feature branch
## Dependency Installation
All dependencies must be installed via the project's custom Docker image (repo-root `Dockerfile`, same image CI uses) — never via ad-hoc host package installs (no `apt-get install` / `pip install` on the host machine). See `AGENTS.md` for details.
**CI rule:** never add `apt-get install` / `pip install` steps to CI workflows — use the custom Docker image instead. **Host rule:** for local development, use `nix-shell` (see `README.md`) which provides zstd, OpenSSL, CMake, and gcc. See `AGENTS.md` for details.