Build Jido

Outcome: A small Jido change uses the target repository's current APIs, keeps state and effects at the correct boundary, and has focused tests.

Done: The requested action, agent, runtime, AI, or test contract is complete; focused success and failure tests pass; required repository checks pass or have reported limits; and the local change is ready for review or commit.

Assignment

The required inputs are one Jido change request and its target Elixir repository. Direct user authority or inherited caller authority permits local source, test, fixture, and configuration-template edits inside that request. Do not install dependencies, stage, commit, push, publish, store credentials, use a live provider, or change remote or live state. HTTP, database, file, shell, provider, and other external effects need authority from the task and a clear owner. Ask when the effect or runtime boundary is unclear.