Submain sits 12 commits ahead of main, ready for a merge that's been "most likely next" in every daily log for days. If you want to catch a project in a moment of tension, there's no better time. No commits added recently, but in the quiet lies the pushback of a pending decision.
Current State
Main holds strong at 380 passes and zero fails—a pristine test matrix. On its tail, submain checks in at 345 passes, zero fails, but with 51 skips across 396 test fixtures. Despite the skips, nothing's broken. As far as v0.3.2 goes, we're stable post-release after adding gene/phen support, operator overloading, and fixing the struct-return ABI. Not a single regression logged.
The Submain Situation
Let's talk about submain’s restless state, dangling those 12 commits. The work includes some key technical progress like exit and const lowering, a crucial parser guard fix, and a README accuracy pass. Moreover, there's a comprehensive audit pushing the C1-C4 enforcement layer to completion. We've got no visible merge conflicts. All that's missing is a green light for integration—tests are passing, the diff is clean, and yet, the commits remain stranded. Not a blocker in sight, just an unturned page in this project’s log.
