Repo Workflows

Canonical Commands

Use run.sh from the repo root whenever possible:

./run.sh doctor
./run.sh dev all
./run.sh build all
./run.sh test
./run.sh verify-all

Job	Source of truth
New demo app flow	`@elata-biosciences/create-elata-demo`
Consumer-facing install path and package landing pages	npm package pages
Consumer-facing package docs	package `README.md` files
SDK build, test, release orchestration	`run.sh`
Public app-launch, protocol, and XP context	`../elata-protocol`
Release policy and recovery	/sdk/maintainers/releasing
Repo and package ownership questions	`docs/repo-map.md` in `elata-bio-sdk`

When you need to confirm whether something is current or canonical:

Scaffolder changes: ./run.sh test create-elata-demo
Consumer onboarding or packaging changes: pnpm smoke:consumers
run.sh changes: run the narrowest affected command, then broaden if release paths changed
Release tooling changes: ./run.sh verify-all if feasible
Docs that mention onboarding: verify the create-elata-demo path and the parent-workspace caveat

If you are debugging beyond package boundaries, also use the public protocol repo:

../elata-protocol for contracts, local Anvil deployments, config generation, XP tooling, and simulations

See Related Repos for the developer-focused map.