@tenderprompt/cli 0.1.6 → 0.1.8

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 +14 -7
  2. package/dist/index.js +543 -135
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -16,7 +16,7 @@ npm install -g @tenderprompt/cli
16
16
  Then run:
17
17
 
18
18
  ```bash
19
- tender --help
19
+ tender capabilities --json
20
20
  ```
21
21
 
22
22
  ## What You Can Do
@@ -28,6 +28,8 @@ session:
28
28
  - list, create, and rename apps
29
29
  - bootstrap a local app checkout with Tender project context
30
30
  - configure the Tender artifact Git remote and credential helper
31
+ - discover the current CLI command surface with `tender capabilities --json`
32
+ - preview outbound HTTP binding files without writing them
31
33
  - validate app source locally before pushing
32
34
  - build and preview a commit through the Tender API
33
35
  - publish only after a dry run or explicit `--confirm publish`
@@ -44,9 +46,11 @@ interactive prompts unless the command is explicitly an auth flow.
44
46
  ## Typical Flow
45
47
 
46
48
  ```bash
49
+ tender capabilities --json
50
+
47
51
  tender auth login --device --profile edit-preview --artifact artifact_123 --ttl 7d
48
52
 
49
- tender app git setup artifact_123 --dir ./widget
53
+ tender app init artifact_123 --dir ./widget --json
50
54
 
51
55
  cd ./widget
52
56
  npm run check
@@ -59,11 +63,12 @@ tender app publish artifact_123 --commit "$(git rev-parse HEAD)" --confirm publi
59
63
 
60
64
  For agents, keep the pattern simple:
61
65
 
62
- 1. use `tender app context fetch` or `tender app init` to get local context
63
- 2. inspect and edit files locally
64
- 3. run `tender app doctor` and local project checks
65
- 4. push source with Git
66
- 5. call `preview`, `publish --dry-run`, then `publish --confirm publish` only
66
+ 1. start with `tender capabilities --json`
67
+ 2. use `tender app init` to clone/bootstrap an existing app checkout
68
+ 3. inspect and edit files locally
69
+ 4. run `tender app doctor` and local project checks
70
+ 5. push source with Git
71
+ 6. call `preview`, `publish --dry-run`, then `publish --confirm publish` only
67
72
  when the user asked to publish
68
73
 
69
74
  ## Auth
@@ -102,10 +107,12 @@ indexing the accepted commit after upstream Git accepts the push.
102
107
  ## Useful Commands
103
108
 
104
109
  ```bash
110
+ tender capabilities --json
105
111
  tender app list --json
106
112
  tender app create --name "Exit Intent Widget" --json
107
113
  tender app update artifact_123 --name "Sale Widget" --json
108
114
  tender app init artifact_123 --dir ./widget --json
115
+ tender app bindings outbound --id shopify --host admin.shopify.com --dry-run --json
109
116
  tender app context status artifact_123 --dir ./widget --json
110
117
  tender app doctor --dir ./widget --json
111
118
  tender app validate artifact_123 --json