visible run-scoped worker labels may be coarse English role-family names such as `frontend`, `backend`, or `test`, but Meta_Kim does not project those execution labels as durable agents
state the next sequence: research -> three core documents -> wait for user confirmation -> Spec / tasks -> frontend first with runtime verification -> backend / tests / delivery.
- The first reply must explicitly promise that
state the next sequence: research -> three core documents -> wait for user confirmation -> Spec / tasks -> frontend first with runtime verification -> backend / tests / delivery.
- The first reply must explicitly promise that
Frontend AGENTS.md
## Frontend-Backend Contracts
1. Browser requests use the Go relay API directly through same-origin `/api/*`, `/sdk/*`, and `/discovery*` paths.
2. Relay path constants are owned by `../types/paths.go
with a typed scanner core and a local React app:
- `scripts/*.ts`: local CLI, frontend build, and dev server entry points.
- `src-core/`: scanner, storage, validation, and model-analysis modules
models
uv run python clarity.py models --debug # explain how credentials resolved
# Rebuild the React frontend (only when changing web/ source)
cd web && npm install && npm run build
# Frontend dev server
application is a read-only SQLite API (Python, standard library only) behind
a React/Vite frontend. Nothing here trains, labels, or writes prompt data.
## Get it running
Prerequisites: Node.js
Project Structure & Module Organization
This repo contains a Bun-powered bridge and a React/Vite frontend for Herdr.
Frontend code lives in `web/src`, with reusable UI under `web/src/components`,
assets under `web/src/assets
dependency-light**: Python standard library plus
`cryptography` (used only to encrypt export bundles). No frontend build.
- The install writes to exactly two places: `~/.local/share/claude-unlimited/`
(the app and its virtualenv