I'm quite aware of how version numbers work in software. And you don't release a "1.0" if it has parts of it that literally say "Work in Progress." 1.0 would be a release candidate. If it's still in progress - not "there's a few bugs that slipped through" or "we thought of new features/content to add" - then it's not a release candidate, ergo should not be numbered 1.0.You seem to think that "1.0" means "complete". Sometimes it does, sometimes it doesn't. The versions could go 0.7, 0.8, 0.9, 0.10, 0.11 ... . Or they could go 0.7, 0.8, 0.9, 1.0, 1.1, ...
A 1.1, 1.2, etc. that includes content added on? Sure, makes sense. A 1.0 that releases and asks for money as a "finished product" while still having "work in progress" signs in places? Nope. That isn't how software works, at least not with professional companies. (At least the "AAA" publishers who use the "live service" excuse release something that doesn't tell you it's unfinished. "Road maps" are meant to be additional content, not finishing the intended release version.)
I'd assume that because it actually does say "work in progress" in places, the work is intending to be done. Yes, plans may change. But if so, then I'd expect those things would be removed from the game as a 1.0 release, and then added back in later as a 1.X release once they're in release state.