Release Readiness and Test Gate
This page exists to keep the public docs honest.
6.0 is internal development, not production-ready.
What is green today
This audit verified the C# build lane:
That command is the only currently verified green lane from this docs pass.
What the workflow suite is intended to prove
The focused workflow coverage suite is still the right target for proving:
- placement start, validation, and execution
- occupancy updates after placement
- move preview updates
- rotate and flip during manipulation
- confirm-move finalization
- demolition and cleanup behavior
What is still blocked
The focused workflow coverage suite is currently broken on the audited branch.
The current failures include drift around legacy API signatures, so it should not be described as green until those tests pass again.
The historical all-in-one core test project is also still broken.
That is a major reason the public docs should not describe 6.0 as fully production-ready yet.
Public documentation rule
If a page claims that 6.0 is stable, scalable, or ready for broad use, it should be able to point back to:
- the currently green C# build command
- the current workflow coverage status
If a claim cannot be supported by those sources, it should be softened or removed.
Recommended release gate for docs consumers
Before you trust a 6.0 integration slice, do at least this:
- build the C# runtime lane
- run the workflow coverage test lane and treat failures as release blockers
- review the current release-readiness guide for current blockers
That is the minimal honest gate the public docs can support right now. Today, only the C# build lane is verified green from this audit.