# Gito Client

Flutter control surface for Gito.

The first slice keeps the client scaffold light. It should consume Gito through
proto-socket for operation requests, event streams, and log streams. REST is only
for health/readiness and operational compatibility endpoints.

Agent interaction UI should come from the sibling Flutter package:

```yaml
dependencies:
  agent_shell:
    path: ../agent-shell
```

That package is UI/domain surface only. The backend/runtime for agent execution,
shell command execution, command policy, cancellation, and log redaction belongs
to the sibling `../iop` project. Gito's client should treat Gito as the Git
control surface and operation/event stream, not as the agent runtime backend.
