Okay.. My reasons are that webinos_config.json is handy while running grunt and also while building for Android. So after running grunt you will have webinos version available in webinos_config. I could have either update webinos_config or package.json. I choosed webinos_config.json because I also felt in forum, webinos_config.json should be updated anytime by the user. I also scan for port changes in webinos_config. 

Problem is that parameters in webinos_config cannot be provided via web interface as they are required before starting PZP, So expecting user to change value in .webinos folder looks bit tedious for the developer. 

My implementation prints version as such tag.num-commits(commit id) ex: v0.8.0.15(bbd3d04). This will be different from what information is available in package.json and might not be that useful (I used as a fall off when information is not available in webinos_config.json on package.json value). Advantage of above version is that people can use this while reporting issue and also I plan to use it for WP-730 where webinos version will be checked and webinos_config will have another flag to recreate .webinos folder if configuration has changed. As previously it has turned out people have found it tough when to delete webinos folder. I am going to control it via this version field.