iii turns backends into observable workers

Hot take: this is less “yet another framework” and more an attempt to standardize the runtime layer underneath modern backend systems.

• –The three-primitives model, `worker / function / trigger`, is the real product; everything else hangs off that abstraction.
• –Strong fit for teams that want agents, queues, cron, and service orchestration to behave like one system instead of separate integrations.
• –The promise is compelling, but adoption will hinge on whether the runtime stays simple enough to replace existing glue without adding a new one.
• –The open-source angle matters: if the ecosystem around workers, SDKs, and observability is solid, this could become infrastructure rather than just a framework.