Sync main with production

.env.model

@@ -1,5 +1,6 @@
 ENV=development
 LOCALENV=true
+BACKUP_DIR=/mnt/SR/DATA/BKP/
 
 POSTGRES_USER=socialroots
 POSTGRES_DB=socialroots_default

.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+#github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+#patreon: # Replace with a single Patreon username
+open_collective: socialroots-projects
+#ko_fi: # Replace with a single Ko-fi username
+#tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+#community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+#liberapay: # Replace with a single Liberapay username
+#issuehunt: # Replace with a single IssueHunt username
+#lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+#polar: # Replace with a single Polar username
+#buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+#thanks_dev: # Replace with a single thanks.dev username
+#custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.gitmodules

@@ -1,31 +1,31 @@
 [submodule "modules/ORCHESTRATOR"]
 	path = modules/ORCHESTRATOR
 	url = git@github.com:SocialRoots/rootshoots-orchestrate.git
-	branch = integration
+	branch = alpha
 [submodule "modules/RS-USERS"]
 	path = modules/RS-USERS
 	url = git@github.com:SocialRoots/rootshoot-users.git
-	branch = integration
+	branch = alpha
 [submodule "modules/RS-GROUPS"]
 	path = modules/RS-GROUPS
 	url = git@github.com:SocialRoots/rootshoot-groups.git
-	branch = integration
+	branch = alpha
 [submodule "modules/RS-CONNECTIONS"]
 	path = modules/RS-CONNECTIONS
 	url = git@github.com:SocialRoots/rootshoots-connections.git
-	branch = integration
+	branch = alpha
 [submodule "modules/RS-NOTIFICATIONS"]
 	path = modules/RS-NOTIFICATIONS
 	url = git@github.com:SocialRoots/rootshoot-notification.git
-	branch = integration
+	branch = alpha
 [submodule "modules/RS-NOTES"]
 	path = modules/RS-NOTES
 	url = git@github.com:SocialRoots/rootshoot-sendmail.git
-	branch = integration
+	branch = alpha
 [submodule "modules/RS-RESPONSES"]
 	path = modules/RS-RESPONSES
 	url = git@github.com:SocialRoots/rootshoot-responsecapture.git
-	branch = integration
+	branch = alpha
 [submodule "modules/RS-UTILS"]
 	path = modules/RS-UTILS
 	url = git@github.com:SocialRoots/sr-microservices-utils.git

CLAUDE.md → AGENTS.md

@@ -1,6 +1,6 @@
-# CLAUDE.md
+# AGENTS.md
 
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+This file provides guidance to AI coding assistants when working with code in this repository.
 
 ## Architecture Overview
 
@@ -28,8 +28,8 @@ Each microservice is a separate Go module with its own database, migrations, and
 git submodule update --init --recursive
 
 # Set up databases (requires PostgreSQL running)
-chmod +x init-db.sh
-./init-db.sh
+chmod +x bin/init-db.sh
+./bin/init-db.sh
 ```
 
 ### Docker Operations
@@ -116,6 +116,17 @@ go run cmd/script/main.go  # Run utility scripts
 - Test databases configured via `.env.test` files
 - Integration tests communicate with other services via HTTP clients
 
+### Testing Best Practices
+- **IMPORTANT**: Tests use a dedicated test DATABASE (`rootshoot-tests`), NOT `_test` suffixed tables
+- Do NOT use `TestCk()` or similar table suffix functions in tests - use the main table names
+- The `.env.test` file points to the test database, so migrations create tables with normal names there
+- **IMPORTANT**: The test database is shared across modules. Before running migrations for a module, you must reset the database:
+  ```bash
+  PGPASSWORD='th15.R00TZ' psql -U socialroots -h localhost -d rootshoot-tests -c "DROP SCHEMA public CASCADE; CREATE SCHEMA public; GRANT ALL ON SCHEMA public TO socialroots;"
+  ```
+- Then run migrations: `set -a && source .env.test && set +a && ./scripts/migrate.sh migrate`
+- To run tests: `set -a && source .env.test && set +a && go test -v ./pkg/db`
+
 ### Security & Authentication
 - ORCHESTRATOR handles authentication and authorization
 - Services validate requests through user tokens and service keys