Problem
Several Go test files use a downstream deployment name (tiverton) as the fixture agent/service ID — e.g. internal/cllama/context_test.go (~8 refs) and cllama/internal/agentctx/agentctx_test.go. The repo is public and project convention keeps downstream deployment names out of committed artifacts (see the public-surface rules in AGENTS.md). These are pre-existing/historical fixtures, so they are intentionally left alone until a deliberate cleanup is authorized.
Scope
Rename the tiverton fixture agent/service IDs to generic names (e.g. analyst, svc-a) across the affected test files. Pure test-fixture rename; no production code or behavior change. Keep each test self-consistent.
Why now
Surfaced during the #308 review (2026-07-01): a new assertion extended an existing tiverton-based test. Rather than proliferate the name, tracking a single deliberate genericization pass here.
Acceptance
grep -ri tiverton over Go test files returns nothing.go test ./... (root) and go test ./... (cllama submodule) stay green.
Problem
Several Go test files use a downstream deployment name (
tiverton) as the fixture agent/service ID — e.g.internal/cllama/context_test.go(~8 refs) andcllama/internal/agentctx/agentctx_test.go. The repo is public and project convention keeps downstream deployment names out of committed artifacts (see the public-surface rules in AGENTS.md). These are pre-existing/historical fixtures, so they are intentionally left alone until a deliberate cleanup is authorized.Scope
Rename the
tivertonfixture agent/service IDs to generic names (e.g.analyst,svc-a) across the affected test files. Pure test-fixture rename; no production code or behavior change. Keep each test self-consistent.Why now
Surfaced during the #308 review (2026-07-01): a new assertion extended an existing
tiverton-based test. Rather than proliferate the name, tracking a single deliberate genericization pass here.Acceptance
grep -ri tivertonover Go test files returns nothing.go test ./...(root) andgo test ./...(cllama submodule) stay green.