The zarf collection was removed, and where it went

ansible/colonel_byte/zarf, internal/zarfmod, cmd/zarf/ and test/e2e/zarf used to live here. They were a proof of ZEP-0072, which proposes native Ansible module support for zarf, and they were built in this repository because the pattern the proposal describes is the one colonel_byte.cargoship already runs – see choice-ansible-module – so the cheapest place to find out whether the pattern held for zarf was beside the implementation it copies. That reason expired when the proof outgrew being a guest here. It now lives in colonel-byte/ansible-collection-zarf, which released v0.87.0 carrying the same signed collection tarball, module binaries and Linux packages that cargoship’s release used to, and the copy here was deleted in #822 rather than maintained as a second, worse one.

This file is kept, at the name the removal plan had, for two reasons. The page was published, so the name is a URL somebody may still hold; and a reader who finds zarf all over go.mod, pkg/action and pkg/coci and no zarf collection should not have to work out whether something was lost. Nothing was: cargoship depends on zarf-dev/zarf as a library, for package formats, architecture detection and OCI handling, and has since long before the collection existed. go mod tidy was run on the removal and changed nothing. The collection was never reachable from any cargoship code path – nothing outside internal/zarfmod and cmd/zarf/ imported it, and the cargoship collection never referred to it – which is what made it safe to remove on short notice.

The decision records that explained the proof went with it: choice-zarf-ansible-module, on why the modules are wrapper binaries rather than zarf itself and what that costs, and choice-zarf-info-modules, on why the read-only modules are plain action plugins and why zarf_state_info withholds credentials by default.