@tokenoftrust/cli 1.0.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.
- package/LICENSE +202 -0
- package/README.md +50 -0
- package/bin/tot.mjs +124 -0
- package/package.json +41 -0
- package/src/auth.mjs +132 -0
- package/src/commands/checkout.mjs +233 -0
- package/src/commands/dev.mjs +564 -0
- package/src/commands/doctor.mjs +172 -0
- package/src/commands/ideas.mjs +45 -0
- package/src/commands/login.mjs +107 -0
- package/src/commands/start.mjs +450 -0
- package/src/commands/submit.mjs +284 -0
- package/src/commands/validate.mjs +99 -0
- package/src/commands/whoami.mjs +69 -0
- package/src/context.mjs +97 -0
- package/src/errors.mjs +64 -0
- package/src/last-tenant.mjs +49 -0
- package/src/mcp.mjs +100 -0
- package/src/oauth.mjs +409 -0
- package/src/open.mjs +63 -0
- package/src/token-store.mjs +65 -0
- package/src/validate.mjs +291 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
# @tokenoftrust/cli — the `tot` developer CLI
|
|
2
|
+
|
|
3
|
+
One command to go from a Token of Trust invite to a running store.
|
|
4
|
+
|
|
5
|
+
```sh
|
|
6
|
+
npm i -g @tokenoftrust/cli
|
|
7
|
+
|
|
8
|
+
tot checkout # list the stores you can build on
|
|
9
|
+
tot checkout <tenant> --clone ./my-store
|
|
10
|
+
cd my-store
|
|
11
|
+
tot dev # run it locally with save→reload — no Docker needed
|
|
12
|
+
tot submit # (coming) submit it for preview
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
**Prerequisites: Node.js and an invite. Nothing else.** `tot dev` downloads the
|
|
16
|
+
moat-free storefront runner and runs it as a plain host process — no Docker
|
|
17
|
+
install, no hand-provisioned AWS credentials. (Docker remains available as a
|
|
18
|
+
fallback — `tot dev --docker` — or automatically if the native artifact can't
|
|
19
|
+
be fetched.)
|
|
20
|
+
|
|
21
|
+
## Commands
|
|
22
|
+
|
|
23
|
+
| Command | Status | What it does |
|
|
24
|
+
| --- | --- | --- |
|
|
25
|
+
| `tot checkout [<tenant>]` | **built** | Clone a store you're entitled to build on, with an authenticated remote configured. No arg → list your stores. |
|
|
26
|
+
| `tot validate` | next | Lint your store before you submit. |
|
|
27
|
+
| `tot dev` | **built** | Run your store locally with save→reload — NATIVELY (no Docker; falls back to it with `--docker` or automatically if the native artifact isn't available). |
|
|
28
|
+
| `tot submit` | next | Submit your store for preview (pushes the preview ref, reports the reconcile/compliance verdict + preview URL). |
|
|
29
|
+
| `tot doctor` | built | Check this machine is ready and show which context `tot` detected. |
|
|
30
|
+
|
|
31
|
+
## Context-aware
|
|
32
|
+
|
|
33
|
+
The same `tot` does the right thing wherever you run it (walks up like `git`):
|
|
34
|
+
|
|
35
|
+
- **storefront monorepo** — a full platform checkout;
|
|
36
|
+
- **tenant checkout** — a standalone `content/ public/ theme.json .tot/config.json` clone (tenant read from `.tot/config.json`);
|
|
37
|
+
- **loose** — anywhere else; `tot checkout <tenant> --clone <dir>` gets you a checkout.
|
|
38
|
+
|
|
39
|
+
`tot doctor` prints the detected context.
|
|
40
|
+
|
|
41
|
+
## Auth
|
|
42
|
+
|
|
43
|
+
`tot` talks to the Token of Trust MCP (default `https://mcp.tokenoftrust.com`, override with `--mcp` or `MCP_BASE_URL`). It authenticates as one of two identities, transparently:
|
|
44
|
+
|
|
45
|
+
- **developer** — you, signed in against the MCP (the real invited-developer path). Depends on entitlement-derived MCP access; until that ships, `tot` reports it clearly and points you at operator creds.
|
|
46
|
+
- **operator** — `TOT_API_KEY` / `TOT_SECRET_KEY` / `TOT_APP_DOMAIN` in the environment (how we dogfood the CLI and how CI exercises it).
|
|
47
|
+
|
|
48
|
+
## Design notes
|
|
49
|
+
|
|
50
|
+
Dependency-free by design (global `fetch` + `git` + the system `tar`), so `npm i -g @tokenoftrust/cli` stays light. `tot dev` is the only command that pulls in the storefront runner: for a standalone checkout it downloads the moat-free runner artifact (`dev_renderer_artifact`, entitlement-gated, same shape as the Docker pull-token path) once per version to `~/.tot/cache/renderer/<version>/`, `pnpm install`s it there (via corepack — no separate pnpm install needed), and reuses that cache on every later run. See `src/` for the small modules: `context.mjs` (detection), `mcp.mjs` (transport), `auth.mjs` (the identity seam), `commands/`.
|
package/bin/tot.mjs
ADDED
|
@@ -0,0 +1,124 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
/**
|
|
3
|
+
* `tot` — the Token of Trust developer CLI.
|
|
4
|
+
*
|
|
5
|
+
* One command a developer learns to go from an invite to a running store:
|
|
6
|
+
*
|
|
7
|
+
* tot start invite → running store in one command ← built (orchestrates the below, value-first)
|
|
8
|
+
* tot login sign in to Token of Trust (OAuth) ← built (MCP OAuth PKCE loopback; caches ~/.tot/credentials.json)
|
|
9
|
+
* tot whoami who you're signed in as ← built
|
|
10
|
+
* tot checkout [<tenant>] clone a store you can build on ← built
|
|
11
|
+
* tot validate lint your store before you submit ← built
|
|
12
|
+
* tot dev run your store locally with save→reload ← built (monorepo: host astro; standalone: runs the published runner image)
|
|
13
|
+
* tot submit submit your store for preview ← built (validate + push preview ref; MCP preview_status read-back)
|
|
14
|
+
* tot doctor check this machine is ready
|
|
15
|
+
* tot ideas copy-paste AI prompts that reliably wow
|
|
16
|
+
* tot help this help
|
|
17
|
+
*
|
|
18
|
+
* Context-aware (see src/context.mjs): the same `tot` does the right thing from
|
|
19
|
+
* inside the storefront monorepo, from inside a standalone tenant checkout, or
|
|
20
|
+
* from anywhere else. Every command receives the detected context.
|
|
21
|
+
*
|
|
22
|
+
* This package is `@tokenoftrust/cli` (bin `tot`). Its heaviest command, `tot dev`,
|
|
23
|
+
* bundles the moat-free storefront runner; `tot checkout/validate/submit` are
|
|
24
|
+
* pure Node. Dependency-free by design so `npm i -g @tokenoftrust/cli` stays light.
|
|
25
|
+
*/
|
|
26
|
+
import { detectContext } from "../src/context.mjs";
|
|
27
|
+
import { printError } from "../src/errors.mjs";
|
|
28
|
+
|
|
29
|
+
const BUILD_ORDER = ["checkout", "validate", "dev", "submit"];
|
|
30
|
+
|
|
31
|
+
function usage() {
|
|
32
|
+
console.log(`
|
|
33
|
+
tot — Token of Trust developer CLI
|
|
34
|
+
|
|
35
|
+
tot start invite → running store in one command (start here)
|
|
36
|
+
tot login sign in to Token of Trust
|
|
37
|
+
tot whoami show who you're signed in as
|
|
38
|
+
tot checkout [<tenant>] clone a store you can build on
|
|
39
|
+
tot validate lint your store before you submit
|
|
40
|
+
tot dev run your store locally with save→reload
|
|
41
|
+
tot submit submit your store for preview
|
|
42
|
+
tot doctor check this machine is ready
|
|
43
|
+
tot ideas copy-paste AI prompts that reliably wow
|
|
44
|
+
tot help show this help
|
|
45
|
+
|
|
46
|
+
Run \`tot <command> --help\` for command-specific options.
|
|
47
|
+
`);
|
|
48
|
+
}
|
|
49
|
+
|
|
50
|
+
async function main() {
|
|
51
|
+
const [cmd, ...rest] = process.argv.slice(2);
|
|
52
|
+
const ctx = detectContext();
|
|
53
|
+
|
|
54
|
+
if (!cmd || cmd === "help" || cmd === "--help" || cmd === "-h") {
|
|
55
|
+
usage();
|
|
56
|
+
return cmd ? 0 : 2;
|
|
57
|
+
}
|
|
58
|
+
|
|
59
|
+
if (cmd === "start") {
|
|
60
|
+
const { run } = await import("../src/commands/start.mjs");
|
|
61
|
+
return run(rest, ctx);
|
|
62
|
+
}
|
|
63
|
+
|
|
64
|
+
if (cmd === "login") {
|
|
65
|
+
const { run } = await import("../src/commands/login.mjs");
|
|
66
|
+
return run(rest, ctx);
|
|
67
|
+
}
|
|
68
|
+
|
|
69
|
+
if (cmd === "whoami") {
|
|
70
|
+
const { run } = await import("../src/commands/whoami.mjs");
|
|
71
|
+
return run(rest, ctx);
|
|
72
|
+
}
|
|
73
|
+
|
|
74
|
+
if (cmd === "doctor") {
|
|
75
|
+
const { run } = await import("../src/commands/doctor.mjs");
|
|
76
|
+
return run(rest, ctx);
|
|
77
|
+
}
|
|
78
|
+
|
|
79
|
+
if (cmd === "ideas") {
|
|
80
|
+
const { run } = await import("../src/commands/ideas.mjs");
|
|
81
|
+
return run(rest, ctx);
|
|
82
|
+
}
|
|
83
|
+
|
|
84
|
+
if (cmd === "checkout") {
|
|
85
|
+
const { run } = await import("../src/commands/checkout.mjs");
|
|
86
|
+
return run(rest, ctx);
|
|
87
|
+
}
|
|
88
|
+
|
|
89
|
+
if (cmd === "validate") {
|
|
90
|
+
const { run } = await import("../src/commands/validate.mjs");
|
|
91
|
+
return run(rest, ctx);
|
|
92
|
+
}
|
|
93
|
+
|
|
94
|
+
if (cmd === "dev") {
|
|
95
|
+
const { run } = await import("../src/commands/dev.mjs");
|
|
96
|
+
return run(rest, ctx);
|
|
97
|
+
}
|
|
98
|
+
|
|
99
|
+
if (cmd === "submit") {
|
|
100
|
+
const { run } = await import("../src/commands/submit.mjs");
|
|
101
|
+
return run(rest, ctx);
|
|
102
|
+
}
|
|
103
|
+
|
|
104
|
+
if (BUILD_ORDER.includes(cmd)) {
|
|
105
|
+
console.error(
|
|
106
|
+
`\`tot ${cmd}\` isn't built yet.\n\n` +
|
|
107
|
+
`Build order: ${BUILD_ORDER.map((c) => (c === "checkout" ? `${c}✓` : c)).join(" → ")}.\n` +
|
|
108
|
+
`Inside a storefront checkout you can use the in-repo scripts today ` +
|
|
109
|
+
`(e.g. \`pnpm tot ${cmd}\`).`,
|
|
110
|
+
);
|
|
111
|
+
return 2;
|
|
112
|
+
}
|
|
113
|
+
|
|
114
|
+
console.error(`unknown command: ${cmd}\n`);
|
|
115
|
+
usage();
|
|
116
|
+
return 2;
|
|
117
|
+
}
|
|
118
|
+
|
|
119
|
+
main()
|
|
120
|
+
.then((code) => process.exit(code ?? 0))
|
|
121
|
+
.catch((e) => {
|
|
122
|
+
printError(e); // never a raw stack trace — house-style ✗ … → next: …
|
|
123
|
+
process.exit(1);
|
|
124
|
+
});
|
package/package.json
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@tokenoftrust/cli",
|
|
3
|
+
"version": "1.0.0",
|
|
4
|
+
"description": "Token of Trust developer CLI — check out a tenant store, run it locally with save→reload, and submit it for preview. Installs the `tot` command.",
|
|
5
|
+
"license": "Apache-2.0",
|
|
6
|
+
"author": "Token of Trust",
|
|
7
|
+
"homepage": "https://www.tokenoftrust.com",
|
|
8
|
+
"repository": {
|
|
9
|
+
"type": "git",
|
|
10
|
+
"url": "https://github.com/tokenoftrust/storefront.git",
|
|
11
|
+
"directory": "packages/cli"
|
|
12
|
+
},
|
|
13
|
+
"keywords": [
|
|
14
|
+
"tokenoftrust",
|
|
15
|
+
"tot",
|
|
16
|
+
"cli",
|
|
17
|
+
"identity-verification",
|
|
18
|
+
"age-verification",
|
|
19
|
+
"developer-tools"
|
|
20
|
+
],
|
|
21
|
+
"type": "module",
|
|
22
|
+
"bin": {
|
|
23
|
+
"tot": "./bin/tot.mjs"
|
|
24
|
+
},
|
|
25
|
+
"files": [
|
|
26
|
+
"bin",
|
|
27
|
+
"src",
|
|
28
|
+
"README.md",
|
|
29
|
+
"LICENSE"
|
|
30
|
+
],
|
|
31
|
+
"engines": {
|
|
32
|
+
"node": ">=20"
|
|
33
|
+
},
|
|
34
|
+
"publishConfig": {
|
|
35
|
+
"access": "public",
|
|
36
|
+
"registry": "https://registry.npmjs.org"
|
|
37
|
+
},
|
|
38
|
+
"scripts": {
|
|
39
|
+
"test": "node --test"
|
|
40
|
+
}
|
|
41
|
+
}
|
package/src/auth.mjs
ADDED
|
@@ -0,0 +1,132 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Auth providers for `tot` — how we establish a VALIDATED MCP session before a
|
|
3
|
+
* privileged tool call (tenant_checkout, client_switch, …).
|
|
4
|
+
*
|
|
5
|
+
* There are two identities that can drive `tot`, and the whole point of this
|
|
6
|
+
* seam is that every command calls `resolveSession(client)` and never cares
|
|
7
|
+
* which one answered:
|
|
8
|
+
*
|
|
9
|
+
* operator — TOT_API_KEY / TOT_SECRET_KEY / TOT_APP_DOMAIN in the env →
|
|
10
|
+
* credential_validate. This is a STOREFRONT-OPERATOR (or CI)
|
|
11
|
+
* identity, resolved from SSM in our tooling. It is NOT what an
|
|
12
|
+
* invited external developer has — it's how WE dogfood the CLI
|
|
13
|
+
* end-to-end today, and how CI exercises it.
|
|
14
|
+
*
|
|
15
|
+
* developer — the invited developer, signed in as THEMSELVES against the MCP
|
|
16
|
+
* via OAuth (the same identity `claude mcp add … tot` + `/mcp`
|
|
17
|
+
* establishes). `tot login` runs the MCP OAuth PKCE loopback and
|
|
18
|
+
* caches the token (~/.tot/credentials.json via token-store.mjs);
|
|
19
|
+
* this provider reads it back, silently refreshing when expired,
|
|
20
|
+
* and attaches it as the client's Bearer. Entitlement is derived
|
|
21
|
+
* server-side from the developer's ToT memberships — no local check.
|
|
22
|
+
*
|
|
23
|
+
* Selection: operator creds win when present (explicit, deterministic, what CI
|
|
24
|
+
* sets); otherwise we fall to the developer provider.
|
|
25
|
+
*/
|
|
26
|
+
import {
|
|
27
|
+
defaultCredentialsPath, readCredentials, writeCredentials, isExpired,
|
|
28
|
+
} from "./token-store.mjs";
|
|
29
|
+
import { refreshAccessToken, credentialsFromToken } from "./oauth.mjs";
|
|
30
|
+
|
|
31
|
+
/** Thrown when no provider can authenticate — carries actionable guidance. */
|
|
32
|
+
export class AuthUnavailableError extends Error {
|
|
33
|
+
constructor(message, { hint } = {}) {
|
|
34
|
+
super(message);
|
|
35
|
+
this.name = "AuthUnavailableError";
|
|
36
|
+
this.hint = hint || null;
|
|
37
|
+
}
|
|
38
|
+
}
|
|
39
|
+
|
|
40
|
+
/** True when a full operator credential triple is present in the environment. */
|
|
41
|
+
export function hasOperatorCreds(env = process.env) {
|
|
42
|
+
return Boolean(env.TOT_API_KEY && env.TOT_SECRET_KEY && env.TOT_APP_DOMAIN);
|
|
43
|
+
}
|
|
44
|
+
|
|
45
|
+
/**
|
|
46
|
+
* Establish a validated session on `client`.
|
|
47
|
+
*
|
|
48
|
+
* @param {ReturnType<import("./mcp.mjs").createMcpClient>} client
|
|
49
|
+
* @param {{ env?: NodeJS.ProcessEnv, prefer?: "operator"|"developer" }} [opts]
|
|
50
|
+
* @returns {Promise<{ identity: "operator"|"developer", appDomain: string|null }>}
|
|
51
|
+
*/
|
|
52
|
+
export async function resolveSession(client, opts = {}) {
|
|
53
|
+
const env = opts.env || process.env;
|
|
54
|
+
const prefer = opts.prefer || (hasOperatorCreds(env) ? "operator" : "developer");
|
|
55
|
+
|
|
56
|
+
if (prefer === "operator") {
|
|
57
|
+
if (!hasOperatorCreds(env)) {
|
|
58
|
+
throw new AuthUnavailableError(
|
|
59
|
+
"operator auth requested but TOT_API_KEY / TOT_SECRET_KEY / TOT_APP_DOMAIN are not all set.",
|
|
60
|
+
{ hint: "source apps/storefront/lib/resolve-tot-credentials.sh (from a storefront checkout), or unset --identity to use developer sign-in." },
|
|
61
|
+
);
|
|
62
|
+
}
|
|
63
|
+
await client.callTool("credential_validate", {
|
|
64
|
+
totApiKey: env.TOT_API_KEY,
|
|
65
|
+
totSecretKey: env.TOT_SECRET_KEY,
|
|
66
|
+
appDomain: env.TOT_APP_DOMAIN,
|
|
67
|
+
});
|
|
68
|
+
return { identity: "operator", appDomain: env.TOT_APP_DOMAIN };
|
|
69
|
+
}
|
|
70
|
+
|
|
71
|
+
// developer provider — the real invited-dev path.
|
|
72
|
+
return resolveDeveloperSession(client, env);
|
|
73
|
+
}
|
|
74
|
+
|
|
75
|
+
/**
|
|
76
|
+
* Developer (OAuth-as-yourself) provider. Reads the token `tot login` cached,
|
|
77
|
+
* refreshes it in place when expired, and attaches it as the client's Bearer so
|
|
78
|
+
* every tool call carries the developer identity. Fails with a clear next step
|
|
79
|
+
* (never a stack trace) when there's no usable session.
|
|
80
|
+
*
|
|
81
|
+
* @param {import("./mcp.mjs").createMcpClient extends (...a:any)=>infer R ? R : any} client
|
|
82
|
+
* @param {NodeJS.ProcessEnv} env
|
|
83
|
+
* @param {{ fetchImpl?: typeof fetch, now?: number }} [deps] injectable for tests
|
|
84
|
+
* @returns {Promise<{ identity: "developer", appDomain: null, token: string }>}
|
|
85
|
+
*/
|
|
86
|
+
export async function resolveDeveloperSession(client, env, deps = {}) {
|
|
87
|
+
const { fetchImpl = fetch, now = Date.now() } = deps;
|
|
88
|
+
const path = defaultCredentialsPath(env);
|
|
89
|
+
let creds = readCredentials(path);
|
|
90
|
+
|
|
91
|
+
if (!creds || !creds.accessToken) {
|
|
92
|
+
throw new AuthUnavailableError(
|
|
93
|
+
"you're not signed in to Token of Trust.",
|
|
94
|
+
{ hint: "run `tot login` to sign in, then re-run." },
|
|
95
|
+
);
|
|
96
|
+
}
|
|
97
|
+
|
|
98
|
+
if (isExpired(creds, { now })) {
|
|
99
|
+
if (!creds.refreshToken || !creds.tokenEndpoint) {
|
|
100
|
+
throw new AuthUnavailableError(
|
|
101
|
+
"your Token of Trust session has expired.",
|
|
102
|
+
{ hint: "run `tot login` to sign in again." },
|
|
103
|
+
);
|
|
104
|
+
}
|
|
105
|
+
let refreshed;
|
|
106
|
+
try {
|
|
107
|
+
refreshed = await refreshAccessToken(
|
|
108
|
+
creds.tokenEndpoint,
|
|
109
|
+
{ refreshToken: creds.refreshToken, clientId: creds.clientId },
|
|
110
|
+
fetchImpl,
|
|
111
|
+
);
|
|
112
|
+
} catch (e) {
|
|
113
|
+
throw new AuthUnavailableError(
|
|
114
|
+
`couldn't refresh your Token of Trust session: ${e?.message || e}`,
|
|
115
|
+
{ hint: "run `tot login` to sign in again." },
|
|
116
|
+
);
|
|
117
|
+
}
|
|
118
|
+
creds = credentialsFromToken({
|
|
119
|
+
mcpUrl: creds.mcpUrl,
|
|
120
|
+
clientId: creds.clientId,
|
|
121
|
+
tokenEndpoint: creds.tokenEndpoint,
|
|
122
|
+
scope: creds.scope,
|
|
123
|
+
// a refresh response may omit a new refresh_token — keep the prior one.
|
|
124
|
+
token: { ...refreshed, refresh_token: refreshed.refresh_token || creds.refreshToken },
|
|
125
|
+
now,
|
|
126
|
+
});
|
|
127
|
+
writeCredentials(path, creds);
|
|
128
|
+
}
|
|
129
|
+
|
|
130
|
+
if (client && typeof client.setToken === "function") client.setToken(creds.accessToken);
|
|
131
|
+
return { identity: "developer", appDomain: null, token: creds.accessToken };
|
|
132
|
+
}
|