Developer

This part is for people who change repobs itself: how it is built, its API, how it is tested, and why it is the way it is. If you want to use repobs, go to the user guide.

Reading order

1. Architecture

   The server, the Git reader, the agent adapters, persistence and the web UI, and how they fit together.

2. HTTP API

   Every endpoint and schema of the loopback API, generated from the contracts.

3. Testing

   The commands, the synthetic fixtures and demo, and what each suite covers.

4. Progress

   Dated checkpoints: what was built, how it was verified, and what is next.

5. Reference audit

   The EnergyAtlas interface conventions the application follows.

6. Product handoff

   The original brief repobs was built from.

Decisions

1. Product foundation
2. Engineering choices
3. Dashboard and commit graph
4. Reference UI alignment
5. Views and File menu
6. Release packaging
7. Documentation site style
8. Automation rules and hiding
9. Agent plans in checklists