@mesh-tech/mesh-cli 0.20.0 → 0.20.2

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 (49) hide show
  1. package/README.md +13 -8
  2. package/dist/bin/mesh.js +272 -52
  3. package/dist/bin/mesh.js.map +4 -4
  4. package/dist/build-info.json +2 -2
  5. package/dist/src/commands/app-check.d.ts +1 -1
  6. package/dist/src/commands/app-check.d.ts.map +1 -1
  7. package/dist/src/commands/app-check.js +13 -0
  8. package/dist/src/commands/app-check.js.map +1 -1
  9. package/dist/src/commands/create-app.d.ts +14 -0
  10. package/dist/src/commands/create-app.d.ts.map +1 -1
  11. package/dist/src/commands/create-app.js +25 -2
  12. package/dist/src/commands/create-app.js.map +1 -1
  13. package/dist/src/commands/init/wizard.d.ts +21 -4
  14. package/dist/src/commands/init/wizard.d.ts.map +1 -1
  15. package/dist/src/commands/init/wizard.js +51 -10
  16. package/dist/src/commands/init/wizard.js.map +1 -1
  17. package/dist/src/commands/local/hub-local.d.ts +35 -0
  18. package/dist/src/commands/local/hub-local.d.ts.map +1 -1
  19. package/dist/src/commands/local/hub-local.js +61 -1
  20. package/dist/src/commands/local/hub-local.js.map +1 -1
  21. package/dist/src/commands/local/index.d.ts.map +1 -1
  22. package/dist/src/commands/local/index.js +15 -1
  23. package/dist/src/commands/local/index.js.map +1 -1
  24. package/dist/src/commands/local/seed-hub-catalog.d.ts +33 -0
  25. package/dist/src/commands/local/seed-hub-catalog.d.ts.map +1 -0
  26. package/dist/src/commands/local/seed-hub-catalog.js +90 -0
  27. package/dist/src/commands/local/seed-hub-catalog.js.map +1 -0
  28. package/dist/src/commands/login.d.ts +12 -0
  29. package/dist/src/commands/login.d.ts.map +1 -1
  30. package/dist/src/commands/login.js +52 -7
  31. package/dist/src/commands/login.js.map +1 -1
  32. package/dist/src/commands/registry.d.ts +22 -3
  33. package/dist/src/commands/registry.d.ts.map +1 -1
  34. package/dist/src/commands/registry.js +36 -4
  35. package/dist/src/commands/registry.js.map +1 -1
  36. package/dist/src/commands/temporal.js +20 -6
  37. package/dist/src/commands/temporal.js.map +2 -2
  38. package/dist/src/utils/aws-auth.d.ts +19 -0
  39. package/dist/src/utils/aws-auth.d.ts.map +1 -1
  40. package/dist/src/utils/aws-auth.js +30 -9
  41. package/dist/src/utils/aws-auth.js.map +1 -1
  42. package/dist/src/utils/registry-identity.d.ts +35 -0
  43. package/dist/src/utils/registry-identity.d.ts.map +1 -1
  44. package/dist/src/utils/registry-identity.js +47 -1
  45. package/dist/src/utils/registry-identity.js.map +1 -1
  46. package/package.json +2 -2
  47. package/skills/core/SKILL.md +2 -2
  48. package/templates/api-auth/index.ts.hbs +3 -1
  49. package/templates/api-role-gating/index.ts.hbs +3 -1
package/README.md CHANGED
@@ -64,7 +64,9 @@ trip).
64
64
  **If your account does not hold the grant yet**, the command tells you so and
65
65
  prints the access-request URL the platform returned (or names the admin to
66
66
  ask). Contact your Mesh contact to have **registry access granted to your
67
- user**, then run `mesh registry login` again.
67
+ user**, then run `mesh registry login` again — it re-mints your sign-in so the
68
+ new role is in the token the broker sees. If it still says not authorized,
69
+ start a fresh sign-in: `mesh registry logout && mesh registry login`.
68
70
 
69
71
  Everything after this point — installing `@mesh-tech/*` packages, scaffolding
70
72
  an app, and the local docs server — depends on this step. `mesh init` (next)
@@ -76,11 +78,12 @@ runs it for you.
76
78
  mesh init
77
79
  ```
78
80
 
79
- Run it in your `<tenant>-mesh-apps` clone (an empty one is fine). The wizard
80
- asks which tenant this repo belongs to and where it runs — *local only*
81
- (`mesh start` / `mesh dev`) or *a deployed Mesh platform* — then checks your
82
- registry access (signing you in if step 2 was skipped), bootstraps the repo
83
- layout, installs the agent skills, and prints a summary with the next command.
81
+ Run it in your `<tenant>-mesh-apps` clone, or in a brand-new empty folder — the
82
+ wizard runs `git init` there for you. It asks which tenant this repo belongs to
83
+ and where it runs — *local only* (`mesh start` / `mesh dev`) or *a deployed Mesh
84
+ platform* — then checks your registry access (signing you in if step 2 was
85
+ skipped), bootstraps the repo layout, installs the agent skills, and prints a
86
+ summary with the next command.
84
87
  Every answer has a flag, so a headless run is one line:
85
88
 
86
89
  ```bash
@@ -241,8 +244,10 @@ everywhere else.
241
244
 
242
245
  Your account and session are fine; you don't hold the registry grant yet. The
243
246
  message names the request URL (or the admin to ask) — see
244
- [step 2](#2-get-registry-access). Once granted, `mesh registry login` again;
245
- your sign-in is kept.
247
+ [step 2](#2-get-registry-access). Once granted, `mesh registry login` again —
248
+ it re-mints your sign-in so the new role reaches the broker (a role only rides
249
+ in tokens issued after it was granted). Still refused?
250
+ `mesh registry logout && mesh registry login` starts a fresh sign-in.
246
251
 
247
252
  ### `No registry access on this machine — @mesh-tech packages cannot be installed.`
248
253