docs: cross-link the git-refs backend doc so it's discoverable

add234d→main·

Soph·1w ago·2 files·+3 added/-0 removed

A new architecture doc that nothing points at is easy to miss. Link the ref-checkpoint-backend doc from the two places a reader looking for checkpoint internals already lands: the Overview of sessions-and-checkpoints.md (its sibling) and the checkpoint Deep-Dive Reference list in CLAUDE.md (AGENTS.md is a symlink, so agents get it too).

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Sessions

01KX32R4BJTGAV3EQKN6RWDNG3View transcript

Build Checkpoints Store Based on DesignClaude Code·Opus 4.8[1m]·8 steps Document git-refs Checkpoint Backend ArchitectureClaude Code·Opus 4.8[1m]·1 step

Changes

2

• MCLAUDE.md+1

• docs/architecture

• Msessions-and-checkpoints.md+2

603 unmodified lines

604
605
606
607
608
609
610

603 unmodified lines

- [Sessions and Checkpoints](docs/architecture/sessions-and-checkpoints.md) - domain model, storage layout, checkpoint ID linking, commit trailers, package structure
- [Checkpoint Scenarios](docs/architecture/checkpoint-scenarios.md) - phase state machine and worked condensation scenarios
- [Ref-Based Checkpoint Backend](docs/architecture/ref-checkpoint-backend.md) - git-refs backend: primary/mirror taxonomy, ref layout + sharding, push-discovery queue, read routing, config + rollout

#### When Modifying the Strategy

MCLAUDE.md+1

3 unmodified lines

4
5
6
7
8
9
10
11

3 unmodified lines

Entire CLI creates checkpoints for AI coding sessions. The system is agent-agnostic - it works with Claude Code, Codex, Gemini CLI, OpenCode, Cursor, Factory AI Droid, Copilot CLI, or any tool that triggers Entire hooks.

This document covers the domain model shared by both checkpoint storage backends. For how the **git-refs** backend stores checkpoints as one ref per checkpoint — its layout, push/fetch model, read routing, and configuration — see [Ref-Based Checkpoint Backend](ref-checkpoint-backend.md).

## Domain Model

### Session