spacetime dev issues

issues i currently have are:

• no docs that explains the setup of spacetime dev (not found in https://spacetimedb.com/docs/cli-reference or somewhere i could find)
• that --database name and --client-lang name has to be written every the time or it will use a random new db name and the same client language as the module even if other language files are already in the module bindings
• that spacetime dev is creating another project folder and thus requires a vscode restart to that sub folder or it won't run the next time the cli is called
• it doesn't handle table/type changes and migrations and just fails to publish without asking to do -c publish
  • to fix that you need to
    • cancel dev
    • cd into the spacetimedb sub folder
    • run publish with -c
    • cd out again
    • run spacetime dev --dbname x --client-lang y again
    • (or have a separate terminal open for manual publish)

what i wish it had:

• remembering the db name
  • for now asking the name would be fine but currently it is choosing a new rng name each time creating new modules on the maincloud or localhost.
• remembering the client language or use the language of the existing module_bindings files
• choose to not create module_bindings automatically for clients that have their own code gen setup (custom sdk and so on).

No source files or tests are named. Start by tracing the spacetime dev CLI workflow for database naming, client-language selection, project-folder creation, and publish failures; done would require resolving the reported workflow problems and supporting the requested configuration behavior.