@topolo/cli 0.1.9 → 0.1.11

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 +19 -6
  2. package/dist/index.js +1823 -87
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -114,6 +114,8 @@ topolo apps requirements mail --json
114
114
  topolo apps audit mail --json
115
115
  topolo apps audit mail --local --repo-root /Users/ashes/Projects/topolo --fail-on needs_review --json
116
116
  topolo apps scaffold insights --json
117
+ topolo apps scaffold insights --write --repo-root /Users/ashes/Projects/topolo --json
118
+ topolo apps scaffold score --target developer --write --repo-root ./starters --json
117
119
  topolo apps scaffold insights --workflow-only --no-json
118
120
  ```
119
121
 
@@ -127,12 +129,23 @@ include filesystem evidence from the app repo, CloudControl metadata, and
127
129
  TopoloDocs. Add `--fail-on needs_review` for the default new-work gate, or
128
130
  `--fail-on partial` for strict release readiness.
129
131
 
130
- `topolo apps scaffold <app>` generates the required new-application scaffold
131
- manifest, including expected package/auth/shell/docs/CloudControl files and a
132
- `topolo-conformance.yml` GitHub Actions workflow. The generated workflow checks
133
- out the app under `PlatformApplications/<AppDir>`, checks out `Topolo-io/docs`,
134
- `Topolo-io/topolo-sdk`, and `Topolo-io/TopoloCli`, builds the current CLI from
135
- source, then runs the local conformance audit with `--fail-on needs_review`.
132
+ `topolo apps scaffold <app>` generates the required new-application scaffold,
133
+ including package/auth/shell/docs/CloudControl files, a deploy-ready
134
+ Wrangler Worker/static-assets baseline, an Auth service manifest, and a
135
+ `topolo-conformance.yml` GitHub Actions workflow for first-party platform
136
+ apps. Add `--write --repo-root <topolo-checkout>` to create the files on disk;
137
+ existing files are refused unless `--force` is passed. The generated workflow
138
+ checks out the app under `PlatformApplications/<AppDir>`, checks out
139
+ `Topolo-io/docs`, `Topolo-io/topolo-sdk`, and `Topolo-io/TopoloCli`, builds the
140
+ current CLI from source, then runs the local conformance audit with
141
+ `--fail-on needs_review`.
142
+
143
+ For third-party developers, use `--target developer` or `--developer`. Developer
144
+ scaffolds are standalone starter projects with `topolo.app.json`, `.env.example`,
145
+ an OAuth authorization-code + PKCE browser starter, and no internal TopoloDocs,
146
+ CloudControl, or private first-party package dependencies. Developer scaffolds
147
+ are browser-only by default; add `--with-api` to include a protected Worker
148
+ baseline that validates bearer tokens through Topolo Auth over HTTP.
136
149
 
137
150
  ### `topolo api <service> <method> <path>`
138
151