apps/portal: thin Angular application shell and route composition.apps/api: Effect-based API control plane.apps/runner: thin runner entrypoint and deployment target.libs/audit/**: audit domain code shared across portal, API, runner, contracts, model, and persistence.libs/platform/**: cross-cutting platform services such as observability.libs/ui/**: reusable web UI primitives.
The API integration suite and full local browser journey are independently runnable Nx targets. See docs/testing/integration-and-e2e.md for prerequisites, artifacts, and troubleshooting.
This workspace provides an Nx target to run @effect/language-service diagnostics per project.
Run diagnostics for a single library:
pnpm exec nx run <project-name>:effect:diagnostics
Example:
pnpm exec nx run platform-observability:effect:diagnosticsEmit JSON (useful for machine processing or sharing with Codex):
pnpm exec nx run platform-observability:effect:diagnostics --format=json --outputFile=.tmp/effect/obs.jsonRun diagnostics for multiple libraries:
pnpm exec nx run-many -t effect:diagnostics --projects=platform-observability,audit-persistence,audit-runner --parallel=3For publishable Angular libraries with secondary entry points, keep the root package name, tsconfig.base.json aliases, and consumer imports in the same canonical form.
Reference: