runtime (DeepAgents/LangGraph). The runtime
emits native
`@langchain/protocol` `ProtocolEvent` frames via `streamEvents(v3)`; every
frontend consumes them through the `@langchain/langgraph-sdk`
`Client`/`ThreadStream`/`StreamController` over HTTP/SSE. The seam is that
**protocol
inline regex literals when reused or non-trivial
---
## Trust the contract
If backend and frontend are part of the same system, and the backend explicitly guarantees a response shape
Node CLI scripts, the test suite, the optional local dashboard server, and/or the Vite frontends.
## Setup, tests, and checks
- Runtime: Node.js (CI pins Node 20; Node 22 works). Single
downloading PE binaries from Winbindex and extracting symbol/type/syscall data from matching PDBs.
- **windiff_frontend** — Next.js/React static site that loads those databases and provides Browse/Diff UI.
## Commands
### windiff_cli (Rust
built in `prepare-package` and copied into the jar just before it is assembled (`frontend-maven-plugin` + `maven-resources-plugin` in `pom.xml`). So `compile`, `test` and `quarkus:dev` never
upstream orchestration live in `internal/` (`internal/runtime`, `internal/httpapi`, `internal/upstream`, `internal/storage`).
- Vue/Tailwind assets are kept in `frontend/`; bundled static output is embedded from `web/`.
- Integration and regression assets reside under `tests
does it only defend against an
attacker who already controls the local Owner account?
## Frontend package manager
The WebUI uses pnpm 11.1.2, pinned by the `packageManager` field in
`web/package.json
format
cargo fmt --manifest-path src-tauri/Cargo.toml # Rust format
# Test
npx vitest run # Frontend tests
npm run test:e2e # Playwright e2e: real headless backend + real browser (see e2e/)
cargo
commands are in `package.json` scripts:
- `pnpm run dev:all` — start the full stack: Vite frontend `:3000`, Node server
`:3001`, Lobster executor `:3031`, and Python engine `:9700`. This is the
normal
lint # Catch broken local imports + undefined names
make hal-test # Run HAL tests
# Web frontend (React/Vite/Tailwind in system/web)
make web-install # npm install
make web-dev # Vite dev server
make
Keep durable service behavior
under `tradingcodex_service/application/` and use direct canonical imports.
- Frontend source lives under `frontend/`; compiled assets under
`tradingcodex_service/static/tradingcodex_web/` are generated, not hand-edited.
- Keep prompts, skills
Electrobun), web dashboard, and platform connectors (Telegram, Discord, WeChat, etc.). Inherits `~/.codex/AGENTS.md`.
## Cloud frontend visual review (REQUIRED for any UI change)
Any change in `eliza/packages/cloud-frontend/` MUST go through the manual
repo's Prettier (this covers Markdown too).
## JavaScript tooling
- Use `jlpm` for every frontend command (install, build, lint, test). Do not use a system `yarn` or `npm`. `jlpm
recolor models for aesthetics.
- Verify both directory cards and detail pages.
For frontend work, avoid landing-page-style redesigns. This is a utilitarian catalog: dense, searchable, and scan-friendly. Cards