v0.3.4

Fix nil-map panic in S3 client discovered during dogfooding

Summary

Patch release fixing a runtime panic when writing artifact chunks through the S3 storage backend. The NewLodeS3Client constructor failed to initialize internal tracking maps, causing a nil-map assignment panic on the first WriteChunks call. This was discovered during Phase 6 dogfooding with Cloudflare R2.

Highlights

• 🐛 Fix: NewLodeS3Client now correctly initializes offsets and chunksSeen maps — artifact streaming to S3/R2 works end-to-end
• ♻️ Refactor: Extracted shared newClient() constructor helper — all client constructors (FS, factory, S3) share a single initialization path, preventing future drift
• ✅ Test: Added TestNewClient_InitializesMaps regression test that guards against nil-map constructor bugs
• All existing tests continue to pass (Go + 172 SDK + 109 executor-node)

Upgrade Notes

• This is a patch release with no breaking changes
• Recommended for all users of --storage-backend s3 (the FS backend was unaffected)
• Drop-in replacement for v0.3.3

Full Changelog: v0.3.3...v0.3.4

What's Changed

• fix(lode): 🐛 initialize artifact maps in S3 client constructor by @justapithecus in #92
• chore(release): 🔖 prepare v0.3.4 release by @justapithecus in #93

Full Changelog: v0.3.3...v0.3.4