Block a user
A module release does not record which topdata it shipped against
Resolution
Pin a tag at release — but as a record, not a binding. The module build must fetch a topdata catalog anyway to get sow_top.hak and sow_tlk.tlk digests for the NWSync…
Wayfinder: Westgate palette re-tune and game-site structure
depot: replace
--target local with --out DIR, matching crucible nwsync
Wire the consumer repos to the settled crucible nwsync interface
Where the nwsync verbs live in the command surface
Where the nwsync verbs live in the command surface
The surface, as it will read in
Resolution
nwsync is its own builder group with its own binary, crucible-nwsync, holding both verbs.
The surface, as it will read in docs/command-surface.md
Where the per-artifact NSYM lives, now that topdata is not a hak
Where the per-artifact NSYM lives, now that topdata is not a hak
Resolved: the NSYM is a sibling of its artifact, and
Resolved: the NSYM is a sibling of its artifact, and emit derives its key
Settled with the four sub-questions taken in order. The short version: `artifacts//sha256///.ns…
Five restype numbers in internal/erf disagree with upstream
A module release does not record which topdata it shipped against
The emit upload path and NWCompressedBuffer round-trip
Inherited from #55 and #57 — settled, build against these
#55 (Bunny API) and #57 (restypes) both landed and pushed work into this ticket rather than leaving it open. Folding it in here so it…
Where the per-artifact NSYM lives, now that topdata is not a hak
Bunny zone: how a blob is uploaded and how existence is checked without mounting
Bunny zone: how a blob is uploaded and how existence is checked without mounting
Resolved: probe per object, and extend
Resolved: probe per object, and extend internal/depot's backend rather than writing a new client
The API
Flat REST filesystem: `PUT
Restype resolution for emit: what Crucible has, what upstream's table says
Restype resolution for emit: what Crucible has, what upstream's table says
Resolved: no new table needed, but lowercase the resref and mirror upstream's table
emit needs no new restype table. Crucible already has exactly one, and erf.Read already keeps the…
Does sow-module CI know the full artifact set at release time?
Resolved: yes for haks, a small closeable gap for topdata
sow-platform#94's claim that only the channel resolver knows the…
Does sow-module CI know the full artifact set at release time?
The emit upload path and NWCompressedBuffer round-trip
Bunny write credential for sow-module CI