gigabuddy 0.1.0 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +5 -3
  2. package/bin/cli.js +14113 -86
  3. package/index.js +14100 -72
  4. package/package.json +1 -1
  5. package/src/lib/doctor.d.ts +5 -0
package/README.md CHANGED
@@ -26,9 +26,11 @@ separately, so a staging login never becomes your production one.
26
26
 
27
27
  ## What lands on disk
28
28
 
29
- `login` stores a **refresh token** in `~/.gigabuddy/credentials.json` (0600).
30
- Platform tokens are minted from it on demand and live an hour, so nothing
31
- long-lived and fully-authoritative sits on your filesystem.
29
+ `login` stores a **refresh token** in `~/.gigabuddy/user-credentials.json`
30
+ (0600). Platform tokens are minted from it on demand and live an hour. The
31
+ session behind it is deliberately narrow — it identifies you, lets you see what
32
+ you can reach, install from the Gigabuddy registry, and run agents you sponsor;
33
+ it is not your full account authority.
32
34
 
33
35
  `login --npm` adds two lines to `~/.npmrc` (0600), leaving everything else in
34
36
  that file exactly where it was: