What happened
Fresh failproofai config (CLI 1.0.4-beta.0, darwin-arm64) fails at the daemon step:
failed to download failproofaid v1.0.4-beta.0 for darwin-arm64: GET .../releases/download/v1.0.4-beta.0/SHA256SUMS returned 404
The tag itself 404s via the releases API. Newer tags (v1.0.4-beta.8, v1.0.5-beta.1) carry failproofaid-darwin-arm64.gz + SHA256SUMS fine — the pin just points at a deleted/never-published tag.
Workaround (verified)
curl -sL -o failproofaid-darwin-arm64.gz https://github.com/FailproofAI/failproofai/releases/download/v1.0.5-beta.1/failproofaid-darwin-arm64.gz
# verify against that tag's SHA256SUMS, gunzip to ~/.failproofai/bin/failproofaid
FAILPROOFAI_DAEMON_BINARY="$HOME/.failproofai/bin/failproofaid" failproofai config
Setup then completes (12 harnesses, daemon live, stay-local).
Suggest
Retag/republish the v1.0.4-beta.0 daemon assets, or float the daemon pin to latest-good instead of CLI-locked.
What happened
Fresh
failproofai config(CLI 1.0.4-beta.0, darwin-arm64) fails at the daemon step:failed to download failproofaid v1.0.4-beta.0 for darwin-arm64: GET .../releases/download/v1.0.4-beta.0/SHA256SUMS returned 404The tag itself 404s via the releases API. Newer tags (v1.0.4-beta.8, v1.0.5-beta.1) carry
failproofaid-darwin-arm64.gz+ SHA256SUMS fine — the pin just points at a deleted/never-published tag.Workaround (verified)
Setup then completes (12 harnesses, daemon live, stay-local).
Suggest
Retag/republish the v1.0.4-beta.0 daemon assets, or float the daemon pin to latest-good instead of CLI-locked.