fix: scope yates roles to active database

[LucianBuzzo]

Summary

• determine the active database during setup so role management can be scoped per instance
• include the database scope when generating ability and role identifiers to avoid collisions
• ensure setup and role creation initialize the scope before issuing grants or revocations

Testing

• npm test

---

Codex Task

[github-actions]

Published beta package version: 3.7.2-beta.dangerous.0952f83

[Copilot]

Pull Request Overview

This PR adds database scoping to Yates roles to support multi-tenant setups where multiple Prisma clients connect to different databases on the same server. The changes ensure that role and ability identifiers include the database name to prevent collisions between tenants.

Key changes:

• Database scope is determined during initialization by querying the current database name
• Role and ability identifiers now include the database scope as a prefix to avoid naming conflicts
• Setup process initializes the database scope before creating roles or granting permissions

Reviewed Changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/index.ts	Refactored role management into a Yates class with database scoping support; moved utility functions to instance methods
test/integration/multi-tenant-db.spec.ts	Added integration test verifying isolation between tenants using different databases
prisma/schema2.prisma	Added second Prisma schema for multi-tenant testing with subset of models
package.json	Updated setup script to generate and migrate both schemas
docker-compose.yml	Configured second database instance for multi-tenant testing
docker-init/setup-databases.sh	Added script to create multiple PostgreSQL databases during Docker initialization
biome.json	Excluded generated Prisma client files from linting
prisma/migrations/20251115091853_init/migration.sql	Migration file removing unused tables from schema

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This binding appears unnecessary since createRoleName is already an arrow function property of the class, which automatically binds this. The variable is also unused in the subsequent code.

Suggested change

const createRoleName = this.createRoleName.bind(this);

[sonarqubecloud]

Quality Gate failed

Failed conditions
40.7% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud