The Fougere CLI, under its unscoped name — compose a workspace, serve a frond, call an operation.

Scaffold a Fougere workspace — `npm create fougere`.

Optional call log for Fougere: a bounded ring of every dispatch, served as an rpc operation. Read it with `fougere devtools`.

The conventional boot of a Fougere app — the one place storage is wired.

The Fougere CLI — compose a workspace, serve a frond, call an operation.

Optional observability for Fougere: one span per operation, W3C Trace Context across any transport.

A back-office derived from what the app already says it hosts — a react-admin DataProvider over the Fougere wire.

The Vite plugin: what any Vite-built host must know to run a Fougere app.

The host-independent half of a Fougere app: boot, call envelope, REST table, form contract.

Logging for Fougere: two lines for every call, in every process, and a file destination for the lines.

The scan: Fougere reading a project's source to produce the descriptors core boots from. Needs a filesystem and a TypeScript program.

The core — scan, call contract, façades, remote stand-ins.

HTTP router and middleware.

Entity → REST routes.

The Nuxt module: Fougere's client primitives and server surface.

Tests derived from the declaration — cases, stubs and a gradient of realities.

The entity and its 4 axes — shape, role, lifecycle, boundary. Subject-owned judgments, edge-safe.

Fougere's DI container: resolution by type, wired from the AST scan. Zero dependencies.

Configuration sugar (@config) — declarative, never hidden runtime.

Fougere's auth — a translation layer onto better-auth.