mainsequence-metatable 0.1.34.dev64__tar.gz → 0.1.35.dev65__tar.gz

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/.agents/skills/client/metatables-meta-tables/SKILL.md

@@ -118,9 +118,7 @@ There is no declared table list: `MetaTableOperationScopeTable`,
 `MetaTableOperationScope` and `scope_tables` were intentionally removed. Do not
 recreate them, add per-query registration checks, or parse SQL to enforce a client
 scope. Use existing physical bindings in SQLAlchemy models. Registration and
-schema evolution belong to their lifecycle workflows. For older applications,
-use the [legacy upgrade skill](../metatables-upgrade-legacy-app/SKILL.md) and
-`docs/client/upgrade-legacy-app.md`.
+schema evolution belong to their lifecycle workflows.
 
 `operation="select"` selects read execution; the other labels select write
 execution. The label does not classify the SQL. Database permissions enforce

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/.agents/skills/client/metatables-migrations/SKILL.md

@@ -12,10 +12,6 @@ client. It covers application-facing models and workflows. Client-library
 implementation, this repository's development/release tooling, and API internals
 have separate ownership.
 
-For upgrading older client imports, SQL scopes or provider integration, use the
-[legacy upgrade skill](../metatables-upgrade-legacy-app/SKILL.md). This skill
-covers authoring and running application schema revisions.
-
 In a copied skill, resolve the `docs/` and `src/metatables/examples/` paths below relative to
 this skill's `references/` directory. The client CLI bundles the matching version's
 guides and examples there, including their linked documents. In the MetaTables
@@ -253,9 +249,9 @@ Read `docs/operations/recovery-and-observability.md`.
   its module resolves to with
   `python -c "import importlib.util as u; print(u.find_spec('migrations').origin)"`,
   replacing `migrations` with the provider module. A shared module name means
-  another install overwrote it. Move the provider as the
-  [legacy upgrade skill](../metatables-upgrade-legacy-app/SKILL.md) describes;
-  do not edit files in `site-packages`.
+  another install overwrote it. Move the provider under an application-owned
+  module (see [Provider placement](#provider-placement)), preserving its provider
+  identity and applied revision history. Do not edit files in `site-packages`.
 - If reservation fails with `namespace_not_writable` or `table_not_editable`
   (403), the caller lacks Writer through the owning Team. Add the
   `caller_user_uid` from the error to the Team with Writer on the namespace, or,

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.34.dev64
+Version: 0.1.35.dev65
 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.34.dev64 → mainsequence_metatable-0.1.35.dev65}/docs/adr/api/0007-database-enforced-table-access.md

@@ -200,7 +200,7 @@ Client upgrade clarification, 2026-10-01: removing `MetaTableOperationScopeTable
 select a DataSource and remove scope-only helpers and checks; they must not rebuild
 this layer through client SQL parsing or per-query catalog lookups. Table lifecycle
 registration remains separate. The [legacy application upgrade guide](../../client/upgrade-legacy-app.md)
-and packaged `metatables-upgrade-legacy-app` skill document the conversion.
+documents the conversion.
 
 The API removes every check of what the SQL means:
 

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/docs/client/installation-and-connection.md

@@ -88,8 +88,8 @@ metatables --json copy-metatables-skills --path /path/to/application
 `metatables` does not copy skills.
 
 The destination is `<application>/.agents/skills/metatables/`. It contains the
-local development, table, application migration, table discovery, time-index updater and legacy
-application upgrade skills, with matching
+local development, table, application migration, table discovery and time-index
+updater skills, with matching
 guide/example snapshots in each skill's `references/` folder. The installed client
 version is recorded in `PINNED_FROM.txt`. Skills for API implementation or
 MetaTables project development are outside this bundle.
@@ -104,11 +104,6 @@ installed client does not ship, including any added there, are removed. Keep the
 application's own skills in another `.agents/skills/` namespace; the copy never
 changes it.
 
-Use `metatables-upgrade-legacy-app` when replacing older MainSequence/MetaTables
-imports, declared SQL scopes or API-owned application migration setup. The
-[legacy application upgrade guide](upgrade-legacy-app.md) explains the current
-DataSource contract and includes before/after repository compiler examples.
-
 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

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/docs/client/upgrade-legacy-app.md

@@ -8,8 +8,7 @@ scope classes are intentional removals, not missing features to recreate.
 Install the target client and its compatible SDK in the application's Python
 environment using [installation and connection](installation-and-connection.md).
 Refresh the matching agent guidance with `metatables copy-metatables-skills`.
-The `metatables-upgrade-legacy-app` skill covers this upgrade; the
-`metatables-migrations` skill covers application Alembic schema changes.
+The `metatables-migrations` skill covers application Alembic schema changes.
 
 ## Identify the old interfaces
 

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/pyproject.toml

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

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/src/mainsequence_metatable.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.34.dev64
+Version: 0.1.35.dev65
 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.34.dev64 → mainsequence_metatable-0.1.35.dev65}/src/mainsequence_metatable.egg-info/SOURCES.txt

@@ -12,7 +12,6 @@ uv.lock
 .agents/skills/client/metatables-migrations/SKILL.md
 .agents/skills/client/metatables-table-discovery/SKILL.md
 .agents/skills/client/metatables-time-index-table-updates/SKILL.md
-.agents/skills/client/metatables-upgrade-legacy-app/SKILL.md
 .agents/skills/discover-tables/SKILL.md
 .agents/skills/ms_tau_sdk/PINNED_FROM.txt
 .agents/skills/ms_tau_sdk/tau_a2a_runtime_adapter/SKILL.md

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/tests/packaging/test_client_skills.py

@@ -21,7 +21,6 @@ SKILLS = {
     "metatables-migrations",
     "metatables-table-discovery",
     "metatables-time-index-table-updates",
-    "metatables-upgrade-legacy-app",
 }
 
 

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/tests/packaging/test_installed_distribution.py

@@ -93,7 +93,7 @@ def test_client_skills_copy_from_installed_bundle_outside_checkout(tmp_path, mon
     result = CliRunner().invoke(app, ["--json", "copy-metatables-skills"])
     assert result.exit_code == 0, result.output
     payload = json.loads(result.output)
-    assert payload["updated_count"] == 6
+    assert payload["updated_count"] == 5
     assert payload["pinned_version"] == version("mainsequence-metatable")
     if source_checkout_root() is None:
         assert payload["source"] == "metatables/_client_skills"
@@ -109,8 +109,6 @@ def test_client_skills_copy_from_installed_bundle_outside_checkout(tmp_path, mon
     assert (installed / "metatables-table-discovery/SKILL.md").is_file()
     assert (installed / "metatables-table-discovery/references/docs/adr/api/0018-table-search.md").is_file()
     assert (installed / "metatables-time-index-table-updates/SKILL.md").is_file()
-    assert (installed / "metatables-upgrade-legacy-app/SKILL.md").is_file()
-    assert (installed / "metatables-upgrade-legacy-app/references/docs/client/upgrade-legacy-app.md").is_file()
 
 
 def test_migration_templates_are_installed():

{mainsequence_metatable-0.1.34.dev64 → mainsequence_metatable-0.1.35.dev65}/uv.lock

@@ -825,7 +825,7 @@ mcp = [
 
 [[package]]
 name = "mainsequence-metatable"
-version = "0.1.34"
+version = "0.1.35"
 source = { editable = "." }
 dependencies = [
     { name = "alembic" },

mainsequence_metatable-0.1.34.dev64/.agents/skills/client/metatables-upgrade-legacy-app/SKILL.md

@@ -1,116 +0,0 @@
----
-name: metatables-upgrade-legacy-app
-description: "Upgrade consuming applications from MainSequence 8.x MetaTables or older extracted clients to the installed metatables package. Use for legacy imports, removed SQL scopes, repository compilers, application migration-provider integration and provider modules that collide with other installed packages. Excludes MetaTables client/API implementation and ordinary schema revision authoring."
----
-
-# Upgrade a legacy MetaTables application
-
-## Scope and references
-
-Update the consuming application to the installed client's current contract.
-Removed scope APIs are intentional; do not restore them in the client or create
-application compatibility shims. Keep identity/login and Git source integration
-in the MainSequence SDK.
-
-Read `docs/client/upgrade-legacy-app.md` for the conversion table and before/after
-repository compiler examples. In a copied skill, resolve the `docs/` and
-`src/metatables/examples/` paths here relative to this skill's `references/` directory. In the
-MetaTables source checkout, resolve them from the repository root.
-
-Use `docs/client/installation-and-connection.md` to establish the target package
-and compatible SDK versions. Refresh copied skills after a client upgrade with
-`metatables copy-metatables-skills`. Inspect the installed public exports and CLI
-help before mapping an unfamiliar old interface; avoid broad import rewrites.
-
-## Find and replace legacy usage
-
-Inspect dependency pins, table imports, shared repository compilers and their
-callers, runtime setup, and existing Alembic provider integration. Useful search
-terms are `mainsequence.client.metatables`, `mainsequence.meta_tables`,
-`MetaTableOperationScopeTable`, `MetaTableOperationScope`, `scope_tables`, and
-`application_migration_providers`.
-
-For SQL operations:
-
-- Import public table resources from `metatables` and the compiler from
-  `metatables.compiled_sql.v1`.
-- Send SQL and a DataSource. The API executes as the authenticated user, and the
-  selected engine enforces that user's table permissions on actual SQL access.
-  Removing the declared table list does not remove table permissions.
-- Delete scope classes, `scope_tables`, and scope-only wrappers or parameters,
-  including `models`, `access`, aliases or `reserved_policy` when they serve only
-  scope construction. Update callers and old nested wire payloads together.
-- Do not substitute per-query catalog lookups, registration/binding preflights,
-  local permission checks or SQL parsing for the removed scope machinery.
-  Registration/finalization remain table lifecycle operations. Preserve separate
-  application business rules.
-- Let the compiler obtain DataSource and dialect from the selected API runtime,
-  or supply both explicitly for offline compilation. Never use a MetaTable UID as
-  a DataSource UID or infer a new database from the retired table list.
-- Preserve the query's physical bindings, bound parameters, result behavior,
-  execution mode, offsets, row limits, statement deadlines and HTTP timeouts.
-  `select` selects read execution; the other operation labels select write
-  execution. These labels do not classify the SQL statement.
-
-Read `docs/client/query-and-mutate.md` for current query behavior and
-`docs/adr/api/0007-database-enforced-table-access.md` for the decision. The retained
-`compiled-sql.v1` label does not make the old scoped payload compatible.
-
-## Upgrade application migration integration
-
-Keep the existing provider `package=` value, namespace, model registry,
-version-table binding and applied revision history. Update bootstrap/import wiring
-to the installed client's public migration interfaces. Do not scaffold a replacement
-provider, rewrite applied history or stamp the database to bypass an upgrade issue.
-
-### Move a provider whose module name collides
-
-A provider installed under a generic top-level module, such as `migrations`,
-shares files and imports with every other installed package that chose the same
-name. Move it under a module the application owns, for example `ledger.migrations`
-or `ledger_migrations`:
-
-- Move the provider package with its `env.py`, `script.py.mako` and `versions/`
-  tree.
-- Update `script_location`, `version_location_prefix`, the `env.py` import,
-  imports inside the provider, packaging configuration, and every provider
-  reference in code, scripts and jobs.
-- Keep `package=`, `migration_namespace`, the version-table binding and the
-  revision files unchanged. The catalog binds provider tables to
-  `package:namespace` and rejects a reservation from a different key. Alembic
-  stores only revision IDs, so the module path can change.
-- Do not ship a module under the old name. A forwarding module would keep the
-  file collision.
-
-Then confirm that `migrations current` reports the same revision as before the
-move, and that the built wheel no longer installs the old top-level name.
-
-Providers load in the application process from Python references such as
-`ledger.migrations:migration`. The client executes Alembic with the environment
-connection; the API handles authorization, reservations and finalization. The
-environment operator supplies database DDL privileges. Remove retired API provider
-allowlists and aliases; the API needs no application provider code installed.
-MetaTables' internal catalog migrations remain a separate history.
-
-Use the [application migrations skill](../metatables-migrations/SKILL.md),
-`docs/client/define-and-migrate-tables.md`, and
-`docs/adr/api/0013-application-owned-migrations.md` for that workflow. Ordinary
-SQL continues through the governed API, independently of the migration connection.
-If the application's deployment workflow does not yet run its providers in a
-migration Job before its API and agents roll out, add one as
-`docs/client/deploy-application-migrations.md` describes.
-
-## Verify the upgrade
-
-Run imports and offline compilation first. The guide includes an example that
-needs no registration, credentials or running API. Check actual query parameters,
-mode and limits; use existing tests for application business behavior. Review
-provider loading and unchanged Alembic history. Remove obsolete tests that assert
-scope construction rather than recreating that behavior to make them pass.
-
-For application execution checks, follow the
-[local development skill](../metatables-local-development/SKILL.md), verify the
-actual local runtime, and exercise the smallest relevant workflow. Respect the
-requested scope for database mutations; a client upgrade alone does not authorize
-hosted migrations. Distinguish offline verification from API execution and from
-hosted-engine verification in the result.