@quatronic/qore 0.1.3 → 0.1.4

package/README.md

@@ -428,6 +428,26 @@ qore dev --kill-others        # the first module to exit stops the rest
   module that would start is already trusted and has an env file on disk;
   one exception fails the whole run with the original error.
 
+**Feedback.** Before anything starts, a module not yet cloned is offered as
+`Clone <module>, <module> now with qore sync? [Y/n]` (a TTY only, never
+with `--json`/`--no-input`; `--yes` does not accept it). A module sync
+cannot clone (a conflicting directory, no repository yet, an unsupported
+repository URL, GitHub not linked, no repository access) gets its own
+warning naming the real next step, and no prompt. While preflight runs, one progress line per
+module per step (package manager, install, env, ports) is printed as it
+completes. Once every module with a port is either listening or has been
+reported as not running, a one-line summary follows: `✔ All modules
+running:` (or `✔ Running:` / `! Not running:` when some were skipped) lists
+each module with its URL or its reason. A module that crashes while others
+keep running gets a restart hint
+(`Restart it on its own: qore dev --only <module>`, in another terminal;
+the others keep running); on shutdown, a final
+line lists what stopped cleanly and what crashed, with how long it ran.
+When the failure is about the developer's machine rather than the app
+(Docker, Node version, a port busy with something other than a previous
+`qore dev`, a package manager), the error is followed by a pointer to
+`qore doctor` for a full check.
+
 **Output.** Every line of a dev server's own stdout/stderr is prefixed per
 module and column-aligned: