simplecadapi 2.2.1__tar.gz → 2.2.3__tar.gz

{simplecadapi-2.2.1 → simplecadapi-2.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: simplecadapi
-Version: 2.2.1
+Version: 2.2.3
 Summary: A simplified OCP-native CAD modeling Python API
 Project-URL: Homepage, https://github.com/PhySpace/SimpleCADAPI
 Project-URL: Repository, https://github.com/PhySpace/SimpleCADAPI
@@ -412,37 +412,21 @@ the full crank cycle sweeps clean in the same sim ·
 
 ---
 
-## Update Notes (2.2.1)
+## Update Notes (2.2.3)
 
 > Validate generated definitions, assembly constraints, and manufacturing
 > geometry before production use.
 
-- **New editor.** `sca edit` is part of the SDK now (`pip install
-  "simplecadapi[editor]"`). It runs a workspace's notebooks in a marimo kernel
-  with the SDK's own cell executor, previews the live model straight from the
-  solids, writes your viewport picks as selection code, and lets an agent see
-  what you see (`sca snapshot`). **Re-Studio is removed**: the reverse-
-  engineering studio (the `Re-mode` workspace of the standalone sca-web-editor)
-  is gone, and the standalone sca-web-editor is replaced by `sca edit`. STEP
-  reconstruction continues through the inspection API and the skill's
-  step-reconstruction workflow.
-- **One runtime, one cache.** The editor, `sca run` and
-  `simplecadapi.runtime.run_notebook()` share the per-cell cache, so what one
-  computed the others restore. Notebook parameters come from `# ---- params
-  ----` cells with an optional `# ui:` comment; local modules (shared
-  dimensions) get their own view in the editor.
-- **Landing path.** `docs/landing.md` is the script an agent follows to install
-  the SDK and its skill and open an example; `sca example u_link` copies the
-  bundled workspace and `sca skill where` shows where the skill goes.
-- Earlier: 2.1.3b1 shipped the addon ecosystem (`sca addon ...`, the
-  `sca-addon.toml` descriptor, the `.scadpkg` format spec); see its
-  [update notes](docs/updates/2.1.3b1.md).
-
-Every example model is a notebook; its export scripts load the product with
-`run_notebook`, capture one `.scadpkg`, and translate AP242 `.step` and
-editable `.FCStd` from that same package. The AP242/Gmsh example under
-`examples/ap242_gmsh_volume_mesh/` exposes each export and FEM stage as a
-separate directly runnable script.
+- **The editor takes in edits made to the notebook file.** An agent's saved change is applied
+  cell by cell (changed cells update and run again, no reload), and is no longer written over by
+  the editor. If a cell was edited in both places, the file's version is kept and your unsaved
+  text goes to the log. Notebooks added to the workspace appear in the list by themselves.
+- **`sca cell` and `sca new`.** `sca cell ls|get|put|insert|rm|run` edits the open notebook's cells
+  through the running editor (the page updates live, each write prints the cell's status and
+  errors); `sca new NAME` creates a notebook the editor then lists.
+
+Full notes for this version: [`docs/updates/2.2.3.md`](docs/updates/2.2.3.md).
+Earlier versions: the [changelog](CHANGELOG.md) and [`docs/updates/`](docs/updates/).
 
 ---
 
@@ -462,7 +446,7 @@ in a compact public API for creating solids, applying features, tagging semantic
 intent, querying topology, exporting manufacturing files, and translating recorded
 models into FreeCAD workflows.
 
-Current release: `simplecadapi==2.2.1`.
+Current release: `simplecadapi==2.2.3`.
 
 ## What It Provides
 
@@ -977,6 +961,8 @@ and the [STEP reconstruction workflow](docs/skill/references/workflows/step-reco
 
 ## Documentation
 
+- 2.2.3 update notes: [`docs/updates/2.2.3.md`](docs/updates/2.2.3.md)
+- 2.2.2 update notes: [`docs/updates/2.2.2.md`](docs/updates/2.2.2.md)
 - 2.2.1 update notes: [`docs/updates/2.2.1.md`](docs/updates/2.2.1.md)
 - 2.1.3b1 update notes: [`docs/updates/2.1.3b1.md`](docs/updates/2.1.3b1.md)
 - 2.1.2 update notes: [`docs/updates/2.1.2.md`](docs/updates/2.1.2.md)

{simplecadapi-2.2.1 → simplecadapi-2.2.3}/README.md

@@ -149,37 +149,21 @@ the full crank cycle sweeps clean in the same sim ·
 
 ---
 
-## Update Notes (2.2.1)
+## Update Notes (2.2.3)
 
 > Validate generated definitions, assembly constraints, and manufacturing
 > geometry before production use.
 
-- **New editor.** `sca edit` is part of the SDK now (`pip install
-  "simplecadapi[editor]"`). It runs a workspace's notebooks in a marimo kernel
-  with the SDK's own cell executor, previews the live model straight from the
-  solids, writes your viewport picks as selection code, and lets an agent see
-  what you see (`sca snapshot`). **Re-Studio is removed**: the reverse-
-  engineering studio (the `Re-mode` workspace of the standalone sca-web-editor)
-  is gone, and the standalone sca-web-editor is replaced by `sca edit`. STEP
-  reconstruction continues through the inspection API and the skill's
-  step-reconstruction workflow.
-- **One runtime, one cache.** The editor, `sca run` and
-  `simplecadapi.runtime.run_notebook()` share the per-cell cache, so what one
-  computed the others restore. Notebook parameters come from `# ---- params
-  ----` cells with an optional `# ui:` comment; local modules (shared
-  dimensions) get their own view in the editor.
-- **Landing path.** `docs/landing.md` is the script an agent follows to install
-  the SDK and its skill and open an example; `sca example u_link` copies the
-  bundled workspace and `sca skill where` shows where the skill goes.
-- Earlier: 2.1.3b1 shipped the addon ecosystem (`sca addon ...`, the
-  `sca-addon.toml` descriptor, the `.scadpkg` format spec); see its
-  [update notes](docs/updates/2.1.3b1.md).
-
-Every example model is a notebook; its export scripts load the product with
-`run_notebook`, capture one `.scadpkg`, and translate AP242 `.step` and
-editable `.FCStd` from that same package. The AP242/Gmsh example under
-`examples/ap242_gmsh_volume_mesh/` exposes each export and FEM stage as a
-separate directly runnable script.
+- **The editor takes in edits made to the notebook file.** An agent's saved change is applied
+  cell by cell (changed cells update and run again, no reload), and is no longer written over by
+  the editor. If a cell was edited in both places, the file's version is kept and your unsaved
+  text goes to the log. Notebooks added to the workspace appear in the list by themselves.
+- **`sca cell` and `sca new`.** `sca cell ls|get|put|insert|rm|run` edits the open notebook's cells
+  through the running editor (the page updates live, each write prints the cell's status and
+  errors); `sca new NAME` creates a notebook the editor then lists.
+
+Full notes for this version: [`docs/updates/2.2.3.md`](docs/updates/2.2.3.md).
+Earlier versions: the [changelog](CHANGELOG.md) and [`docs/updates/`](docs/updates/).
 
 ---
 
@@ -199,7 +183,7 @@ in a compact public API for creating solids, applying features, tagging semantic
 intent, querying topology, exporting manufacturing files, and translating recorded
 models into FreeCAD workflows.
 
-Current release: `simplecadapi==2.2.1`.
+Current release: `simplecadapi==2.2.3`.
 
 ## What It Provides
 
@@ -714,6 +698,8 @@ and the [STEP reconstruction workflow](docs/skill/references/workflows/step-reco
 
 ## Documentation
 
+- 2.2.3 update notes: [`docs/updates/2.2.3.md`](docs/updates/2.2.3.md)
+- 2.2.2 update notes: [`docs/updates/2.2.2.md`](docs/updates/2.2.2.md)
 - 2.2.1 update notes: [`docs/updates/2.2.1.md`](docs/updates/2.2.1.md)
 - 2.1.3b1 update notes: [`docs/updates/2.1.3b1.md`](docs/updates/2.1.3b1.md)
 - 2.1.2 update notes: [`docs/updates/2.1.2.md`](docs/updates/2.1.2.md)

{simplecadapi-2.2.1 → simplecadapi-2.2.3}/docs/landing.md

@@ -195,6 +195,9 @@ each instruction to one action and wait for them.
      these edges by 1 mm"). You read the selection from the file (`selection` cell) or with
      `sca snapshot`, and you can look at `.sca-editor/viewport.png` to see what they see. Then
      you edit the notebook; they see your change in the editor.
+   - **Work through the editor.** Change cells with `sca cell` (`sca cell ls`, `put`, `insert`):
+     the page updates live and nothing the person typed is overwritten. Editing the file works
+     too: the editor takes the change in within a second.
    - **"Change this cell."** Every cell has a copy button that copies a reference such as
      `/path/u_link.py:L47-L48 (cell 02 ...)`. They paste it to you with what they want changed,
      and you edit exactly those lines.

{simplecadapi-2.2.1 → simplecadapi-2.2.3}/docs/skill/SKILL.md

@@ -4,9 +4,9 @@ description: Build, assemble, inspect, reconstruct, and export parametric CAD mo
 license: Apache-2.0
 metadata:
   project: simplecadapi
-  version: 2.2.1
+  version: 2.2.3
   package-name: simplecadapi
-  package-version: 2.2.1
+  package-version: 2.2.3
 ---
 
 # SimpleCAD SDK Skill
@@ -50,7 +50,9 @@ Paths are relative to this file's directory.
   selected, and you MUST read
   `references/domains/editor-collaboration.md` first to see what they
   see (selection cell, `sca snapshot`, cell references) and how to
-  hand the work back.
+  hand the work back. While the editor runs, change its notebooks with
+  `sca cell` (or the file; never both blindly): the editor is the
+  file's writer.
 - Creating, installing, updating, or removing a SimpleCADAPI addon (a
   third-party skill+tooling package around `.scadpkg`) enters no
   workflow; you MUST use `references/domains/addon-development.md`
@@ -202,7 +204,7 @@ print(len(rebuilt))
 - `references/inspect/brep-reverse-engineering.md`
 - `references/domains/addon-development.md` — `sca` addon CLI and authoring guide
 - `references/domains/editor-collaboration.md` — working with a person in `sca edit`:
-  selection cell, snapshot, cell references, parameters
+  selection cell, snapshot, cell references, `sca cell` / `sca new`, parameters
 - `references/docs/guides/reconstruction-agent-test-prompt.md`
 - `references/docs/guides/reconstruction-agent-strategy.md`
 - `references/docs/guides/notebook-runtime.md`

{simplecadapi-2.2.1 → simplecadapi-2.2.3}/docs/skill/references/domains/editor-collaboration.md

@@ -6,11 +6,26 @@ edit code. It is not a workflow. The modeling you do still follows the workflow
 you selected; this page says how to see what the person sees and how to hand
 work back.
 
-The notebook file is the only shared state. The editor autosaves every edit to
+The notebook file is the shared state. The editor autosaves every edit to
 it, and every message the person gives you (a selection, a cell reference, a
 tuned value) is also something you can read from disk. Never rely on what the
 person says they selected when the file or the snapshot can tell you.
 
+The editor holds the open notebook in memory and is the one writer of its
+file. You have two safe ways to change it while it runs; use the first:
+
+1. **`sca cell` (preferred).** It edits through the editor: the page shows the
+   change live (no reload, no flicker), the cell runs, and you get its state back.
+2. **Edit the file.** The editor notices a saved change within a second, compares
+   it with its cells and applies only what differs (changed cells are edited in
+   place and run again, added or removed cells appear or go away). A change to the
+   setup cell or an `@app.function` cell restarts the kernel instead. A file that
+   does not parse is ignored until the next save that does.
+
+If the person has the same cell open with unsaved typing, **your version wins**:
+their text is dropped and kept in the editor's log for them. Do not rewrite a
+cell the person is typing in without telling them.
+
 ## Start the editor for a person
 
 ```bash
@@ -28,6 +43,29 @@ sca edit <workspace> --no-browser --port 7180
   the assembly that fixes them together) to `./u_link_motor_mount`, then
   `sca edit ./u_link_motor_mount`.
 
+## Edit cells through the editor: `sca cell`
+
+```bash
+sca cell ls [--code]                 # numbered cells with status, errors and output
+sca cell get 3                       # one cell: code, status, errors, output
+echo 'L = 90' | sca cell put 3       # replace the code of cell 3 and run it (--no-run to only save)
+sca cell insert --after 3 -f new.py  # add a cell (--after start|end|CELL, --name fn_name)
+sca cell rm 4
+sca cell run [CELL ...]              # run cells (default all) and what they feed
+sca new bracket --kind part          # a new notebook; the open editor lists it, the person's view stays
+```
+
+- A cell is named by its number in `sca cell ls`, its `key`, its function name, or its id.
+  Numbers move when cells are added or removed: read the list the command prints back.
+- Each write prints the touched cell's state (`status`, `errors`, `output`). That is the
+  feedback: read it before the next step, as with any other operation.
+- `put` fails with a conflict if you pass a base that is out of date; without one it
+  replaces the cell, so `get` first when the person may have changed it.
+- The commands find the running editor through `<workspace>/.sca-editor/server.json`. With no
+  editor running, or with another notebook open, `ls` and `get` read the file and the write
+  commands refuse: then edit the file directly, nothing else holds it.
+- `@app.function` cells cannot be changed this way; edit them in the file.
+
 ## Read what the person is doing
 
 | Need | Where |
@@ -140,10 +178,12 @@ file first, since every cell is blocked until it compiles.
 
 ## Rules of thumb
 
-- Re-read the file before editing: the person edits and autosaves too, and the
-  editor rewrites the selection cell.
-- Edit by cell. A change that touches many cells at once makes the person's
+- Re-read the cell before editing (`sca cell get`, or the file): the person edits and
+  autosaves too, and the editor rewrites the selection cell.
+- Edit by cell, with `sca cell`. A change that touches many cells at once makes the person's
   screen reflow and loses their place.
+- New notebooks: `sca new`, not a bare file write plus a request to refresh; the editor
+  lists a new file by itself either way.
 - After an edit, say which cells you changed (by reference) and what to look
   at, so the person can run them and judge the result.
 - Never edit `__marimo__/` or `.sca-editor/`; both are generated.

simplecadapi-2.2.3/docs/updates/2.2.2.md

@@ -0,0 +1,27 @@
+# 2.2.2 Update Notes
+
+Two additions to the code-first editor (`sca edit`), and a fix that made one of them usable.
+
+## Code completion from the SDK
+
+`scad.` (and `scad.ql.`, `scad.std.gear.`, `ql.`, `Q.`) lists the real functions with their
+signatures; the side panel shows every parameter with its default and the docstring.
+
+- Accepting a function, or typing `(` after a known name, writes the call with every
+  **required** parameter as `name=`: `scad.make_box_rsolid(width=, height=, depth=)`.
+  **Tab** moves to the next parameter.
+- Inside a call, the parameters not given yet complete as `name=`, required ones first.
+- The names come from the running package (`GET /api/sdk`), so they cannot drift from the code.
+
+## Create a notebook from the workspace tab
+
+A **new** action in the notebooks header starts a notebook from the SDK's template: a part, or an
+assembly that uses the first two parts of the workspace. The name is checked as you type. An empty
+workspace opens on that form, so `sca edit` on an empty directory is usable.
+
+## Fixed
+
+The cell editors rebuilt their configuration on every render, which dropped a snippet in progress
+and could disturb typing; the editor's `onChange` and options are stable now.
+
+See the [changelog](../../CHANGELOG.md) for the complete list.

simplecadapi-2.2.3/docs/updates/2.2.2.zh-CN.md

@@ -0,0 +1,25 @@
+# 2.2.2 更新说明
+
+`sca edit` 编辑器的两项新增，以及一个让其中一项能正常使用的修复。
+
+## 来自 SDK 的代码补全
+
+输入 `scad.`（以及 `scad.ql.`、`scad.std.gear.`、`ql.`、`Q.`）会列出真实存在的函数和签名；
+右侧面板显示每个参数、默认值和文档说明。
+
+- 选中一个函数，或在已知函数名后输入 `(`，会把每个**必填**参数写成 `name=`：
+  `scad.make_box_rsolid(width=, height=, depth=)`。**Tab** 跳到下一个参数。
+- 在调用括号内，还没写的参数会补全成 `name=`，必填的排在最前。
+- 名字来自正在运行的包（`GET /api/sdk`），不会和代码不一致。
+
+## 在工作区页面创建 notebook
+
+notebooks 标题处新增 **new**，按 SDK 模板创建 notebook：一个零件，或一个使用工作区前两个零件的装配。
+边输入边检查名字。空工作区会直接打开这个表单，所以对空目录运行 `sca edit` 也能用了。
+
+## 修复
+
+cell 编辑器每次渲染都会重建配置，导致进行中的占位跳转丢失，也可能干扰输入；现在编辑器的
+`onChange` 和选项都是稳定的。
+
+完整列表见[更新日志](../../CHANGELOG.md)。

simplecadapi-2.2.3/docs/updates/2.2.3.md

@@ -0,0 +1,37 @@
+# 2.2.3 Update Notes
+
+The editor (`sca edit`) and an agent can now work on the same notebook without overwriting each other.
+
+## The editor takes in edits made to the file
+
+Before, the editor held the open notebook in memory and rewrote the file on each edit, so a change
+an agent saved was overwritten by the editor's next save and never shown. Now the file is watched:
+a saved change is compared with the editor's cells and applied cell by cell. Changed cells are
+updated and run again, added or removed cells appear or go away, and the page does not reload or
+flicker. A change to the setup cell or an `@app.function` cell restarts the kernel instead; a file
+that does not parse is ignored until the next save that does.
+
+If a cell was edited in both places, **the file's version is kept** and the text you had not saved
+goes to the log at the bottom. Notebooks added to or removed from the workspace appear in the list
+by themselves.
+
+## `sca cell` and `sca new`
+
+```bash
+sca cell ls [--code]                 # numbered cells with status, errors and output
+sca cell get 3
+echo 'L = 90' | sca cell put 3       # replace a cell's code and run it
+sca cell insert --after 3 -f new.py
+sca cell rm 4
+sca cell run [CELL ...]
+sca new bracket --kind part          # a new notebook, listed by the running editor
+```
+
+These go through the running editor, found by `<workspace>/.sca-editor/server.json`: the page shows
+the change live and each write prints the touched cell's status, errors and output. With no editor
+running, or another notebook open, `ls` and `get` read the file and the write commands refuse: edit
+the file directly then.
+
+The skill (`editor-collaboration`) and `landing.md` now tell agents to work this way.
+
+See the [changelog](../../CHANGELOG.md) for the complete list.

simplecadapi-2.2.3/docs/updates/2.2.3.zh-CN.md

@@ -0,0 +1,33 @@
+# 2.2.3 更新说明
+
+`sca edit` 编辑器和 agent 现在可以同时处理同一个 notebook，互不覆盖。
+
+## 编辑器会接收对文件的修改
+
+以前编辑器把打开的 notebook 放在内存里，每次编辑都重写文件，agent 保存的修改会被编辑器的下一次保存
+覆盖，也不会显示出来。现在编辑器会监视文件：保存后的修改会与编辑器里的 cell 对比，按 cell 逐个应用。
+变化的 cell 会更新并重新运行，新增或删除的 cell 会出现或消失，页面不会刷新或闪烁。setup cell 或
+`@app.function` cell 的修改会重启 kernel；无法解析的文件会被忽略，直到下一次可解析的保存。
+
+如果同一个 cell 两边都改了，**保留文件里的版本**，你还没保存的文字会记在底部日志里。工作区里新增或删除的
+notebook 会自动出现在列表中。
+
+## `sca cell` 和 `sca new`
+
+```bash
+sca cell ls [--code]                 # 带编号的 cell，含状态、错误和输出
+sca cell get 3
+echo 'L = 90' | sca cell put 3       # 替换 cell 代码并运行
+sca cell insert --after 3 -f new.py
+sca cell rm 4
+sca cell run [CELL ...]
+sca new bracket --kind part          # 新建 notebook，运行中的编辑器会列出它
+```
+
+这些命令通过运行中的编辑器工作（由 `<workspace>/.sca-editor/server.json` 找到）：页面实时显示修改，每次写入
+都会打印被改 cell 的状态、错误和输出。没有运行中的编辑器，或编辑器打开的是别的 notebook 时，`ls` 和 `get`
+读取文件，写命令会拒绝：这时直接编辑文件即可。
+
+skill（`editor-collaboration`）和 `landing.md` 已让 agent 按这种方式工作。
+
+完整列表见[更新日志](../../CHANGELOG.md)。

{simplecadapi-2.2.1 → simplecadapi-2.2.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "simplecadapi"
-version = "2.2.1"
+version = "2.2.3"
 description = "A simplified OCP-native CAD modeling Python API"
 readme = "README.md"
 license = { file = "LICENSE" }

simplecadapi-2.2.3/src/simplecadapi/editor/apiindex.py

@@ -0,0 +1,120 @@
+"""The SDK's public API as plain data, for the editor's code completion.
+
+The cell editor completes ``scad.<name>``, and a call's parameters as ``name=`` placeholders, from
+this index.  It is read from the live package (``inspect``), so it is always the API of the
+version that is running and cannot drift from the code.  Namespaces are the places a notebook
+reaches names through: ``scad`` (the package), ``scad.ql`` and ``scad.std.<module>``.
+"""
+
+from __future__ import annotations
+
+import functools
+import inspect
+import types
+from typing import Any
+
+import simplecadapi
+
+_KINDS = {
+    inspect.Parameter.POSITIONAL_ONLY: "p",
+    inspect.Parameter.POSITIONAL_OR_KEYWORD: "",
+    inspect.Parameter.KEYWORD_ONLY: "",
+    inspect.Parameter.VAR_POSITIONAL: "a",
+    inspect.Parameter.VAR_KEYWORD: "w",
+}
+_DOC_LIMIT = 240
+_DEFAULT_LIMIT = 40
+
+
+def _summary(obj: Any) -> str:
+    """The first paragraph of the docstring, on one line."""
+
+    doc = inspect.getdoc(obj) or ""
+    first = doc.strip().split("\n\n", 1)[0]
+    text = " ".join(first.split())
+    return text if len(text) <= _DOC_LIMIT else text[: _DOC_LIMIT - 1].rstrip() + "…"
+
+
+def _parameters(obj: Any) -> list[dict[str, Any]] | None:
+    try:
+        signature = inspect.signature(obj)
+    except (TypeError, ValueError):
+        return None
+    rows: list[dict[str, Any]] = []
+    for parameter in signature.parameters.values():
+        if parameter.name == "self" or parameter.name.startswith("_"):
+            continue
+        required = parameter.default is inspect.Parameter.empty and parameter.kind in (
+            inspect.Parameter.POSITIONAL_ONLY,
+            inspect.Parameter.POSITIONAL_OR_KEYWORD,
+            inspect.Parameter.KEYWORD_ONLY,
+        )
+        row: dict[str, Any] = {"n": parameter.name, "r": required, "k": _KINDS[parameter.kind]}
+        if parameter.default is not inspect.Parameter.empty and not str(parameter.default).startswith("<"):
+            text = repr(parameter.default)
+            row["d"] = text if len(text) <= _DEFAULT_LIMIT else text[: _DEFAULT_LIMIT - 1] + "…"
+        rows.append(row)
+    return rows
+
+
+def _entry(name: str, obj: Any) -> dict[str, Any] | None:
+    if inspect.isclass(obj):
+        kind = "c"
+    elif inspect.isfunction(obj) or inspect.isbuiltin(obj):
+        kind = "f"
+    else:
+        return None
+    parameters = _parameters(obj)
+    if parameters is None:
+        return None
+    return {"n": name, "k": kind, "p": parameters, "d": _summary(obj)}
+
+
+def _ours(obj: Any) -> bool:
+    """Defined by the SDK itself, not a typing helper or another library re-exported."""
+
+    module = getattr(obj, "__module__", "") or ""
+    return module == "simplecadapi" or module.startswith("simplecadapi.")
+
+
+def _entries(module: types.ModuleType, names: list[str] | None = None, *, own: bool = False) -> list[dict[str, Any]]:
+    """Entries for the callables of *module*; with *own*, only those defined in that module (not re-exports)."""
+
+    rows = []
+    for name in sorted(names if names is not None else dir(module)):
+        if name.startswith("_"):
+            continue
+        obj = getattr(module, name, None)
+        if obj is None or isinstance(obj, types.ModuleType) or not _ours(obj):
+            continue
+        if own and not (getattr(obj, "__module__", "") or "").startswith(module.__name__):
+            continue
+        row = _entry(name, obj)
+        if row is not None:
+            rows.append(row)
+    return rows
+
+
+@functools.lru_cache(maxsize=1)
+def build_index() -> dict[str, Any]:
+    """``{"namespaces": {path: [entry]}, "submodules": {path: [name]}}``.
+
+    An entry is ``{"n": name, "k": "f"|"c", "p": [parameter], "d": summary}``; a parameter is
+    ``{"n": name, "r": required, "k": "p"|"a"|"w"|"", "d"?: default}`` (``p`` positional only,
+    ``a`` the ``*args`` one, ``w`` the ``**kwargs`` one).
+    """
+
+    from simplecadapi import ql, std
+
+    namespaces: dict[str, list[dict[str, Any]]] = {
+        "scad": _entries(simplecadapi, list(getattr(simplecadapi, "__all__", dir(simplecadapi)))),
+        "scad.ql": _entries(ql, own=True),
+    }
+    std_modules = sorted(
+        name for name in dir(std) if not name.startswith("_") and isinstance(getattr(std, name), types.ModuleType)
+    )
+    for name in std_modules:
+        module = getattr(std, name)
+        namespaces[f"scad.std.{name}"] = _entries(module, list(getattr(module, "__all__", dir(module))), own=True)
+    submodules = {"scad": ["ql", "std"], "scad.std": std_modules}
+    return {"version": getattr(simplecadapi, "__version__", ""), "namespaces": namespaces, "submodules": submodules}