Artifact d9c0ad9effa9627c1e773758778d6dc068a5c450e52c87feda10e92961e416a1:
- File
internal/sync/client.go
-
2026-10-22 16:46:16
— part of check-in
[1abe24cd2b]
on branch feat/horizon-cones
— fix(sync): decide a structural store's depth only on a pull's reply
A push alone carries no horizon pragma, so its reply says nothing about how the horizon is served, and a structural store pushing to its origin fell back to the content horizon. The first reply decides only when the request pulled. Preconditions of the structural serving and receiving paths are asserted. (user: [email protected], size: 69139) [annotate] [blame] [check-ins using]
-
2026-10-22 17:01:15
— part of check-in
[78ed31bf91]
on branch feat/horizon-cones
— Merge branch 'wip/horizon-structural' into feat/horizon-cones
The structural horizon (draft-fossil-horizon-00 Appendix A step 5): a store at structural depth elides manifests and nodes below the horizon and keeps boundary labels; the client sends horizon-structural and horizon-seed and holds the seed it is sent; the origin restricts manifests to the held set, labels the boundary, mints and sends the seed, and serves structural only when the seed is current. Interoperates with zit at 9bf7ebfe0f in both directions. (user: [email protected], size: 69139) [annotate] [blame] [check-ins using]
-
2026-10-22 16:46:16
— part of check-in
[1abe24cd2b]
on branch feat/horizon-cones
— fix(sync): decide a structural store's depth only on a pull's reply