Baking System is not reliable to bake client/server entity

[whole pelican]

Sometimes I found that Baking System will fail to bake client/server entity which is super annoying that the baking system failed to detect client/server entity from baker authoring that is bake as client/server entity. It seems like Baking System is not battle tested for serious production dots netcode project. Will official address this issue soon so it will guarantee it will always working properly?

I see there's effort working on new global entities store. Will this improvement going to address Baking System issue?
We're working on a new global entities store. Previously, entities were allocated per world and it was often confusing to determine which world an entity belonged to. Entities will be allocated globally so their values are unique when created in different worlds. When debugging, there’s no ambiguity anymore about which world an entity belongs to and this ensures that the data displayed by debug watches is always reliable.

[heavy lake]

There was many issue with the baker that we fixed and tested. In many cases it was due to the fact changing the Entitis/Build settings were not detected correctly by the asset post-processor.
I'm not aware of any issue in that regards in 1.1 onward

[whole pelican]

🤔 Currently I'm using latest 1.1.0-pre.3 still have this issue. It's really weird that when it's not working at authoring baker A but it's working at authoring baker B which is unpredictable. From what I found it's always working properly if u bake usual entity that has the same component at both client and server side but it will have high chance not working properly when u try to bake component only at client or server and then baking system sometime will fail to detect it

[heavy lake]

Ok, so let's clarify:
How do you setup these? Using the [GhostComponentAttribute] or checking the NetcodeVersionTarget?
Also, how the Entities/Build setting are setup?
Because this latter one is what govern most of the things.
Askiing because it is legit to have the component baked in the entity and then stripped at runtime in many cases.