willchen96 quietly unbreaks shared projects and opens the storage backend

Two small compatibility fixes land together - one rescues collaboration, the other frees Mike from being AWS-only.

infrastructureworkflow

The first fix is the kind of bug that doesn't show up in screenshots but quietly ruins a team's day: anyone with a project shared to them was hitting an error when they tried to list their projects. The underlying cause was a mismatch between how the database stores sharing information and how the query was being constructed - close enough to work in testing, wrong enough to fail in production. willchen96 patched both places the broken query lived, so the fix is whole rather than half.

The second change is a single configuration flag that lets Mike's storage layer talk to S3-compatible services that aren't actually AWS - local development tools like MinIO, or any of the other object stores that mimic the S3 protocol. Until now Mike effectively required real AWS; now it doesn't.

So what Anyone evaluating Mike for team use or planning to self-host on non-AWS infrastructure should note this - collaboration now works, and the storage tie to AWS is gone.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?