tai42-e2e 0.3.0__tar.gz

tai42_e2e-0.3.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

tai42_e2e-0.3.0/NOTICE

@@ -0,0 +1,9 @@
+tai42
+Copyright 2026 tai42
+
+This product includes software developed at tai42 (https://tai42.ai).
+Licensed under the Apache License, Version 2.0.
+
+This repository packages the tai42 core libraries (tai42-contract, tai42-kit,
+tai42-skeleton), the tai42 plugins, and the tai42-e2e harness. Each distributed
+package carries the same attribution above.

tai42_e2e-0.3.0/PKG-INFO

@@ -0,0 +1,234 @@
+Metadata-Version: 2.4
+Name: tai42-e2e
+Version: 0.3.0
+Summary: Cross-repo end-to-end functional test suite for the tai / AgenticOS ecosystem: boots the real multi-process deployment topology (multi-worker skeleton server, backend worker, metrics server, real Redis, real Postgres) and exercises it over HTTP.
+Author-email: tai42 <oss@tai42.ai>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://tai42.ai
+Keywords: mcp,e2e,integration-tests,cross-process,tai
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Operating System :: OS Independent
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: tai42-contract<0.4,>=0.3
+Requires-Dist: tai42-kit[curl,jq,llm,postgres,redis,uvicorn]<0.3,>=0.2
+Requires-Dist: tai42-skeleton[files,toolbox]<0.5,>=0.4
+Requires-Dist: tai42-toolbox[chain,http,prometheus,proxy]<0.4,>=0.3
+Requires-Dist: tai42-tools-stripe<0.4,>=0.3
+Requires-Dist: tai42-agents<0.4,>=0.3
+Requires-Dist: tai42-identity-redis<0.3,>=0.2
+Requires-Dist: tai42-accounts-postgres<0.4,>=0.3
+Requires-Dist: tai42-accounts-oidc<0.3,>=0.2
+Requires-Dist: tai42-identity-oidc<0.3,>=0.2
+Requires-Dist: tai42-backend-arq<0.4,>=0.3
+Requires-Dist: tai42-backend-celery<0.4,>=0.3
+Requires-Dist: tai42-backend-rq<0.4,>=0.3
+Requires-Dist: tai42-storage-local<0.3,>=0.2
+Requires-Dist: tai42-webhook-verifier-github<0.3,>=0.2
+Requires-Dist: tai42-webhook-verifier-stripe<0.3,>=0.2
+Requires-Dist: tai42-channel-telegram<0.3,>=0.2
+Requires-Dist: tai42-channel-slack<0.3,>=0.2
+Requires-Dist: tai42-channel-twilio<0.3,>=0.2
+Requires-Dist: tai42-channel-whatsapp<0.3,>=0.2
+Requires-Dist: tai42-monitoring-langfuse<0.3,>=0.2
+Requires-Dist: pytest>=8
+Requires-Dist: pytest-asyncio>=0.25
+Requires-Dist: pytest-timeout>=2.3
+Requires-Dist: httpx>=0.28
+Requires-Dist: fastmcp<4,>=3.2
+Requires-Dist: redis>=5
+Requires-Dist: psycopg[binary]>=3.2
+Requires-Dist: prometheus-client>=0.24
+Requires-Dist: joserfc<2,>=1.7
+Requires-Dist: fastapi>=0.135
+Requires-Dist: uvicorn>=0.43
+Requires-Dist: pydantic>=2.12
+Requires-Dist: pydantic-settings>=2.13
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: celery<6,>=5.6
+Requires-Dist: celery-pydantic<2,>=1.0
+Dynamic: license-file
+
+# tai42-e2e
+
+The cross-repo, real-stack, end-to-end functional test suite for the tai /
+AgenticOS ecosystem. It boots the REAL deployment topology — a multi-worker
+uvicorn skeleton server, a separate backend worker process, a separate metrics
+server process, real Redis, real Postgres — and drives it over HTTP.
+
+**Why this suite exists.** Every member suite (tai42-contract, tai42-kit,
+tai42-toolbox, tai42-agents, tai42-skeleton) is single-process, in-memory, and
+FakeRedis-backed by design, and stays that way. That leaves a whole class of
+bug invisible: the ones that live in the seam between processes — env-var
+ordering across a spawn boundary, a registry mutated on one worker and read on
+another, a socket flipped process-wide, a counter written in one process and
+scraped from another. `tai-e2e` is the only suite that can catch them, because
+it is the only one that runs the real multi-process topology.
+
+## Quickstart
+
+```bash
+docker compose up -d          # core profile: redis:7-alpine + postgres:16
+uv python install 3.13
+uv sync
+uv run pytest                 # the default variant leg: arq + redis identity + local storage
+```
+
+The suite runs sequentially in one pytest process (no xdist by design — a stack
+is already 5-8 OS processes). A missing Redis/Postgres fails loudly at session
+start with the `docker compose up -d` hint. The shared Redis needs no modules —
+access control stores its records as plain hashes and counters.
+
+### Variant legs
+
+Every stack is rendered through a plugin VARIANT triple, selected per pytest
+process and printed in the run header. An unknown value fails loudly, naming the
+valid set.
+
+| Env var | Values | Default |
+|---------|--------|---------|
+| `TAI_E2E_BACKEND` | `arq` \| `rq` \| `celery` | `arq` |
+| `TAI_E2E_IDENTITY` | `redis` \| `fixture` (PG-backed, from `tai42_e2e_fixtures`) | `redis` |
+| `TAI_E2E_STORAGE` | `local` \| `fixture` (own on-disk layout) | `local` |
+
+```bash
+# the rq and celery backend legs — celery needs its broker
+docker compose --profile celery up -d
+TAI_E2E_BACKEND=rq     uv run pytest -m "not backendless"
+TAI_E2E_BACKEND=celery uv run pytest -m "not backendless"
+
+# the second identity/storage values, on the identity/storage-bearing suites
+TAI_E2E_IDENTITY=fixture TAI_E2E_STORAGE=fixture uv run pytest tests/redis_semantics tests/storage tests/harness
+```
+
+`backendless` marks a module whose stack runs no backend worker: it exercises no
+backend seam, so the non-default backend legs deselect it with
+`-m "not backendless"` instead of re-running it three times.
+
+### The checkpoint Redis (agents state)
+
+The langgraph `redis` checkpoint/store provider needs the RediSearch + RedisJSON
+modules, which `redis:7-alpine` does not carry. A second, module-capable Redis is
+compose-gated behind the `agents-redis` profile and pointed at by
+`TAI_E2E_CHECKPOINT_REDIS_URL` (see `.env.example`); the specs that drive it skip
+loudly with the compose hint when it is unset, and session start fails loudly if
+the URL points at an image without the modules.
+
+```bash
+docker compose --profile agents-redis up -d
+```
+
+## Seam classes
+
+| # | Bug class | Test dir |
+|---|-----------|----------|
+| C1 | Multiproc-metrics writer/reader split across processes | `tests/metrics/` |
+| C2 | Import-order / module-freeze of `prometheus_client` | `tests/metrics/` |
+| C3 | Cross-entrypoint lifecycle on the shared mmap dir | `tests/metrics/` |
+| C4 | Cross-worker registry divergence (sub-MCP, presets, tool-extensions) | `tests/crossworker/` |
+| C5 | Cross-process lost-update on shared config files | `tests/crossworker/` |
+| C6 | Real-Redis / real-Postgres semantics (rate limit, AC, interactions, connectors) | `tests/redis_semantics/`, `tests/interactions/`, `tests/connectors/` |
+| C7 | Cross-repo running-service contract (agents, webhooks, tool-runs, storage, monitoring) | `tests/agents/`, `tests/webhooks/`, ... |
+| C8 | Process-global socket-state bleed (proxy extension) | `tests/proxy/` |
+| C9 | Reload / control-plane fan-out divergence | `tests/reload/` |
+| P1 | Plugin-seam switch (backend / identity / storage variants, broker isolation) | `tests/backend/`, `tests/storage/` |
+| P2 | Infra failure injection (worker crash, Redis/Postgres outage) | `tests/failures/` |
+| P3 | Scheduling across backends (`schedule_task`, the scheduler process) | `tests/scheduling/` |
+| P4 | Correctness under width (4 uvicorn workers, ≥32 in-flight) | `tests/scale/` |
+| P5 | Tool extensions through the stack (cache, chain, monitor, ask_external, output_schema) | `tests/extensions/` |
+
+## Layout
+
+- `src/tai42_e2e/` — the harness library (imported by tests, never by the SUT):
+  boot engine (`stack.py`), process spawning (`procs.py`), Redis/PG/RabbitMQ admin
+  (`redisx.py`, `pg.py`, `rabbitx.py`), the plugin-variant adapters (`variants.py`),
+  manifest/env profile builders (`manifests.py`), the scripted LLM stub
+  (`llmstub.py`), the net fixtures (`netfixtures.py`), the severable TCP relay the
+  outage specs inject with (`tcprelay.py`), the single waiting primitive
+  (`waiting.py`), and failure diagnostics (`diagnostics.py`).
+- `src/tai42_e2e_fixtures/` — SUT-SIDE modules the spawned server imports via its
+  manifest: the probe tools (`tools.py`), the fixture OAuth connector provider
+  (`connector_provider.py`), and the second value on each pluggable axis — the
+  PG-backed identity provider (`identity_provider.py`), the storage backend
+  (`storage.py`), and the monitoring backend (`monitor_backend.py`).
+- `tests/` — the suites by seam class, plus `tests/harness/` self-tests.
+- `docs/adding-a-test.md` — the 6-step recipe for a new feature's e2e test.
+
+## Metrics-dir isolation (the C2 hard rule)
+
+The harness NEVER sets `PROMETHEUS_MULTIPROC_DIR` in a child env — stamping it
+is the entrypoint's own job (`activate_multiproc_env`) and is exactly what the
+C2 import-order tests verify. Per-stack (and per-replica) metrics dirs are
+controlled entirely via `TMPDIR`: `MetricsSettings.prometheus_multiproc_dir`
+defaults to `<tempfile.gettempdir()>/tai42_prometheus`, so pointing a process's
+`TMPDIR` at a per-run-family dir gives that family its own multiproc dir with
+the env var untouched. `stack.py` asserts the rule on every child env.
+
+## xfail policy
+
+A test for a fix that has not yet landed in the workspace is marked
+`xfail(strict=True)` with the observed-behavior reason, so it flips loudly
+(xpass → failure) the moment the fix lands.
+
+## CI
+
+The fleet e2e runs from the monorepo root workflow, `.github/workflows/ci.yml`,
+in two jobs gated by the `changes` filter (any member carrying an e2e trigger, or
+a change to a shared root, sets `run_e2e`):
+
+- `e2e` — one matrix leg per triggered backend (`arq`, `rq`, `celery`), under
+  `TAI_E2E_FLEET=1` with `redis` identity and `local` storage. Services:
+  `redis:7-alpine` (shared), `postgres:16-alpine`, and `redis:8` — the
+  module-capable checkpoint Redis the arq leg points
+  `TAI_E2E_CHECKPOINT_REDIS_URL` at. The celery leg brings its RabbitMQ up from
+  the compose `celery` profile; non-arq legs deselect `-m "not backendless"`. The
+  langfuse monitoring profile runs on the arq leg only when the `run_monitoring`
+  gate is on (a change under `plugins/monitoring-langfuse`, `core`, or `e2e`, or a
+  manual `workflow_dispatch`). When the private-repo token is present it also runs
+  the marketplace suite (`TAI_E2E_MARKETPLACE=1`), installing the git-sourced
+  `tai42-marketplace` and booting it as harness processes.
+- `ui-e2e` — needs `e2e`; boots redis + postgres, clones `tai-studio`, builds the
+  Studio SPA, and runs the Playwright chromium suite in `ui/`. When the `run_browsers`
+  gate is on (a change under `e2e/ui`, or a manual `workflow_dispatch`) it also
+  widens the matrix onto firefox + webkit. With the token it also clones the private
+  `tai-marketplace-web` and runs the marketplace browser specs under
+  `TAI_E2E_MARKETPLACE=1`.
+
+The marketplace legs need the private `tai42ai/tai-marketplace` and
+`tai42ai/tai-marketplace-web` repos, so they run only when the `RELEASE_PLEASE_TOKEN`
+secret is available — a fork PR has no secrets, so those steps skip with a visible
+`::warning::` rather than failing. Other external consumers install this harness as
+the published `tai42-e2e` package and run their own suites against it. Any consumer
+booting the studio stack must also install the Studio reference plugin from the
+`tai42ai/tai-studio` repo (`e2e/reference-plugin`), which the studio profile manifest
+names but the harness does not carry as a runtime dependency.
+
+## Marketplace area (opt-in)
+
+`tests/marketplace/` only collects when `TAI_E2E_MARKETPLACE=1`; unset, it is
+skipped at collection like `tests/monitoring/`. When on, the harness boots the
+`tai42-marketplace` registry — installed from its git source via the `marketplace`
+dependency group — as a harness-managed process (the API server) on an isolated
+Postgres database: **no extra compose profile**; it rides the core
+`docker compose up -d` infra. The suite forges REAL fixture wheels (and one source
+tarball) from the in-repo `fixtures/marketplace_plugins` tree
+(`TAI_E2E_MARKETPLACE_FIXTURES` overrides it), served over a local package index,
+seeds them through the registry's real ingest pipeline, which publishes each version
+synchronously, and the skeleton REALLY pip-installs them into the one shared venv —
+so every lifecycle spec ends with its own uninstall and a session guard raises loudly
+on any leftover distribution (never auto-cleaning). The ui leg additionally
+pnpm-builds and serves the public `tai-marketplace-web` checkout and drives the Studio
+marketplace page and the public site over a browser.
+
+```bash
+docker compose up -d
+TAI_E2E_MARKETPLACE=1 uv run pytest tests/marketplace
+# the browser legs (built Studio dist + the tai-marketplace-web checkout):
+cd ui && TAI_E2E_MARKETPLACE=1 pnpm exec playwright test tests/marketplace.spec.ts tests/marketplace-web.spec.ts
+```

tai42_e2e-0.3.0/README.md

@@ -0,0 +1,177 @@
+# tai42-e2e
+
+The cross-repo, real-stack, end-to-end functional test suite for the tai /
+AgenticOS ecosystem. It boots the REAL deployment topology — a multi-worker
+uvicorn skeleton server, a separate backend worker process, a separate metrics
+server process, real Redis, real Postgres — and drives it over HTTP.
+
+**Why this suite exists.** Every member suite (tai42-contract, tai42-kit,
+tai42-toolbox, tai42-agents, tai42-skeleton) is single-process, in-memory, and
+FakeRedis-backed by design, and stays that way. That leaves a whole class of
+bug invisible: the ones that live in the seam between processes — env-var
+ordering across a spawn boundary, a registry mutated on one worker and read on
+another, a socket flipped process-wide, a counter written in one process and
+scraped from another. `tai-e2e` is the only suite that can catch them, because
+it is the only one that runs the real multi-process topology.
+
+## Quickstart
+
+```bash
+docker compose up -d          # core profile: redis:7-alpine + postgres:16
+uv python install 3.13
+uv sync
+uv run pytest                 # the default variant leg: arq + redis identity + local storage
+```
+
+The suite runs sequentially in one pytest process (no xdist by design — a stack
+is already 5-8 OS processes). A missing Redis/Postgres fails loudly at session
+start with the `docker compose up -d` hint. The shared Redis needs no modules —
+access control stores its records as plain hashes and counters.
+
+### Variant legs
+
+Every stack is rendered through a plugin VARIANT triple, selected per pytest
+process and printed in the run header. An unknown value fails loudly, naming the
+valid set.
+
+| Env var | Values | Default |
+|---------|--------|---------|
+| `TAI_E2E_BACKEND` | `arq` \| `rq` \| `celery` | `arq` |
+| `TAI_E2E_IDENTITY` | `redis` \| `fixture` (PG-backed, from `tai42_e2e_fixtures`) | `redis` |
+| `TAI_E2E_STORAGE` | `local` \| `fixture` (own on-disk layout) | `local` |
+
+```bash
+# the rq and celery backend legs — celery needs its broker
+docker compose --profile celery up -d
+TAI_E2E_BACKEND=rq     uv run pytest -m "not backendless"
+TAI_E2E_BACKEND=celery uv run pytest -m "not backendless"
+
+# the second identity/storage values, on the identity/storage-bearing suites
+TAI_E2E_IDENTITY=fixture TAI_E2E_STORAGE=fixture uv run pytest tests/redis_semantics tests/storage tests/harness
+```
+
+`backendless` marks a module whose stack runs no backend worker: it exercises no
+backend seam, so the non-default backend legs deselect it with
+`-m "not backendless"` instead of re-running it three times.
+
+### The checkpoint Redis (agents state)
+
+The langgraph `redis` checkpoint/store provider needs the RediSearch + RedisJSON
+modules, which `redis:7-alpine` does not carry. A second, module-capable Redis is
+compose-gated behind the `agents-redis` profile and pointed at by
+`TAI_E2E_CHECKPOINT_REDIS_URL` (see `.env.example`); the specs that drive it skip
+loudly with the compose hint when it is unset, and session start fails loudly if
+the URL points at an image without the modules.
+
+```bash
+docker compose --profile agents-redis up -d
+```
+
+## Seam classes
+
+| # | Bug class | Test dir |
+|---|-----------|----------|
+| C1 | Multiproc-metrics writer/reader split across processes | `tests/metrics/` |
+| C2 | Import-order / module-freeze of `prometheus_client` | `tests/metrics/` |
+| C3 | Cross-entrypoint lifecycle on the shared mmap dir | `tests/metrics/` |
+| C4 | Cross-worker registry divergence (sub-MCP, presets, tool-extensions) | `tests/crossworker/` |
+| C5 | Cross-process lost-update on shared config files | `tests/crossworker/` |
+| C6 | Real-Redis / real-Postgres semantics (rate limit, AC, interactions, connectors) | `tests/redis_semantics/`, `tests/interactions/`, `tests/connectors/` |
+| C7 | Cross-repo running-service contract (agents, webhooks, tool-runs, storage, monitoring) | `tests/agents/`, `tests/webhooks/`, ... |
+| C8 | Process-global socket-state bleed (proxy extension) | `tests/proxy/` |
+| C9 | Reload / control-plane fan-out divergence | `tests/reload/` |
+| P1 | Plugin-seam switch (backend / identity / storage variants, broker isolation) | `tests/backend/`, `tests/storage/` |
+| P2 | Infra failure injection (worker crash, Redis/Postgres outage) | `tests/failures/` |
+| P3 | Scheduling across backends (`schedule_task`, the scheduler process) | `tests/scheduling/` |
+| P4 | Correctness under width (4 uvicorn workers, ≥32 in-flight) | `tests/scale/` |
+| P5 | Tool extensions through the stack (cache, chain, monitor, ask_external, output_schema) | `tests/extensions/` |
+
+## Layout
+
+- `src/tai42_e2e/` — the harness library (imported by tests, never by the SUT):
+  boot engine (`stack.py`), process spawning (`procs.py`), Redis/PG/RabbitMQ admin
+  (`redisx.py`, `pg.py`, `rabbitx.py`), the plugin-variant adapters (`variants.py`),
+  manifest/env profile builders (`manifests.py`), the scripted LLM stub
+  (`llmstub.py`), the net fixtures (`netfixtures.py`), the severable TCP relay the
+  outage specs inject with (`tcprelay.py`), the single waiting primitive
+  (`waiting.py`), and failure diagnostics (`diagnostics.py`).
+- `src/tai42_e2e_fixtures/` — SUT-SIDE modules the spawned server imports via its
+  manifest: the probe tools (`tools.py`), the fixture OAuth connector provider
+  (`connector_provider.py`), and the second value on each pluggable axis — the
+  PG-backed identity provider (`identity_provider.py`), the storage backend
+  (`storage.py`), and the monitoring backend (`monitor_backend.py`).
+- `tests/` — the suites by seam class, plus `tests/harness/` self-tests.
+- `docs/adding-a-test.md` — the 6-step recipe for a new feature's e2e test.
+
+## Metrics-dir isolation (the C2 hard rule)
+
+The harness NEVER sets `PROMETHEUS_MULTIPROC_DIR` in a child env — stamping it
+is the entrypoint's own job (`activate_multiproc_env`) and is exactly what the
+C2 import-order tests verify. Per-stack (and per-replica) metrics dirs are
+controlled entirely via `TMPDIR`: `MetricsSettings.prometheus_multiproc_dir`
+defaults to `<tempfile.gettempdir()>/tai42_prometheus`, so pointing a process's
+`TMPDIR` at a per-run-family dir gives that family its own multiproc dir with
+the env var untouched. `stack.py` asserts the rule on every child env.
+
+## xfail policy
+
+A test for a fix that has not yet landed in the workspace is marked
+`xfail(strict=True)` with the observed-behavior reason, so it flips loudly
+(xpass → failure) the moment the fix lands.
+
+## CI
+
+The fleet e2e runs from the monorepo root workflow, `.github/workflows/ci.yml`,
+in two jobs gated by the `changes` filter (any member carrying an e2e trigger, or
+a change to a shared root, sets `run_e2e`):
+
+- `e2e` — one matrix leg per triggered backend (`arq`, `rq`, `celery`), under
+  `TAI_E2E_FLEET=1` with `redis` identity and `local` storage. Services:
+  `redis:7-alpine` (shared), `postgres:16-alpine`, and `redis:8` — the
+  module-capable checkpoint Redis the arq leg points
+  `TAI_E2E_CHECKPOINT_REDIS_URL` at. The celery leg brings its RabbitMQ up from
+  the compose `celery` profile; non-arq legs deselect `-m "not backendless"`. The
+  langfuse monitoring profile runs on the arq leg only when the `run_monitoring`
+  gate is on (a change under `plugins/monitoring-langfuse`, `core`, or `e2e`, or a
+  manual `workflow_dispatch`). When the private-repo token is present it also runs
+  the marketplace suite (`TAI_E2E_MARKETPLACE=1`), installing the git-sourced
+  `tai42-marketplace` and booting it as harness processes.
+- `ui-e2e` — needs `e2e`; boots redis + postgres, clones `tai-studio`, builds the
+  Studio SPA, and runs the Playwright chromium suite in `ui/`. When the `run_browsers`
+  gate is on (a change under `e2e/ui`, or a manual `workflow_dispatch`) it also
+  widens the matrix onto firefox + webkit. With the token it also clones the private
+  `tai-marketplace-web` and runs the marketplace browser specs under
+  `TAI_E2E_MARKETPLACE=1`.
+
+The marketplace legs need the private `tai42ai/tai-marketplace` and
+`tai42ai/tai-marketplace-web` repos, so they run only when the `RELEASE_PLEASE_TOKEN`
+secret is available — a fork PR has no secrets, so those steps skip with a visible
+`::warning::` rather than failing. Other external consumers install this harness as
+the published `tai42-e2e` package and run their own suites against it. Any consumer
+booting the studio stack must also install the Studio reference plugin from the
+`tai42ai/tai-studio` repo (`e2e/reference-plugin`), which the studio profile manifest
+names but the harness does not carry as a runtime dependency.
+
+## Marketplace area (opt-in)
+
+`tests/marketplace/` only collects when `TAI_E2E_MARKETPLACE=1`; unset, it is
+skipped at collection like `tests/monitoring/`. When on, the harness boots the
+`tai42-marketplace` registry — installed from its git source via the `marketplace`
+dependency group — as a harness-managed process (the API server) on an isolated
+Postgres database: **no extra compose profile**; it rides the core
+`docker compose up -d` infra. The suite forges REAL fixture wheels (and one source
+tarball) from the in-repo `fixtures/marketplace_plugins` tree
+(`TAI_E2E_MARKETPLACE_FIXTURES` overrides it), served over a local package index,
+seeds them through the registry's real ingest pipeline, which publishes each version
+synchronously, and the skeleton REALLY pip-installs them into the one shared venv —
+so every lifecycle spec ends with its own uninstall and a session guard raises loudly
+on any leftover distribution (never auto-cleaning). The ui leg additionally
+pnpm-builds and serves the public `tai-marketplace-web` checkout and drives the Studio
+marketplace page and the public site over a browser.
+
+```bash
+docker compose up -d
+TAI_E2E_MARKETPLACE=1 uv run pytest tests/marketplace
+# the browser legs (built Studio dist + the tai-marketplace-web checkout):
+cd ui && TAI_E2E_MARKETPLACE=1 pnpm exec playwright test tests/marketplace.spec.ts tests/marketplace-web.spec.ts
+```