rdstudio 0.2.0__tar.gz → 0.4.0__tar.gz

{rdstudio-0.2.0 → rdstudio-0.4.0}/.gitignore

@@ -28,8 +28,13 @@ src/rdstudio/_node/
 # Release staging (mise run release:npm, and the release workflow)
 .release/
 npm-dist/
-# The SvelteKit app
+# The SvelteKit app, and the dashboard it builds (npm run build --workspace @rdstudio/app)
 app/.svelte-kit/
-app/build/
-app/static/
+src/rdstudio/web/
 # openapi.json and src/lib/api/ are generated (npm run generate) but committed, so builds need no server.
+
+# End-to-end screenshots (mise run e2e)
+.e2e/
+
+# The embedding model for search by meaning (T89): fetched, not kept in git (mise run embed:model)
+packages/cli/models/

{rdstudio-0.2.0 → rdstudio-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: rdstudio
-Version: 0.2.0
+Version: 0.4.0
 Summary: Agentic research and development studio: OKF knowledge bundles, a read-only dashboard, MCP and skills.
 Author: Lachlan Stewart
 License-File: LICENSE
@@ -84,6 +84,11 @@ tailscale serve --bg --https=8003 http://127.0.0.1:8003
 Use one port per project. `rdstudio serve --host 0.0.0.0` also works, but
 serves plain HTTP to your whole network.
 
+Anyone who can open the dashboard from `rdstudio serve` can edit notes in it
+(the Edit button on a note), with edits recorded as yours. Keep it to your own
+devices, as above, or start it with `rdstudio serve --read-only`. Exported
+snapshots (`rdstudio export`) are always read-only.
+
 Over HTTPS (or on localhost) the dashboard keeps a copy of itself and of the
 notes in the browser: after the first visit it reopens at once, even over a
 slow tunnel, and it can be read offline. Only changed notes are fetched again.
@@ -113,6 +118,21 @@ Add `?nosw` to the address to bypass the copy.
   # path = "~/knowledge/learning"   # optional: somewhere versioned and private
   ```
 
+- **Models inside the app** (Axis in the editor, Ask Atlas, the tutor) call
+  OpenRouter: connect an account on the Axis page. To use a gateway your
+  organisation runs instead (any OpenAI-compatible one, with its own
+  certificate authority, client certificate or proxy), add this to
+  `~/.config/rdstudio/config.toml` and run `rdstudio provider check`:
+
+  ```toml
+  [teacher.provider]
+  url = "https://ai.example.com/v1"
+  key_env = "MY_AI_KEY"
+  ca_file = "/etc/ssl/certs/my-org-ca.pem"
+  ```
+
+  Every setting, and where to patch what they do not cover, is in
+  `knowledge/procedures/enterprise-models.md`.
 - **Static site:** `rdstudio export <dir>` writes a snapshot that any static
   host can serve (see below).
 
@@ -171,7 +191,7 @@ Tasks live in `mise.toml`; run them with `mise run <task>` (`mise tasks` lists
 them), or run the command each one names.
 
 ```sh
-mise run setup      # Node 24 (mise), Python and npm dependencies, Chromium for the benchmarks
+mise run setup      # Node 24 (mise), Python and npm dependencies, the dashboard, Chromium for the benchmarks
 mise run test       # the Python tests, then the TypeScript packages
 mise run core:test  # the TypeScript core against the conformance fixtures
 mise run core:agree ~/notes/knowledge   # do the Python and TypeScript cores agree on a bundle?
@@ -195,7 +215,12 @@ two: the core on real bundles, every command's output, every file `build`,
 server's tools and replies. In a checkout, `rdstudio` runs the TypeScript
 sources directly; `mise run bundle` builds the single file a release ships.
 
+The dashboard is a SvelteKit app in `app/`. `mise run app:build` builds it into
+`src/rdstudio/web/`, where `rdstudio build` and `serve` find it (it is not
+committed, so a fresh checkout needs it once); `mise run app:dev` runs it with
+live reloading.
+
 ## Licence
 
 MIT. The bundled libraries and fonts keep their own licences, which are in
-`src/rdstudio/web/vendor/licenses/`.
+`app/static/vendor/licenses/`.

{rdstudio-0.2.0 → rdstudio-0.4.0}/README.md

@@ -71,6 +71,11 @@ tailscale serve --bg --https=8003 http://127.0.0.1:8003
 Use one port per project. `rdstudio serve --host 0.0.0.0` also works, but
 serves plain HTTP to your whole network.
 
+Anyone who can open the dashboard from `rdstudio serve` can edit notes in it
+(the Edit button on a note), with edits recorded as yours. Keep it to your own
+devices, as above, or start it with `rdstudio serve --read-only`. Exported
+snapshots (`rdstudio export`) are always read-only.
+
 Over HTTPS (or on localhost) the dashboard keeps a copy of itself and of the
 notes in the browser: after the first visit it reopens at once, even over a
 slow tunnel, and it can be read offline. Only changed notes are fetched again.
@@ -100,6 +105,21 @@ Add `?nosw` to the address to bypass the copy.
   # path = "~/knowledge/learning"   # optional: somewhere versioned and private
   ```
 
+- **Models inside the app** (Axis in the editor, Ask Atlas, the tutor) call
+  OpenRouter: connect an account on the Axis page. To use a gateway your
+  organisation runs instead (any OpenAI-compatible one, with its own
+  certificate authority, client certificate or proxy), add this to
+  `~/.config/rdstudio/config.toml` and run `rdstudio provider check`:
+
+  ```toml
+  [teacher.provider]
+  url = "https://ai.example.com/v1"
+  key_env = "MY_AI_KEY"
+  ca_file = "/etc/ssl/certs/my-org-ca.pem"
+  ```
+
+  Every setting, and where to patch what they do not cover, is in
+  `knowledge/procedures/enterprise-models.md`.
 - **Static site:** `rdstudio export <dir>` writes a snapshot that any static
   host can serve (see below).
 
@@ -158,7 +178,7 @@ Tasks live in `mise.toml`; run them with `mise run <task>` (`mise tasks` lists
 them), or run the command each one names.
 
 ```sh
-mise run setup      # Node 24 (mise), Python and npm dependencies, Chromium for the benchmarks
+mise run setup      # Node 24 (mise), Python and npm dependencies, the dashboard, Chromium for the benchmarks
 mise run test       # the Python tests, then the TypeScript packages
 mise run core:test  # the TypeScript core against the conformance fixtures
 mise run core:agree ~/notes/knowledge   # do the Python and TypeScript cores agree on a bundle?
@@ -182,7 +202,12 @@ two: the core on real bundles, every command's output, every file `build`,
 server's tools and replies. In a checkout, `rdstudio` runs the TypeScript
 sources directly; `mise run bundle` builds the single file a release ships.
 
+The dashboard is a SvelteKit app in `app/`. `mise run app:build` builds it into
+`src/rdstudio/web/`, where `rdstudio build` and `serve` find it (it is not
+committed, so a fresh checkout needs it once); `mise run app:dev` runs it with
+live reloading.
+
 ## Licence
 
 MIT. The bundled libraries and fonts keep their own licences, which are in
-`src/rdstudio/web/vendor/licenses/`.
+`app/static/vendor/licenses/`.

{rdstudio-0.2.0 → rdstudio-0.4.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rdstudio"
-version = "0.2.0"
+version = "0.4.0"
 description = "Agentic research and development studio: OKF knowledge bundles, a read-only dashboard, MCP and skills."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -22,14 +22,15 @@ build-backend = "hatchling.build"
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/rdstudio"]
-# The bundled Node program is built at release (npm run bundle) and not committed.
-artifacts = ["src/rdstudio/_node/*.mjs"]
+# The bundled Node program and the dashboard are built at release (npm run
+# bundle, npm run build --workspace @rdstudio/app) and not committed.
+artifacts = ["src/rdstudio/_node/*.mjs", "src/rdstudio/web/**"]
 
 [tool.hatch.build.targets.sdist]
 # Only the Python package (the TypeScript sources are on GitHub and npm), and
-# the bundle, since uv builds the wheel from this archive.
+# the built files, since uv builds the wheel from this archive.
 only-include = ["src/rdstudio", "README.md", "LICENSE"]
-artifacts = ["src/rdstudio/_node/*.mjs"]
+artifacts = ["src/rdstudio/_node/*.mjs", "src/rdstudio/web/**"]
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]

{rdstudio-0.2.0 → rdstudio-0.4.0}/src/rdstudio/__init__.py

@@ -1,3 +1,3 @@
 """rdstudio: an agentic research and development studio built on OKF."""
 
-__version__ = "0.2.0"
+__version__ = "0.4.0"