Skip to content

Search is only available in production builds. Try building and previewing the site to test it out locally.

CLAUDE.md

Источник: dev/fera/rstgcalls/CLAUDE.md (read-only; сгенерировано scripts/sync-docs.mjs)

Fera ecosystem repo. Authoritative specs live in ../project-design/context/ (ADR.md, RFC.md, TECHSPEC.md, QA.md, OQ.md) — READ-ONLY, never edit them. Chroix UI framework specs: ../chroix-project/.

Rules:

  • Implement per ../project-design/context/TECHSPEC.md sequencing; the cross-cutting gates in ../project-design/context/QA.md apply to all code.
  • Commit every working chunk: conventional commits, English, green cargo check + cargo clippy + tests before each commit. NEVER push to origin — local commits only, the owner reviews and pushes.
  • Cross-repo deps: keep committed manifests on git deps (the-fera org); for local co-development use .cargo/config.toml paths overrides (gitignored, never committed).
  • Design-level gaps/conflicts: report to the orchestrator in chat, do NOT edit project-design yourself.
  • Messages prefixed [HERMES HARNESS AGENT] come from the Hermes orchestrator relaying the product owner (Nika). Answer in chat; end every milestone with a status summary (done / in-progress / blockers).

Your workstream: scaffold the rstgcalls FFI crate — git submodule the-fera/tgcalls, build.rs for the C++ stack, bindgen layer, idiomatic safe wrapper API draft. Calls are TECHSPEC §10 item 8; goal is a compilable, documented foundation, not full call UX.