journal

type Debouncer struct {
	// contains filtered or unexported fields
}

type Journal struct {
	// contains filtered or unexported fields
}

type Options struct {
	MaxBytes int64            // rotate the active segment past this size (0 = unbounded)
	MaxFiles int              // keep at most this many segments (0 = unbounded)
	Clock    func() time.Time // record timestamp source (defaults to time.Now)
}

type Record struct {
	SchemaVersion int          `json:"schema_version"`
	Cursor        uint64       `json:"cursor"`
	TS            time.Time    `json:"ts"`
	SessionID     string       `json:"session_id"`
	Type          RecordType   `json:"type"`
	Group         status.Group `json:"group,omitempty"` // set on group_transition
	// Agent is the session's agent identity (persist.Meta.AgentType), so the phone can label
	// a session with the CLI running it. The daemon sets it on the roster snapshot and on all
	// four journalworthy transitions (internal/daemon/journal.go); the `deleted` record
	// (lifecycle.go) deliberately carries none, because it REMOVES the session from the
	// phone's model and an agent name on a tombstone would describe nothing.
	//
	// It is omitempty and its ABSENCE IS MEANINGFUL: a record with no agent carries no
	// agent, and readers must never read "" as an agent by that name.
	//
	// Adding it did NOT bump SchemaVersion, and internal/journal/agentfield_test.go pins
	// why in both directions: this build reads pre-Agent lines (an absent key decodes to
	// ""), and a build predating the field reads records carrying one (encoding/json
	// ignores the unknown key). A bump would instead make every older daemon reject every
	// record this build writes, costing them the whole journal to gain nothing.
	Agent string `json:"agent,omitempty"`
	// Name is the session's USER-GIVEN label (persist.Meta.Name), so the phone can head a row
	// with what a person called the session instead of the 16-char random local id. It is set
	// at exactly the sites Agent is -- the roster snapshot and all four journalworthy
	// transitions -- and the `deleted` record deliberately carries none, for Agent's reason: a
	// tombstone REMOVES the session, and a label on it would describe nothing.
	//
	// It is omitempty and its ABSENCE IS MEANINGFUL, again as Agent's: most sessions are never
	// labelled, so an empty name means the user gave none. The phone falls back to the id
	// (mobile/app.go's session()); nothing anywhere may substitute a plausible label for a
	// missing one.
	//
	// Adding it did NOT bump SchemaVersion, and internal/journal/namefield_test.go pins why in
	// both directions, exactly as agentfield_test.go did for Agent.
	Name string `json:"name,omitempty"`
	// StateSince is the MACHINE's own stamp of when the session entered its CURRENT state --
	// persist.Meta.EffectiveGroupEnteredAt(), with that method's own fallbacks for records
	// written before GroupEnteredAt existed -- set at exactly the sites Agent and Name are
	// (the roster snapshot and the four journalworthy transitions), so the phone can age a
	// row from a clock it did not invent (phone-refit-playbook W7.1). It is NOT LastActivity:
	// that is written only at launch and exit, so "Waiting on you · 3h" would have meant
	// "launched 3h ago" and twins launched together would age identically. Zero means the
	// meta carried no instant at all, and it is omitzero so a record without one serialises
	// as it did before the field existed. It is distinct from TS, which is when THIS RECORD
	// was appended.
	StateSince time.Time       `json:"state_since,omitzero"`
	Payload    json.RawMessage `json:"payload,omitempty"` // opaque per-type extra
}

type RecordType string

type Resume struct {
	Cursor     uint64
	Roster     []Record
	Events     []Record
	FullResync bool
}