@topolo/cli 0.1.31 → 0.1.34

package/README.md

@@ -165,10 +165,15 @@ including package/auth/shell/docs/CloudControl files, a deploy-ready
 Wrangler Worker/static-assets baseline, an Auth service manifest, and a
 `topolo-conformance.yml` GitHub Actions workflow for first-party platform
 apps. Add `--write --repo-root <topolo-checkout>` to create the files on disk;
-existing files are refused unless `--force` is passed. The generated workflow
-checks out the app under `PlatformApplications/<AppDir>`, checks out
-`Topolo-io/TopoloDocs`, `Topolo-io/topolo-sdk`, and `Topolo-io/TopoloCli`, builds the
-current CLI from source, then runs the local conformance audit with
+existing files are refused unless `--force` is passed. The first-party scaffold
+writes apps under `apps/<AppDir>`, writes canonical docs under
+`system-apps/TopoloDocs/apps/web/src/content`, writes Auth service manifests
+under `topolo-platform/core/TopoloAuth/catalog/service-manifests`, emits a
+project-local `AGENTS.md` for future agent work in the scaffold, and pins the
+generated starter to the current published shared package baseline. The
+generated workflow checks out the app under `apps/<AppDir>`, checks out
+`Topolo-io/TopoloDocs`, `Topolo-io/topolo-sdk`, and `Topolo-io/TopoloCli`, builds
+the current CLI from source, then runs the local conformance audit with
 `--fail-on needs_review`.
 
 For third-party developers, use `--target developer` or `--developer`. Developer
@@ -218,7 +223,7 @@ topolo api auth GET /api/me
 topolo api mail POST /api/mail/mailboxes/primary/messages --data '{"subject":"Hello"}' --confirm
 ```
 
-Use `topolo services --json` to discover service ids permitted for the current
+Use `topolo services --json` to discover app ids permitted for the current
 credential before calling a service that does not have a typed command yet.
 
 ## Output modes