None of the changes in the SteamVR changelog point to why it could be broken for me now, so I don't think we can infer such things
my point was that its the other way around.
(im basing this on my understanding of your most recent previous posts, clearly i dont know everything you've tried, so i apologise if ive missunderstood and thank you for taking the time to report your experiences!)
my understanding was you tried it with the firmware that came with sample CV1 and run time 1.0 and after some fiddling, Steamvr and ED sort of worked but not very well?
you then patched the firmware and thus had to upgrade to runtime 1.1 and now neither of them work at all?
im not suggesting that the recent change to steamvr have broken it im just saying that it sounded like steamvr wasn't 100% compatible with the original cv1 firmware/runtime you had and is not compatible at all with the updated cv1 firmware/runtime? if this is the case then would that explain why ED is not working? (ie we're in a similar backwards compatibility situation to when they went from runtime 0.5/0.6/0.7?, except this time its new firmware and a new runtime?)
i brought up the recent update just to mention that as we see in the latest release of steamvr updates for improving rift support, they are clearly still working on updates specifically aimed at the rift so it would seem likely that we will see at some point in the future an update to steamvr to include the cv1 release firmware/runtime compatibility? (which i would guess would then leave us in the same place we are with DK2/0.8 at the moment?)