mainsequence-metatable 0.1.18.dev30__tar.gz → 0.1.19.dev31__tar.gz

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/.agents/skills/client/metatables-local-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: metatables-local-development
-description: "Develop and test applications using the installed MetaTables client against local SQLite before returning to the intended environment database. Covers project/API/Admin setup, runtime verification, isolated fixtures, application-owned migrations and switching back after verification. Excludes MetaTables client/API implementation and hosted frontend deployment."
+description: "Develop and test applications using the installed MetaTables client against local SQLite before returning to the intended environment database. Covers project/API/Admin setup, runtime verification, isolated fixtures, application-owned migrations and returning to the environment after verification. Excludes MetaTables client/API implementation and hosted frontend deployment."
 ---
 
 # Local-first MetaTables application development
@@ -25,17 +25,17 @@ Three controls have different meanings:
 
 - `local_mode_available: true` permits local development; it does not select the
   current database. `metatables init --local` prepares this configuration.
-- `metatables serve --local` starts the API in Local mode. Add `--admin` to run
-  the existing Vite development frontend. Admin Settings can subsequently switch
-  that running API to Hosted without changing its loopback address.
-- Global `metatables --local ...` and `configure_local_client()` select the
-  project's running API connection. They do not force its database back to Local.
+- `metatables serve --local` starts the laptop's one local API, always in Local
+  mode. Add `--admin` to run the existing Vite development frontend. Running it in
+  another project while the API is up reports the running API and exits.
+- Global `metatables --local ...` and `configure_local_client()` select that
+  running API from any checkout.
 
 Before migrations or a batch of test writes, inspect the API's actual runtime.
 A loopback URL, a local token, a test namespace or an updater hash is not proof of
 storage isolation. Require `local_mode: true`; after initialization also require
 `dialect: sqlite` and the expected local runtime DataSource. If these disagree,
-stop the mutating work and select Local in Settings or restart with `serve --local`.
+stop the mutating work and restart with `serve --local`.
 Do not retry against automatic hosted discovery when a local connection fails.
 
 ## One local runtime per laptop
@@ -131,8 +131,8 @@ Run pure contract/frame checks first, then the smallest useful API integration
 case: apply the reviewed provider, seed a small fixture, execute the query or
 producer, read and assert its output, and repeat to verify the intended incremental
 or idempotent behavior. For a persistence claim, restart and read existing rows
-before seeding again. Recheck runtime state after any restart or mode/source change;
-do not switch modes while tests or producers are running.
+before seeding again. Recheck runtime state after any restart or source change;
+do not change the runtime source while tests or producers are running.
 
 Local storage persists across launches, and other projects' tables and fixtures share
 the same runtime. A new branch or project does not create a fresh test database. Use
@@ -153,11 +153,11 @@ Revisions need no SQLite variants: column and constraint changes run through Ale
 batch mode. Only raw PostgreSQL SQL must check `op.get_bind().dialect.name`. Do not use the shared environment database as the default
 integration-test fixture.
 
-## Finish verification and switch back
+## Finish verification and return to the environment
 
 Record what passed, the runtime/DataSource used, and any engine-specific work still
 unverified. Commit the reviewed application code and its migration revisions together;
-local rows, catalog UIDs, credentials and fixture data are not promoted by a switch.
+local rows, catalog UIDs, credentials and fixture data are never promoted.
 The application's deployment workflow applies those revisions to the hosted runtime
 before the code rolls out; see the [migrations skill](../metatables-migrations/SKILL.md)
 and `docs/client/deploy-application-migrations.md`. Add the migration Job if the
@@ -165,20 +165,15 @@ workflow lacks one.
 
 When returning to the environment is part of the requested workflow:
 
-1. Finish local tests and stop active writers. In Admin **Settings → Runtime mode**,
-   inspect the displayed hosted environment and use **Switch to Hosted**. Hosted
-   opens the runtime database the API's deployment declares, through the same
-   Environment Secret; there is no DataSource to choose and the launcher never
-   migrates it. This changes the API worker and database; it does not copy or merge
-   the local database. Leave local capability enabled if the developer needs to
-   switch back later.
+1. Finish local tests and stop active writers. The local API stays Local; it has
+   no switch to Hosted. Reach the environment through its deployed API: start a
+   fresh client process without `--local` or `configure_local_client()`, following
+   the installation guide's hosted endpoint selection, and use the deployed Admin
+   for hosted data. Remove only transport overrides introduced for local work.
 2. Re-read runtime status and verify `local_mode: false`, the intended verified
    hosted environment, the expected DataSource and readiness. `migration_required`
-   means the branch has system migrations the deployed API does not have yet; it
-   clears once that code is deployed. The same local
-   connection command still reaches this supervised API; its `--local` flag alone
-   does not prove SQLite. If the switch fails and the old worker is restored,
-   report the actual mode instead of claiming the switch succeeded.
+   means the deployed API's database has pending system migrations; its deployment
+   applies them.
 3. Restart application/test client processes and resolve catalog bindings again.
    Do not reuse local table UIDs or already-bound updater instances against the
    environment database. Do not apply application revisions from this session;
@@ -187,10 +182,6 @@ When returning to the environment is part of the requested workflow:
    requested scope; passing local tests is not itself a request to seed fixtures
    or run backfills.
 
-If the user instead wants to connect to a separately deployed API, follow the
-installation guide's hosted endpoint selection. Restore prior connection settings
-and start a fresh client process without `configure_local_client()`; remove only
-transport overrides introduced for local work. Do not redirect the SDK platform
-endpoint, invent `serve --hosted`, or use an environment-variable runtime toggle.
-A task limited to local development can finish with verified local results and
-clear remaining steps, without switching the runtime or modifying hosted data.
+Do not redirect the SDK platform endpoint, invent `serve --hosted`, or use an
+environment-variable runtime toggle. A task limited to local development can finish
+with verified local results and clear remaining steps, without modifying hosted data.

{mainsequence_metatable-0.1.18.dev30/src/mainsequence_metatable.egg-info → mainsequence_metatable-0.1.19.dev31}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.18.dev30
+Version: 0.1.19.dev31
 Summary: Main Sequence MetaTables Python client and standalone API
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/adr/api/0001-unified-api-storage-and-local-sqlite.md

@@ -6,6 +6,12 @@
 > conflicting application-migration execution and credential restrictions;
 > governed API operations and MetaTables system migrations remain separate.
 
+> Amendment (2026-10-03): the developer launcher is always Local. Runtime switching
+> (`POST /runtime-mode/`, **Settings → Runtime mode**, `.local/runtime-selection.json`
+> and the launcher's Hosted worker) is removed, superseding this ADR's switching
+> sections. Hosted data is reached through the deployed API and Admin, or from a
+> client without `--local`.
+
 
 Date: 2026-09-28
 

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/adr/client/0011-cli-local-development-with-managed-admin.md

@@ -5,6 +5,13 @@
 > Applications now load providers and execute Alembic through the client using
 > their environment connection. Launcher/Admin installation decisions remain valid.
 
+> Amendment (2026-10-03): the laptop runs one local API, matching its one local
+> runtime. The launcher publishes its connection as `server.json` in the local storage
+> directory instead of a per-project `.local/development-client.json`, and every
+> checkout connects through it. `serve --local` in another project reports the
+> running API and exits. The API no longer rejects clients from another checkout
+> or branch, and commits never require an API restart.
+
 
 Date: 2026-09-30
 
@@ -200,7 +207,8 @@ SDK authentication and API identity refresh requirements still apply.
 | Location | Contents and execution context |
 | --- | --- |
 | Consuming application's Python environment | Installed MetaTables client/API and application migration providers. Use this interpreter to start the API. |
-| Consuming application directory | `configuration.yaml`, Git context, runtime selection and `.local/development-client.json`. This is the API working directory. |
+| Consuming application directory | `configuration.yaml`, Git context and runtime selection of the project that launched the API. This is the API working directory. |
+| Local storage directory | The shared SQLite runtime and `server.json`, the running API's private connection for every checkout. |
 | Managed Admin directory or `--admin-path` | Frontend source, `package-lock.json` and `node_modules`. This is Vite's working directory. |
 | Existing API-selected storage | SQLite system catalog, credentials and application rows; initialization and selection remain API-owned. |
 

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/api/authentication-and-errors.md

@@ -41,8 +41,8 @@ admission after cache expiry, with a maximum one-hour cache lifetime. Reads do
 not extend that lifetime. Table and namespace grants are checked live against
 the catalog, so their revocation does not wait for the platform-fact cache.
 An expired entry whose refresh fails returns 503; it cannot supply stale access.
-Restart the API after changing its SDK account or endpoint. Worker restarts and
-runtime-mode changes discard caches. No cache environment variables are needed.
+Restart the API after changing its SDK account or endpoint. Worker restarts
+discard caches. No cache environment variables are needed.
 
 Environment display metadata is cached separately for one hour, including
 not-found and unavailable results. `/runtime-context/` still reads current runtime,

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/api/openapi.json

@@ -3148,16 +3148,6 @@
               }
             ]
           },
-          "hosted_environment_target": {
-            "anyOf": [
-              {
-                "$ref": "#/components/schemas/HostedEnvironment"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
           "is_admin": {
             "default": false,
             "title": "Is Admin",
@@ -3200,22 +3190,6 @@
             ],
             "title": "Runtime Instance Id"
           },
-          "runtime_switch_available": {
-            "default": false,
-            "title": "Runtime Switch Available",
-            "type": "boolean"
-          },
-          "runtime_switch_error": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ],
-            "title": "Runtime Switch Error"
-          },
           "transfer_limits": {
             "anyOf": [
               {
@@ -3248,24 +3222,6 @@
         "title": "RuntimeContext",
         "type": "object"
       },
-      "RuntimeSelection": {
-        "additionalProperties": false,
-        "properties": {
-          "mode": {
-            "enum": [
-              "local",
-              "hosted"
-            ],
-            "title": "Mode",
-            "type": "string"
-          }
-        },
-        "required": [
-          "mode"
-        ],
-        "title": "RuntimeSelection",
-        "type": "object"
-      },
       "RuntimeSourceInput": {
         "additionalProperties": false,
         "properties": {
@@ -7371,45 +7327,6 @@
         ]
       }
     },
-    "/runtime-mode/": {
-      "post": {
-        "operationId": "select_runtime_runtime_mode__post",
-        "requestBody": {
-          "content": {
-            "application/json": {
-              "schema": {
-                "$ref": "#/components/schemas/RuntimeSelection"
-              }
-            }
-          },
-          "required": true
-        },
-        "responses": {
-          "202": {
-            "content": {
-              "application/json": {
-                "schema": {}
-              }
-            },
-            "description": "Successful Response"
-          },
-          "422": {
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/HTTPValidationError"
-                }
-              }
-            },
-            "description": "Validation Error"
-          }
-        },
-        "summary": "Select Runtime",
-        "tags": [
-          "Runtime"
-        ]
-      }
-    },
     "/security/access-history/": {
       "get": {
         "operationId": "security_history_security_access_history__get",

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/api/overview.md

@@ -48,13 +48,11 @@ Local mode also exposes `POST /runtime-bootstrap/destroy-local/` for an explicit
 confirmed workspace reset. It removes the selected local database and returns to
 initialization without running migrations. Hosted runtimes reject this endpoint.
 
-The descriptor also reports `local_mode_available`, `runtime_switch_available`,
-`runtime_instance_id`, and `runtime_switch_error`. In a supervised developer API,
-`POST /runtime-mode/` with `{"mode": "local"}` or `{"mode": "hosted"}` requests a
-complete worker restart and returns 202. Disabled/unsupervised switching returns
-403; active work returns 409. After acceptance, application
-requests receive 503 while the worker drains. Clients reload `/runtime-context/`
-and clear their views after a new instance appears. Admin sends
+The descriptor also reports `local_mode_available` and `runtime_instance_id`. The
+local developer API always runs Local; there is no runtime-mode switch. Runtime
+reconfiguration in Settings returns 409 while other work is active, and application
+requests receive 503 while it runs. Clients reload `/runtime-context/` and clear
+their views after a new instance appears. Admin sends
 `X-MetaTables-Runtime-Instance`; a value from a previous runtime is rejected with
 409. The identity names the runtime binding (mode, runtime database, DataSource,
 activation and catalog revision), so it survives an API restart or deploy and is

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/api/reference.md

@@ -58,7 +58,6 @@ These methods and paths are mounted by the current application. See the [OpenAPI
 | POST | `/runtime-bootstrap/migrate/` | Migrate | 200 |
 | GET | `/runtime-context/` | Runtime Context | 200 |
 | POST | `/runtime-migrations/{lease_uid}/release/` | Release Migration | 200 |
-| POST | `/runtime-mode/` | Select Runtime | 202 |
 | GET | `/security/access-history/` | Security History | 200 |
 | GET | `/security/database-permissions/` | Database Permission Status | 200 |
 | POST | `/security/namespaces/` | Create Namespace | 201 |

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/client/installation-and-connection.md

@@ -44,7 +44,8 @@ revision and refuses to replace an installation used by a running launcher.
 
 For API-only development, omit `--admin`. Set alternate ports with `--port` and
 `--admin-port`. `init` preserves existing configuration; startup never migrates a
-database. In another terminal in the same project:
+database. The laptop runs one local API: `serve --local` in another project reports
+the running API and exits. In another terminal in any project:
 
 ```bash
 metatables --local runtime status
@@ -52,7 +53,7 @@ metatables --local runtime initialize
 metatables --local meta-table list
 ```
 
-Global `--local` selects the project's private, live connection. A missing or
+Global `--local` selects the laptop's private, live connection. A missing or
 stale connection fails locally. It never falls back to hosted discovery. The
 launcher generates the token and removes its connection file on exit. Python
 clients select it before using the public resources:
@@ -66,7 +67,7 @@ print(get_runtime_status())
 ```
 
 The API uses your SDK login for identity. Native local requests use the private
-launcher token and Git provenance; SDK platform credentials are not redirected to
+launcher token; SDK platform credentials are not redirected to
 the local API. See the [complete write/read example](../examples/local_app/README.md)
 and [runtime guide](../operations/local-runtime.md) for explicit initialization,
 application migrations, persistence and credentials.
@@ -107,7 +108,7 @@ Use `metatables-local-development` to guide application work from local setup
 through verification and an explicit return to the intended environment. It
 checks actual runtime mode and DataSource before test writes, keeps fixtures in
 local SQLite, and distinguishes passing local tests from verification of an
-engine-specific feature. Switching runtimes never promotes local data.
+engine-specific feature. Local data is never promoted to a hosted runtime.
 
 Rerunning the command replaces matching skill folders, including local edits to
 those folders, and preserves unrelated skill folders and namespaces. Use

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/client/tutorial.md

@@ -87,7 +87,7 @@ These are system migrations only. The tutorial's application migrations run
 in the application's Python process through the client in both modes:
 
 ```bash
-python -m metatables.examples.scripts.setup_metatables --development-client .local/development-client.json
+python -m metatables.examples.scripts.setup_metatables --development-client ~/.local/share/metatables/server.json
 ```
 
 Omit `--development-client` to use hosted deployment discovery. The application

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/examples/tutorial/README.md

@@ -32,7 +32,7 @@ so the API can execute the reviewed tutorial on a hosted deployment too.
 
 Open the MetaTables Python project and start **MetaTables: API (18473) + Admin
 (19473)**. This launcher reads `configuration.yaml`, where
-`local_mode_available: true` enables switching storage modes in Admin Settings.
+`local_mode_available: true` enables the Local runtime.
 
 Select an example launch:
 
@@ -55,10 +55,9 @@ script itself only creates/migrates tables. To run
 and prints the API target without reading tables. There are no input prompts.
 
 The API/Admin launcher writes its current endpoint and private process token to
-the ignored `.local/development-client.json` with permissions `0600`, and removes
+`~/.local/share/metatables/server.json` with permissions `0600`, and removes
 it on shutdown. The local example reads it before importing the SDK. The connection
-works with either Local or Hosted storage selected in Settings, including custom
-API ports. Restart an older API/Admin launch once to create this connection file.
+works with custom API ports. Restart an older API/Admin launch once to create this connection file.
 
 The configuration runs `python -m metatables.examples.tutorial` using the project's `.venv`,
 and prints its selected step and API endpoint in the Debug Console.
@@ -70,7 +69,7 @@ python -m metatables.examples.tutorial update --prepare-data --root returns
 python -m metatables.examples.tutorial update --prepare-data --root volatility
 ```
 
-Add `--development-client .local/development-client.json` to use the running local
+Add `--development-client ~/.local/share/metatables/server.json` to use the running local
 launcher, or omit it for hosted discovery.
 
 `DailyReturns` declares `RecordedPrices` as a dependency. `RollingVolatility`
@@ -118,7 +117,7 @@ the new revision. The API does not load tutorial code.
 To run migration setup alone from the repository root:
 
 ```bash
-python -m metatables.examples.scripts.setup_metatables --development-client .local/development-client.json
+python -m metatables.examples.scripts.setup_metatables --development-client ~/.local/share/metatables/server.json
 ```
 
 For a hosted deployment, omit `--development-client`; normal endpoint discovery

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/operations/configuration.md

@@ -19,18 +19,16 @@ to the platform and Environment and retains only the resolved endpoint
 and target identity; `/runtime-context/` continues to supply fresh DataSource
 state. See [client connection](../client/installation-and-connection.md).
 
-The supervisor passes runtime mode and listener/token parameters directly to each
-worker through a private inherited descriptor. `METATABLES_LOCAL_RUNTIME` is
+The supervisor passes listener/token parameters directly to its Local worker
+through a private inherited descriptor. `METATABLES_LOCAL_RUNTIME` is
 ignored. Deployment configuration is read from `configuration.yaml` in the working
 directory, or the explicit `--configuration` path on the launcher/CLI; there is no
 environment-variable override for that capability or configuration path. The
-migration Job and the launcher's Hosted mode read `runtime_database` from the
-API's packaged `configuration.yaml` instead.
+migration Job reads `runtime_database` from the API's packaged `configuration.yaml`
+instead.
 
-A developer's selected mode is persisted separately in ignored
-`.local/runtime-selection.json`, only after successful startup. Shared deployments
-use `local_mode_available: false`; the developer checkout uses `true`.
-See [mode switching](local-runtime.md#switch-modes-in-one-admin-site).
+Shared deployments use `local_mode_available: false`; the developer checkout uses
+`true`. The launcher always runs Local; see [Local only](local-runtime.md#local-only).
 
 Configure the API’s SDK session for ordinary platform Secret access and supply
 trusted caller-verifier settings. Use the SDK's own configuration contract;
@@ -49,7 +47,7 @@ by the API, and persistent across restarts. Hosted writes no selection file.
 Resolved passwords and TLS material remain in memory, never in files.
 
 Separate catalog URLs, physical-file overrides and default-source UID overrides are
-retired. Neither startup nor runtime-mode selection automatically runs Alembic.
+retired. Startup never automatically runs Alembic.
 
 Application providers run in their own Python process through the client. Use
 `metatables migrations upgrade --provider ledger.migrations:migration` with the

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/operations/hosted-runtime.md

@@ -167,14 +167,6 @@ application tables stay in that one database.
 The verified hosted Environment remains display metadata supplied through ordinary SDK
 interfaces. The declared database does not change SDK context or Environment requirements.
 
-## Developer launcher in Hosted mode
-
-After `metatables serve --local --admin` is switched to Hosted, the launcher reads
-the API's packaged deployment configuration and the same Secret, resolved in the
-developer's SDK Environment, so it uses the same database as the deployed API.
-It never migrates. If the local branch has newer migrations than the deployed API,
-it reports `migration_required` until that code is deployed.
-
 ## Application grants
 
 Platform Users, Teams and their membership are resolved through the SDK. MetaTables

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/operations/local-runtime.md

@@ -35,16 +35,18 @@ credentials already set in the environment. The launch prints which one it used
 (`credentials: saved session` or `credentials: exported tokens`).
 
 In another terminal, use `metatables --local runtime status`. Python applications
-call `metatables.configure_local_client()` before client operations. The private
-`.local/development-client.json` binds the project, token and live launcher process;
-`init` adds `.local/` to `.gitignore`. Stop the launcher with Ctrl-C to stop its
-owned services and remove its connection file. A second launcher for the same
-project fails without replacing that connection.
+call `metatables.configure_local_client()` before client operations. The laptop
+runs one local API, like its one local runtime: the launcher publishes its address,
+private token and live process in `server.json` in the local storage directory, and
+every checkout connects through it. `metatables serve --local` in another project
+prints `MetaTables API already running: http://127.0.0.1:18473` and exits; it never
+starts a second API. Stop the launcher with Ctrl-C to stop its owned services and
+remove its connection file. `init` adds `.local/` to `.gitignore`.
 
 The launcher validates a private loopback listener and uses the ordinary SDK login
 for user identity and independent Git discovery. Browser writes require the configured
-exact loopback origin. Native clients use the private token and their Git descriptor.
-A client from another branch or checkout is rejected. The SDK provides developer identity. Local DataSource credentials use the API
+exact loopback origin. Native clients from any checkout or branch use the private
+token; commits and branch changes never require an API restart. The SDK provides developer identity. Local DataSource credentials use the API
 CredentialStore without a hosted Secret requirement.
 
 ## Initialize explicitly
@@ -65,34 +67,23 @@ Apply application providers through the client with
 `metatables --local migrations upgrade --provider ledger.migrations:migration`. See the
 [write/read example](../examples/local_app/README.md).
 
-## Switch modes in one Admin site
-
-Each mode lists only its own runtime catalog's DataSources. Local shows the workspace
-catalog and keeps its passwords in the local CredentialStore; Hosted shows the catalog
-of the deployed runtime database and keeps passwords as managed Main Sequence Secrets.
-A DataSource registered in Local never appears in Hosted, and neither mode copies the
-other's registrations or credentials.
-
-To use the hosted database, choose Hosted under **Settings → Runtime mode** and click
-**Switch to Hosted**. The worker restarts in Hosted and opens the database the API's
-deployment declares: it reads the API's packaged deployment configuration and the same
-Environment Secret, resolved in your SDK Environment. Hosted Settings is read-only and
-the launcher never migrates. If your branch has newer system migrations than the
-deployed API, it reports `migration_required` until that code is deployed. See
-[the developer launcher in Hosted mode](hosted-runtime.md#developer-launcher-in-hosted-mode).
-Switching stops the old worker before starting the selected mode; it never copies data.
-Failed worker startup restores the previous worker. Mode selection is recorded in
-`.local/runtime-selection.json`; the Local SQLite selection is recorded separately
+## Local only
+
+The local API always runs Local; it has no switch to a hosted runtime. Its Admin lists
+the workspace catalog's DataSources and keeps their passwords in the local
+CredentialStore. Hosted data and its DataSources, whose passwords are managed Main
+Sequence Secrets, are reached through the deployed API and Admin, or from a client
+that omits `--local` and `configure_local_client()`. Neither runtime copies the
+other's registrations, credentials or data. The Local SQLite selection is recorded
 under `local` in `.local/runtime-data-sources.json`.
 
-The API refuses switching or source reconfiguration while other requests, open
-migration connections, reserved migrations, unfinished updates or unresolved physical
-operations exist. Stale runtime-instance headers are rejected after a transition.
-Migration connections use the selected runtime credentials and hold supervised
-runtime switching until the client releases them.
+The API refuses source reconfiguration while other requests, open migration
+connections, reserved migrations, unfinished updates or unresolved physical
+operations exist. Stale runtime-instance headers are rejected after the runtime
+binding changes. Migration connections use the runtime credentials and hold
+reconfiguration until the client releases them.
 
-`metatables serve --local` starts with Local selected and uses the shared supervisor.
-Shared hosted deployments disable local mode. Switching affects the whole API instance.
+Shared hosted deployments disable local mode.
 
 ## Workspace storage
 
@@ -108,9 +99,7 @@ configure another absolute SQLite file. A new file's identity derives from its
 location; an existing file keeps the identity recorded in its scope marker, so a file
 moved together with its marker keeps its DataSource UID and run logs. The selected
 file is stored under the single `local` entry in `.local/runtime-data-sources.json`.
-Branch changes and restarts reuse it, its credentials and its DataSource UID. Git
-context still describes the running code; changing that context requires restarting
-the API.
+Branch changes and restarts reuse it, its credentials and its DataSource UID.
 
 Existing files retain their paths, storage markers and IDs. A checkout that saved a
 per-checkout file under an earlier release keeps using it after an upgrade; select

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/docs/security/permissions.md

@@ -14,7 +14,7 @@ Organization admin status comes from the platform through the SDK.
 | Enter the application and browse permitted resources | Yes | Yes |
 | Create or register a table in an available DataSource | Yes | Yes |
 | Configure, validate, disable, or remove DataSources | No | Yes |
-| Select runtime mode or the runtime DataSource where supported | No | Yes |
+| Select the runtime DataSource where supported | No | Yes |
 | Initialize or upgrade MetaTables system tables in Local Settings (Hosted: the deployment's migration Job) | No | Yes |
 | Destroy a local runtime database through Settings | No | Yes |
 | Change application-wide Settings and security policies | No | Yes |

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mainsequence-metatable"
-version = "0.1.18.dev30"
+version = "0.1.19.dev31"
 description = "Main Sequence MetaTables Python client and standalone API"
 readme = "README.md"
 requires-python = ">=3.13"

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/scripts/check_boundaries.py

@@ -29,15 +29,14 @@ SHARED_MODULES = frozenset({'metatables.local_connection', 'metatables.local_fil
 # models, constraints and storage policy remain forbidden from owning them.
 DISPLAY_PROVENANCE = {
     "src/metatables/endpoint.py": {"environment_uid", "organization_environment_uid", "resolve_organization_environment_uid"},
-    "src/metatables/cli/local.py": {"sdk_session_environment", "vite_environment", "api_environment"},
+    "src/metatables/cli/local.py": {"sdk_session_environment", "vite_environment"},
     "src/metatables/sdk_compat.py": {"is_organization_admin"},
     'src/metatables/api/app/auth/boundary.py': {'environment_uid', 'organization_environment_uid', 'is_organization_admin'},
     'src/metatables/api/app/runtime.py': {'environment_cache'},
     'src/metatables/api/app/routes/runtime_context.py': {'environment', 'environment_uid', 'hosted_environment',
-                                         'verified_environment', 'OrganizationEnvironment', 'environment_target',
-                                         'developer_hosted_environment', 'hosted_environment_target', 'organization_environment_uid',
-                                         'cached_environment', 'environment_cache'},
-    'src/metatables/runtime_contract.py': {'hosted_environment', 'hosted_environment_target'},
+                                         'verified_environment', 'OrganizationEnvironment',
+                                         'organization_environment_uid', 'cached_environment', 'environment_cache'},
+    'src/metatables/runtime_contract.py': {'hosted_environment'},
 }
 PLATFORM_PATH = re.compile(r'/(?:orm/api|auth/jwt-token|api/v1/data[-_]sources)(?:/|$)')
 

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31/src/mainsequence_metatable.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.18.dev30
+Version: 0.1.19.dev31
 Summary: Main Sequence MetaTables Python client and standalone API
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT

{mainsequence_metatable-0.1.18.dev30 → mainsequence_metatable-0.1.19.dev31}/src/mainsequence_metatable.egg-info/SOURCES.txt

@@ -480,7 +480,6 @@ tests/e2e/test_public_imports.py
 tests/e2e/test_remaining_client_routes.py
 tests/e2e/test_run_graphs.py
 tests/e2e/test_run_logs.py
-tests/e2e/test_runtime_transition.py
 tests/e2e/test_runtime_upgrade.py
 tests/e2e/test_sdk_local_startup.py
 tests/e2e/test_sqlite_runtime.py