4 Commits

Include renames

Author	SHA1	Message	Date
archvillainetteandClaude Opus 5	f3ca6be698	feat(ci): prune release assets outside the newest two tags (#52) ... Gitea has no release-asset retention, so every v* tag kept its full cross-platform binary set forever — 31 tags had accumulated 1.8 GB on the production host disk. Nothing consumes an old asset: CI takes the Crucible binary from the Nix flake, and every deleted file is reproducible from its tag. scripts/prune-release-assets.sh lists every release page, sorts by creation date, skips the newest two published releases, and deletes the remaining releases' attachments. Two rather than one so a release in flight never leaves the previous download broken. Drafts never consume a keep slot. Releases, tags, source archives and release notes are untouched. Nothing is excluded — SHA256SUMS and the wrappers go with the binaries: the checksums are only meaningful next to the files they cover, and the consumer drift-check reads the wrappers from the latest release, which stays complete. The step is best-effort: a stale asset is cheaper than a blocked publish, so API failures warn and the step carries continue-on-error. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-29 09:51:10 +02:00
archvillainette	b058846e16	chore(ci): consolidate Gitea CI (#47) ... ## Summary - consolidate vet, tests, lint, smoke, and cross-build into one pull-request-only job - keep binary releases strictly v-tag-only with release-only write permission - retain wrapper synchronization only for canonical wrapper changes on main - pin actions and enforce exact trigger contracts ## Verification - nix develop --command make check - trigger mutation contract - 28-workflow cross-repository actionlint audit Generated with Claude CodeReviewed-on: #47 Co-authored-by: vickydotbat <vickydotbat@tutamail.com>	2026-07-22 16:54:26 +00:00
archvillainette	43fe5e0373	Retire the Crucible container image (#41) ... ## Summary The `registry.westgate.pw/deployment/crucible` image has no consumer: `prod.yml` no longer reserves a slot for it (contract settled in sow-platform PR #64) and no runtime or recovery path pulls it. Binaries, wrappers, and the Nix input remain the supported ways to run Crucible. ## What changed - Deleted `.gitea/workflows/build-image.yml`, `publish-image.yml`, `test-image.yml` - Deleted `docker/Dockerfile` and the `make image` target - Updated README, AGENTS.md, and `docs/consumer-contract.md` to state the image is retired Existing `deployment/crucible` images in the registry can be deleted at leisure; nothing references them. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: #41 Co-authored-by: vickydotbat <vickydotbat@tutamail.com> Co-committed-by: vickydotbat <vickydotbat@tutamail.com>	2026-07-17 07:26:58 +00:00
archvillainette	97f8427c4b	Phase 5: scaffold Crucible (sow-tools) — dispatcher + builder shims, container, PR-first CI, fail-closed (D11, D19).	2026-06-11 20:36:13 +02:00