Guide for developers and agents
Start with getting started, public API, architecture, object packages and creating objects.
engine/ owns generic services and imports no object or shell code. Each objects/package/ folder is independently portable and receives the engine API as a constructor argument. shell/ is a consumer demonstrating application logic. All documentation and licenses belong under docs/. Preserve existing third-party notices.
Maintain tests when changing behavior. Run npm test, npm run verify and the browser checks. Browser fixtures using synthetic input do not establish physical-device coverage. Use npm run build to prepare distribute/ and its complete ZIP, keeping historical and temporary files out of the public output.
The included package.json supplies the current version and supported commands. Code derives local roots from module locations; do not add hard-coded machine paths.