docs(skill): attribute supabase/evals harness reference (Apache-2.0)

The reference's concepts, runtime descriptions, and commands are derived
from the supabase/evals README, which is Apache-2.0. Add an attribution
section to references/agent-evals.md with the license link and list the
harness repository in references/source-index.md, per the repository's
attribution convention.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
This commit is contained in:
Magnus Hedemark
2026-08-09 18:14:15 -04:00
co-authored by factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
parent 7b5845d52d
commit 2114147c21
2 changed files with 5 additions and 0 deletions
+4
View File
@@ -83,3 +83,7 @@ Use the scenario set that matches the workflow under evaluation, and prefer scen
- Do not use this reference to design evaluation methodology, datasets, or graders — that is [agent-evals-and-observability](../../agent-evals-and-observability/SKILL.md).
- Do not confuse supabase/evals with this skill's own `evals/evals.json`: the former runs agents against scored scenarios, the latter is a static output-quality contract validated by this repository.
## Attribution
Concepts, runtime descriptions, and commands in this reference are derived from the [supabase/evals README](https://github.com/supabase/evals), Copyright Supabase, licensed under [Apache-2.0](https://github.com/supabase/evals/blob/main/LICENSE). Definitions are paraphrased or quoted for documentation; the harness and its skills submodule remain external to this repository.
+1
View File
@@ -40,6 +40,7 @@ Use current official documentation and source before making version-sensitive cl
- Supavisor: https://github.com/supabase/supavisor
- Supabase Postgres: https://github.com/supabase/postgres
- PostgREST: https://github.com/PostgREST/postgrest
- Agent evals harness: https://github.com/supabase/evals (Apache-2.0; concepts/commands checked 2026-08-09)
Within the official Docker directory, read `README.md`, `CONFIG.md`, `CHANGELOG.md`, `versions.md`, `.env.example`, `docker-compose.yml`, `run.sh`, and the relevant `tests/` file together. `CONFIG.md` explicitly distinguishes source-derived facts from interpretive descriptions; use each service's own documentation or source when intent matters.