evidence

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

type CommitInfo struct {
	SHA        string `json:"sha"`
	Subject    string `json:"subject"`
	AuthorTime int64  `json:"author_time"`
	// IssueIDs is reserved for the H4 issue-id extraction stage; left
	// empty by H3 so the schema is stable now and the Agent doesn't
	// crash on a missing field once H4 lands.
	IssueIDs []string `json:"issue_ids,omitempty"`
	// TopFiles is populated by TicketIndex's pickSampleCommits — the
	// top-3 most-frequently-touched directory paths across the
	// commit's hunks (e.g. ["crypto/secp256k1", "consensus", "core"]).
	// Lets the viewer's TicketIndex panel hint at a ticket's reach
	// before the user pays the cost of fetching the full EvidencePack.
	// Left empty (omitempty) by EvidencePack's BuildPack flow because
	// hunk file_path is already surfaced per-HunkRow there.
	TopFiles []string `json:"top_files,omitempty"`
}

type Hit struct {
	Commit CommitInfo `json:"commit"`
	Hunks  []HunkRow  `json:"hunks"`
}

type HunkRow struct {
	ID        string         `json:"id"`
	FilePath  string         `json:"file_path"`
	StartLine int            `json:"start_line"`
	EndLine   int            `json:"end_line"`
	PatchText string         `json:"patch_text"`
	Modifies  []ModifiesInfo `json:"modifies,omitempty"`
}

type ModifiesInfo struct {
	Qname     string `json:"qname"`
	Type      string `json:"type"`
	FilePath  string `json:"file_path"`
	StartLine int    `json:"start_line"`
	EndLine   int    `json:"end_line"`
}

type Options struct {
	Intent       string
	SeedQname    string
	IssueID      string
	K            int
	BudgetTokens int
	// Offset skips the first N commits in the recency-sorted result —
	// the "Load more" page boundary. Used by viewer/agent flows that
	// already consumed page 0 and want to keep walking back through a
	// large ticket without raising BudgetTokens (which would also
	// inflate the per-call payload). Stable across calls because
	// commit recency tie-breaks on SHA in groupByCommit's sort.
	Offset int
	// Mode picks the term-match strategy applied on top of the BM25
	// ranking:
	//   - "" or "or" (default): keep BM25's any-term-match behaviour.
	//     A high-scoring hit only needs to share one query token with
	//     the candidate doc; useful for fuzzy semantic search.
	//   - "and": after BM25 ranking, drop hits whose virtual document
	//     doesn't contain *every* query token. Useful for precise
	//     agent queries like "all hunks mentioning RetryPolicy AND
	//     Backoff" where OR's looser fuzzy match would surface noise.
	//
	// AND is purely a post-filter: the BM25 ranking still computes
	// across the full corpus, so the relative scoring among AND-mode
	// survivors matches what they would have been in OR mode.
	Mode string
}

type Pack struct {
	Intent string `json:"intent"`
	Hits   []Hit  `json:"hits"`
}

type TicketRow struct {
	IssueID       string       `json:"issue_id"`
	HunkCount     int          `json:"hunk_count"`
	CommitCount   int          `json:"commit_count"`
	SampleCommits []CommitInfo `json:"sample_commits,omitempty"`
}