Artifact 6e18b87482ec33728dcd54073cdd404e0ad216151339a7a10128105cee5d0177:
- File
repo_history.go
-
2026-10-23 02:16:05
— part of check-in
[1823fe8ca8]
on branch feat/horizon-cones
— feat(annotate): report lines from at or below a structural horizon
draft-fossil-horizon-00 §5.5 requires an operation needing history below the horizon to detect the crossing and name the horizon. Annotating back past C stopped at the parent the store does not hold and credited every remaining line to the oldest version it reached, presenting a guess as an attribution.
The walk now asks content.BelowHorizon about the parent it could not load; when it lies below the structural horizon, the lines left without credit are marked BelowHorizon and reported against the horizon's check-in. The public AnnotatedLine carries the flag, and repo annotate prints such lines against ^<horizon> with one trailing note naming the horizon and repo cone deepen. A content horizon holds every manifest, so BelowHorizon never fires there; a conformance case clones both depths to show it. HZ-5.5-1 is now covered for every operation it lists. (user: [email protected], size: 30373) [annotate] [blame] [check-ins using]
-
2026-10-23 02:38:31
— part of check-in
[479cbaad12]
on branch feat/horizon-cones
— Merge branch 'wip/hz-close-annotate' into feat/horizon-cones
Annotate in a structural store marks the lines that reach the horizon and names the deepen that would show their origin (§5.5); the origin memo keeps the trees a horizon's walk reads in a bounded cache, so a second horizon over the same store reads only trees the first did not. (user: [email protected], size: 30373) [annotate] [blame] [check-ins using]
-
2026-10-23 02:16:05
— part of check-in
[1823fe8ca8]
on branch feat/horizon-cones
— feat(annotate): report lines from at or below a structural horizon