Step 2: The rsdb runtime

Extend @concourse/rsdb with the runtime contract and MySQL tests

Goal

Extend the private Step 0 package with an empty production registry, runtime access, and version-matched MySQL tests.

Scope

Extend packages/rsdb with:

Explicit connection settings.
An empty generated registry.
Lazy MySQL pools and Drizzle handles.
The shared connection verifier.
Two local fixture databases.
MySQL lifecycle helpers.
A fixture regeneration command.

Add a MySQL service to CI / verify. Pin its image to the Step 0 server distribution and version. Do not add production credentials to CI.

Implement the complete runtime package contract: the registry exports, empty-registry behavior, configured factory, pool lifecycle, and the shared connection verifier with its two object-list sources.

Tests

Cover the Test 1 suite, including:

Stable registry order and empty-registry behavior.
Literal-name inference and runtime-union narrowing.
Correct schema, relations, database, and pool pairing.
Unknown-name rejection before connection.
TLS-required configuration.
Zero-row queries for every table and view.
Pool reuse, close-one, and close-all behavior.
Isolation after one database error.
Rolled-back runtime data changes.
Runtime DDL and grant denial.
Snapshot base-table read, data-change, and table-DDL denial.
Complete cleanup of accounts, databases, pools, and files.
Fixture drift against a fresh programmatic pull.
Server-only package boundaries.

Gate and stop conditions

Merge with an empty production registry. Deploy and verify that the package remains server-only. The Step 1 tracer must still pass.

Stop if the package needs environment access, a client bundle can import it, or unrelated schemas need one unioned schema.

Step 2: The rsdb runtime

Extend @concourse/rsdb with the runtime contract and MySQL tests

Goal

Extend the private Step 0 package with an empty production registry, runtime access, and version-matched MySQL tests.

Scope

Extend packages/rsdb with:

Explicit connection settings.
An empty generated registry.
Lazy MySQL pools and Drizzle handles.
The shared connection verifier.
Two local fixture databases.
MySQL lifecycle helpers.
A fixture regeneration command.

Add a MySQL service to CI / verify. Pin its image to the Step 0 server distribution and version. Do not add production credentials to CI.

Tests

Cover the Test 1 suite, including:

Stable registry order and empty-registry behavior.
Literal-name inference and runtime-union narrowing.
Correct schema, relations, database, and pool pairing.
Unknown-name rejection before connection.
TLS-required configuration.
Zero-row queries for every table and view.
Pool reuse, close-one, and close-all behavior.
Isolation after one database error.
Rolled-back runtime data changes.
Runtime DDL and grant denial.
Snapshot base-table read, data-change, and table-DDL denial.
Complete cleanup of accounts, databases, pools, and files.
Fixture drift against a fresh programmatic pull.
Server-only package boundaries.

Gate and stop conditions

Merge with an empty production registry. Deploy and verify that the package remains server-only. The Step 1 tracer must still pass.

Stop if the package needs environment access, a client bundle can import it, or unrelated schemas need one unioned schema.

Step 2: The rsdb runtime

Extend @concourse/rsdb with the runtime contract and MySQL tests

Goal

Extend the private Step 0 package with an empty production registry, runtime access, and version-matched MySQL tests.

Scope

Extend packages/rsdb with:

Explicit connection settings.
An empty generated registry.
Lazy MySQL pools and Drizzle handles.
The shared connection verifier.
Two local fixture databases.
MySQL lifecycle helpers.
A fixture regeneration command.

Add a MySQL service to CI / verify. Pin its image to the Step 0 server distribution and version. Do not add production credentials to CI.

Tests

Cover the Test 1 suite, including:

Stable registry order and empty-registry behavior.
Literal-name inference and runtime-union narrowing.
Correct schema, relations, database, and pool pairing.
Unknown-name rejection before connection.
TLS-required configuration.
Zero-row queries for every table and view.
Pool reuse, close-one, and close-all behavior.
Isolation after one database error.
Rolled-back runtime data changes.
Runtime DDL and grant denial.
Snapshot base-table read, data-change, and table-DDL denial.
Complete cleanup of accounts, databases, pools, and files.
Fixture drift against a fresh programmatic pull.
Server-only package boundaries.

Gate and stop conditions

Merge with an empty production registry. Deploy and verify that the package remains server-only. The Step 1 tracer must still pass.

Stop if the package needs environment access, a client bundle can import it, or unrelated schemas need one unioned schema.

Step 2: The rsdb runtime

Extend @concourse/rsdb with the runtime contract and MySQL tests

Goal

Extend the private Step 0 package with an empty production registry, runtime access, and version-matched MySQL tests.

Scope

Extend packages/rsdb with:

Explicit connection settings.
An empty generated registry.
Lazy MySQL pools and Drizzle handles.
The shared connection verifier.
Two local fixture databases.
MySQL lifecycle helpers.
A fixture regeneration command.

Add a MySQL service to CI / verify. Pin its image to the Step 0 server distribution and version. Do not add production credentials to CI.

Tests

Cover the Test 1 suite, including:

Stable registry order and empty-registry behavior.
Literal-name inference and runtime-union narrowing.
Correct schema, relations, database, and pool pairing.
Unknown-name rejection before connection.
TLS-required configuration.
Zero-row queries for every table and view.
Pool reuse, close-one, and close-all behavior.
Isolation after one database error.
Rolled-back runtime data changes.
Runtime DDL and grant denial.
Snapshot base-table read, data-change, and table-DDL denial.
Complete cleanup of accounts, databases, pools, and files.
Fixture drift against a fresh programmatic pull.
Server-only package boundaries.

Gate and stop conditions

Merge with an empty production registry. Deploy and verify that the package remains server-only. The Step 1 tracer must still pass.

Stop if the package needs environment access, a client bundle can import it, or unrelated schemas need one unioned schema.

Search documentation

Search documentation

Search documentation

Goal

Scope

Tests

Gate and stop conditions

Search documentation

Goal

Scope

Tests

Gate and stop conditions

Search documentation

Search documentation

Goal

Scope

Tests

Gate and stop conditions

Search documentation

Goal

Scope

Tests

Gate and stop conditions