Guy,
You’re absolutely right — for all intents and purposes the content assist for the different file formats we support are all dynamic, pulled from the build path or meta in the file itself (like in XML). In this particular case it seems to be a bug causing the parser to parse the wrong file for content assist and validation information. That’s the reason for the wait, we need to fix the bug.