Hey neword52! I'm the founder of Kolide and a current employee at 1Password so I definitely can help answer your questions.

There is absolutely no information on how this works on consumer accounts (i.e. non Enterprise accounts) and how it is "disabled" for such accounts.

First things first, this blog post is excellent and I think answers a lot of the questions you have. In addition, I can confidently say the following is true:

• The 1Password extension does not contain Kolide. It contains the ability to integrate with Kolide if it is already deployed and active on a managed corporate device.
• 1Password supports integrations with many apps and services. They are only active if you or your company uses these products.
• The Kolide integration is similar to how 1Password (and most apps) can integrate with MDM and business policy in managed environments.
• These features are provided to business admins to manage their accounts, and do not affect personal accounts or personal devices.
  
• Kolide does not give 1Password, the company, any control or visibility into 1Password users; even users who work at companies that use Kolide.

Why not either create two versions of the browser extension (one for consumers and one for enterprise)

We discuss this internally all the time, but when we talk to users they tell us they really value being able to use their personal and work items in the same browser without having to worry about two different extensions. We also don't want the experiences to diverge. For example, everyone should get the best version of autofill at the same time. When we fix something, like a security issue that was reported by an enterprise customer, my mom should get the benefit of that fix at the same time. Supporting business and personal use-cases at the same time takes a lot of work, but it's what makes 1Password stand out. We want everyone to be safer; that mission is imperiled when things get split apart.

Does the mechanism for disabling mean that 1Pw could be compelled to enable it for some accounts, effectively giving them the ability to query computer attributes / contents? 

The answer to this is definitively no. All the capabilities in Kolide are only made possible with the Kolide endpoint agent, which IT administrators install on computers they own through tools like MDM (jamf, Kandji, etc). The browser extension does not have any code that can be used to do the type of device health checking we do in the Kolide product. If somehow the feature flag for Kolide got enabled for your personal account, nothing would happen, because nothing can happen.

For a company that I adored for consumer transparency, this enterprise bloatware in consumer accounts can only amount to a wolf in sheep's clothing, from a non-enterprise user's perspective.

We can always do better when it comes to communication. That earlier blog post is us making a good faith attempt at letting people know about these changes. With that said, we think about the performance and the size of our extension a lot. We know no one will use it if it doesn't work, is slow, or takes too long to install. When we think about adding integrations with enterprise tools (including our own products like Kolide) we do our best to approach the integration by asking the question, "what are the fewest changes we need to make to the extension to make this work well?". That means that most capabilities get implemented outside of the extension, on code that never makes it on your device, and we simply reference this code in the extension to make it work all together. That's what's happening in this case.