chore: say teams in the README, and sync the lockfile workspace versions

The README's v1.0.0 priorities listed Credential Sharing as covering
".env, Doppler, Railway variables, and GitHub Secrets" -- the same drift
just fixed on the marketing page in #123. End-to-end-encrypted team
vaults shipped on 2026-07-13 and sh1pt landed as a provider on 07-30,
so the highest-traffic surface in the repo still told readers teams did
not exist.

Separately, packages/cli and plugins/credential-sharing were bumped to
0.1.1 in their package.json without the lockfile following, so it still
recorded 0.1.0 for both. Reconciled with `npm install
--package-lock-only`; the diff is those two version fields and nothing
else. This was cosmetic rather than breaking -- `npm ci` tolerated the
mismatch, which is why CI never caught it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

package-lock.json

@@ -7753,7 +7753,7 @@
     },
     "packages/cli": {
       "name": "@logicsrc/cli",
-      "version": "0.1.0",
+      "version": "0.1.1",
       "dependencies": {
         "@logicsrc/account-core": "file:../account-core",
         "@logicsrc/openontology": "file:../openontology",
@@ -7910,7 +7910,7 @@
     },
     "plugins/credential-sharing": {
       "name": "@logicsrc/plugin-credential-sharing",
-      "version": "0.1.0",
+      "version": "0.1.1",
       "dependencies": {
         "@logicsrc/account-core": "file:../../packages/account-core",
         "@logicsrc/plugin-core": "file:../../packages/plugin-core",