No contact form. Just the repository.

• Report a bug or request a featureGitHub Issues — search first, then open a new issue with repro steps or a clear use case.
• Contribute codeCONTRIBUTING.md — dev setup, the project's testing rules, and the full offline test-suite matrix.
• Browse the sourceThe GitHub repository — every component, every commit.
• Read the licenseMIT — use it, fork it, ship it, modify it.

Project rules, in short

From CONTRIBUTING.md, so you know what a pull request is held to:

• Every change ships with offline tests — nothing touches the network (the e2e suite talks only to an in-process fake PostgREST on 127.0.0.1).
• Robot statuses use the canonical vocabulary in core/yantracore — never a new ad-hoc spelling.
• Robot-affecting actions always go through the commands approval-gate table, never a direct state write.
• Schema changes are new, numbered, idempotent SQL files in supabase/ — an already-applied migration is never edited in place.