Artifact 5f67d258bf305f94399dbca26c75409ba8507e377d07b320ff418a9445152b3b:
- File
internal/manifest/log.go
-
2026-10-22 17:21:12
— part of check-in
[ee3ccc7c67]
on branch feat/horizon-cones
— feat(history): render a horizon boundary as the horizon
A parent the origin labelled below a structural horizon is the horizon itself (draft-fossil-horizon-00 5.4), but the history views showed it as a bare parent hash, and the ancestry walk tried to read an event for it.
LogEntry and TimelineEntry gain HorizonParents, the subset of Parents that carries a boundary label; Ancestry ends at such a parent without an error; repo timeline prints it as "parent: <hash> (horizon)". An absent parent that is not labelled is transit and renders as before. (user: [email protected], size: 4979) [annotate] [blame] [check-ins using]
-
2026-10-22 17:21:31
— part of check-in
[d0c44dbc25]
on branch feat/horizon-cones
— Merge branch 'wip/horizon-render' into feat/horizon-cones
History views render a labelled horizon boundary as the horizon (draft-fossil-horizon-00 ยง5.4): Repo.Ancestry ends there without an error, Repo.Timeline and LogEntry report it in HorizonParents, and repo timeline prints it as (horizon). An unlabelled absent parent renders as before. (user: [email protected], size: 4979) [annotate] [blame] [check-ins using]
-
2026-10-22 18:30:02
— part of check-in
[75ed88e8e9]
on branch feat/horizon-cones
— Merge branch 'feat/horizon-cones' into wip/horizon-step6
# Conflicts: # conformance/requirements/horizon.tsv (user: [email protected], size: 4979) [annotate] [blame] [check-ins using]
-
2026-10-22 17:21:12
— part of check-in
[ee3ccc7c67]
on branch feat/horizon-cones
— feat(history): render a horizon boundary as the horizon