Slice: inspect native Memory Git graph and full-body diff #260

Parent

Part of #259. Related: #114, #115, #75.

What to build

A Human opens a PersonaBot DM and sees the Memory Repository's native local Git branch/commit graph in the right Channel sidebar. Every displayed commit carries a clear accepted, pending, or needs-repair status; current branch and HEAD are visible. Selecting a commit replaces the entire Channel body with its changed-file list and readable diff. Returning to Chat restores the draft and reading position.

This is a real read-only path through the Host Memory Service, Client bridge, and Channel UI, using the repository's Git objects/refs plus Memory acceptance metadata. It does not invent a second commit authority.

Acceptance criteria

• A real Memory Repository with multiple local branches shows their reachable commits, parent relationships, branch labels, current branch/HEAD, and acceptance/repair markers; pending raw Git commits are visible without being presented as accepted Memory.
• Graph and commit queries are bounded, validate commit identity, and return safe errors for missing or invalid refs; the Client never reads the repository directly.
• Selecting a commit shows changed files and diff across the full Channel body, including the composer region; returning to Chat preserves an unsent draft and scroll position.
• Refresh and Host restart reconstruct the same graph/status view from Git and durable Memory acceptance facts.
• Focused Host/Client integration tests cover observable behavior; a real DSH instance provides a Human-testable URL and saved light/dark screenshots. Stop for Human QA before expanding branch mutation.

Blocked by

None — can start immediately.