tileflow 0.1.0-alpha.14 → 0.1.0-alpha.16

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/README.md CHANGED
@@ -222,13 +222,17 @@ browser bundle, copied prompt, or command-line argument.
222
222
  ```sh
223
223
  npx tileflow login
224
224
  npx tileflow whoami --json
225
+ npx tileflow deploy --origin https://www.example.com
225
226
  npx tileflow deploy --map-id map_AbCdEfGhIjKlMnOp
226
227
  npx tileflow status --map-id map_AbCdEfGhIjKlMnOp
227
228
  ```
228
229
 
229
- Replace the example Map ID with the destination created in Tileflow. It is a public identifier,
230
- not a credential or the portable `id` in your config. A CI deploy key must authorize that destination.
231
- `logout` removes the saved personal session.
230
+ Without `--map-id`, a logged-in `deploy` first creates the Map in the Team you administer (it asks,
231
+ or takes `--team @team`, when several qualify) with the browser access you choose: exact origins
232
+ with `--origin`, or `--any-website`. It prints the Map ID to use for later deploys;
233
+ `tileflow maps create` creates the Map without deploying. The Map ID is a public identifier, not a
234
+ credential or the portable `id` in your config. CI always deploys an existing Map with a deploy key
235
+ for that destination. `logout` removes the saved personal session.
232
236
 
233
237
  Deploy publishes the compiled concrete-theme family and managed icon assets; it does not ask the
234
238
  server to compile TypeScript. Repeating an unchanged deployment reuses its version. Build writers