arraybridge 0.2.10__tar.gz → 0.3.0__tar.gz

{arraybridge-0.2.10 → arraybridge-0.3.0}/.github/workflows/ci.yml

@@ -155,4 +155,4 @@ jobs:
       - name: Run mypy (type checking)
         continue-on-error: true  # Scientific code often has complex types
         run: |
-          mypy src/ --ignore-missing-imports
+          mypy src/

{arraybridge-0.2.10 → arraybridge-0.3.0}/.github/workflows/coverage-pages.yml

@@ -6,7 +6,7 @@ on:
   workflow_dispatch:
 
 permissions:
-  contents: write  # Needed for badge commit
+  contents: read
   pages: write
   id-token: write
 
@@ -40,7 +40,6 @@ jobs:
           pip install torch --index-url https://download.pytorch.org/whl/cpu
 
       - name: Run tests with coverage
-        continue-on-error: true  # Continue workflow even if tests fail
         run: |
           mkdir -p site
           python -m pytest --cov=arraybridge \
@@ -50,8 +49,7 @@ jobs:
 
       - name: Generate coverage badge
         run: |
-          mkdir -p .github/badges
-          genbadge coverage -i coverage.xml -o .github/badges/coverage.svg -n "coverage"
+          genbadge coverage -i coverage.xml -o site/coverage-badge.svg -n "coverage"
 
       - name: Create index.html and README
         run: |
@@ -72,7 +70,7 @@ jobs:
           # Create README.md in the site directory
           echo "# arraybridge Code Coverage Reports" > site/README.md
           echo "" >> site/README.md
-          echo "This site contains the code coverage reports for the [arraybridge](https://github.com/trissim/arraybridge) project." >> site/README.md
+          echo "This site contains the code coverage reports for the [arraybridge](https://github.com/OpenHCSDev/arraybridge) project." >> site/README.md
           echo "" >> site/README.md
           echo "## Navigation" >> site/README.md
           echo "" >> site/README.md
@@ -85,19 +83,10 @@ jobs:
           echo "" >> site/README.md
           echo "Last updated: $(date)" >> site/README.md
 
-      - name: Commit and push if coverage badge changed
-        if: github.event_name == 'push' && github.ref == 'refs/heads/main'
-        run: |
-          git config --local user.email "github-actions[bot]@users.noreply.github.com"
-          git config --local user.name "github-actions[bot]"
-          git add .github/badges/coverage.svg -f
-          git commit -m "chore: update coverage badge" || exit 0
-          git push
-
       - name: Check GitHub Pages status
         run: |
           echo "⚠️ IMPORTANT: Make sure GitHub Pages is enabled in your repository settings!"
-          echo "Go to https://github.com/trissim/arraybridge/settings/pages"
+          echo "Go to https://github.com/OpenHCSDev/arraybridge/settings/pages"
           echo "Set 'Source' to 'GitHub Actions' to enable GitHub Pages deployment."
 
       - name: Setup Pages

{arraybridge-0.2.10 → arraybridge-0.3.0}/.github/workflows/publish.yml

@@ -20,6 +20,8 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
 
       - name: Set up Python
         uses: actions/setup-python@v5
@@ -29,7 +31,21 @@ jobs:
       - name: Install build dependencies
         run: |
           python -m pip install --upgrade pip
-          pip install build
+          pip install -e ".[dev]"
+
+      - name: Validate source and tests
+        run: |
+          ruff check src/ scripts/
+          black --check src/ scripts/
+          mypy src/
+          pytest -q --no-cov
+
+      - name: Verify release tag and main ancestry
+        run: |
+          declared_version=$(python -c 'import tomllib; print(tomllib.load(open("pyproject.toml", "rb"))["project"]["version"])')
+          test "$GITHUB_REF_NAME" = "v$declared_version"
+          git fetch origin main
+          git merge-base --is-ancestor "$GITHUB_SHA" origin/main
 
       - name: Build package
         run: python -m build
@@ -39,6 +55,9 @@ jobs:
           pip install twine
           twine check dist/*
 
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
       - name: Create GitHub Release
         uses: softprops/action-gh-release@v2
         with:
@@ -46,6 +65,3 @@ jobs:
           generate_release_notes: true
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Publish to PyPI
-        uses: pypa/gh-action-pypi-publish@release/v1

arraybridge-0.3.0/ADDING_NEW_FRAMEWORKS.md

@@ -0,0 +1,63 @@
+# Adding a framework
+
+This is a maintainer how-to for extending ArrayBridge's closed framework
+taxonomy. Applications should consume `MemoryType`; they should not add their
+own framework registry.
+
+## 1. Define typed leaves
+
+Add an `ArrayOperations` bundle in
+`src/arraybridge/array_operations.py`. It must provide four ordinary callables:
+
+- project an array to NumPy;
+- create an array from NumPy on the requested framework-local device;
+- stack prepared 2D arrays into one 3D array;
+- apply the framework's dtype-scaling semantics.
+
+Define device, stream, DLPack, cleanup, and OOM leaves in
+`src/arraybridge/types.py`. Use the no-op defaults in `FrameworkRuntime` only
+when the framework genuinely lacks that capability. Do not encode behavior as
+strings or add a parallel `MemoryType`-keyed table.
+
+## 2. Add the declaration
+
+Add one `MemoryType` member carrying:
+
+1. its stable value and import name;
+2. its display name and module aliases;
+3. whether it is GPU-backed;
+4. any environment defaults that must be set before first import;
+5. its `FrameworkRuntime` leaves;
+6. its `ArrayOperations` bundle.
+
+The converter classes, target conversion methods, compatibility operation view,
+dtype-scaling view, cleanup adapters, and framework decorator are generated
+from the enum. Do not wire them manually.
+
+## 3. Prove the extension
+
+Add focused tests for:
+
+- module-name detection and optional-dependency failure;
+- NumPy round trips and every supported DLPack pair;
+- CPU-only installations of a nominally GPU framework;
+- invalid, negative, and multiple framework-local device IDs;
+- same-framework moves between two devices;
+- one-, two-, and multi-slice stack/unstack behavior;
+- immutable array types;
+- cleanup and OOM behavior without importing an absent framework;
+- generated registry and export completeness.
+
+Run:
+
+```bash
+ruff check src tests
+black --check src tests
+mypy src --ignore-missing-imports
+pytest
+python -m sphinx -E -W --keep-going -b html docs/source /tmp/arraybridge-docs
+```
+
+When GPU hardware is available, also exercise every installed framework pair in
+one process. This catches import-order, allocator-coexistence, DLPack, and real
+API-shape defects that isolated mocks cannot prove.

{arraybridge-0.2.10 → arraybridge-0.3.0}/CONTRIBUTING.md

@@ -35,7 +35,7 @@ We are committed to providing a welcoming and inclusive environment. Please be r
 
 ### Finding Issues
 
-- Check the [issue tracker](https://github.com/trissim/arraybridge/issues)
+- Check the [issue tracker](https://github.com/OpenHCSDev/arraybridge/issues)
 - Look for issues labeled `good first issue` or `help wanted`
 - Feel free to create new issues for bugs or feature requests
 
@@ -49,7 +49,7 @@ git clone https://github.com/YOUR_USERNAME/arraybridge.git
 cd arraybridge
 
 # Add upstream remote
-git remote add upstream https://github.com/trissim/arraybridge.git
+git remote add upstream https://github.com/OpenHCSDev/arraybridge.git
 ```
 
 ### 2. Create Virtual Environment
@@ -135,13 +135,11 @@ def convert_memory(data: Any, source_type: str, target_type: str, gpu_id: int) -
         MemoryConversionError: If conversion fails
 
     Example:
-        ```python
         import numpy as np
         from arraybridge import convert_memory
 
         data = np.array([1, 2, 3])
         result = convert_memory(data, "numpy", "torch", gpu_id=0)
-        ```
     """
 ```
 
@@ -334,35 +332,48 @@ git push origin feature/your-feature-name
 
 ### 1. Update Version
 
-Edit `pyproject.toml`:
+Update all three validated version projections with the side-effect-free helper:
 
-```toml
-[project]
-version = "0.2.0"
+```bash
+python scripts/update_version.py 0.3.0
 ```
 
+Review the package, project, and documentation changes, then run
+`python scripts/verify_release_ready.py --allow-dirty` before committing.
+
 ### 2. Update Changelog
 
 Add release notes to `CHANGELOG.md` (if exists) or create GitHub release notes.
 
-### 3. Create Tag
+### 3. Validate, Commit, and Push
 
 ```bash
-# Ensure you're on main branch
-git checkout main
-git pull upstream main
+ruff check src tests scripts
+black --check src scripts
+mypy src --ignore-missing-imports
+pytest
+python -m sphinx -E -W --keep-going -b html docs/source /tmp/arraybridge-docs
+git commit
+git push origin HEAD:main
+```
 
-# Create and push tag
-git tag -a v0.2.0 -m "Release version 0.2.0"
-git push upstream v0.2.0
+### 4. Create the Release Tag
+
+After the pushed commit is exactly `origin/main`, run:
+
+```bash
+python scripts/release.py
 ```
 
-### 4. Automated Publishing
+The script validates the clean published commit, confirms the PyPI version, and
+pushes the matching annotated tag.
+
+### 5. Automated Publishing
 
 GitHub Actions will automatically:
-1. Build the package
-2. Create GitHub release
-3. Publish to PyPI
+1. verify the tag, source, tests, and package metadata;
+2. publish to PyPI;
+3. create the GitHub release.
 
 ## Development Guidelines
 
@@ -393,12 +404,14 @@ GitHub Actions will automatically:
 
 To add support for a new framework:
 
-1. Update `MemoryType` enum in `types.py`
-2. Add framework config in `framework_config.py`
-3. Implement converter in `conversion_helpers.py`
-4. Add decorator support in `decorators.py`
-5. Update documentation
-6. Add tests with availability checks
+1. Add typed array-operation leaves in `array_operations.py`.
+2. Add one `MemoryType` declaration carrying those operations and its runtime leaves.
+3. Add detection, conversion-pair, stack, cross-device, and optional-dependency tests.
+4. Update the extension and reference documentation.
+
+Do not add framework behavior to `_FRAMEWORK_CONFIG`, a consumer registry, or
+generated decorator exports. See `ADDING_NEW_FRAMEWORKS.md` for the complete
+declaration-owned extension procedure.
 
 ## Getting Help
 

arraybridge-0.3.0/PKG-INFO

@@ -0,0 +1,143 @@
+Metadata-Version: 2.4
+Name: arraybridge
+Version: 0.3.0
+Summary: Unified API for NumPy, CuPy, PyTorch, TensorFlow, JAX, and pyclesperanto with automatic memory type conversion
+Project-URL: Homepage, https://github.com/OpenHCSDev/arraybridge
+Project-URL: Documentation, https://arraybridge.readthedocs.io
+Project-URL: Repository, https://github.com/OpenHCSDev/arraybridge
+Project-URL: Issues, https://github.com/OpenHCSDev/arraybridge/issues
+Author-email: Tristan Simas <tristan.simas@mail.mcgill.ca>
+License: MIT
+License-File: LICENSE
+Keywords: array,conversion,cupy,gpu,jax,numpy,pytorch,tensor,tensorflow
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: metaclass-registry>=0.1.5
+Requires-Dist: numpy>=1.20
+Provides-Extra: all
+Requires-Dist: cupy>=10.0; extra == 'all'
+Requires-Dist: jax>=0.3; extra == 'all'
+Requires-Dist: jaxlib>=0.3; extra == 'all'
+Requires-Dist: pyclesperanto>=0.10; extra == 'all'
+Requires-Dist: tensorflow>=2.8; extra == 'all'
+Requires-Dist: torch>=1.10; extra == 'all'
+Provides-Extra: cupy
+Requires-Dist: cupy>=10.0; extra == 'cupy'
+Provides-Extra: dev
+Requires-Dist: black>=23.0; extra == 'dev'
+Requires-Dist: build>=1.0; extra == 'dev'
+Requires-Dist: mypy>=1.0; extra == 'dev'
+Requires-Dist: packaging>=23.0; extra == 'dev'
+Requires-Dist: pytest-cov>=4.0; extra == 'dev'
+Requires-Dist: pytest>=7.0; extra == 'dev'
+Requires-Dist: ruff>=0.1.0; extra == 'dev'
+Requires-Dist: twine>=5.0; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: sphinx-autodoc-typehints>=1.25; extra == 'docs'
+Requires-Dist: sphinx-rtd-theme>=2.0; extra == 'docs'
+Requires-Dist: sphinx>=7.0; extra == 'docs'
+Provides-Extra: gpu
+Requires-Dist: cucim-cu12<26.0.0,>=25.6.0; extra == 'gpu'
+Requires-Dist: cupy-cuda12x<14.0.0,>=13.3.0; extra == 'gpu'
+Requires-Dist: jax-cuda12-pjrt<0.6.0,>=0.5.3; extra == 'gpu'
+Requires-Dist: jax-cuda12-plugin<0.6.0,>=0.5.3; extra == 'gpu'
+Requires-Dist: jax<0.6.0,>=0.5.3; extra == 'gpu'
+Requires-Dist: jaxlib<0.6.0,>=0.5.3; extra == 'gpu'
+Requires-Dist: pyclesperanto>=0.17.1; extra == 'gpu'
+Requires-Dist: tensorflow-probability[tf]<0.26.0,>=0.25.0; extra == 'gpu'
+Requires-Dist: tensorflow<2.20.0,>=2.19.0; extra == 'gpu'
+Requires-Dist: torch<2.8.0,>=2.6.0; extra == 'gpu'
+Requires-Dist: torchvision<0.23.0,>=0.21.0; extra == 'gpu'
+Provides-Extra: jax
+Requires-Dist: jax>=0.3; extra == 'jax'
+Requires-Dist: jaxlib>=0.3; extra == 'jax'
+Provides-Extra: pyclesperanto
+Requires-Dist: pyclesperanto>=0.10; extra == 'pyclesperanto'
+Provides-Extra: tensorflow
+Requires-Dist: tensorflow>=2.8; extra == 'tensorflow'
+Provides-Extra: torch
+Requires-Dist: torch>=1.10; extra == 'torch'
+Description-Content-Type: text/markdown
+
+# arraybridge
+
+ArrayBridge provides explicit conversion and shared lifecycle utilities for
+NumPy, CuPy, PyTorch, TensorFlow, JAX, and pyclesperanto arrays.
+
+Core dependencies are NumPy and metaclass-registry. Other frameworks are
+optional.
+
+## Quick start
+
+```python
+import numpy as np
+
+from arraybridge import convert_memory, detect_memory_type
+
+value = np.arange(6).reshape(2, 3)
+assert detect_memory_type(value) == "numpy"
+
+copy = convert_memory(
+    value,
+    source_type="numpy",
+    target_type="numpy",
+    gpu_id=0,
+)
+```
+
+`convert_memory` requires the declared source type, target type, and device id.
+The source and target `MemoryType` declarations perform conversion directly.
+The device id is required even for CPU conversions so call sites have one
+stable signature. A GPU target must declare that identifier as available;
+ArrayBridge does not silently place the value on the CPU.
+
+## Declarative decorators
+
+```python
+from arraybridge import numpy
+
+@numpy
+def normalize(image):
+    return image / max(float(image.max()), 1.0)
+```
+
+The framework decorators attach `input_memory_type`, `output_memory_type`, and
+`execution_memory_type` metadata, provide dtype/slice runtime parameters, and
+add framework-specific stream/OOM handling where supported. They do **not**
+convert inputs or outputs between frameworks and do not accept a `gpu_id`
+argument. A host runtime must call `convert_memory` at the boundary it plans and
+scope execution using the execution declaration.
+
+## Stack utilities
+
+```python
+import numpy as np
+
+from arraybridge import stack_slices, unstack_slices
+
+slices = [np.zeros((8, 8)), np.ones((8, 8))]
+stack = stack_slices(slices, memory_type="numpy", gpu_id=0)
+restored = unstack_slices(stack, memory_type="numpy", gpu_id=0)
+```
+
+`stack_slices` requires non-empty 2D inputs. `unstack_slices` requires a 3D
+array. Both validate shape and use explicit target memory/device declarations.
+
+## Installation
+
+```bash
+pip install arraybridge
+pip install "arraybridge[torch]"
+pip install "arraybridge[cupy]"
+```
+
+Documentation: <https://arraybridge.readthedocs.io>

arraybridge-0.3.0/README.md

@@ -0,0 +1,73 @@
+# arraybridge
+
+ArrayBridge provides explicit conversion and shared lifecycle utilities for
+NumPy, CuPy, PyTorch, TensorFlow, JAX, and pyclesperanto arrays.
+
+Core dependencies are NumPy and metaclass-registry. Other frameworks are
+optional.
+
+## Quick start
+
+```python
+import numpy as np
+
+from arraybridge import convert_memory, detect_memory_type
+
+value = np.arange(6).reshape(2, 3)
+assert detect_memory_type(value) == "numpy"
+
+copy = convert_memory(
+    value,
+    source_type="numpy",
+    target_type="numpy",
+    gpu_id=0,
+)
+```
+
+`convert_memory` requires the declared source type, target type, and device id.
+The source and target `MemoryType` declarations perform conversion directly.
+The device id is required even for CPU conversions so call sites have one
+stable signature. A GPU target must declare that identifier as available;
+ArrayBridge does not silently place the value on the CPU.
+
+## Declarative decorators
+
+```python
+from arraybridge import numpy
+
+@numpy
+def normalize(image):
+    return image / max(float(image.max()), 1.0)
+```
+
+The framework decorators attach `input_memory_type`, `output_memory_type`, and
+`execution_memory_type` metadata, provide dtype/slice runtime parameters, and
+add framework-specific stream/OOM handling where supported. They do **not**
+convert inputs or outputs between frameworks and do not accept a `gpu_id`
+argument. A host runtime must call `convert_memory` at the boundary it plans and
+scope execution using the execution declaration.
+
+## Stack utilities
+
+```python
+import numpy as np
+
+from arraybridge import stack_slices, unstack_slices
+
+slices = [np.zeros((8, 8)), np.ones((8, 8))]
+stack = stack_slices(slices, memory_type="numpy", gpu_id=0)
+restored = unstack_slices(stack, memory_type="numpy", gpu_id=0)
+```
+
+`stack_slices` requires non-empty 2D inputs. `unstack_slices` requires a 3D
+array. Both validate shape and use explicit target memory/device declarations.
+
+## Installation
+
+```bash
+pip install arraybridge
+pip install "arraybridge[torch]"
+pip install "arraybridge[cupy]"
+```
+
+Documentation: <https://arraybridge.readthedocs.io>

arraybridge-0.3.0/TESTING.md

@@ -0,0 +1,46 @@
+# Testing ArrayBridge
+
+This is the practical test guide. The workflow files under `.github/workflows`
+are the authority for the current CI matrix.
+
+## Local core checks
+
+```bash
+python -m pip install -e ".[dev,docs]"
+ruff check src tests
+black --check src tests
+mypy src --ignore-missing-imports
+pytest
+python -m sphinx -E -W --keep-going -b html docs/source /tmp/arraybridge-docs
+```
+
+The default suite uses real optional frameworks when installed and otherwise
+exercises declared unavailable paths and focused fakes. Markers such as
+`torch`, `tensorflow`, `jax`, `cupy`, `pyclesperanto`, and `gpu` can select or
+exclude framework-specific tests.
+
+## Real GPU lattice check
+
+On a GPU host, validate more than a single NumPy round trip:
+
+- import all installed frameworks in one fresh process;
+- enumerate framework-local devices through each `MemoryType`;
+- convert a small exact array through every available source-target pair;
+- stack and unstack one, two, and several planes in every framework;
+- verify same-framework movement across multiple local devices when present;
+- confirm absent frameworks are not imported by discovery or cleanup;
+- exercise DLPack success and explicit CPU fallback paths;
+- target OOM cleanup to the device that owned execution.
+
+Use a fresh process and unset TensorFlow/JAX allocator variables when checking
+that declaration-owned import defaults work. Framework warnings about shared
+CUDA plugin registration should be recorded separately from value, device, or
+shape failures.
+
+## Interpreting CI
+
+The main CI workflow runs the test suite across its declared Python and OS
+matrix. The manual GPU-named workflow installs CPU-capable Torch and JAX on a
+standard runner; it does not prove CUDA behavior. Real multi-framework and
+multi-device results therefore remain a required release check on suitable
+hardware.

{arraybridge-0.2.10 → arraybridge-0.3.0/docs/archive}/CI_IMPROVEMENTS.md

@@ -190,4 +190,3 @@ If issues arise, revert to previous CI by:
 ## Questions?
 
 See `TESTING.md` for detailed testing documentation.
-

arraybridge-0.3.0/docs/archive/README.md

@@ -0,0 +1,5 @@
+# Archived ArrayBridge notes
+
+These CI incident reports, migration summaries, conflict guides, and dated
+coverage plans are superseded history. Use `README.md`, `CONTRIBUTING.md`,
+`TESTING.md`, and the active Sphinx site under `docs/source/`.

arraybridge-0.3.0/docs/ci-cd.md

@@ -0,0 +1,7 @@
+# CI/CD documentation
+
+The maintained CI/CD documentation is
+[`source/ci-cd.rst`](source/ci-cd.rst). It deliberately links to the current
+[GitHub Actions workflows](https://github.com/OpenHCSDev/arraybridge/actions)
+instead of duplicating a version matrix or release procedure that can drift
+from the workflow files.

arraybridge-0.3.0/docs/source/README.md

@@ -0,0 +1,15 @@
+# ArrayBridge documentation source
+
+The active Sphinx source is this directory.
+
+From the repository root:
+
+```bash
+python -m pip install -e ".[docs]"
+python -m sphinx -E -W --keep-going -b html docs/source docs/source/_build/html
+```
+
+Narrative pages document public behavior and ownership. `api_reference.rst`
+tracks the root export surface. Keep code examples valid under
+`scripts/validate_docs.py` in the OpenHCS superproject and verify signatures
+against `src/arraybridge/` when public APIs change.

arraybridge-0.3.0/docs/source/advanced_topics.rst

@@ -0,0 +1,24 @@
+Advanced extension topics
+=========================
+
+Framework behavior is carried by each ``MemoryType`` member. Add a framework by
+extending that owning declaration:
+
+1. add the ``MemoryType`` member;
+2. provide its typed runtime and array-operation leaves;
+3. define conversion, stack, scaling, and device behavior;
+4. add cleanup and OOM behavior only when the framework supports them;
+5. exercise detection and every supported conversion pair.
+
+Do not add a parallel framework-name table in a consumer. Generic consumers use
+``MemoryType`` directly. The converter registry and historical framework config
+are generated projections, not authorities.
+
+Version 0.3 keeps the private ``_FRAMEWORK_CONFIG`` and ``_FRAMEWORK_OPS`` names
+only as read-only operation views. Their historical mapping shape is not a
+compatibility contract. Migrate callers to ``MemoryType`` methods.
+
+Conversion caching and batching belong to the caller because value lifetime and
+semantic identity are application concerns. ArrayBridge functions remain
+stateless at the conversion boundary except for declared thread-local GPU
+context.

arraybridge-0.3.0/docs/source/api_reference.rst

@@ -0,0 +1,40 @@
+API reference
+=============
+
+Public imports
+--------------
+
+``MemoryType``, ``CPU_MEMORY_TYPES``, ``GPU_MEMORY_TYPES``, ``SUPPORTED_MEMORY_TYPES``
+  Framework declarations. Each member owns import identity, conversion,
+  stacking, dtype scaling, device discovery, scoped selection, movement,
+  DLPack import/export, cleanup, and pre-import coexistence defaults.
+
+``detect_memory_type`` and ``convert_memory``
+  Detection and explicit conversion.
+
+``memory_types``, ``numpy``, ``cupy``, ``torch``, ``tensorflow``, ``jax``, ``pyclesperanto``
+  Callable memory declarations and wrappers.
+
+``DtypeConversion``
+  Output dtype policy values.
+
+``stack_slices``, ``unstack_slices``, ``process_slices``
+  Validated plane/stack operations.
+
+``cleanup_all_gpu_frameworks``
+  Installed-framework cache cleanup.
+
+``MemoryConversionError``
+  Conversion failure boundary.
+
+The canonical export list is ``arraybridge.__all__``. Names beginning with an
+underscore are implementation surfaces even when temporarily re-exported for a
+host migration.
+
+Documented public surface
+-------------------------
+
+.. automodule:: arraybridge
+   :members:
+   :exclude-members: _FRAMEWORK_CONFIG, _FRAMEWORK_OPS, _ensure_module, _execute_with_oom_recovery, _get_device_id, _supports_dlpack
+   :member-order: bysource