refactor(instrumentation)!: Schema-based instrumentation architecture

.github/workflows/cpp.yml

@@ -51,18 +51,6 @@ jobs:
             ~/.cargo/git/db/
           key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
           restore-keys: ${{ runner.os }}-cargo-
-      - name: Build legacy C++ integration example
-        run: |
-          pixi run cmake -B examples/legacy/cpp-integration/cpp/build -S examples/legacy/cpp-integration/cpp
-          pixi run cmake --build examples/legacy/cpp-integration/cpp/build
-      - name: Run legacy C++ integration example
-        run: ./examples/legacy/cpp-integration/cpp/build/example
-      - name: Build C++ query engine bridge test
-        run: |
-          pixi run cmake -B domains/query_engine/tests/cpp/cpp/build -S domains/query_engine/tests/cpp/cpp
-          pixi run cmake --build domains/query_engine/tests/cpp/cpp/build
-      - name: Run C++ query engine bridge test
-        run: ./domains/query_engine/tests/cpp/cpp/build/example
       - name: Test schema codegen C++
         run: pixi run cargo test --manifest-path experimental/vibe/codegen/Cargo.toml -p quent-demo-cpp-test -p quent-cpp-list-test
       - name: Build and run schema codegen C++ tutorials

.github/workflows/python.yml

@@ -53,24 +53,6 @@ jobs:
             ~/.cargo/git/db/
           key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
           restore-keys: ${{ runner.os }}-cargo-
-      - name: Build legacy Python integration example
-        run: |
-          pixi run maturin develop --uv -m examples/legacy/python-integration/bridge/Cargo.toml
-      - name: Run legacy Python integration example
-        run: |
-          pixi run python examples/legacy/python-integration/main.py
-      - name: Type check legacy Python integration example
-        run: |
-          pixi run ty check examples/legacy/python-integration/
-      - name: Build Python query engine bridge test
-        run: |
-          pixi run maturin develop --uv -m domains/query_engine/tests/python/bridge/Cargo.toml
-      - name: Run Python query engine bridge test
-        run: |
-          pixi run pytest -v domains/query_engine/tests/python/
-      - name: Type check query engine bridge test
-        run: |
-          pixi run ty check domains/query_engine/tests/python/
       - name: Build schema codegen Python tests
         run: |
           pixi run maturin develop --uv -m experimental/vibe/codegen/python/test/bridge/Cargo.toml

.github/workflows/ui.yml

@@ -153,10 +153,15 @@ jobs:
             ~/.cargo/git/db/
           key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
           restore-keys: ${{ runner.os }}-cargo-
-      - run: pixi run cargo run -p quent-simulator-ui-bindings --locked
+      - run: pixi run cargo run -p quent-query-engine-ui-bindings --locked
       - name: Generate base bindings
         run: |
-          if [ -d base/experimental/vibe/simulator/ui-bindings ] || \
+          if [ -d base/domains/query_engine/ui-bindings ]; then
+            pixi run --locked --manifest-path base/pixi.toml cargo run \
+              --manifest-path base/Cargo.toml \
+              -p quent-query-engine-ui-bindings \
+              --locked
+          elif [ -d base/experimental/vibe/simulator/ui-bindings ] || \
              [ -d base/examples/simulator/ui-bindings ]; then
             pixi run --locked --manifest-path base/pixi.toml cargo run \
               --manifest-path base/Cargo.toml \

AGENTS.md

@@ -1,28 +1,28 @@
 # Agent instructions
 
-## Temporary schema migration freeze
+## `quent-open` compatibility
 
-Major refactors are in progress to remove proof-of-concept technical debt and
-complete the schema-based instrumentation architecture:
+`quent-open` builds a viewer against the Quent revision recorded in an
+artifact's `model.qmi`. Existing artifacts must remain openable when public
+crates, package names, features, or APIs used by the generated wrapper change.
 
-- [#638: schema-based C++ and Python generators][pr-638]
-- [#699: schema-based instrumentation architecture][pr-699]
+Before making such a breaking change:
 
-Before starting work that affects the areas below, check whether both pull
-requests have merged. Until both have merged, do not make significant changes
-to:
+- Add an immutable full commit SHA from `upstream/main` immediately before the
+  change as a compatibility boundary.
+- Select the complete wrapper contract from Git ancestry before building. Do
+  not use failed builds or compiler error text for feature detection.
+- Retain the wrapper generation path required by revisions before the boundary.
+- Do not move or remove an existing boundary while artifacts may reference
+  revisions on either side of it.
+- Extend the `quent-open` compatibility test to cover the preserved path.
 
-- `quent-model` and `quent-model-macros` (`crates/model`,
-  `crates/model-macros`)
-- `quent-codegen` (`crates/codegen`)
-- `quent-stdlib` and `quent-query-engine-model` (`crates/stdlib`,
-  `domains/query_engine/model`)
-- related examples, tests, and minor crates being removed or migrated by either
-  pull request
+A predecessor SHA is a valid boundary only when the breaking change is the next
+change merged into `upstream/main`. If that ordering cannot be guaranteed, use
+the final merge commit or another commit that unambiguously contains the new
+contract. With a predecessor boundary, only strict descendants use the new
+contract; older and unrelated branch revisions use the preserved contract.
 
-If requested work overlaps these areas while either pull request remains open,
-report the conflict and ask the user how to proceed before editing. This
-restriction expires after both pull requests merge.
-
-[pr-638]: https://github.com/rapidsai/quent/pull/638
-[pr-699]: https://github.com/rapidsai/quent/pull/699
+Once releases are available, prefer the first release tag containing a new
+wrapper contract as its compatibility boundary. Keep full-SHA boundaries for
+artifacts produced from untagged development revisions.