spawnio 1.0.7__tar.gz → 1.0.9__tar.gz

spawnio-1.0.9/CONTRIBUTING.md

@@ -0,0 +1,178 @@
+# Contributing to spawnio
+
+Solo-maintained, but PRs are welcome. Here's what you need to know.
+
+---
+
+## Prerequisites
+
+- Python 3.12+ (`uv python install 3.12` if using uv)
+- [uv](https://github.com/astral-sh/uv) installed
+
+---
+
+## Setup
+
+```bash
+git clone https://github.com/Abhiix0/Spawn.git
+cd Spawn
+uv sync --all-groups
+```
+
+---
+
+## Running tests
+
+```bash
+uv run pytest
+```
+
+With coverage:
+
+```bash
+uv run pytest --cov=src/spawn --cov-report=term-missing
+```
+
+---
+
+## Testing and fixtures
+
+- **Factory:** the `spawn_project` fixture in `tests/conftest.py` generates a project offline: `spawn_project("backend-api", framework="fastapi")` returns its `Path`. The `no_toolchain` fixture stubs git, uv and package installs.
+- **Golden trees:** `tests/fixtures/trees/<archetype>.txt` lists every file of a generated archetype. After an intentional output change, regenerate with `SPAWN_UPDATE_TREES=1 uv run pytest tests/test_fixtures.py` and review the diff.
+- **Offline rule:** tests must not use the network, real `git` or real `uv`; use `no_toolchain`.
+- **Adding an archetype:** add an entry to `tests/fixtures/archetypes.py`, run once with `SPAWN_UPDATE_TREES=1` to create its golden tree, and review it.
+
+---
+
+## Linting and formatting
+
+```bash
+uv run ruff check .
+uv run ruff format .
+```
+
+Both must pass before opening a PR. CI enforces this.
+
+---
+
+## Adding a new template
+
+Templates follow a consistent three-file pattern. MCP Server (`src/spawn/templates/mcp_server/`) is the cleanest minimal example to copy from.
+
+### 1. Create the template package
+
+```
+src/spawn/templates/<your_slug>/
+    __init__.py     # MyTemplate(BaseTemplate) class
+    content.py      # string constants + make_readme() + make_agents_md()
+```
+
+**`content.py`** holds all file content as triple-quoted strings with `{project_name}` placeholders (resolved later via `.format_map(context)`). Export `make_readme()` and `make_agents_md()` as functions that return the formatted string — these are called by `BaseTemplate` machinery automatically.
+
+**`__init__.py`** subclasses `BaseTemplate`:
+
+```python
+class MyTemplate(BaseTemplate):
+    def __init__(self, extras: list[str] | None = None) -> None:
+        self.extras = extras or []
+        super().__init__(
+            name="My Template",
+            folders=["src", "tests"],
+            starter_files=[
+                ("src/__init__.py", INIT_CONTENT),
+                ("src/main.py",     MAIN_CONTENT),
+                (".env.example",    ENV_CONTENT),
+            ],
+            next_steps=["cd {project_name}", "uv run python -m src.main"],
+        )
+
+    def get_readme_content(self, context: dict) -> str | None:
+        return make_readme().format_map(context)
+
+    def get_agents_md_content(self, context: dict) -> str | None:
+        return make_agents_md().format_map(context)
+
+    def get_dependencies(self) -> list[str]:
+        base = ["some-package"]
+        if "pytest" in self.extras:
+            base.append("pytest")
+        return base
+
+    def post_install(self, project_path: Path) -> None:
+        # Write pyproject.toml sections, CI workflows, etc. as needed.
+        pass
+```
+
+If your template needs framework or provider selection, look at `ChatbotTemplate` or `AgentTemplate` — those accept `framework` and `provider` constructor args and use `get_supported_providers()` to filter the provider list per framework.
+
+### 2. Register in `src/spawn/core/registry.py`
+
+Add an import and a `TemplateMetadata` entry to `TEMPLATES`:
+
+```python
+from spawn.templates.my_template import MyTemplate
+
+TEMPLATES = {
+    # ... existing entries ...
+    "my-slug": TemplateMetadata(
+        slug="my-slug",
+        display_name="My Template",
+        description="One-line description shown in spawn doctor output",
+        template_class=MyTemplate,
+        available_extras=["ruff", "pytest", "github-actions"],
+        # available_frameworks, available_providers, available_cli_types,
+        # available_data_types — only set the fields your template uses.
+    ),
+}
+```
+
+`instantiate_template()` inspects the constructor signature and forwards only the fields the class accepts, so no changes to that function are needed.
+
+### 3. Write tests
+
+Add two test files mirroring the existing pattern:
+
+| File | What to test |
+|---|---|
+| `tests/test_<slug>_template.py` | Template constants, `get_dependencies()`, `get_readme_content()`, `py_compile` on each Python starter file, no unescaped braces |
+| `tests/test_<slug>_generator.py` | `generate_project(config)` (or `ProjectGenerator().generate()`) with mocked uv/git/install, directory structure, README content, `.spawn/meta.json` fields |
+
+See `tests/test_mcp_server_template.py` and `tests/test_mcp_server_generator.py` for the exact mock patterns (`_mock_uv_and_install()` context manager, `_cfg()` helper, `patch.object(MyTemplate, "post_install")`).
+
+Also update `tests/test_registry.py`: increment the `len(slugs) == N` assertion and add `assert "my-slug" in slugs`.
+
+---
+
+## Branch and commit conventions
+
+The git log uses a lightweight conventional-commits style — prefix commits with `feat:`, `fix:`, `docs:`, or `chore:` and use the imperative mood in the subject line:
+
+```
+feat: add <slug> template
+fix: handle edge case in parse_structure
+docs: update CONTRIBUTING.md
+chore: bump version to 1.0.8
+```
+
+Branch off `main`, use a short descriptive name (`feat/my-template`, `fix/windows-path`, etc.).
+
+---
+
+## PR expectations
+
+- All existing tests must pass (`uv run pytest`).
+- New templates require both a `_template` and a `_generator` test file.
+- `uv run ruff check .` and `uv run ruff format --check .` must be clean.
+- CI (`.github/workflows/ci.yml`) must be green.
+- Keep PRs focused — one template or fix per PR.
+
+---
+
+## Reporting issues / asking questions
+
+GitHub Issues are currently **restricted** on this repo. To reach the maintainer:
+
+- Open a [GitHub Discussion](https://github.com/Abhiix0/Spawn/discussions) if Discussions are enabled.
+- Otherwise, leave a comment on an existing PR or tag `@Abhiix0` in your PR description.
+
+If you hit a bug that's blocking you, a PR with a failing test that reproduces it is a faster path to a fix than waiting for issues to be opened.

{spawnio-1.0.7 → spawnio-1.0.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: spawnio
-Version: 1.0.7
+Version: 1.0.9
 Summary: Spawn a ready-to-use Python project in seconds
 License-File: LICENSE
 Requires-Python: >=3.12
@@ -88,6 +88,7 @@ It's repetitive. It's inconsistent. And you haven't written a single line of *re
 | **Arrow-key menus** | Every prompt in `spawn create` is arrow-key/spacebar driven, not typed numbers |
 | **GitHub publishing** | Connects your project to an existing GitHub repo and pushes the initial commit |
 | **spawn doctor** | Scores your project's health out of 100, with per-category breakdowns and a prioritized next step |
+| **spawn doctor --fix** | Fixes missing files and config automatically — never overwrites, never installs packages |
 
 ---
 
@@ -143,7 +144,7 @@ Running `spawn` with no arguments shows the banner, the installed version, and t
 
 ```
 SPAWN — scaffold your next project
-v1.0.6
+v1.0.9
 
 Commands
   create    Scaffold a new project
@@ -190,7 +191,15 @@ Use the arrow keys to move, Enter to select — the same pattern every prompt in
 
 **Step 3 — Additional prompts** *(template-dependent — framework, provider, project type, and/or extras, depending on what you picked. See [Project Templates](#project-templates) below for each one's exact flow.)*
 
-**Step 4 — Git**
+**Step 4 — License**
+
+```
+? Choose a license (Use arrow keys)
+ » MIT
+   None
+```
+
+**Step 5 — Git**
 
 ```
 Initialize Git? [Y/n]: Y
@@ -253,9 +262,11 @@ my-api/
  ● pytest
  ○ docker
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `docker` `github-actions`
+**Available extras:** `ruff` `pytest` `docker` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -306,9 +317,11 @@ my-cli/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -345,9 +358,11 @@ my-automation/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -397,9 +412,11 @@ my-chatbot/
  ● pytest
  ○ rich
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `rich` `github-actions`
+**Available extras:** `ruff` `pytest` `rich` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -447,11 +464,13 @@ my-agent/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
 > If you pick `openai-agents`, only `openai` and `openrouter` appear as provider choices — the list is filtered per framework.
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -492,11 +511,13 @@ my-rag/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
 RAG System uses a fixed stack — **LlamaIndex + ChromaDB + OpenAI** — so there's no framework or provider prompt, unlike Chatbot and Agent. On first run, it automatically ingests documents from `data/` into a local ChromaDB index, then lets you ask questions against them. Requires an `OPENAI_API_KEY` (used for both the LLM and embeddings).
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -540,9 +561,11 @@ my-data-project/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -586,11 +609,13 @@ my-mcp-server/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
 MCP Server uses a fixed stack — the official `mcp` Python SDK's `FastMCP` — so there's no framework or provider prompt, the same as RAG System.
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -641,6 +666,7 @@ Dependencies (comma separated, optional): fastapi, uvicorn
  ● Pytest
  ○ Pre-commit
  ○ Dockerfile
+ ○ Mypy
 
 Additional ignore patterns (optional, comma separated): data/, *.csv
 
@@ -654,7 +680,7 @@ Proceed? [Y/n]: Y
 
 **The Dependencies prompt** (shown only when uv is enabled) installs packages immediately via `uv add`.
 
-**The Optional Setup menu** installs dev tools via `uv add --dev` and generates their config files: `ruff.toml`, `tests/__init__.py`, `.pre-commit-config.yaml`, and/or `Dockerfile`.
+**The Optional Setup menu** installs dev tools via `uv add --dev` and generates their config files: `ruff.toml`, `tests/__init__.py`, `.pre-commit-config.yaml`, `Dockerfile`, and/or `[tool.mypy]` in `pyproject.toml`.
 
 ### Non-Interactive Mode
 
@@ -663,7 +689,7 @@ Skip all prompts by passing flags directly or pointing to a JSON config file.
 **Using flags:**
 
 ```bash
-spawn create --name my-api --template backend-api --framework fastapi --extras ruff,pytest --git
+spawn create --name my-api --template backend-api --framework fastapi --extras ruff,pytest --license mit --git
 ```
 
 **Using a config file:**
@@ -674,6 +700,7 @@ spawn create --name my-api --template backend-api --framework fastapi --extras r
   "template": "backend-api",
   "framework": "fastapi",
   "extras": ["ruff", "pytest"],
+  "license": "mit",
   "git": true,
   "uv": true
 }
@@ -683,7 +710,7 @@ spawn create --name my-api --template backend-api --framework fastapi --extras r
 spawn create --config spawn.json
 ```
 
-`--config` takes precedence over individual flags. Add `--dry-run` to either form to validate the config and print it without creating any files.
+`--config` takes precedence over individual flags (an explicit `--no-git`/`--no-uv` is ignored with a warning). Add `--dry-run` to either form to validate the config and print it without creating any files.
 
 > Custom Structure is interactive-only in this version.
 
@@ -741,11 +768,30 @@ spawn doctor ./path/to/project
 
 Checks span six categories — Documentation, Version Control, Configuration, Testing, Automation, and Code Quality (Ruff, type checking, pre-commit) — all filesystem-based, nothing is executed or sent over the network.
 
+#### Automatic Remediation with `--fix`
+
+`spawn doctor --fix` creates missing files and config automatically. It **never overwrites** pre-existing files and **never installs packages** directly (instead printing `uv add` commands for optional tools).
+
+```bash
+# Automatically create missing files and config
+spawn doctor --fix
+spawn doctor ./path/to/project --fix
+
+# Preview what would be created without touching disk
+spawn doctor --fix --dry-run
+
+# Run non-interactively without the confirmation prompt
+spawn doctor --fix --yes
+
+# Also add an MIT license if missing
+spawn doctor --fix --license mit
+```
+
 ### `spawn version`
 
 ```bash
 spawn version
-# → Spawn v1.0.7
+# → Spawn v1.0.9
 ```
 
 ### Publish to GitHub
@@ -779,6 +825,8 @@ All tests should pass. If they don't, please [open an issue](https://github.com/
 
 | Version | Highlight |
 |---|---|
+| **v1.0.9** | Core hardening: documented exit-code contract (generation, toolchain and publish failures exit non-zero), `--no-uv` honored for templates (file-only extras still written), path-traversal protection for custom structures, `read_project_metadata` extension boundary |
+| **v1.0.8** | `spawn doctor --fix` (`--dry-run`, `--yes`, `--license`), `--license` flag and prompt on `create`, `CHANGELOG.md` generated for every project, `pre-commit` and `mypy` extras across all templates, Custom Structure Mypy option |
 | **v1.0.7** | Fixed UTF-8 console crash on Windows when stdout is redirected/piped, added Windows reserved device name validation (`CON`, `PRN`, `AUX`, `NUL`, `COM1`–`9`, `LPT1`–`9`), clarified Python 3.12 requirement |
 | **v1.0.6** | Removed duplicate banner from `spawn create`; `spawn` alone now shows the banner and command overview |
 | **v1.0.5** | Published to PyPI as `spawnio`; arrow-key selection menus, no-args banner, consistent Ctrl+C handling |

{spawnio-1.0.7 → spawnio-1.0.9}/README.md

@@ -77,6 +77,7 @@ It's repetitive. It's inconsistent. And you haven't written a single line of *re
 | **Arrow-key menus** | Every prompt in `spawn create` is arrow-key/spacebar driven, not typed numbers |
 | **GitHub publishing** | Connects your project to an existing GitHub repo and pushes the initial commit |
 | **spawn doctor** | Scores your project's health out of 100, with per-category breakdowns and a prioritized next step |
+| **spawn doctor --fix** | Fixes missing files and config automatically — never overwrites, never installs packages |
 
 ---
 
@@ -132,7 +133,7 @@ Running `spawn` with no arguments shows the banner, the installed version, and t
 
 ```
 SPAWN — scaffold your next project
-v1.0.6
+v1.0.9
 
 Commands
   create    Scaffold a new project
@@ -179,7 +180,15 @@ Use the arrow keys to move, Enter to select — the same pattern every prompt in
 
 **Step 3 — Additional prompts** *(template-dependent — framework, provider, project type, and/or extras, depending on what you picked. See [Project Templates](#project-templates) below for each one's exact flow.)*
 
-**Step 4 — Git**
+**Step 4 — License**
+
+```
+? Choose a license (Use arrow keys)
+ » MIT
+   None
+```
+
+**Step 5 — Git**
 
 ```
 Initialize Git? [Y/n]: Y
@@ -242,9 +251,11 @@ my-api/
  ● pytest
  ○ docker
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `docker` `github-actions`
+**Available extras:** `ruff` `pytest` `docker` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -295,9 +306,11 @@ my-cli/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -334,9 +347,11 @@ my-automation/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -386,9 +401,11 @@ my-chatbot/
  ● pytest
  ○ rich
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `rich` `github-actions`
+**Available extras:** `ruff` `pytest` `rich` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -436,11 +453,13 @@ my-agent/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
 > If you pick `openai-agents`, only `openai` and `openrouter` appear as provider choices — the list is filtered per framework.
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -481,11 +500,13 @@ my-rag/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
 RAG System uses a fixed stack — **LlamaIndex + ChromaDB + OpenAI** — so there's no framework or provider prompt, unlike Chatbot and Agent. On first run, it automatically ingests documents from `data/` into a local ChromaDB index, then lets you ask questions against them. Requires an `OPENAI_API_KEY` (used for both the LLM and embeddings).
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -529,9 +550,11 @@ my-data-project/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -575,11 +598,13 @@ my-mcp-server/
  ● ruff
  ● pytest
  ○ github-actions
+ ○ pre-commit
+ ○ mypy
 ```
 
 MCP Server uses a fixed stack — the official `mcp` Python SDK's `FastMCP` — so there's no framework or provider prompt, the same as RAG System.
 
-**Available extras:** `ruff` `pytest` `github-actions`
+**Available extras:** `ruff` `pytest` `github-actions` `pre-commit` `mypy`
 
 **Run it:**
 
@@ -630,6 +655,7 @@ Dependencies (comma separated, optional): fastapi, uvicorn
  ● Pytest
  ○ Pre-commit
  ○ Dockerfile
+ ○ Mypy
 
 Additional ignore patterns (optional, comma separated): data/, *.csv
 
@@ -643,7 +669,7 @@ Proceed? [Y/n]: Y
 
 **The Dependencies prompt** (shown only when uv is enabled) installs packages immediately via `uv add`.
 
-**The Optional Setup menu** installs dev tools via `uv add --dev` and generates their config files: `ruff.toml`, `tests/__init__.py`, `.pre-commit-config.yaml`, and/or `Dockerfile`.
+**The Optional Setup menu** installs dev tools via `uv add --dev` and generates their config files: `ruff.toml`, `tests/__init__.py`, `.pre-commit-config.yaml`, `Dockerfile`, and/or `[tool.mypy]` in `pyproject.toml`.
 
 ### Non-Interactive Mode
 
@@ -652,7 +678,7 @@ Skip all prompts by passing flags directly or pointing to a JSON config file.
 **Using flags:**
 
 ```bash
-spawn create --name my-api --template backend-api --framework fastapi --extras ruff,pytest --git
+spawn create --name my-api --template backend-api --framework fastapi --extras ruff,pytest --license mit --git
 ```
 
 **Using a config file:**
@@ -663,6 +689,7 @@ spawn create --name my-api --template backend-api --framework fastapi --extras r
   "template": "backend-api",
   "framework": "fastapi",
   "extras": ["ruff", "pytest"],
+  "license": "mit",
   "git": true,
   "uv": true
 }
@@ -672,7 +699,7 @@ spawn create --name my-api --template backend-api --framework fastapi --extras r
 spawn create --config spawn.json
 ```
 
-`--config` takes precedence over individual flags. Add `--dry-run` to either form to validate the config and print it without creating any files.
+`--config` takes precedence over individual flags (an explicit `--no-git`/`--no-uv` is ignored with a warning). Add `--dry-run` to either form to validate the config and print it without creating any files.
 
 > Custom Structure is interactive-only in this version.
 
@@ -730,11 +757,30 @@ spawn doctor ./path/to/project
 
 Checks span six categories — Documentation, Version Control, Configuration, Testing, Automation, and Code Quality (Ruff, type checking, pre-commit) — all filesystem-based, nothing is executed or sent over the network.
 
+#### Automatic Remediation with `--fix`
+
+`spawn doctor --fix` creates missing files and config automatically. It **never overwrites** pre-existing files and **never installs packages** directly (instead printing `uv add` commands for optional tools).
+
+```bash
+# Automatically create missing files and config
+spawn doctor --fix
+spawn doctor ./path/to/project --fix
+
+# Preview what would be created without touching disk
+spawn doctor --fix --dry-run
+
+# Run non-interactively without the confirmation prompt
+spawn doctor --fix --yes
+
+# Also add an MIT license if missing
+spawn doctor --fix --license mit
+```
+
 ### `spawn version`
 
 ```bash
 spawn version
-# → Spawn v1.0.7
+# → Spawn v1.0.9
 ```
 
 ### Publish to GitHub
@@ -768,6 +814,8 @@ All tests should pass. If they don't, please [open an issue](https://github.com/
 
 | Version | Highlight |
 |---|---|
+| **v1.0.9** | Core hardening: documented exit-code contract (generation, toolchain and publish failures exit non-zero), `--no-uv` honored for templates (file-only extras still written), path-traversal protection for custom structures, `read_project_metadata` extension boundary |
+| **v1.0.8** | `spawn doctor --fix` (`--dry-run`, `--yes`, `--license`), `--license` flag and prompt on `create`, `CHANGELOG.md` generated for every project, `pre-commit` and `mypy` extras across all templates, Custom Structure Mypy option |
 | **v1.0.7** | Fixed UTF-8 console crash on Windows when stdout is redirected/piped, added Windows reserved device name validation (`CON`, `PRN`, `AUX`, `NUL`, `COM1`–`9`, `LPT1`–`9`), clarified Python 3.12 requirement |
 | **v1.0.6** | Removed duplicate banner from `spawn create`; `spawn` alone now shows the banner and command overview |
 | **v1.0.5** | Published to PyPI as `spawnio`; arrow-key selection menus, no-args banner, consistent Ctrl+C handling |