feat: lab-robot Phase 0 — PEI protocol + Opentrons OT-2 driver

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+* @labclaw/core-team
+robots/opentrons_ot2/ @labclaw/robot-drivers

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: labclaw

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: Report a bug in lab-robot
+title: "bug: "
+labels: bug
+assignees: ""
+---
+
+## Bug Description
+
+<!-- Clear description of the bug -->
+
+## Steps to Reproduce
+
+```python
+# Code that triggers the bug
+```
+
+## Expected Behavior
+
+<!-- What should happen -->
+
+## Actual Behavior
+
+<!-- What actually happens -->
+
+## Environment
+
+- Python version:
+- lab-robot version:
+- OS:
+- Robot hardware (if applicable):
+
+## Additional Context
+
+<!-- Logs, screenshots, or other relevant info -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature request
+about: Request a new feature or enhancement
+title: "feat: "
+labels: enhancement
+assignees: ""
+---
+
+## Feature Description
+
+<!-- Clear description of the requested feature -->
+
+## Motivation
+
+<!-- Why is this feature needed? What problem does it solve? -->
+
+## Proposed Solution
+
+<!-- Describe your proposed implementation approach -->
+
+## Alternatives Considered
+
+<!-- Any alternative approaches you've thought about -->
+
+## Additional Context
+
+<!-- Any other relevant information -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+## Description
+
+<!-- Describe your changes -->
+
+## Type
+
+- [ ] `feat` - New feature
+- [ ] `fix` - Bug fix
+- [ ] `docs` - Documentation only
+- [ ] `test` - Tests only
+- [ ] `chore` - Build, CI, tooling
+
+## Checklist
+
+- [ ] Tests pass (`make test`)
+- [ ] Coverage 100% (`pytest --cov --cov-report=term-missing`)
+- [ ] Lint clean (`ruff check .`)
+- [ ] Documentation updated (if applicable)
+- [ ] Conventional commit messages

.github/dependabot.yml

@@ -0,0 +1,9 @@
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    labels:
+      - "dependencies"
+      - "automated"

.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  lint:
+    name: lint
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - run: pip install -e ".[dev]"
+      - run: ruff check .
+      - run: ruff format --check .
+      - uses: pre-commit/action@v3.0.1
+
+  test:
+    name: test (py${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    needs: lint
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: pytest --cov --cov-fail-under=100

.gitignore

@@ -0,0 +1,28 @@
+# Python
+__pycache__/
+*.pyc
+*.pyo
+.venv/
+venv/
+
+# Testing
+.coverage
+.pytest_cache/
+htmlcov/
+
+# Linting
+.ruff_cache/
+.mypy_cache/
+
+# Packaging
+*.egg-info/
+dist/
+build/
+.eggs/
+uv.lock
+
+# Secrets (defensive)
+.env
+.env.*
+*.pem
+*.key

.pre-commit-config.yaml

@@ -0,0 +1,17 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.9.6
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: check-yaml
+      - id: check-toml
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: no-commit-to-branch
+        args: [--branch, main]

CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog
+
+All notable changes to lab-robot will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-03-24
+
+### Added
+
+- PEI (Physical Execution Interface) protocol specification with 4-layer action hierarchy
+- `RobotDriver` async protocol: connect, disconnect, execute, stop, capabilities
+- `RobotManifest` extending SkillManifest with robot-specific metadata
+- `ActionResult` rich result type with success, state, measurements, error detail
+- `ActionType` enum with Layer 0 (motion), Layer 1 (lab-ops), Layer 2 (perception), Layer 3 (system)
+- `RobotSafetyGuard` chain-of-responsibility safety framework
+- `SafetyLevel` enum (CRITICAL, HIGH, MEDIUM, LOW)
+- Opentrons OT-2 driver with simulate mode
+- Robot driver template for bootstrapping new hardware
+- Example usage and quick-start documentation
+- Full public API exports in `__init__.py`
+- 100% test coverage with pytest
+- Ruff linting and formatting configuration
+- GitHub Actions CI workflow (Python 3.11, 3.12, 3.13)
+- Pre-commit hooks (ruff, check-yaml, check-toml, no-commit-to-branch)
+- Security policy and responsible disclosure guidelines
+- PR and issue templates

CLAUDE.md

@@ -0,0 +1,37 @@
+# CLAUDE.md — lab-robot
+
+## Project Overview
+
+Physical Execution Interface (PEI) for science labs. Connects LabClaw's AI brain
+to physical robot hardware. Phase 0: Opentrons OT-2 driver (simulate mode).
+
+**Tech stack:** Python 3.11+, Pydantic 2.x, opentrons SDK, hatchling
+**Ecosystem role:** LabClaw Layer 1 — physical execution (alongside device-use for GUI)
+
+## Build & Test
+
+pip install -e ".[dev,opentrons]"
+make test
+make lint
+
+## Architecture
+
+- `src/lab_robot/` — core library (PEI protocol, types, safety)
+- `robots/` — per-robot driver packages (like device-skills' devices/)
+- RobotDriver Protocol: connect, disconnect, execute, stop, capabilities
+- Actions return rich ActionResult (not just bool)
+- Safety level defaults to CRITICAL for all robots
+
+## Code Style
+
+Same as device-skills: ruff (E,F,I,N,W,UP), line-length 100, type hints required,
+`from __future__ import annotations` in every module, Pydantic for all schemas.
+100% test coverage enforced.
+
+## Key Abstractions
+
+- `RobotDriver` — async Protocol for robot hardware (execute actions, not read data)
+- `RobotManifest` — extends SkillManifest with robot-specific fields
+- `ActionResult` — rich result with success, state, measurements, error detail
+- `RobotSafetyGuard` — chain-of-responsibility safety (planned: force, workspace, collision)
+- PEI primitives: Layer 0 (motion), Layer 1 (lab-ops), Layer 2 (perception), Layer 3 (system)

CODE_OF_CONDUCT.md

@@ -0,0 +1,117 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a
+harassment-free experience for everyone, regardless of age, body size, visible or invisible
+disability, ethnicity, sex characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive,
+and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning
+  from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their
+  explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable
+behavior and will take appropriate and fair corrective action in response to any behavior that
+they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments,
+commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of
+Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual
+is officially representing the community in public spaces. Examples of representing our
+community include using an official e-mail address, posting via an official social media account,
+or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the
+community leaders responsible for enforcement at conduct@labclaw.org. All complaints will be
+reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any
+incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences
+for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or
+unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around
+the nature of the violation and an explanation of why the behavior was inappropriate. A public
+apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the
+people involved, including unsolicited interaction with those enforcing the Code of Conduct,
+for a specified period of time. This includes avoiding interactions in community spaces as well
+as external channels like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained
+inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the
+community for a specified period of time. No public or private interaction with the people
+involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed
+during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including
+sustained inappropriate behavior, harassment of an individual, or aggression toward or
+disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1,
+available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][moz].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[moz]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations