nuspace 0.3.0__tar.gz → 0.4.0__tar.gz

{nuspace-0.3.0 → nuspace-0.4.0}/.github/workflows/publish-nuspace-ui.yml

@@ -3,9 +3,9 @@
 #
 # The nuspace-ui wheel is nothing but the compiled vite SPA, force-included at
 # the wheel path `nuspace_ui/build/`. It carries no python source and no
-# dependencies. The runtime locates it with `import nuspace_ui` -- see
-# `_bundled_static()` in src/nuspace/web/serve/app.py -- and skips the static
-# mount entirely if it is not installed.
+# dependencies. The web device hands `static="nuspace_ui"` to nustd.ws_server,
+# which locates it by import (see `serve_web` in
+# src/nuspace/system/devices/web/device.py).
 #
 # Keeping the bundle in its own distribution is the point: PyPI caps project
 # size, and a compiled SPA rebuilt on every UI tweak would burn through the
@@ -20,8 +20,8 @@
 #     Environment name: (leave blank)
 #
 # Release flow:
-#   1. Bump `version` in both `ts/pyproject.toml` and
-#      `ts/package.json` (keep them equal).
+#   1. Bump `version` in both `pkgs/ts/nuspace-ui/pyproject.toml`
+#      and `pkgs/ts/nuspace-ui/package.json` (keep them equal).
 #   2. Commit and push to main.
 #   3. `git tag nuspace-ui@X.Y.Z && git push origin nuspace-ui@X.Y.Z`.
 name: Publish nuspace-ui to PyPI
@@ -40,7 +40,7 @@ concurrency:
   cancel-in-progress: false
 
 env:
-  UI_DIR: ts
+  UI_DIR: pkgs/ts/nuspace-ui
 
 jobs:
   publish:
@@ -53,7 +53,7 @@ jobs:
         with:
           node-version: 24
           cache: npm
-          cache-dependency-path: ts/package-lock.json
+          cache-dependency-path: pkgs/ts/nuspace-ui/package-lock.json
 
       - uses: actions/setup-python@v5
         with:
@@ -115,5 +115,5 @@ jobs:
         if: startsWith(github.ref, 'refs/tags/nuspace-ui@')
         uses: pypa/gh-action-pypi-publish@release/v1
         with:
-          packages-dir: ts/wheel-dist
+          packages-dir: pkgs/ts/nuspace-ui/wheel-dist
           skip-existing: true

{nuspace-0.3.0 → nuspace-0.4.0}/.github/workflows/publish-nuspace.yml

@@ -13,19 +13,20 @@
 #     Workflow name: publish-nuspace.yml
 #     Environment name: (leave blank)
 #
-# Two distributions ship from this repo, on independent tags:
-#   .                      -> nuspace     (the runtime + the `nuspace` command)
-#   ts     -> nuspace-ui  (the compiled vite bundle)
+# Three distributions ship from this repo, on independent tags:
+#   .                  -> nuspace     (the runtime + the `nuspace` command)
+#   pkgs/nuverse       -> nuverse     (the extensions: Planes, snippets)
+#   pkgs/ts/nuspace-ui -> nuspace-ui  (the compiled vite bundle)
 #
-# They version independently. `nuspace` hard-depends on `nuspace-ui>=X.Y.Z`, so
-# a python release can require a newer bundle, but a bundle-only fix ships on
-# its own tag without republishing this wheel.
+# They version independently. `nuspace` hard-depends on `nuspace-ui>=X.Y.Z` and
+# `nuverse>=X.Y.Z`, so a python release can require a newer bundle, but a
+# bundle-only fix ships on its own tag without republishing this wheel.
 #
-# The wheel deliberately excludes `ts/**` (see the hatch config
-# in pyproject.toml). The compiled assets live in the nuspace-ui wheel and are
-# found at runtime by `import nuspace_ui` -- see `_bundled_static()` in
-# src/nuspace/web/serve/app.py. So this build needs no node toolchain, even
-# though an install always pulls the bundle.
+# The wheel deliberately ships `src/nuspace` alone, `pkgs/**` stays out (see
+# the hatch config in pyproject.toml). The compiled assets live in the
+# nuspace-ui wheel and are found at runtime by import -- see `serve_web` in
+# src/nuspace/system/devices/web/device.py. So this build needs no node
+# toolchain, even though an install always pulls the bundle.
 #
 # Ordering on a coordinated release: push the `nuspace-ui@` tag first, so the
 # bundle is on the index before the wheel that requires it.

nuspace-0.4.0/.github/workflows/publish-nuverse.yml

@@ -0,0 +1,88 @@
+# Publishes the `nuverse` distribution to PyPI on a tag push like `nuverse@0.1.0`.
+# Manual "Run workflow" dispatch builds only, unless you tick `publish`.
+#
+# nuverse is the extensions package: the Planes (`+`) and snippets (`/`) a space
+# offers out of the box. nuspace finds it through the `nuspace.extensions`
+# entry point and hard-depends on it. It carries python source only, no node
+# toolchain needed.
+#
+# `nuspace` tags own release semantics for the repo (GitHub Release). This tag
+# does not cut a release, same as `nuspace-ui`.
+#
+# Setup once (PyPI trusted publisher / OIDC, no secrets):
+#   pypi.org -> account -> Publishing -> Add pending publisher
+#     PyPI project name: nuverse
+#     Owner: nustackdev
+#     Repository name: nuspace
+#     Workflow name: publish-nuverse.yml
+#     Environment name: (leave blank)
+#
+# Ordering on a coordinated release: nuverse depends on nuspace and nuspace on
+# nuverse, so push `nuverse@` first, then `nuspace@`. pip resolves the cycle
+# once both are on the index.
+#
+# Release flow:
+#   1. Bump `version` in `pkgs/nuverse/pyproject.toml`.
+#   2. Commit and push to main.
+#   3. `git tag nuverse@X.Y.Z && git push origin nuverse@X.Y.Z`.
+name: Publish nuverse to PyPI
+
+on:
+  push:
+    tags: ["nuverse@*"]
+  workflow_dispatch:
+    inputs:
+      publish:
+        description: "Publish to PyPI (otherwise build only)"
+        type: boolean
+        default: false
+
+permissions:
+  contents: read
+  id-token: write   # PyPI trusted publishing (OIDC)
+
+concurrency:
+  group: publish-nuverse
+  cancel-in-progress: false
+
+env:
+  PKG_DIR: pkgs/nuverse
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: verify tag matches pyproject.toml version
+        if: startsWith(github.ref, 'refs/tags/nuverse@')
+        working-directory: ${{ env.PKG_DIR }}
+        run: |
+          TAG_VERSION="${GITHUB_REF#refs/tags/nuverse@}"
+          PKG_VERSION=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+          if [ "$TAG_VERSION" != "$PKG_VERSION" ]; then
+            echo "tag nuverse@$TAG_VERSION does not match pyproject.toml version $PKG_VERSION"
+            exit 1
+          fi
+
+      # The workspace source for nuspace is dev-only; a hatchling build is
+      # metadata-only, so the wheel carries the plain PyPI requirement.
+      - name: build distribution
+        working-directory: ${{ env.PKG_DIR }}
+        run: uv build --out-dir dist
+
+      - name: publish nuverse
+        if: >-
+          startsWith(github.ref, 'refs/tags/nuverse@') || inputs.publish
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: pkgs/nuverse/dist
+          skip-existing: true

{nuspace-0.3.0 → nuspace-0.4.0}/.gitignore

@@ -95,5 +95,5 @@ src/nuspace/web/ui/dist/*
 !src/nuspace/web/ui/dist/.gitkeep
 
 *.db/
-# local archive of the v0 prototype (reference only, never edited)
+# Local archive of the v0 prototype (reference only, never edited)
 _archive/

{nuspace-0.3.0 → nuspace-0.4.0}/CHANGELOG.md

@@ -2,13 +2,84 @@
 
 ## Packages shipped from this repo
 
-- **nuspace** (the runtime, the `nuspace` command) — 0.3.0
-- **nuspace-ui** (the compiled web bundle) — 0.3.0
+- **nuspace** (the runtime, the `nuspace` command) — 0.4.0
+- **nuspace-ui** (the compiled web bundle) — 0.4.0
+- **nuverse** (the Planes and snippets a space ships with) — 0.2.0
 
 Below is the changelog for **nuspace** - the full commit stream. Newest first.
 The `nuspace-ui` wheel is the same source tree's vite output and is not tracked
 separately here.
 
+## 0.4.0 — 2026-09-25
+
+- Cells and planes still loading show skeletons, not blank space or No view
+- Browser tabs show the open plane's title and emoji, or the nu logo
+- Menus, dialogs, empty states and chips now come from the shared kit
+- Opening a missing or headless plane says so instead of showing an empty page
+- Cells that draw nothing show a quiet No view chip on every plane
+- Drag planes into a split, drag tabs to reorder, cmd-click opens a browser tab
+- Pin planes to a row at the top of the sidebar, reorder them by dragging
+- Home and settings start with their own icons, a house and a gear
+- A settings plane with a telemetry switch, and home lives at its own address
+- Planes write like a document: Enter, Cmd+Enter, Backspace across text cells, and box selection
+- A wider sidebar by default, and clicking a resize handle resets its width
+- The plane icon sits in the gutter beside the title, and the emoji tab opens first
+- Planes lay out on one grid, so gutters never hang past a narrow pane
+- Empty planes show how to start, and the cell menu says when nothing matches
+- Start typing on an empty line and a text cell opens with your words
+- Planes take an icon or emoji, picked from the title or the sidebar menu
+- New cells from a snippet open showing what they draw, not their code
+- Rename a plane by editing its title in place, on any plane
+- New lens snippets browse the current plane, or a cell picked from a dropdown
+- A Lens snippet browses any shape in the store as cascading columns
+- A Jobs plane makes headless planes and sets their code, boot and restart
+- Supervised cells can restart after a fixed delay, so a job can run periodically
+- Plane rows open in split from a hover button, and cut-off names show in tooltips
+- The sidebar shows the nuspace wordmark, and planes no longer jump when scrolling starts
+- A calmer, collapsible sidebar with hover chevrons and GitHub and docs links
+- Tooltips wait a moment before showing, the same everywhere
+- Apps become Planes: registered data seeded with cells, created from one add plane popup
+- The sidebar is one tree of planes, reordered and nested by dragging rows
+- Everything is called a plane or a cell, across the interface, wire and code
+- Interface text, labels and messages now use normal sentence case
+- A home page shows recent pages, a live overview and how to get started
+- Split panes get a tab bar to switch, rename and close them
+- A compact page setting tightens the header and drops the space below
+- Panes get a settings menu, resize handles and side scrolling when crowded
+- Pages keep their own settings, like editable and full width, apart from system ones
+- Open several pages side by side in one tab, each running on its own
+- Watch live runs, workers and planes from their own sidebar pages
+- Tests split per package, with shared helpers in one place
+- One example opens a space with the bundled extensions and nothing else
+- A page opened before it finishes being created still comes up
+- Resize the sidebar, and cell controls show on hover and stay in view
+- A cell finishing no longer breaks drawing for the other cells on its page
+- Every cell renders the same way, and / inserts any registered snippet
+- Publish nuverse on its own tag so the extensions ship separately
+- Pick any registered snippet from the / menu
+- An open page runs every cell as soon as you land on it, even after a restart
+- Ship apps and snippets as nuverse, a separate package found on install
+- Run a cell the moment it is added to an open page, and stop it when removed
+- Forget old browser tabs on open, and give the web example prose and program cells
+- Open a space from one call or the command line, with extensions found on install
+- Serve the browser from a device that tracks tabs and never runs planes
+- Start, restart, reload and route planes through ordinary services on workers
+- Run cells on workers through one kernel that records, stops and reaps every run
+- Add the operations every part of a space is built from
+- Store planes, cells and runs apart, and let a program declare its own typed state
+- Clear the v3 source out of the way for the v4 rewrite
+
+## 0.3.1 — 2026-09-23
+
+- Opening a page no longer slows down with each extra cell on it
+- Navigating away clears the old page at once instead of blinking through it
+- Keep workers ready in advance, so opening a plane no longer waits for one to start
+- Draw a page without a web server loaded behind it, so it opens much sooner
+- Let a chat work as long as the work takes, and stop it only when it is stuck
+- Always get a way to say something else, whatever a turn drew
+- Watch a chat work step by step, and never get a broken answer
+- Ask a chat for something and it draws the answer and how you reply
+
 ## 0.3.0 — 2026-09-21
 
 - Make a chat, ask it for something, and watch it work the space

{nuspace-0.3.0 → nuspace-0.4.0}/Makefile

@@ -5,7 +5,7 @@ GREEN := \033[0;32m
 YELLOW := \033[1;33m
 NC := \033[0m
 
-UI_APP := ts
+UI_DIR := pkgs/ts/nuspace-ui
 
 help:
 	@echo "$(BLUE)nuspace$(NC)"
@@ -20,7 +20,7 @@ help:
 	@echo "  make test-cov        Run tests with coverage"
 	@echo "  make test-fast       Run tests (fail fast)"
 	@echo ""
-	@echo "$(GREEN)Code Quality:$(NC)"
+	@echo "$(GREEN)Code quality:$(NC)"
 	@echo "  make lint            Check code with ruff"
 	@echo "  make format          Format code with ruff"
 	@echo "  make check           Run format-check + lint"
@@ -28,7 +28,7 @@ help:
 	@echo "$(GREEN)nuspace-ui web:$(NC)"
 	@echo "  make web-install     npm install in the ui workspace"
 	@echo "  make web-dev         Run vite dev server"
-	@echo "  make web-build       Build the vite bundle into $(UI_APP)/dist"
+	@echo "  make web-build       Build the vite bundle into $(UI_DIR)/dist"
 	@echo ""
 	@echo "$(GREEN)Packages:$(NC)"
 	@echo "  make build-nuspace   Build the nuspace wheel"
@@ -88,17 +88,17 @@ check: format-check lint
 
 web-install:
 	@echo "$(BLUE)Installing ui deps...$(NC)"
-	cd $(UI_APP) && npm install
+	cd $(UI_DIR) && npm install
 	@echo "$(GREEN)Installed$(NC)"
 
 web-dev:
 	@echo "$(BLUE)Starting vite dev server...$(NC)"
-	cd $(UI_APP) && npm run dev
+	cd $(UI_DIR) && npm run dev
 
 web-build:
 	@echo "$(BLUE)Building nuspace-ui web bundle...$(NC)"
-	cd $(UI_APP) && npm run build
-	@echo "$(GREEN)Built: $(UI_APP)/dist/$(NC)"
+	cd $(UI_DIR) && npm run build
+	@echo "$(GREEN)Built: $(UI_DIR)/dist/$(NC)"
 
 build-nuspace:
 	@echo "$(BLUE)Building nuspace wheel...$(NC)"
@@ -109,8 +109,8 @@ build-ui: web-build
 	@echo "$(BLUE)Building nuspace-ui web-bundle wheel...$(NC)"
 	# --out-dir keeps the wheel out of dist/, which IS the vite output we
 	# force-include into it. Writing there packages the last wheel into the next.
-	cd $(UI_APP) && uv build --wheel --out-dir wheel-dist
-	@echo "$(GREEN)Built: $(UI_APP)/wheel-dist/$(NC)"
+	cd $(UI_DIR) && uv build --wheel --out-dir wheel-dist
+	@echo "$(GREEN)Built: $(UI_DIR)/wheel-dist/$(NC)"
 
 build-all: build-nuspace build-ui
 	@echo "$(GREEN)Both wheels built$(NC)"

{nuspace-0.3.0 → nuspace-0.4.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.5
 Name: nuspace
-Version: 0.3.0
-Summary: Nu runtime built on Nu. A self-hosted programmable space that runs Nu apps in a tree of containers and applications.
+Version: 0.4.0
+Summary: Nu runtime built on Nu. A self-hosted programmable space that runs Nu programs as a tree of planes and cells.
 Project-URL: Repository, https://github.com/nustackdev/nuspace
 Author-email: Gor Arakelyan <gorarkln@gmail.com>
 License-Expression: AGPL-3.0-or-later
@@ -16,10 +16,10 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.10
 Requires-Dist: click>=8.0
-Requires-Dist: nuagent>=0.1.3
-Requires-Dist: nucore>=0.5.2
-Requires-Dist: nuspace-ui>=0.3.0
-Requires-Dist: nustd[all]>=0.5.2
+Requires-Dist: nucore>=0.5.3
+Requires-Dist: nuspace-ui>=0.4.0
+Requires-Dist: nustd[all]>=0.5.3
+Requires-Dist: nuverse>=0.2.0
 Requires-Dist: rich-click>=1.6
 Requires-Dist: rich>=10.7
 Requires-Dist: typing-extensions>=4.7.0
@@ -29,8 +29,8 @@ Description-Content-Type: text/markdown
 
 Nu runtime built on Nu. Self-hosted.
 
-A tree of containers and applications.
-The runtime evaluates Nu apps, provides the fabrics they use (nustd.kv, nustd.proxy, nustd.mp_pool, nulog, nustd.ui), and renders a human interface for the ones that opt in.
+A tree of planes, each a group of cells.
+The runtime evaluates Nu programs, provides the fabrics they use (nustd.kv, nustd.proxy, nustd.mp_pool, nulog, nustd.ui), and renders a human interface for the ones that opt in.
 
 ## License
 

nuspace-0.4.0/README.md

@@ -0,0 +1,10 @@
+# nuspace
+
+Nu runtime built on Nu. Self-hosted.
+
+A tree of planes, each a group of cells.
+The runtime evaluates Nu programs, provides the fabrics they use (nustd.kv, nustd.proxy, nustd.mp_pool, nulog, nustd.ui), and renders a human interface for the ones that opt in.
+
+## License
+
+GNU Affero General Public License v3.0. See [LICENSE.md](LICENSE.md).

nuspace-0.4.0/examples/space.py

@@ -0,0 +1,35 @@
+"""A space in the browser, with nuverse and nothing else.
+
+Every Plane and snippet comes from nuverse, found through its entry point. The
+store is ``examples/space.db``, kept between runs.
+
+Run it::
+
+    python examples/space.py
+
+A browser opens on http://127.0.0.1:8080. Ctrl+C stops it.
+"""
+
+from __future__ import annotations
+
+import logging
+from pathlib import Path
+
+import nu
+import nuspace
+
+
+# Closing the space drops sockets under workers still holding them. Expected.
+# At module scope so spawned workers, which import this file, are quiet too.
+logging.getLogger("invisibles").setLevel(logging.CRITICAL)
+
+
+STORE = str(Path(__file__).parent / "space.db")
+
+
+if __name__ == "__main__":
+    # Load bearing: workers are spawned and re-import __main__.
+    try:
+        nu.run_in_loop(nuspace.open_space(STORE))
+    except KeyboardInterrupt:
+        print("stopped")

{nuspace-0.3.0 → nuspace-0.4.0}/pyproject.toml

@@ -4,25 +4,29 @@ build-backend = "hatchling.build"
 
 [project]
 name = "nuspace"
-version = "0.3.0"
-description = "Nu runtime built on Nu. A self-hosted programmable space that runs Nu apps in a tree of containers and applications."
+version = "0.4.0"
+description = "Nu runtime built on Nu. A self-hosted programmable space that runs Nu programs as a tree of planes and cells."
 readme = "README.md"
 license = "AGPL-3.0-or-later"
 authors = [{ name = "Gor Arakelyan", email = "gorarkln@gmail.com" }]
 requires-python = ">=3.10"
 dependencies = [
-    # The whole stack, every extra. A space runs arbitrary Nu apps and its own
-    # sections in pool workers, so it reaches most fabrics: kv for the store,
+    # The whole stack, every extra. A space runs arbitrary Nu programs and its own
+    # services in pool workers, so it reaches most fabrics: kv for the store,
     # ui for the browser, proxy (invisibles) for the worker's session, mp_pool
     # for the workers themselves. Picking extras just means discovering the
     # missing one at import time.
-    "nucore>=0.5.2",
-    "nustd[all]>=0.5.2",
+    "nucore>=0.5.3",
+    "nustd[all]>=0.5.3",
     # The compiled web bundle. A separate distribution only because PyPI caps
     # project size and a SPA rebuilt on every UI tweak would eat the quota --
     # not optional. `pip install nuspace` gives you the browser.
-    "nuspace-ui>=0.3.0",
-    "nuagent>=0.1.3",
+    "nuspace-ui>=0.4.0",
+    # The extensions a space offers out of the box: Planes, snippets. Always
+    # pulled, split into extras when its deps grow. nuspace never imports it:
+    # it is found through the `nuspace.extensions` entry point, like any
+    # third party.
+    "nuverse>=0.2.0",
     "typing-extensions>=4.7.0",
     "click>=8.0",
     "rich>=10.7",
@@ -52,23 +56,33 @@ classifiers = [
 Repository = "https://github.com/nustackdev/nuspace"
 
 [project.scripts]
-nuspace = "nuspace.cli:main"
+nuspace = "nuspace.host.cli:main"
 
 [tool.hatch.build.targets.wheel]
+# Whole directories, not python files: the agent's system prompt is prose in
+# `nuspace/agent/prompt/text/*.md`, read at runtime through
+# importlib.resources. hatchling ships every file under a listed package, so
+# this needs no data entry of its own -- but adding an `include` or
+# `only-include` here would drop the prose and leave a wheel whose chats
+# raise on their first message. Don't.
 packages = ["src/nuspace"]
 
 [tool.hatch.build.targets.sdist]
+# pkgs/ holds the sibling distributions (nuverse, nuspace-ui), each shipped
+# from its own directory on its own tag.
 exclude = [
-    "ts/node_modules",
-    "ts/dist",
+    "pkgs",
 ]
 
+[tool.uv.workspace]
+members = ["pkgs/nuverse"]
+
 [tool.uv.sources]
-nuspace-ui = { path = "./ts" }
+nuverse = { workspace = true }
+nuspace-ui = { path = "./pkgs/ts/nuspace-ui" }
 nucore = { path = "../nu", editable = true }
 nustd = { path = "../nu/pkgs/nustd", editable = true }
 nucli = { path = "../nu/pkgs/nucli", editable = true }
-nuagent = { path = "../nuagent", editable = true }
 
 [tool.uv]
 default-groups = ["dev"]
@@ -88,6 +102,11 @@ dev = [
 testpaths = [
     "tests",
 ]
+# `tests/_lib` is the only test directory on sys.path, and `_support` the only
+# thing in it: shared helpers, importable by spawned workers too.
+pythonpath = [
+    "tests/_lib",
+]
 python_files = ["test_*.py"]
 python_classes = ["Test*"]
 python_functions = ["test_*"]
@@ -128,6 +147,7 @@ line-length = 100
 target-version = "py310"
 src = [
     "src",
+    "pkgs/nuverse/src",
 ]
 extend-exclude = [".venv", "build", "dist", "*.egg-info"]
 
@@ -170,6 +190,7 @@ convention = "google"
 [tool.ruff.lint.isort]
 known-first-party = [
     "nuspace",
+    "nuverse",
     "nu",
     "nustd",
     "nucli",

nuspace-0.4.0/src/nuspace/__init__.py

@@ -0,0 +1,39 @@
+"""nuspace: runs Nu programs as a space of planes and cells.
+
+What a host and a program need, without knowing the layers:
+
+- :func:`open_space`, and :class:`Extension`, :class:`Plane`, :class:`Snippet`
+  to register (the store's own plane shape is ``shapes.Plane``), and
+  :data:`TEXT`, the name reserved for the text snippet;
+- :class:`CellState`, :class:`PlaneState`, so a program says
+  ``class Tick(nuspace.CellState)``;
+- :mod:`ops`, and the few a host reaches for first: :func:`boot`,
+  :func:`unboot`, :func:`supervise`, :func:`env`.
+
+Workers import this package: nothing here may pull in a server.
+"""
+
+from nuspace import ops, shapes
+from nuspace.host import Extension, open_space
+from nuspace.ops import TEXT, Plane, Snippet, env
+from nuspace.shapes import CellState, PlaneState, Space
+from nuspace.system.services import boot, supervise, unboot, unsupervise
+
+
+__all__ = [
+    "TEXT",
+    "CellState",
+    "Extension",
+    "Plane",
+    "PlaneState",
+    "Snippet",
+    "Space",
+    "boot",
+    "env",
+    "open_space",
+    "ops",
+    "shapes",
+    "supervise",
+    "unboot",
+    "unsupervise",
+]

nuspace-0.4.0/src/nuspace/host/__init__.py

@@ -0,0 +1,21 @@
+"""Layer three: the host composes the system.
+
+- :mod:`.registry`: extensions, their discovery, and the merged registry.
+- :mod:`.space`: :func:`open_space`, the whole system in one term.
+- :mod:`.cli`: the ``nuspace`` command. Not imported here: workers import
+  :mod:`nuspace`, and the command line is no business of theirs.
+"""
+
+from .registry import GROUP, Extension, Registry, RegistryWarning, discover
+from .space import open_space, space_registry
+
+
+__all__ = [
+    "GROUP",
+    "Extension",
+    "Registry",
+    "RegistryWarning",
+    "discover",
+    "open_space",
+    "space_registry",
+]

nuspace-0.4.0/src/nuspace/host/cli/__init__.py

@@ -0,0 +1,10 @@
+"""The ``nuspace`` command: open a space, served in a browser or headless.
+
+A space is a directory one process locks at a time, so either command holds
+it for as long as it is up.
+"""
+
+from .main import cli, main
+
+
+__all__ = ["cli", "main"]

nuspace-0.4.0/src/nuspace/host/cli/__main__.py

@@ -0,0 +1,11 @@
+"""Enables ``python -m nuspace.host.cli``.
+
+The guard is load bearing: workers are spawned, and a child re-imports
+whatever ``__main__`` is. Without it, opening a space forks forever.
+"""
+
+from .main import main
+
+
+if __name__ == "__main__":
+    main()