@myelinbridge/cli 0.6.0 → 0.6.1

package/README.md

@@ -53,9 +53,10 @@ Two kinds of key exist, and they are not interchangeable. Everything above needs
 question your own systems ask once the data has landed: *the bucket is full of UUIDs —
 what is this?*
 
-By default a client key is **organisation-wide**: one key, every partner, one answer. Your
-organisation admin creates it in **Organisation → API keys**. If your governance is per-partner,
-a bridge owner can create a bridge-scoped one instead in **Bridge → API → "Your read keys"**.
+Where they live follows from what they are. A **partner key belongs to one bridge**, because a
+partner does. A **client key belongs to your organisation**: one key, every partner, one answer.
+Your organisation admin creates it in **Organisation → API keys**. To narrow one to a single
+partner's data, scope it to that partner's projects.
 
 ```bash
 export MYELIN_API_KEY=myl_live_…

package/bin/myelin.js

@@ -521,7 +521,7 @@ Commands:
   status <batch|name> [--watch]           review status + fix-loop findings
   sandbox <file>                          partner-side test transfer (bridge activation)
 
-Client-side commands (need a CLIENT key — Bridge → API → "Your read keys"):
+Client-side commands (need a CLIENT key — Organisation → API keys):
   deliveries [--project <id>]             what landed in your destination bucket
              [--dataset <id>] [--since <iso>] [--limit <n>]
   resolve <path|prefix|id>                what a path in your bucket actually is —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@myelinbridge/cli",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "Myelin Partner Ingestion CLI — push R&D data deliveries from a pipeline: preflight against the client's quality rules, resumable upload, submit, track review outcomes.",
   "type": "module",
   "bin": {