railcode 0.1.1 → 0.1.5

package/README.md

@@ -46,7 +46,7 @@ mkdir my-app
 cd my-app
 railcode init my-app
 railcode dev
-railcode design-system pull design-system.md
+railcode get design-system
 railcode deploy
 ```
 
@@ -56,20 +56,22 @@ at the root, and deployable build output goes in `dist/`. Direct dependencies
 in the starter are exact version pins.
 
 `railcode dev` installs missing app dependencies on first run, then runs the app
-from the current Railcode directory with no login step. Identity, access
-metadata, KV, and files run locally; backend-backed APIs such as SQL and LLM are
-forwarded to the configured Railcode URL when that backend access is available.
+from the current Railcode directory with no login step. It starts on
+`127.0.0.1:7331` and automatically uses the next available port when another dev
+server is already running; use the printed URL. For inferred Vite apps, the
+asset dev server likewise starts at `5173` and moves upward when needed.
+Identity, access metadata, KV, and files run locally; backend-backed APIs such
+as SQL and LLM are forwarded to the configured Railcode URL when that backend
+access is available.
 
 `railcode login` opens a browser authorization flow. Pass `--api-url` or set
 `RAILCODE_API_URL` to choose the Railcode auth/API origin; if neither is set and
 no saved URL exists, the CLI prompts for the domain and assumes `https://` when
 you enter a bare domain.
 
-`railcode design-system pull` fetches the platform design-system markdown from
+`railcode get design-system` fetches the platform design-system markdown from
 `/v1/config/design-system` using the saved browser-authorized API token or
-`RAILCODE_API_TOKEN`. It
-prints markdown to stdout by default, or writes to a path passed positionally or
-with `--output`.
+`RAILCODE_API_TOKEN` and prints it to stdout.
 
 `railcode deploy` runs from the current Railcode app directory, builds the app,
 and publishes the inferred app output over HTTP to the canonical API host. It