@quatronic/qore 0.1.8 → 0.1.10-test.0da2f9c

package/README.md

@@ -23,6 +23,9 @@ qore version            # CLI + portal version info
 
 qore env pull           # write this module's local secrets into an env file
 qore run -- <command>   # run a command with those secrets in its environment
+qore roles list         # roles in your code, on local, and yours there
+qore roles sync         # announce your code's roles for local, keep yours
+qore roles use <role…>  # announce your code's roles for local and take these
 
 qore errors --env stag                              # recent unresolved errors
 qore errors FRONTEND-1A --env prod --with trace,logs  # one error, its trace and logs
@@ -145,6 +148,19 @@ not in the interactive conflict prompt, not in `--verbose` logs, and not in
 the portal's own audit trail, which records key names only (see
 `app.local_env.fetched`).
 
+#### `qore roles`
+
+Run in the app's frontend module. `qore roles sync` does the announcing alone:
+local learns every role in `permissions.ts` and your own roles stay as they are.
+`qore roles use inspector` reads the roles in
+`src/lib/permissions.ts`, tells the portal they exist on `local` (only there —
+staging and production learn roles from the code that environment deploys:
+`main` for staging, the `production` branch for production), and makes exactly
+the named roles yours on `local`. Sign out and back in to the local app
+afterwards. `qore roles list` shows the roles in your code, the ones `local`
+knows, and yours. Needs write on the module, like `qore env pull`. An announced
+role stays on `local`; nothing removes it automatically.
+
 #### `qore run`
 
 Runs a command with this module's local secrets injected into its