tl;dr: if stw-cgi/video.cgi is still working for you and you don’t want to lose it - do not upgrade your camera. I’ve checked SNH-P6410BN only, but most likely other models will follow that path very soon.
I’ve checked their most recent firmware - 1.07. Unfortunately, they have removed all of the www access to the camera. However, the firmware still has the files, but it’s not available via www. lighttpd is pointed to www/htdocs, but htdocs is symlinked to htdocs_weboff. There is also additional htdocs_webon folder with all of the content and pages that we are familiar with from previous versions, but it’s not accessible via web.
There is one mysterious url/file that I’m inspecting: www/kxmzoa11/xpzmdnls09woskxm20/dnpqtjqltm . Looks like random set of strings, so I’m curious what they are trying to hide. 
It may be just upnp client that camera listens on, but it’s not a standard one as far as I can see. For example, it has SetWebServiceMode method/variable that potentially produces “======== Change Webservice Mode %d, %s ========” output. It’s possible this is used by developers to debug and switch back to the htdocs_webon folder, but actual probability of it is very low.
Here are all of the available urls as of now if you want to play with it (version: 1.07_151030).
note: default username and password is: admin/4321
http://{put_your_camera_IP_here}/device/network/aplist
http://{put_your_camera_IP_here}/information
http://{put_your_camera_IP_here}/device/network
… and SmarTthings RESTful api endpoints …
http://{put_your_camera_IP_here}/stw-cgi-rest/system/deviceinfo
http://{put_your_camera_IP_here}/stw-cgi-rest/system/date
http://{put_your_camera_IP_here}/stw-cgi-rest/system/date/timezonelist
http://{put_your_camera_IP_here}/stw-cgi-rest/system/factoryreset
http://{put_your_camera_IP_here}/stw-cgi-rest/system/power
http://{put_your_camera_IP_here}/stw-cgi-rest/system/firmwareupdate
http://{put_your_camera_IP_here}/stw-cgi-rest/network/interface
http://{put_your_camera_IP_here}/stw-cgi-rest/network/wifi
http://{put_your_camera_IP_here}/stw-cgi-rest/network/wifi/scan
http://{put_your_camera_IP_here}/stw-cgi-rest/network/wifi/connect
http://{put_your_camera_IP_here}/stw-cgi-rest/security/users
http://{put_your_camera_IP_here}/stw-cgi-rest/security/ssl
http://{put_your_camera_IP_here}/stw-cgi-rest/transfer/smtp
http://{put_your_camera_IP_here}/stw-cgi-rest/transfer/subscription
http://{put_your_camera_IP_here}/stw-cgi-rest/eventsources/videoanalysis
http://{put_your_camera_IP_here}/stw-cgi-rest/eventsources/audiodetection
http://{put_your_camera_IP_here}/stw-cgi-rest/image/camera
http://{put_your_camera_IP_here}/stw-cgi-rest/image/imageenhancements
http://{put_your_camera_IP_here}/stw-cgi-rest/image/flip
http://{put_your_camera_IP_here}/stw-cgi-rest/image/overlay
http://{put_your_camera_IP_here}/stw-cgi-rest/io/otheroutputs
http://{put_your_camera_IP_here}/stw-cgi-rest/io/lullaby
http://{put_your_camera_IP_here}/stw-cgi-rest/media/audioinput
http://{put_your_camera_IP_here}/stw-cgi-rest/media/audiooutput
In short: if stw-cgi/video.cgi is still working for you and you don’t want to lose it - do not upgrade your camera. I hope they will revert this change as a lot of users are already complaining giving pretty negative comments at amazon for this camera.
Another option would be to build a custom firmware for this thing. I know how to do it, just don’t have enough time as of now.