Artifact afdd0f9faa27f2bd0ccb9937f43b86d35570d8bfaf35b73b6ff40798ed32e73d:
- File
horizon_cost.go
-
2026-10-23 03:02:17
— part of check-in
[834b28d9fe]
on branch feat/horizon-cones
— feat(cli): report what each horizon rule would hold
Draft ยง3.4 asks a tool that suggests a horizon to show, before the choice, what each rule would hold in check-ins and bytes. repo cone cost <check-in> prints that for descendants and leaves from the local repository, and Repo.HorizonCost returns the figures. The --horizon help of repo clone and repo cone store points to it, noting that a clone has no repository yet. (user: [email protected], size: 2618) [annotate] [blame] [check-ins using]
-
2026-10-23 03:02:35
— part of check-in
[77e74bd011]
on branch feat/horizon-cones
— Merge branch 'wip/repin-5d61' into feat/horizon-cones
The horizon draft pinned at zit horizon-rfc 5d618aaeb1: an origin with no tag in force mints no seed and serves the content level, and choosing C is shown with each rule's cost (repo cone cost, Repo.HorizonCost). (user: [email protected], size: 2618) [annotate] [blame] [check-ins using]
-
2026-10-23 03:02:17
— part of check-in
[834b28d9fe]
on branch feat/horizon-cones
— feat(cli): report what each horizon rule would hold