egma 0.2.0__tar.gz

egma-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 Egma
+
+   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.

egma-0.2.0/PKG-INFO

@@ -0,0 +1,398 @@
+Metadata-Version: 2.4
+Name: egma
+Version: 0.2.0
+Summary: Test and monitor LiveKit agents with Egma.
+Keywords: livekit,voice,agents,testing,mock tools,egma
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Testing
+Requires-Dist: livekit-agents>=1.6.7,<1.7
+Requires-Dist: openai>=2,<3
+Requires-Dist: opentelemetry-exporter-otlp-proto-http>=1.39,<2
+Requires-Dist: opentelemetry-sdk>=1.39,<2
+Requires-Python: >=3.11
+Project-URL: Homepage, https://github.com/egma-ai/egma
+Project-URL: Repository, https://github.com/egma-ai/egma
+Project-URL: Documentation, https://github.com/egma-ai/egma/tree/main/sdks/python#readme
+Description-Content-Type: text/markdown
+
+# Egma Python SDK
+
+Test a LiveKit agent with mock tools and send its production spans to Egma.
+
+The two functions are separate:
+
+- `mockable(...)` lets Egma answer tools in an Egma simulation. It does
+  nothing in production.
+- `monitor_livekit(...)` sends production LiveKit spans to the
+  Monitoring page. It does nothing in an Egma simulation.
+
+Calling one function never enables or changes the other.
+
+## Install
+
+```bash
+pip install 'egma>=0.2.0'
+```
+
+`0.2.0` is the floor because it is the first release that knows a
+simulation by the room's name, and so the first that holds on every one of
+the three dispatch paths. An unpinned install can resolve to a release
+that looks in the dispatch metadata instead, where Egma no longer writes
+anything — inert inside a real simulation on all three.
+
+For a LiveKit agent on Python 3.11 or newer.
+
+## Production monitoring
+
+Open **Monitoring → Start monitoring** and choose **LiveKit**. That page
+shows the same SDK, key, and helper steps below. It is instructions only: a
+LiveKit agent pushes its own spans, so there is nothing to switch on in Egma.
+
+Set the Egma API origin and an existing project API key in the agent's
+environment:
+
+```bash
+export EGMA_URL=https://api.egma.ai
+export EGMA_API_KEY=egma_sk_...
+```
+
+For self-hosted Egma, prefer the published API address, such as
+`http://localhost:3100`. The web address also works because Egma forwards
+`/v1/traces` to the API, but the API is one hop shorter. The agent process must
+be able to make HTTP or HTTPS requests to the address you choose.
+
+In a customer-hosted worker, set these values through your normal deployment
+secret store. For LiveKit Cloud, place them in a gitignored secrets file and
+apply it to the agent:
+
+```bash
+lk agent update-secrets --secrets-file=.env.monitoring
+```
+
+Use the same file with `lk agent create --secrets-file=.env.monitoring` for a
+new deployment. LiveKit Cloud restarts the agent after a secret update.
+
+Call `monitor_livekit` before `AgentSession.start`:
+
+```python
+from egma import monitor_livekit
+from livekit import agents
+from livekit.agents import Agent, AgentSession
+
+
+async def entrypoint(ctx: agents.JobContext) -> None:
+    monitor_livekit(ctx)
+    await ctx.connect()
+
+    agent = Agent(instructions=INSTRUCTIONS, tools=[check_calendar])
+    session = AgentSession(stt=..., llm=..., tts=...)
+    await session.start(agent=agent, room=ctx.room)
+```
+
+You can pass the same values directly when environment variables are not the
+right configuration source:
+
+```python
+monitor_livekit(ctx, endpoint="https://api.egma.ai", api_key=project_key)
+```
+
+Use the same call for an agent hosted in your cloud and an agent hosted in
+LiveKit Cloud. The helper adds Egma to a compatible OpenTelemetry provider; it
+does not remove LiveKit Cloud observability or another existing span
+processor. It sends spans in batches and flushes the final batch when the
+LiveKit job stops.
+
+If this job runs in an Egma simulation room, the helper returns without
+adding a production exporter and says so at `WARNING`. The simulation keeps
+its own trace and does not appear a second time in Monitoring.
+
+The helper reads the room's name for that and nothing else. Every Egma
+simulation room is named `egma-sim-…`; a room named anything else gets the
+production exporter. The name arrives with the job, so this decision costs
+no network and happens before `ctx.connect()`.
+
+After deployment, open **Monitoring**. Nothing needs to be confirmed in Egma —
+the deployed helper is what sends spans, and the first production conversation
+appears in the list as soon as it arrives.
+
+The caller's phone, SIP, or WebRTC entry path does not change this setup. The
+SDK does not guess that path from a LiveKit trace.
+
+### Setup status
+
+The helper stops immediately with one direct error when required settings are
+missing or malformed, or when tracer providers conflict. It does not include
+the key in that error.
+
+After deployment, Monitoring stays empty until the first trace reaches Egma,
+then lists each production conversation as it arrives. This release uses one-way
+OTLP export. Egma cannot see a DNS, firewall, or network failure inside the
+worker. Check the worker's OpenTelemetry logs and confirm that it can reach
+`EGMA_URL` when nothing appears.
+
+## Simulation mock tools
+
+A simulation that reaches your real tools has real side effects: it books
+the appointment, sends the message, charges the card. And a real backend
+only ever shows you the branch its data happens to be on — "the calendar
+is full", "the lookup fails", "the booking API errors" are where voice
+agents die in production, and none of them can be ordered up from a real
+backend on demand.
+
+A **mock tool** answers for one of your agent's tools during a
+simulation. It is authored in your Egma project, matched strictly by tool
+name, and its answer may be a value, an error, or either one after a
+declared delay so a mocked backend takes as long as the real one. This
+package is the piece that lives in your own agent's process and lets Egma
+answer.
+
+Tools no mock tool covers run their real implementations, untouched.
+Egma's record names which of your tools were covered and which were not,
+so you always know whether a simulation was fully isolated.
+
+### Use
+
+One call, after the agent is built and before the session starts:
+
+```python
+from egma import mockable
+```
+
+```python
+async def entrypoint(ctx: agents.JobContext) -> None:
+    agent = Agent(instructions=INSTRUCTIONS, tools=[check_calendar, book_appointment])
+    session = AgentSession(stt=..., llm=..., tts=...)
+
+    await mockable(agent, ctx, session)
+
+    await session.start(agent=agent, room=ctx.room)
+```
+
+That is the whole simulation integration.
+
+### How it knows it is in a simulation
+
+It reads the **room's name** off the job. Every room Egma conducts a
+simulation in is named `egma-sim-…`, and that prefix is fixed. Nothing
+else is read, nothing is asked, and no room is connected to find out.
+
+The name is the signal because it is the one that arrives on every
+dispatch path an agent can end up in an Egma room by — whether Egma
+dispatches your worker by name, whether LiveKit walks an unnamed worker
+into the room, and whether your own token endpoint puts the agent there.
+A signal carried by an explicit dispatch arrives on only the first of
+those.
+
+In a simulation room, `mockable` connects the job with LiveKit's own
+`JobContext.connect()` if your startup has not already done so, then finds
+Egma among the room's participants: Egma joins as `egma-persona` or
+`egma-persona-<simulation>`. On two of the three dispatch paths your
+agent is in the room **before** Egma, so it waits for that participant,
+for up to 45 seconds and without polling anything outside the room. That
+is a long time to hold an agent before it greets anybody, and it is the
+price of the wait being correct on every dispatch path rather than on one;
+a simulation ordinarily pays a fraction of it. It does not reconnect an
+already-connected room, and it never connects a production room.
+
+If nobody by that name arrives, nothing is wrapped, your tools all run
+their own implementations, and the reason is logged at `ERROR`. If two
+participants answer to that name, the exchange is refused for the same
+reason a room with two claimants has no knowable answer — and your tool
+inventory is not sent to either of them.
+
+Then `mockable` reports your agent's tools to Egma — names and schemas,
+read off the agent object, so mock authoring starts from your real tool
+names instead of your memory of them — and learns which of them this
+simulation answers for. Calls to those tools go to Egma and come back with
+the authored answer. Every one of them lands on the simulation's record
+with its arguments, its answer, how long it took, and which mock tool
+answered.
+
+**In every other room it does nothing at all.** A room your own system
+named — which is every production room — is a room where `mockable`
+returns having touched nothing: no wrapper, no message, no connect. Your
+tools are the same objects, called the same way, with no wrapper between
+them and the model. Zero added latency, by construction rather than by
+care. That property is a test in this package (`tests/test_inert.py`),
+not a promise in this file.
+
+Your job's **dispatch metadata is yours**. This SDK writes nothing into it
+and reads nothing out of it — not one key, in any room, for any purpose.
+Neither does Egma: on every dispatch path, both the room's metadata and
+the dispatch's carry the string configured on the connection, byte for
+byte. `json.loads(ctx.job.metadata)["your_key"]` reads the same thing in a
+simulation that it reads in production.
+
+### Where to call it
+
+After the agent object exists and before `session.start`. The report of
+your tools is the first thing said, so an Egma that is not in the room is
+discovered before any tool call rather than half way through a test.
+
+Keep one `mockable` call for the initial agent. The SDK follows LiveKit's
+public handoff events and installs the same simulation couriers for each
+selected `Agent` or `AgentTask` before that activity starts. Each handoff
+also extends one cumulative tool census, so Egma's coverage record keeps
+the tools found on earlier agents.
+
+### What a call to a mocked tool does
+
+- Goes to Egma over the same LiveKit room. No new endpoint, no new
+  credential, nothing new to expose. If needed, `mockable` connects that
+  room through the job context before sending the first RPC.
+- Comes back with the authored answer, or raises the authored error as
+  the tool's own error, so your agent handles it exactly as it would
+  handle a real backend failing.
+- **Falls open** if Egma turns out not to be reachable: your real tool
+  runs, and the agent behaves as it would with this package uninstalled.
+- **Never waits forever.** Every branch ends in an answer, an error the
+  model can hear, or your own tool running.
+
+A tool you attach to the agent *after* calling `mockable` is still
+intercepted on its first call — Egma's answers are held by name. Its
+arguments may be incomplete on the record, and Egma marks that call so
+you can see it.
+
+### Logging
+
+Everything this package says goes to the `egma` logger. It is worth
+having on at `INFO` the first time you wire an agent up: the line after
+the census names how many tools you have and how many Egma answers for.
+
+`ERROR` is reserved for a simulation that could not be isolated and can
+be acted on — no Egma participant arrived in a simulation room, two
+participants claimed to be Egma, or the two halves do not speak the same
+version of the exchange. None of those lines is reachable in a production
+room.
+
+## Before you install anything: the interim recipe
+
+You can get isolation today with no Egma code at all, using LiveKit's own
+`mock_tools` and a guard you write yourself:
+
+```python
+from livekit.agents import mock_tools
+
+
+def in_a_simulation(ctx: agents.JobContext) -> bool:
+    return ctx.job.room.name.startswith("egma-sim-")
+
+
+async def entrypoint(ctx: agents.JobContext) -> None:
+    await ctx.connect()
+    agent = Agent(instructions=INSTRUCTIONS, tools=[check_calendar])
+    session = AgentSession(stt=..., llm=..., tts=...)
+
+    if in_a_simulation(ctx):
+        mock_tools(
+            type(agent),
+            {"check_calendar": lambda day: "No free slots on that day."},
+            session=session,
+        )
+
+    await session.start(agent=agent, room=ctx.room)
+```
+
+A room your own system named means the guard is false and nothing is
+wrapped. Note where that safety comes from, because it is not where
+`mockable`'s comes from: this guard fires on a prefix being *present*
+rather than on Egma being *absent*. So it is true in any room whose name
+begins `egma-sim-`, including one Egma is not in — `mockable` waits for
+Egma's participant and gives up out loud, while this guard has nobody to
+wait for and simply mocks. Refuse that prefix wherever your own side mints
+production tokens, or a production room named to look like a simulation
+runs your canned answers against a live caller.
+
+**Write the guard on the room name, and not on `egmaIdentity` in
+`ctx.job.metadata`.** That key is in no simulation room at all: your
+dispatch metadata is yours, and Egma writes nothing into it on any
+dispatch path. A guard on it does not raise — it quietly fails to fire,
+and every real tool it was meant to hold back runs inside a simulation.
+
+What it cannot do is the rest of the job. One canned world for every
+test, so you cannot write "the calendar is full" as a *test* — you would
+be editing your agent's source to change a test's data. Nothing about
+those calls reaches Egma's record: no arguments, no answers, no timings,
+no coverage stamp, so graders that read tool facts have nothing to read.
+No declared delay, so latency numbers from a mocked run flatter you.
+
+**And the honest caveat: that guard couples your agent's source to how
+Egma announces itself.** The room-name prefix is a stated contract rather
+than an implementation detail, so it is the safe thing to key off — but
+the *rest* of the mechanism is not: where Egma sits in the room, what
+it is called, how long it takes to arrive, and what a room with two
+claimants means are all Egma's to evolve. That is precisely what
+`mockable` exists to own, and your side stays one line.
+
+Use the recipe as the bridge, not as the small tier.
+
+## Compatibility
+
+The `egma-sim-` room-name prefix is a stated contract, not an internal
+detail. Every room Egma opens for a simulation begins with it, on every
+dispatch path, and it is there to be relied on and to be allowlisted in
+a token endpoint. This SDK keys its whole simulation/production decision
+off it.
+
+Every Egma deployment names its rooms that way, so this package works
+against a self-hosted Egma on whatever schedule its owner upgrades it.
+Nothing else is consulted — in particular, neither metadata channel,
+which carries your own configured JSON and nothing of Egma's.
+
+This package pins `livekit-agents` to one minor version
+(`>=1.6.7,<1.7`), and that is deliberate. Interception uses LiveKit's
+testing API. Monitoring also reads LiveKit's current dynamic tracer
+provider because the public telemetry API has a setter but no getter.
+The fixture and live tests verify both seams before the supported range
+changes.
+
+The package also keeps the OpenAI Python package on major version 2.
+LiveKit Agents 1.6 does not support OpenAI 3.
+
+`mock_tools` writes into a side table LiveKit keeps per session. It does
+not touch your agent, your agent's class, or your tool registry, and the
+model keeps seeing your real tool schemas throughout. Never calling it
+leaves everything byte for byte as it was, which is what makes the inert
+path literal.
+
+If that API ever moves, the documented fallback is
+`Agent.update_tools(...)` with `function_tool(raw_schema=...)` wrappers
+built from the real tools' schemas. It is a heavier mechanism — it takes
+responsibility for schema fidelity, for the real implementations, and for
+re-wrapping after a handoff — which is exactly why it is the fallback and
+not the mechanism.
+
+## Developing this package
+
+The toolchain is [uv](https://docs.astral.sh/uv/).
+
+```bash
+uv sync
+uv run ruff check src tests
+uv run pytest
+```
+
+The normal suite is hermetic: no LiveKit server, no project, and no external
+network. One monitoring test uses a local HTTP collector. One live test skips
+visibly when the environment is silent, naming what it needs. To run it, point
+it at a LiveKit project:
+
+```bash
+TEST_LIVEKIT_URL=wss://... \
+TEST_LIVEKIT_API_KEY=... TEST_LIVEKIT_API_SECRET=... \
+TEST_MODEL_API_KEY=... \
+uv run pytest tests/test_live_mockable.py -v
+```
+
+Each name falls back to the plain one the tool's own CLI reads —
+`LIVEKIT_URL`, `LIVEKIT_API_KEY`, `LIVEKIT_API_SECRET`, `OPENAI_API_KEY`
+— so one environment serves this and whatever else you run beside it.
+`TEST_MODEL_NAME` picks the model; it defaults to `gpt-4o-mini`.
+
+## License
+
+Apache-2.0, with the rest of Egma.