test(ai): updated test commands for using a configurable cloudsync server

Author: andinux

.claude/commands/test-sync-roundtrip-sqlitecloud-rls.md

@@ -4,9 +4,13 @@ Execute a full roundtrip sync test between multiple local SQLite databases and t
 
 ## Prerequisites
 - Connection string to a sqlitecloud project
-- HTTP sync server running on http://localhost:8091/<dbname>
+- HTTP sync server running (default: https://cloudsync-staging-testing.fly.dev)
 - Built cloudsync extension (`make` to build `dist/cloudsync.dylib`)
 
+### Step 0: Get Sync Server Address
+
+Ask the user for the HTTP sync server base URL. Propose `https://cloudsync-staging-testing.fly.dev` as the default. Save this as `SYNC_SERVER_URL` for use throughout the test. The full sync endpoint will be `<SYNC_SERVER_URL>/<db_name>`.
+
 ## Test Procedure
 
 ### Step 1: Get DDL from User
@@ -61,7 +65,7 @@ Ask the user to describe the policy in plain English.
 
 ### Step 3: Get sqlitecloud connection string from User
 
-Ask the user to provide a connection string in the form of "sqlitecloud://<host>:<port>/<db_name>?apikey=<apikey>" to be later used with the sqlitecloud cli (sqlc) with `~/go/bin/sqlc "<connection_string>"`
+Ask the user to provide a connection string in the form of "sqlitecloud://<host>:<port>/<db_name>?apikey=<apikey>" to be later used with the sqlitecloud cli (sqlc) with `~/go/bin/sqlc "<connection_string>"`. Save the first subdomain in the connection string address as `PROJECT_ID` for use throughout the test. Save the configuration string `'{"address":"<SYNC_SERVER_URL>","database":"<db_name>","projectID":"<PROJECT_ID>","organizationID":"org_sqlitecloud"}'` as `NETWORK_CONFIG` for use throughout the test.
 
 ### Step 4: Setup SQLiteCloud with RLS
 
@@ -142,7 +146,7 @@ curl -X "POST" "https://<hostname_from_connection_string>/v2/tokens" \
    -H 'Authorization: Bearer <apikey_from_connection_string>' \
    -H 'Content-Type: application/json; charset=utf-8' \
    -d $'{
- "name": "laude2@sqlitecloud.io",
+ "name": "claude2@sqlitecloud.io",
  "userId": "018ecfc2-b2b1-7cc3-a9f0-222222222222"
 }'
 ```
@@ -157,7 +161,7 @@ save the userId and the token values as USER2_ID and TOKEN_USER2 to be reused la
 Create four temporary SQLite databases using the Homebrew version (IMPORTANT: system sqlite3 cannot load extensions):
 
 ```bash
-SQLITE_BIN="/opt/homebrew/Cellar/sqlite/3.50.4/bin/sqlite3"
+SQLITE_BIN="/opt/homebrew/Cellar/sqlite/3.51.2_1/bin/sqlite3"
 # or find it with: ls /opt/homebrew/Cellar/sqlite/*/bin/sqlite3 | head -1
 ```
 
@@ -169,8 +173,8 @@ $SQLITE_BIN /tmp/sync_test_user1_a.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/<db_name>');
-SELECT cloudsync_network_set_token('sqlitecloud://<hostname_from_connection_string>?token=<TOKEN_USER1>');
+SELECT cloudsync_network_init('<NETWORK_CONFIG>');
+SELECT cloudsync_network_set_token('<TOKEN_USER1>');
 ```
 
 **Database 1B (User 1, Device B):**
@@ -181,8 +185,8 @@ $SQLITE_BIN /tmp/sync_test_user1_b.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/<db_name>');
-SELECT cloudsync_network_set_token('sqlitecloud://<hostname_from_connection_string>?token=<TOKEN_USER1>');
+SELECT cloudsync_network_init('<NETWORK_CONFIG>');
+SELECT cloudsync_network_set_token('<TOKEN_USER1>');
 ```
 
 **Database 2A (User 2, Device A):**
@@ -193,8 +197,8 @@ $SQLITE_BIN /tmp/sync_test_user2_a.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
-SELECT cloudsync_network_set_token('sqlitecloud://<hostname_from_connection_string>?token=<TOKEN_USER2>');
+SELECT cloudsync_network_init('<NETWORK_CONFIG>');
+SELECT cloudsync_network_set_token('<TOKEN_USER2>');
 ```
 
 **Database 2B (User 2, Device B):**
@@ -205,8 +209,8 @@ $SQLITE_BIN /tmp/sync_test_user2_b.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
-SELECT cloudsync_network_set_token('sqlitecloud://<hostname_from_connection_string>?token=<TOKEN_USER2>');
+SELECT cloudsync_network_init('<NETWORK_CONFIG>');
+SELECT cloudsync_network_set_token('<TOKEN_USER2>');
 ```
 
 ### Step 7: Insert Test Data
@@ -406,14 +410,14 @@ user_id UUID NOT NULL DEFAULT '00000000-0000-0000-0000-000000000000'
 ```sql
 -- WRONG: Separate sessions won't work
 -- Session 1:
-SELECT cloudsync_network_init('http://localhost:8091/<db_name>');
+SELECT cloudsync_network_init('<NETWORK_CONFIG>');
 SELECT cloudsync_network_set_token('...');
 -- Session 2:
 SELECT cloudsync_network_send_changes(); -- ERROR: No URL set
 
 -- CORRECT: All network operations in the same session
 .load dist/cloudsync.dylib
-SELECT cloudsync_network_init('http://localhost:8091/<db_name>');
+SELECT cloudsync_network_init('<NETWORK_CONFIG>');
 SELECT cloudsync_network_set_token('...');
 SELECT cloudsync_network_send_changes();
 SELECT cloudsync_terminate();

…est-sync-roundtrip-postrges-local-rls.md …ands/test-sync-roundtrip-supabase-rls.md.claude/commands/test-sync-roundtrip-postrges-local-rls.md renamed to .claude/commands/test-sync-roundtrip-supabase-rls.md .claude/commands/test-sync-roundtrip-postrges-local-rls.md renamed to .claude/commands/test-sync-roundtrip-supabase-rls.md

@@ -3,12 +3,24 @@
 Execute a full roundtrip sync test between multiple local SQLite databases and the local Supabase Docker PostgreSQL instance, verifying that Row Level Security (RLS) policies are correctly enforced during sync.
 
 ## Prerequisites
-- Supabase Docker container running (PostgreSQL on port 54322)
-- HTTP sync server running on http://localhost:8091/postgres
+- Supabase instance running (local Docker or remote)
+- HTTP sync server running (default: https://cloudsync-staging-testing.fly.dev)
 - Built cloudsync extension (`make` to build `dist/cloudsync.dylib`)
 
 ## Test Procedure
 
+### Step 0: Get Connection Parameters
+
+Ask the user for the following parameters:
+
+1. **Sync server URL**: Propose `https://cloudsync-staging-testing.fly.dev` as default. Save as `SYNC_SERVER_URL`. The full sync endpoint will be `<SYNC_SERVER_URL>/postgres`.
+
+2. **PostgreSQL connection string**: Propose `postgresql://supabase_admin:postgres@127.0.0.1:54322/postgres` as default. Save as `PG_CONN`. Use this for all `psql` connections throughout the test.
+
+3. **Supabase API key** (used for JWT token generation): Propose `sb_secret_N7UND0UgjKTVK-Uodkm0Hg_xSvEMPvz` as default. Save as `SUPABASE_APIKEY`.
+
+Derive `AUTH_URL` from the PostgreSQL connection string by extracting the host and using port `54321` (Supabase GoTrue). For example, if `PG_CONN` is `postgresql://user:pass@10.0.0.5:54322/postgres`, then `AUTH_URL` is `http://10.0.0.5:54321`. For `127.0.0.1`, use `http://127.0.0.1:54321`.
+
 ### Step 1: Get DDL from User
 
 Ask the user to provide a DDL query for the table(s) to test. It can be in PostgreSQL or SQLite format. Offer the following options:
@@ -79,7 +91,7 @@ Convert the provided DDL to both SQLite and PostgreSQL compatible formats if nee
 
 Connect to Supabase PostgreSQL and prepare the environment:
 ```bash
-psql postgresql://supabase_admin:postgres@127.0.0.1:54322/postgres
+psql <PG_CONN>
 ```
 
 Inside psql:
@@ -148,13 +160,13 @@ Get JWT tokens for both test users by running the token script twice:
 
 **User 1: claude1@sqlitecloud.io**
 ```bash
-cd ../cloudsync && go run scripts/get_supabase_token.go -project-ref=supabase-local -email=claude1@sqlitecloud.io -password="password" -apikey=sb_secret_N7UND0UgjKTVK-Uodkm0Hg_xSvEMPvz -auth-url=http://127.0.0.1:54321
+cd ../cloudsync && go run scripts/get_supabase_token.go -project-ref=supabase-local -email=claude1@sqlitecloud.io -password="password" -apikey=<SUPABASE_APIKEY> -auth-url=<AUTH_URL>
 ```
 Save as `JWT_USER1`.
 
 **User 2: claude2@sqlitecloud.io**
 ```bash
-cd ../cloudsync && go run scripts/get_supabase_token.go -project-ref=supabase-local -email=claude2@sqlitecloud.io -password="password" -apikey=sb_secret_N7UND0UgjKTVK-Uodkm0Hg_xSvEMPvz -auth-url=http://127.0.0.1:54321
+cd ../cloudsync && go run scripts/get_supabase_token.go -project-ref=supabase-local -email=claude2@sqlitecloud.io -password="password" -apikey=<SUPABASE_APIKEY> -auth-url=<AUTH_URL>
 ```
 Save as `JWT_USER2`.
 
@@ -167,7 +179,7 @@ Also extract the user IDs from the JWT tokens (the `sub` claim) for use in INSER
 Create four temporary SQLite databases using the Homebrew version (IMPORTANT: system sqlite3 cannot load extensions):
 
 ```bash
-SQLITE_BIN="/opt/homebrew/Cellar/sqlite/3.50.4/bin/sqlite3"
+SQLITE_BIN="/opt/homebrew/Cellar/sqlite/3.51.2_1/bin/sqlite3"
 # or find it with: ls /opt/homebrew/Cellar/sqlite/*/bin/sqlite3 | head -1
 ```
 
@@ -179,7 +191,7 @@ $SQLITE_BIN /tmp/sync_test_user1_a.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
+SELECT cloudsync_network_init('<SYNC_SERVER_URL>/postgres');
 SELECT cloudsync_network_set_token('<JWT_USER1>');
 ```
 
@@ -191,7 +203,7 @@ $SQLITE_BIN /tmp/sync_test_user1_b.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
+SELECT cloudsync_network_init('<SYNC_SERVER_URL>/postgres');
 SELECT cloudsync_network_set_token('<JWT_USER1>');
 ```
 
@@ -203,7 +215,7 @@ $SQLITE_BIN /tmp/sync_test_user2_a.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
+SELECT cloudsync_network_init('<SYNC_SERVER_URL>/postgres');
 SELECT cloudsync_network_set_token('<JWT_USER2>');
 ```
 
@@ -215,7 +227,7 @@ $SQLITE_BIN /tmp/sync_test_user2_b.db
 .load dist/cloudsync.dylib
 <CREATE_TABLE_query_sqlite>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
+SELECT cloudsync_network_init('<SYNC_SERVER_URL>/postgres');
 SELECT cloudsync_network_set_token('<JWT_USER2>');
 ```
 
@@ -473,14 +485,14 @@ Ensure column types are compatible between SQLite and PostgreSQL:
 ```sql
 -- WRONG: Separate sessions won't work
 -- Session 1:
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
+SELECT cloudsync_network_init('<SYNC_SERVER_URL>/postgres');
 SELECT cloudsync_network_set_token('...');
 -- Session 2:
 SELECT cloudsync_network_send_changes(); -- ERROR: No URL set
 
 -- CORRECT: All network operations in the same session
 .load dist/cloudsync.dylib
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
+SELECT cloudsync_network_init('<SYNC_SERVER_URL>/postgres');
 SELECT cloudsync_network_set_token('...');
 SELECT cloudsync_network_send_changes();
 SELECT cloudsync_terminate();
@@ -518,6 +530,6 @@ INSERT INTO todos (id, ...) VALUES ('11111111-1111-1111-1111-111111111111', ...)
 
 Execute all SQL queries without asking for user permission on:
 - SQLite test databases in `/tmp/` (e.g., `/tmp/sync_test_*.db`)
-- PostgreSQL via `psql postgresql://supabase_admin:postgres@127.0.0.1:54322/postgres`
+- PostgreSQL via `psql <PG_CONN>`
 
 These are local test environments and do not require confirmation for each query.

…ds/test-sync-roundtrip-postgres-local.md …commands/test-sync-roundtrip-supabase.md.claude/commands/test-sync-roundtrip-postgres-local.md renamed to .claude/commands/test-sync-roundtrip-supabase.md .claude/commands/test-sync-roundtrip-postgres-local.md renamed to .claude/commands/test-sync-roundtrip-supabase.md

@@ -3,12 +3,24 @@
 Execute a full roundtrip sync test between a local SQLite database and the local Supabase Docker PostgreSQL instance.
 
 ## Prerequisites
-- Supabase Docker container running (PostgreSQL on port 54322)
-- HTTP sync server running on http://localhost:8091/postgres
+- Supabase instance running (local Docker or remote)
+- HTTP sync server running (default: https://cloudsync-staging-testing.fly.dev)
 - Built cloudsync extension (`make` to build `dist/cloudsync.dylib`)
 
 ## Test Procedure
 
+### Step 0: Get Connection Parameters
+
+Ask the user for the following parameters:
+
+1. **Sync server URL**: Propose `https://cloudsync-staging-testing.fly.dev` as default. Save as `SYNC_SERVER_URL`. The full sync endpoint will be `<SYNC_SERVER_URL>/postgres`.
+
+2. **PostgreSQL connection string**: Propose `postgresql://supabase_admin:postgres@127.0.0.1:54322/postgres` as default. Save as `PG_CONN`. Use this for all `psql` connections throughout the test.
+
+3. **Supabase API key** (used for JWT token generation): Propose `sb_secret_N7UND0UgjKTVK-Uodkm0Hg_xSvEMPvz` as default. Save as `SUPABASE_APIKEY`.
+
+Derive `AUTH_URL` from the PostgreSQL connection string by extracting the host and using port `54321` (Supabase GoTrue). For example, if `PG_CONN` is `postgresql://user:pass@10.0.0.5:54322/postgres`, then `AUTH_URL` is `http://10.0.0.5:54321`. For `127.0.0.1`, use `http://127.0.0.1:54321`.
+
 ### Step 1: Get DDL from User
 
 Ask the user to provide a DDL query for the table(s) to test. It can be in PostgreSQL or SQLite format. Offer the following options:
@@ -61,15 +73,15 @@ Convert the provided DDL to both SQLite and PostgreSQL compatible formats if nee
 
 Run the token script from the cloudsync project:
 ```bash
-cd ../cloudsync && go run scripts/get_supabase_token.go -project-ref=supabase-local -email=claude@sqlitecloud.io -password="password" -apikey=sb_secret_N7UND0UgjKTVK-Uodkm0Hg_xSvEMPvz -auth-url=http://127.0.0.1:54321
+cd ../cloudsync && go run scripts/get_supabase_token.go -project-ref=supabase-local -email=claude@sqlitecloud.io -password="password" -apikey=<SUPABASE_APIKEY> -auth-url=<AUTH_URL>
 ```
 Save the JWT token for later use.
 
 ### Step 4: Setup PostgreSQL
 
 Connect to Supabase PostgreSQL and prepare the environment:
 ```bash
-psql postgresql://supabase_admin:postgres@127.0.0.1:54322/postgres
+psql <PG_CONN>
 ```
 
 Inside psql:
@@ -88,7 +100,7 @@ Inside psql:
 Create a temporary SQLite database using the Homebrew version (IMPORTANT: system sqlite3 cannot load extensions):
 
 ```bash
-SQLITE_BIN="/opt/homebrew/Cellar/sqlite/3.50.4/bin/sqlite3"
+SQLITE_BIN="/opt/homebrew/Cellar/sqlite/3.51.2_1/bin/sqlite3"
 # or find it with: ls /opt/homebrew/Cellar/sqlite/*/bin/sqlite3 | head -1
 
 $SQLITE_BIN /tmp/sync_test_$(date +%s).db
@@ -100,7 +112,7 @@ Inside sqlite3:
 -- Create table with SQLite DDL
 <CREATE_TABLE_query>
 SELECT cloudsync_init('<table_name>');
-SELECT cloudsync_network_init('http://localhost:8091/postgres');
+SELECT cloudsync_network_init('<SYNC_SERVER_URL>/postgres');
 SELECT cloudsync_network_set_token('<jwt_token>');
 -- Insert test data (different from PostgreSQL to test merge)
 <INSERT_statements>
@@ -149,6 +161,6 @@ Report the test results including:
 
 Execute all SQL queries without asking for user permission on:
 - SQLite test databases in `/tmp/` (e.g., `/tmp/sync_test_*.db`)
-- PostgreSQL via `psql postgresql://supabase_admin:postgres@127.0.0.1:54322/postgres`
+- PostgreSQL via `psql <PG_CONN>`
 
 These are local test environments and do not require confirmation for each query.