@hyperscale0/cli 1.0.440 → 1.0.442
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.
- package/LICENSE.md +5 -2
- package/README.md +20 -0
- package/hyperscale.js +456 -248
- package/package.json +2 -2
package/LICENSE.md
CHANGED
|
@@ -7,6 +7,9 @@ terms on which Hyperscale makes the Software available.
|
|
|
7
7
|
Revised 30 October 2026: product names aligned with the Hyperscale family;
|
|
8
8
|
obligations unchanged.
|
|
9
9
|
|
|
10
|
+
Revised 2 November 2026: Verify renamed Hyperscale Assure; obligations
|
|
11
|
+
unchanged.
|
|
12
|
+
|
|
10
13
|
SPDX identifier: `LicenseRef-Hyperscale-IPCL-1.0`
|
|
11
14
|
|
|
12
15
|
Copyright (c) 2026 Hyperscale LLC. All rights reserved.
|
|
@@ -44,7 +47,7 @@ documentation and published example inputs and outputs.
|
|
|
44
47
|
|
|
45
48
|
"Services" means the products and services Hyperscale offers or operates, in
|
|
46
49
|
any form and under any name, including Hyperscale Arc, Hyperscale Design,
|
|
47
|
-
Hyperscale
|
|
50
|
+
Hyperscale Assure, Hyperscale Launch, Hyperscale Connect, Hyperscale
|
|
48
51
|
Enterprise, the Architect, the console, registries, hosted compilers, hosted
|
|
49
52
|
MCP servers, generated SDKs, and every successor product.
|
|
50
53
|
|
|
@@ -79,7 +82,7 @@ it "not a contribution".
|
|
|
79
82
|
|
|
80
83
|
"Marks" means the names, logos, and trade dress of Hyperscale and its products,
|
|
81
84
|
including "Hyperscale", "Hyperscale Arc", "Hyperscale Design", "Hyperscale
|
|
82
|
-
|
|
85
|
+
Assure", "Hyperscale Launch", "Hyperscale Connect", "Hyperscale Enterprise",
|
|
83
86
|
"HSX", "UDL", "ADL", "Architect", the `hyperscale0` GitHub organisation, the
|
|
84
87
|
`@hyperscale0` npm scope, and every confusingly similar name or sign.
|
|
85
88
|
|
package/README.md
CHANGED
|
@@ -113,6 +113,26 @@ A scenario is the same story as a file. It stops at the first step that fails:
|
|
|
113
113
|
|
|
114
114
|
`hyperscale scenario init` writes one that fits your Product.
|
|
115
115
|
|
|
116
|
+
A bank's QA keeps a folder of scenarios beside the Core and runs it with
|
|
117
|
+
`hyperscale scenario run assure/ --rehearsal --json`. Each file runs on a
|
|
118
|
+
fresh rehearsal copy of the Product, every step gets a verdict, and the run
|
|
119
|
+
exits 1 when any step failed. Suites run in sandbox only; live is refused with
|
|
120
|
+
`assure_live_refused`. Three more fields serve them:
|
|
121
|
+
|
|
122
|
+
| Field | Does |
|
|
123
|
+
| ---------- | ----------------------------------------------------------------------------------------------------- |
|
|
124
|
+
| `staff` | Names sandbox team members by staff role; each one's token comes from `HYPERSCALE_STAFF_<NAME>` |
|
|
125
|
+
| `refused` | `"status 403 \"missing_required_permission\""` on a step passes only on that refusal |
|
|
126
|
+
| `approval` | A run that waits for approval keeps it by name; `{ "approve": "<name>", "by": "<staff>" }` decides it |
|
|
127
|
+
|
|
128
|
+
An approver also needs `HYPERSCALE_STAFF_<NAME>_PASSWORD`. The report is kept
|
|
129
|
+
on the Product; a report Arc does not keep exits 1 with
|
|
130
|
+
`assure_report_not_stored`. `hyperscale core evidence <core-id> --out
|
|
131
|
+
evidence/` exports it with the Core's documents, certificate, checks, plan
|
|
132
|
+
and audit events, and needs `audit:read`. `hyperscale core certificate <core-id> --verify` checks the signed
|
|
133
|
+
certificate against your installation's `/release.json`
|
|
134
|
+
([docs/public/assure.md](../../docs/public/assure.md)).
|
|
135
|
+
|
|
116
136
|
## Watch and debug
|
|
117
137
|
|
|
118
138
|
| Command | Shows |
|