Krabby is slowly switching to a query-based architecture, which somewhat invalidates the motivation for krabby-api (i.e. to support remote execution of tasks). In the future, we could allow communicating queries across the network, but this would require a higher-level API than !19. For now, krabby-api doesn't have a distinct purpose; it should be removed to simplify the codebase.
Krabby is slowly switching to a query-based architecture, which somewhat invalidates the motivation for `krabby-api` (i.e. to support remote execution of tasks). In the future, we _could_ allow communicating queries across the network, but this would require a higher-level API than !19. For now, `krabby-api` doesn't have a distinct purpose; it should be removed to simplify the codebase.