Fix CI: declare boto3 as the bedrock extra; install it in CI

The 0.6.0 AWS Bedrock target uses boto3 (live harness create/invoke + skill S3
upload), but boto3 was never a declared dependency — so CI (`.[dev,google]`) ran
without it and `test_live_harness_orchestration.py` (which patches boto3.client)
errored on main.

- pyproject: add `bedrock = ["boto3>=1.43"]` optional extra (parallels `google`);
  live `--target bedrock` deploy needs it (audit/plan/export stay offline-only)
- ci.yml: install `.[dev,google,bedrock]` (offline) and `.[dev,bedrock]` (live)
- test_live_harness_orchestration.py: `pytest.importorskip("boto3")` so a lean
  `.[dev]` install skips it cleanly instead of erroring
- docs/deploy-bedrock.md: `pip install "agentlift[bedrock]"` in the setup

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: phuryn

.github/workflows/ci.yml

@@ -17,9 +17,11 @@ jobs:
       - uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
-      # install the Google ADK stack too, so the ADK-dependent offline tests
-      # (generated-package build + import) actually run on GitHub instead of skipping
-      - run: python -m pip install -e ".[dev,google]"
+      # install the Google ADK + AWS Bedrock (boto3) stacks too, so the ADK- and
+      # boto3-dependent offline tests (generated-package build + import; the harness
+      # deploy-path orchestration test that patches boto3.client) actually run on
+      # GitHub instead of skipping
+      - run: python -m pip install -e ".[dev,google,bedrock]"
       - name: run offline suite (no API key)
         run: pytest -m "not live" -q
 
@@ -34,7 +36,7 @@ jobs:
       - uses: actions/setup-python@v5
         with:
           python-version: "3.12"
-      - run: python -m pip install -e ".[dev]"
+      - run: python -m pip install -e ".[dev,bedrock]"
       - name: run live suite (skips automatically if no key)
         env:
           ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}

docs/deploy-bedrock.md

@@ -106,6 +106,8 @@ managed AgentCore Harness: config only, no container, minutes. `--mode auto` sel
 single-agent folder; a multi-agent *team* routes to the Runtime instead.
 
 ```bash
+pip install "agentlift[bedrock]"          # the live deploy paths need boto3 (audit/plan/export don't)
+
 # IAM creds on PATH (NOT the bearer token), the execution role, + a skills bucket if you have skills:
 export AGENTLIFT_BEDROCK_EXECUTION_ROLE_ARN=arn:aws:iam::<acct>:role/agentlift-harness
 export AGENTLIFT_BEDROCK_S3_BUCKET=my-agentlift-skills-bucket   # only if the folder has skills

pyproject.toml

@@ -33,6 +33,13 @@ google = [
     "google-adk>=1.34.3",
     "google-cloud-aiplatform[adk,agent_engines]>=1.119",
 ]
+# Optional: the AWS Bedrock AgentCore stack. Needed only for the *live* `--target
+# bedrock` deploy paths (the harness create/invoke + skill S3 upload, and the Runtime
+# hosted create); `audit`/`plan`/`export bedrock-strands` are offline and need none of
+# it. The AgentCore harness/runtime control-plane ops require a recent botocore.
+bedrock = [
+    "boto3>=1.43",
+]
 
 [project.urls]
 Homepage = "https://github.com/phuryn/agentlift"

tests/test_live_harness_orchestration.py

@@ -16,6 +16,10 @@
 
 import pytest
 
+# this test patches boto3.client to drive the deploy wrapper offline; skip cleanly if the
+# AWS extra (`pip install agentlift[bedrock]`) isn't installed rather than erroring.
+pytest.importorskip("boto3")
+
 HERE = os.path.dirname(os.path.abspath(__file__))
 ACCOUNT = "424242424242"          # fake account id the receipt must redact
 ARN = f"arn:aws:bedrock-agentcore:us-west-2:{ACCOUNT}:harness/agentlift_assistant-abc1234567"