@thermai/flightdeck-cli 0.1.0-pilot.5 → 0.1.0-pilot.7

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 (3) hide show
  1. package/README.md +83 -17
  2. package/dist/index.js +1802 -45
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -15,8 +15,8 @@ versioned GitHub Release workflow, not merely by merging a version change. The
15
15
  installation command below follows the published `next` channel without
16
16
  tracking an unpublished candidate version.
17
17
  Proprietary terms in `LICENSE` permit redistribution of unchanged official
18
- releases. Internal service qualification is still in progress; package
19
- availability does not open partner onboarding.
18
+ releases. Service access still requires an invitation, configured credits and
19
+ the agreed pilot limits; installing the package alone does not grant access.
20
20
 
21
21
  **`0.1.0-pilot.3`** was published through GitHub Actions on 8 September 2026,
22
22
  including complete log pagination and concise authentication errors. Its
@@ -30,13 +30,33 @@ backend is rejected before job submission; login and credential revocation do no
30
30
  the accounting contract. See the
31
31
  [operator rollout checklist](../docs/runbooks/customer-credits-rollout.md).
32
32
 
33
- **Candidate `0.1.0-pilot.5`** fixes result downloads redirected to signed object
33
+ **`0.1.0-pilot.5`**, published on 21 September 2026, fixes result downloads redirected to signed object
34
34
  storage ([#157](https://github.com/ThermAI-Group/thermai_flightdeck/issues/157))
35
35
  and includes the merged GPU-recovery status display. Downloads validate the
36
36
  accounting contract on Flightdeck's response, then fetch the authorized storage
37
- object without forwarding the CLI credential. This candidate is not published
38
- by merging; an approved versioned GitHub Release is still required. Until that
39
- release is verified, the published pilot.4 download regression remains open.
37
+ object without forwarding the CLI credential. Anonymous Node 22 installation
38
+ and a live result download passed. Upgrade from
39
+ pilot.4 before downloading results. Future releases still require an approved
40
+ versioned GitHub Release; merging alone does not publish.
41
+
42
+ **`0.1.0-pilot.6`**, published on 21 September 2026, adds
43
+ offline-first logout and explicit suspension messages. Release CI, registry
44
+ integrity and anonymous Node 22 installation passed; grouped live acceptance
45
+ was confirmed by the operator on 24 September. These are historical pilot.6
46
+ results, not pilot.7 publication evidence. This update does not modify the
47
+ README inside the already-published immutable tarball.
48
+
49
+ **`0.1.0-pilot.7`** adds the read-only `flightdeck atc` terminal view (alias
50
+ `tui`), flight details/events/logs, name filtering and local sbatch-array tracking
51
+ from [PR #206](https://github.com/ThermAI-Group/thermai_flightdeck/pull/206).
52
+ It requires no backend refresh or new runtime dependencies. Publication still
53
+ requires the approved `cli-v0.1.0-pilot.7` GitHub prerelease and successful release
54
+ workflow; a version bump or merge alone does not publish. After publication, use
55
+ the generated `@next` command below, or pin `@thermai/flightdeck-cli@0.1.0-pilot.7`
56
+ for a reproducible pilot install. Confirm `flightdeck --version` reports
57
+ `0.1.0-pilot.7`. Existing saved credentials remain usable; no logout is required
58
+ just to upgrade. Downloads/cancellation inside ATC remain deferred to #205;
59
+ stale fallback-status indication is tracked in #207.
40
60
 
41
61
  Members and organization administrators receive whole-credit balances,
42
62
  estimates and actual customer charges, without provider-cost information.
@@ -73,15 +93,25 @@ test environment can be selected with `flightdeck login --api-url <HTTPS origin>
73
93
 
74
94
  Login saves a scoped credential in `~/.flightdeck/config.json` with restrictive
75
95
  permissions. Never share that file or include it in a workload bundle. Use
76
- `flightdeck logout` to revoke the credential and remove the local login. Portal
77
- credential management can revoke an individual workstation as well.
96
+ `flightdeck logout` to remove the local login and attempt server revocation.
97
+ Portal credential management can revoke an individual workstation as well.
78
98
 
79
99
  `--name` labels a credential, not a local account profile. There is one saved
80
100
  login per OS user. If already logged in, use `whoami` to inspect it; `login`
81
101
  refuses to replace it. Use a separate OS user to preserve an operator's working
82
102
  credential, or explicitly choose logout/re-login on the same workstation.
83
- Logging out revokes that saved CLI credential; it does not delete the account or
84
- its roles. A later login creates a new credential.
103
+ Logging out removes the saved credential; it does not delete the account or its
104
+ roles. A later login creates a new credential. Check the separate revocation
105
+ result: other copies may remain valid if server revocation was not confirmed.
106
+
107
+ Pilot.6 explains `account_suspended`, `membership_suspended`
108
+ and `organization_suspended` denials during device login and authenticated
109
+ commands. Contact your organization administrator; organization suspension may
110
+ need ThermAI support. These are access restrictions, not a missing local login
111
+ or a request for additional credential scopes. Other 403 responses retain
112
+ generic permissions guidance. Commands still exit nonzero and do not print
113
+ server-supplied messages or stack traces. Older pilot.5 installations need an
114
+ explicit upgrade to receive these messages.
85
115
 
86
116
  ## Pilot quick-start
87
117
 
@@ -89,7 +119,7 @@ Before live use, your ThermAI operator must provision your organization/account,
89
119
  provide a single-use portal invitation, and approve your policy and credit.
90
120
  Activate through the portal, then follow the installation/login commands above.
91
121
  Confirm the expected account with `whoami` and the available credit with
92
- `balance`. The internal proving run comes before partner invitations.
122
+ `balance`. ThermAI will guide the first partner submission under the agreed limits.
93
123
 
94
124
  For a **local-only** readiness check, save the following as `readiness.sbatch`
95
125
  in a new empty directory. Run the dry run from that directory; no account,
@@ -127,7 +157,7 @@ the current directory. Never include credentials or private workstation files.
127
157
 
128
158
  ## Workload commands
129
159
 
130
- After internal qualification and explicit policy/credit approval:
160
+ After your account's policy/credit setup and agreed first-run approval:
131
161
 
132
162
  ```sh
133
163
  flightdeck sbatch workload.sbatch
@@ -144,7 +174,8 @@ supports a subset of single-node Slurm directives, not an arbitrary HPC cluster.
144
174
  Workload images must satisfy the Flightdeck runner contract.
145
175
 
146
176
  An array prints a separate Flightdeck ID for each accepted task. Record them
147
- all: inspect, download and cancel each flight individually. Partial submission
177
+ all: inspect, download and cancel each flight individually (`flightdeck atc
178
+ <job-id>` shows them together). Partial submission
148
179
  can leave accepted flights running even if the command exits unsuccessfully;
149
180
  do not blindly resubmit the whole array. Choose a fresh download directory for
150
181
  each flight: downloads use filename basenames and refuse to overwrite existing
@@ -185,14 +216,49 @@ partial read. Older `0.1.0-pilot.2` installations do not contain this fix;
185
216
  merging source alone neither replaces that immutable package nor publishes a
186
217
  new version. Older non-following clients still need upgrading for full paging.
187
218
 
219
+ ### Watching flights live
220
+
221
+ `flightdeck atc` (alias `flightdeck tui`) opens a read-only, full-screen view in
222
+ the current terminal. Arrow keys select, Enter shows a flight's details and
223
+ events, `l` opens its logs (scroll, `f` to follow), `r` refreshes, Esc goes back
224
+ and `q` quits. It never cancels, submits or downloads anything.
225
+
226
+ ```sh
227
+ flightdeck atc # your recent flights (last 50)
228
+ flightdeck atc <flight-id> # one flight
229
+ flightdeck atc <job-id> # an sbatch array submitted from this machine
230
+ flightdeck atc --name 'molsim*' # flights whose name matches, among your last 200
231
+ flightdeck atc --demo # a simulated array; no account or credits needed
232
+ ```
233
+
234
+ `flightdeck sbatch` records each array's flight IDs under
235
+ `~/.flightdeck/batches/` and ends with `Watch live: flightdeck atc <job-id>`;
236
+ that job ID is the one to pass. The record exists only on the machine that
237
+ submitted it (if it could not be written, sbatch says so; use `--name`). Name
238
+ patterns are case-sensitive. Leaving the view does not stop any job. In
239
+ scripts, keep using `status` and `logs`.
240
+
188
241
  ### Error handling and support
189
242
 
190
243
  The CLI exits with status 1 on command failure. Expected authentication,
191
244
  network and HTTP failures have concise diagnostics instead of a Node stack.
192
- An already-configured login leaves the saved credential unchanged; a failed
193
- logout/revocation retains it so you can retry. `logout --local` deliberately
194
- removes only the local copy and does not revoke remote access; use portal
195
- credential management if remote revocation is needed.
245
+ An already-configured login leaves the saved credential unchanged.
246
+
247
+ **Pilot.6 logout behavior (#143):** remove the local file first, then make
248
+ one best-effort server revocation request with a three-second deadline, including
249
+ the response body. Offline, suspended, failed or malformed API responses cannot
250
+ retain or restore the local login. Local success exits 0; a warning separately
251
+ states when remote revocation was not confirmed and other copies may remain
252
+ valid. Use portal credential management or contact your organization admin.
253
+ Failed local deletion exits 1, reports the problem and makes no API request.
254
+ Missing local login is a successful no-op; malformed config is removed without
255
+ trusting its contents for a request. No credential recovery/retry file is saved.
256
+ `logout --local` removes only the local copy and makes no network request.
257
+
258
+ Older pilot.5 does not include this change; use `flightdeck logout --local`
259
+ as a local-removal workaround before upgrading. It does not revoke remote
260
+ access. The current production backend permits narrowly authenticated
261
+ self-revocation under suspension; ordinary access remains blocked.
196
262
 
197
263
  For unexpected faults, `flightdeck --debug <command>` adds allowlisted error
198
264
  types/codes and bundled CLI line locations, not raw stacks or error bodies.