@pikaa-ai/pikaa 0.3.22 → 0.3.24

package/skills/lamindb/SKILL.md

@@ -1,408 +0,0 @@
----
-name: lamindb
-description: Use when working with LaminDB, the open-source lineage-native lakehouse for biological datasets and models. Covers setup, artifact registration, query/search, lineage tracking, validation, ontology-backed annotation with Bionty, collections, branches, storage, and workflow integrations.
-license: Apache-2.0 license
-metadata:
-  version: "1.1"
-  skill-author: K-Dense Inc.
----
-
-# LaminDB
-
-## Overview
-
-LaminDB is an open-source, lineage-native lakehouse for biology. It makes datasets and models queryable, traceable, validated, reproducible, and FAIR (Findable, Accessible, Interoperable, Reusable) while storing data in open formats across local filesystems, S3, GCS, Hugging Face, SQLite, and Postgres.
-
-**Core Value Proposition:**
-- **Queryability**: Search and filter artifacts, records, runs, features, schemas, and collections
-- **Traceability**: Track inputs, outputs, parameters, source code, and environments for notebooks, scripts, functions, and pipelines
-- **Validation**: Curate DataFrame, AnnData, SpatialData, TileDB-SOMA, Parquet, Zarr, and other biological formats with schemas
-- **FAIR Compliance**: Standardize annotations with Bionty-backed ontologies and custom registries
-- **Change management**: Organize work with projects, branches, spaces, collections, and saved notes or plans
-
-## When to Use This Skill
-
-Use this skill when:
-
-- **Managing biological datasets**: scRNA-seq, bulk RNA-seq, spatial transcriptomics, flow cytometry, multi-modal data, EHR data
-- **Tracking computational workflows**: Notebooks, scripts, functions, shell scripts, and pipeline execution (Nextflow, Snakemake, Redun)
-- **Curating and validating data**: Schema validation, standardization, ontology-based annotation
-- **Working with biological ontologies**: Genes, proteins, cell types, tissues, diseases, pathways (via Bionty)
-- **Building data lakehouses**: Unified query interface across multiple datasets
-- **Ensuring reproducibility**: Automatic versioning, lineage tracking, environment capture
-- **Integrating ML pipelines**: Connecting with Weights & Biases, MLflow, Hugging Face, Lightning, scVI-tools
-- **Deploying data infrastructure**: Setting up local or cloud-based data management systems
-- **Collaborating on datasets**: Sharing curated, annotated data with standardized metadata
-
-## Core Capabilities
-
-LaminDB provides six interconnected capability areas, each documented in detail in the references folder.
-
-### 1. Core Concepts and Data Lineage
-
-**Core entities:**
-- **Artifacts**: Versioned datasets (DataFrame, AnnData, Parquet, Zarr, etc.)
-- **Records & ULabels**: Experimental entities, typed records, and simple labels
-- **Collections**: Versioned, immutable sets of artifacts
-- **Runs & Transforms**: Computational lineage tracking (what code produced what data)
-- **Features**: Typed metadata fields for annotation and querying
-- **Projects, Branches & Spaces**: Project grouping, change management, and access boundaries
-
-**Key workflows:**
-- Create and version artifacts from files or Python objects
-- Track notebook/script execution with `ln.track()` and `ln.finish()`
-- Track function workflows with `@ln.flow()` and `@ln.step()`
-- Annotate artifacts with records, ulabels, projects, and typed features
-- Visualize data lineage graphs with `artifact.view_lineage()`
-- Query by provenance (find all outputs from specific code/inputs)
-
-**Reference:** `references/core-concepts.md` - Read this for detailed information on artifacts, records, runs, transforms, features, versioning, and lineage tracking.
-
-### 2. Data Management and Querying
-
-**Query capabilities:**
-- Registry exploration and lookup with auto-complete
-- Single record retrieval with `get()`, `one()`, `one_or_none()`
-- Filtering with comparison operators (`__gt`, `__lte`, `__contains`, `__startswith`)
-- Feature-based queries, including expression-style queries with `Feature` objects
-- Cross-registry traversal with double-underscore syntax
-- Full-text search across registries
-- Advanced logical queries with `ln.Q` objects (AND, OR, NOT)
-- Streaming large datasets without loading into memory
-
-**Key workflows:**
-- Browse artifacts with filters and ordering
-- Query by features, creation date, creator, size, etc.
-- Stream large files in chunks or with array slicing
-- Organize data with hierarchical keys
-- Group artifacts into collections
-
-**Reference:** `references/data-management.md` - Read this for comprehensive query patterns, filtering examples, streaming strategies, and data organization best practices.
-
-### 3. Annotation and Validation
-
-**Curation process:**
-1. **Validation**: Confirm datasets match desired schemas
-2. **Standardization**: Fix typos, map synonyms to canonical terms
-3. **Annotation**: Link datasets to metadata entities for queryability
-
-**Schema types:**
-- **Flexible schemas**: Validate only known columns, allow additional metadata
-- **Minimal required schemas**: Specify essential columns, permit extras
-- **Strict schemas**: Complete control over structure and values
-
-**Supported data types:**
-- DataFrames (Parquet, CSV)
-- AnnData (single-cell genomics)
-- MuData (multi-modal)
-- SpatialData (spatial transcriptomics)
-- TileDB-SOMA (scalable arrays)
-
-**Key workflows:**
-- Define features and schemas for data validation
-- Use `DataFrameCurator`, `AnnDataCurator`, `SpatialDataCurator`, or `TiledbsomaExperimentCurator` for validation
-- Standardize values with `.cat.standardize()`
-- Map to ontologies with `.cat.add_ontology()`
-- Save curated artifacts with schema linkage
-- Query validated datasets by features
-
-**Reference:** `references/annotation-validation.md` - Read this for detailed curation workflows, schema design patterns, handling validation errors, and best practices.
-
-### 4. Biological Ontologies
-
-**Available ontologies (via Bionty):**
-- Genes (Ensembl), Proteins (UniProt)
-- Cell types (CL), Cell lines (CLO)
-- Tissues (Uberon), Diseases (Mondo, DOID)
-- Phenotypes (HPO), Pathways (GO)
-- Experimental factors (EFO), Developmental stages
-- Organisms (NCBItaxon), Drugs (DrugBank)
-
-**Key workflows:**
-- Import public ontologies with `bt.CellType.import_source()`
-- Search ontologies with keyword or exact matching
-- Standardize terms using synonym mapping
-- Explore hierarchical relationships (parents, children, ancestors)
-- Validate data against ontology terms
-- Annotate datasets with ontology records
-- Create custom terms and hierarchies
-- Handle multi-organism contexts (human, mouse, etc.)
-
-**Reference:** `references/ontologies.md` - Read this for comprehensive ontology operations, standardization strategies, hierarchy navigation, and annotation workflows.
-
-### 5. Integrations
-
-**Workflow managers:**
-- Nextflow: Track pipeline processes and outputs
-- Snakemake: Integrate into Snakemake rules
-- Redun: Combine with Redun task tracking
-- Lightning: Persist checkpoints and training metadata
-
-**MLOps platforms:**
-- Weights & Biases: Link experiments with data artifacts
-- MLflow: Track models and experiments
-- Hugging Face: Track model fine-tuning
-- scVI-tools: Single-cell analysis workflows
-
-**Storage systems:**
-- Local filesystem, AWS S3, Google Cloud Storage
-- S3-compatible (MinIO, Cloudflare R2)
-- HTTP/HTTPS endpoints (read-only)
-- HuggingFace datasets
-
-**Array stores:**
-- TileDB-SOMA (with cellxgene support)
-- DuckDB for SQL queries on Parquet files
-
-**Visualization:**
-- Vitessce for interactive spatial/single-cell visualization
-
-**Version control:**
-- Git integration for source code tracking
-
-**Reference:** `references/integrations.md` - Read this for integration patterns, code examples, and troubleshooting for third-party systems.
-
-### 6. Setup and Deployment
-
-**Installation:**
-- Current stable baseline: `lamindb==2.5.1` (released 2026-06-01; Python >=3.10, <=3.14)
-- Basic: `uv pip install 'lamindb==2.5.1'`
-- With extras: `uv pip install 'lamindb[gcp,zarr-v2,fcs]==2.5.1'`
-- Minimal namespace only: `uv pip install 'lamindb-core==2.5.1'`
-- Bionty module: included in the LaminDB docs and available as `uv pip install 'bionty==2.4.0'`
-- Optional modules: pin reviewed releases for wetlab or clinical schema modules rather than installing floating latest versions
-
-**Instance types:**
-- Local SQLite (development)
-- Cloud storage + SQLite (small teams)
-- Cloud storage + PostgreSQL (production)
-
-**Storage options:**
-- Local filesystem
-- AWS S3 with configurable regions and permissions
-- Google Cloud Storage
-- S3-compatible endpoints (MinIO, Cloudflare R2)
-
-**Configuration:**
-- Cache management for cloud files
-- Multi-user system configurations
-- Git repository sync
-- Named environment variables for credentials and connection URLs
-
-**Deployment patterns:**
-- Local dev → Cloud production migration
-- Multi-region deployments
-- Shared storage with personal instances
-
-**Reference:** `references/setup-deployment.md` - Read this for detailed installation, configuration, storage setup, database management, security best practices, and troubleshooting.
-
-## Safety and Security Defaults
-
-When helping with LaminDB setup or integrations:
-
-- Never display, log, or transmit actual API keys, cloud credentials, database passwords, or full connection strings that include secrets.
-- Prefer IAM roles, workload identity, secret managers, or named environment variables such as `LAMIN_DB_URL`, `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, and `GOOGLE_APPLICATION_CREDENTIALS`; only check whether a named variable is present, not its value.
-- Before saving content from REST APIs, external databases, or user-provided files, validate and sanitize it with an explicit schema or curator.
-- For reproducible installs, pin package versions or use a lock file. Floating installs are acceptable only when the user explicitly wants the latest upstream release.
-
-## Common Use Case Workflows
-
-### Use Case 1: Single-Cell RNA-seq Analysis with Ontology Validation
-
-```python
-import lamindb as ln
-import bionty as bt
-import anndata as ad
-
-# Start tracking a notebook/script run
-ln.track(params={"analysis": "scRNA-seq QC and annotation"})
-
-# Import cell type ontology
-bt.CellType.import_source()
-
-# Load data
-adata = ad.read_h5ad("raw_counts.h5ad")
-
-# Validate and standardize cell types
-adata.obs["cell_type"] = bt.CellType.standardize(adata.obs["cell_type"])
-
-# Curate with schema
-curator = ln.curators.AnnDataCurator(adata, schema)
-curator.validate()
-artifact = curator.save_artifact(key="scrna/validated.h5ad")
-
-# Link ontology-backed annotations for queryability
-cell_types = bt.CellType.from_values(adata.obs["cell_type"])
-artifact.cell_types.add(*cell_types)
-
-ln.finish()
-```
-
-### Use Case 2: Building a Queryable Data Lakehouse
-
-```python
-import lamindb as ln
-
-# Register multiple experiments
-for i, file in enumerate(data_files):
-    artifact = ln.Artifact.from_anndata(
-        ad.read_h5ad(file),
-        key=f"scrna/batch_{i}.h5ad",
-        description=f"scRNA-seq batch {i}"
-    ).save()
-
-    # Annotate with features
-    artifact.features.set_values({
-        "batch": i,
-        "tissue": tissues[i],
-        "condition": conditions[i]
-    })
-
-# Query across all experiments by annotated features
-immune_datasets = ln.Artifact.filter(
-    key__startswith="scrna/",
-    tissue="PBMC",
-    condition="treated"
-).to_dataframe()
-
-# Load specific datasets
-for artifact in immune_datasets:
-    adata = artifact.load()
-    # Analyze
-```
-
-### Use Case 3: ML Pipeline with W&B Integration
-
-```python
-import lamindb as ln
-import wandb
-
-# Initialize both systems
-wandb.init(project="drug-response", name="exp-42")
-ln.track(params={"model": "random_forest", "n_estimators": 100})
-
-# Load training data from LaminDB
-train_artifact = ln.Artifact.get(key="datasets/train.parquet")
-train_data = train_artifact.load()
-
-# Train model
-model = train_model(train_data)
-
-# Log to W&B
-wandb.log({"accuracy": 0.95})
-
-# Save model in LaminDB with W&B linkage
-import joblib
-joblib.dump(model, "model.pkl")
-model_artifact = ln.Artifact("model.pkl", key="models/exp-42.pkl").save()
-model_artifact.features.set_values({"wandb_run_id": wandb.run.id})
-
-ln.finish()
-wandb.finish()
-```
-
-### Use Case 4: Nextflow Pipeline Integration
-
-```python
-# In Nextflow process script
-import lamindb as ln
-
-ln.track()
-
-# Load input artifact
-input_artifact = ln.Artifact.get(key="raw/batch_${batch_id}.fastq.gz")
-input_path = input_artifact.cache()
-
-# Process (alignment, quantification, etc.)
-# ... Nextflow process logic ...
-
-# Save output
-output_artifact = ln.Artifact(
-    "counts.csv",
-    key="processed/batch_${batch_id}_counts.csv"
-).save()
-
-ln.finish()
-```
-
-For native Nextflow projects, prefer the `nf-lamin` plugin and current `nextflow.config` patterns when available; use inline Python tracking for small or custom pipeline steps.
-
-## Getting Started Checklist
-
-To start using LaminDB effectively:
-
-1. **Installation & Setup** (`references/setup-deployment.md`)
-   - Install pinned LaminDB and required extras
-   - Authenticate with `lamin login`
-   - Initialize instance with `lamin init --storage ...`
-
-2. **Learn Core Concepts** (`references/core-concepts.md`)
-   - Understand Artifacts, Records, Runs, Transforms
-   - Practice creating and retrieving artifacts
-   - Implement `ln.track()`/`ln.finish()` or `@ln.flow()`/`@ln.step()` in workflows
-
-3. **Master Querying** (`references/data-management.md`)
-   - Practice filtering and searching registries
-   - Learn feature-based queries and expression-style filters
-   - Experiment with streaming large files
-
-4. **Set Up Validation** (`references/annotation-validation.md`)
-   - Define features relevant to research domain
-   - Create schemas for data types
-   - Practice curation workflows
-
-5. **Integrate Ontologies** (`references/ontologies.md`)
-   - Import relevant biological ontologies (genes, cell types, etc.)
-   - Validate existing annotations
-   - Standardize metadata with ontology terms
-
-6. **Connect Tools** (`references/integrations.md`)
-   - Integrate with existing workflow managers
-   - Link ML platforms for experiment tracking
-   - Configure cloud storage and compute
-
-## Key Principles
-
-Follow these principles when working with LaminDB:
-
-1. **Track everything**: Use `ln.track()` at the start of every analysis for automatic lineage capture
-
-2. **Validate early**: Define schemas and validate data before extensive analysis
-
-3. **Use ontologies**: Leverage public biological ontologies for standardized annotations
-
-4. **Organize with keys**: Structure artifact keys hierarchically (e.g., `project/experiment/batch/file.h5ad`)
-
-5. **Query metadata first**: Filter and search before loading large files
-
-6. **Version, don't duplicate**: Use built-in versioning instead of creating new keys for modifications
-
-7. **Annotate with features**: Define typed features and use `artifact.features.set_values()` for queryable metadata
-
-8. **Document thoroughly**: Add descriptions to artifacts, schemas, and transforms
-
-9. **Leverage lineage**: Use `view_lineage()` to understand data provenance
-
-10. **Start local, scale cloud**: Develop locally with SQLite, deploy to cloud with PostgreSQL
-
-## Reference Files
-
-This skill includes comprehensive reference documentation organized by capability:
-
-- **`references/core-concepts.md`** - Artifacts, records, runs, transforms, features, versioning, lineage
-- **`references/data-management.md`** - Querying, filtering, searching, streaming, organizing data
-- **`references/annotation-validation.md`** - Schema design, curation workflows, validation strategies
-- **`references/ontologies.md`** - Biological ontology management, standardization, hierarchies
-- **`references/integrations.md`** - Workflow managers, MLOps platforms, storage systems, tools
-- **`references/setup-deployment.md`** - Installation, configuration, deployment, troubleshooting
-
-Read the relevant reference file(s) based on the specific LaminDB capability needed for the task at hand.
-
-## Additional Resources
-
-- **Official Documentation**: https://docs.lamin.ai
-- **API Reference**: https://docs.lamin.ai/api
-- **GitHub Repository**: https://github.com/laminlabs/lamindb
-- **Tutorial**: https://docs.lamin.ai/tutorial
-- **FAQ**: https://docs.lamin.ai/faq
-

package/skills/latchbio-integration/SKILL.md

@@ -1,227 +0,0 @@
----
-name: latchbio-integration
-description: Build, register, debug, and operate bioinformatics workflows on Latch using the Python SDK, CLI, Latch Data and Registry, Nextflow, Snakemake, programmatic execution, and Latch MCP. Use when authoring or deploying Latch workflows, configuring resources or interfaces, moving data, integrating Registry, or launching and monitoring runs.
-license: MIT
-allowed-tools: Read Write Edit Bash
-compatibility: Requires network access and a Latch account. The current stable SDK requires Python 3.9+; Python 3.12 is recommended. Uses uv for installation. Docker is needed for local image builds, while remote registration is the CLI default.
-metadata:
-  version: "2.0"
-  skill-author: K-Dense Inc.
----
-
-# LatchBio Integration
-
-## Current Baseline
-
-This skill targets **Latch SDK 2.76.8**, released July 10, 2026. The package
-metadata supports Python 3.9–3.12 and declares Python 3.9+.
-
-Treat the installed package and its changelog as authoritative when a guide
-disagrees with the SDK. Some Latch guides retain older Python ranges or
-compatibility-specific pre-release pins, especially the Snakemake v2 tutorial.
-Never combine commands or imports from different tracks without checking their
-version requirements.
-
-## When to Use
-
-Use this skill to:
-
-- Create or maintain Python SDK workflows and task graphs
-- Package and register Python, Nextflow, or Snakemake pipelines
-- Configure task CPU, memory, storage, GPU, caching, retries, and timeouts
-- Work with Latch Data through `LPath`, `LatchFile`, `LatchDir`, or the CLI
-- Read or update Latch Registry projects, tables, and records
-- Design workflow forms, launch plans, samplesheets, messages, and result links
-- Stage and debug workflow images with `latch register --staging` and `latch develop`
-- Launch and monitor workflows through Python or Latch MCP
-- Discover and use ready-to-run Latch workflows
-
-## Route to the Right Reference
-
-Read only the references needed for the task:
-
-| Need | Reference |
-|---|---|
-| Python workflows, tasks, maps, conditions, caching | `references/workflow-creation.md` |
-| `LPath`, legacy file types, Latch URLs, data CLI | `references/data-management.md` |
-| Registry reads, transactions, samplesheets | `references/registry.md` |
-| CPU, memory, storage, GPU, dynamic resources | `references/resource-configuration.md` |
-| Nextflow and Snakemake packaging | `references/nextflow-snakemake.md` |
-| Metadata, forms, launch plans, messages, automations | `references/ui-and-automation.md` |
-| Registration, development, execution, monitoring | `references/operations-and-debugging.md` |
-| Ready-to-use workflows and `latch.verified` | `references/verified-workflows.md` |
-| Remote MCP setup and tool workflow | `references/latch-mcp.md` |
-
-Before relying on a symbol, run `scripts/inspect_latch_sdk.py` against the
-target SDK version. It performs local imports only and does not authenticate or
-make network requests.
-
-## Installation and Authentication
-
-For a reproducible environment:
-
-```bash
-uv venv --python 3.12
-source .venv/bin/activate
-uv pip install "latch==2.76.8"
-```
-
-On Windows, use WSL for the documented Linux workflow tooling.
-
-Authenticate through the supported OAuth flow; do not read, print, copy, or
-parse `~/.latch/token` manually:
-
-```bash
-latch login
-latch workspace
-```
-
-Select a workspace non-interactively when its numeric ID is already known:
-
-```bash
-latch workspace --id 12345
-```
-
-`latch login` credentials are for the SDK and CLI. Latch MCP uses a separate
-OAuth authorization and its credentials cannot be reused for general SDK
-access.
-
-## Fast Path
-
-Create and remotely register the maintained subprocess template:
-
-```bash
-latch init covid-wf --template subprocess
-latch register --yes --open covid-wf
-```
-
-Remote image building is the default. Use `--no-remote` only when a local
-Docker daemon is available and a local build is intentional.
-
-## Minimal Python Workflow
-
-Keep workflow bodies declarative: invoke tasks and return their promises.
-Perform computation and side effects inside tasks.
-
-```python
-from latch import small_task, workflow
-
-
-@small_task
-def reverse_complement(sequence: str) -> str:
-    table = str.maketrans("ACGTacgt", "TGCAtgca")
-    return sequence.translate(table)[::-1]
-
-
-@workflow
-def reverse_complement_workflow(sequence: str) -> str:
-    """Return the reverse complement of a DNA sequence."""
-    return reverse_complement(sequence=sequence)
-```
-
-Use `@workflow(metadata)` when the generated interface needs custom labels,
-sections, validation rules, samplesheets, or documentation links. Use `LatchFile` or
-`LatchDir` for automatic task input staging and output upload; use `LPath` for
-imperative remote path operations.
-
-## Recommended Development Lifecycle
-
-1. **Inspect compatibility**
-   - Confirm the installed SDK and Python version.
-   - Identify whether the project is Python, Nextflow, the legacy Snakemake
-     flag path, or the separately pinned Snakemake v2 tutorial track.
-
-2. **Define a typed interface**
-   - Annotate every workflow and task input and output.
-   - Keep module import time free of network calls, data mutations, and secret
-     retrieval. Isolate documented exceptions such as `workflow_reference`,
-     which resolves the active workspace when its decorator is evaluated.
-   - Use dataclasses and enums for structured parameters.
-
-3. **Configure metadata and resources**
-   - Match metadata parameter keys to the workflow signature.
-   - Start with named task decorators, then use `custom_task` only when measured
-     requirements justify it.
-
-4. **Validate in the execution image**
-
-   Fresh Nextflow and Snakemake projects must generate their
-   version-compatible Python entrypoint before staging. In SDK 2.76.8, the
-   staging branch does not generate one from `--nf-script` or `--snakefile`.
-
-   ```bash
-   latch register --staging .
-   latch develop .
-   ```
-
-   Re-run staging registration after changing the Dockerfile or dependencies.
-   Edits made inside the development container are not synced back.
-
-5. **Register deliberately**
-
-   ```bash
-   latch register --yes --open .
-   ```
-
-   Useful controls:
-
-   ```bash
-   latch register --workspace-id 12345 .
-   latch register --mark-as-release .
-   latch register --workflow-module wf.custom_entrypoint .
-   ```
-
-   Duplicate registration exits with status `2`; it is not the same as a build
-   failure.
-
-6. **Launch only after reviewing cost and parameters**
-   - Prefer the Console or Latch MCP for interactive operation.
-   - Prefer `latch_cli.services.launch.launch_v2` for Python automation.
-   - Do not use the deprecated `latch launch` CLI as a new integration pattern.
-
-7. **Monitor and verify**
-   - Check terminal status, task logs, result links, and scientific outputs.
-   - Treat successful orchestration as necessary but not sufficient scientific
-     validation.
-
-## Operational Safety
-
-- Ask for confirmation before launching paid compute, especially GPU or large
-  batch runs.
-- Ask for confirmation before `LPath.rmr`, `latch rmr`, Registry deletion, or
-  overwriting shared destinations.
-- Never log secrets, SDK tokens, signed URLs, or secret values.
-- Call `get_secret()` only inside a task, use the returned value only for its
-  intended service, and never return it as workflow output.
-- Do not pass untrusted strings through shell commands. Prefer argument lists
-  with `subprocess.run(..., check=True)`.
-- Pin the SDK and workflow dependencies for releases. Upgrade only after
-  reviewing the changelog and re-running staging tests.
-- Treat generated files as generated: customize the documented extension file
-  rather than editing output that the CLI will overwrite.
-
-## Inspect the Installed SDK
-
-From this skill directory:
-
-```bash
-uv run --no-project --python 3.12 --with "latch==2.76.8" \
-  python scripts/inspect_latch_sdk.py
-```
-
-Use JSON output for automated comparisons:
-
-```bash
-uv run --no-project --python 3.12 --with "latch==2.76.8" \
-  python scripts/inspect_latch_sdk.py --json
-```
-
-## Authoritative Sources
-
-- Documentation index: https://wiki.latch.bio/llms.txt
-- Workflow and SDK guides: https://wiki.latch.bio/workflows/overview
-- SDK API reference: https://wiki.latch.bio/reference/sdk
-- PyPI package: https://pypi.org/project/latch/
-- SDK 2.76.8 release source: https://github.com/latchbio/latch/tree/0faa9dcd8186444ac008f50adf95d43f0fa30e06
-- SDK changelog: https://github.com/latchbio/latch/blob/0faa9dcd8186444ac008f50adf95d43f0fa30e06/CHANGELOG.md
-- Latch Console: https://console.latch.bio