Run isolated PostgreSQL and RustFS tests in Gitea CI

README.md

@@ -5,8 +5,9 @@ Standalone Python archiver for the three fixed `btcprod` tables: `public.binance
 and versioned archive bucket, progress ledger and restricted PostgreSQL role have
 been provisioned; source index preflight and deployment are still pending.**
 An operator run verified the first weekly archive, then hit a ledger transition bug
-before deletion. That bug is now fixed; no deployment has been performed. Remote
-repository hosting and CI/Harbor provisioning remain operator decisions.
+before deletion. That bug is now fixed; deployment is being prepared suspended.
+The repository is hosted at https://git.pmagnus.cloud/magnus/btcdata-archive;
+Gitea Actions and project-scoped Harbor CI/pull credentials are configured.
 
 ## Install and test
 
@@ -38,8 +39,12 @@ kill/network/disk fault testing and production connectivity remain rollout gates
 adds pytest. Regenerate with Python 3.12, pip 25.2 and pip-tools 7.5.1:
 `pip-compile --generate-hashes -o requirements.lock pyproject.toml` and
 `pip-compile --extra test --generate-hashes -o requirements-test.lock pyproject.toml`.
-CI tests before publishing a full-commit tag to the existing approved Harbor registry.
-Deploy using the published digest, not a mutable tag. No remote has been configured.
+CI runs the full suite against disposable PostgreSQL/RustFS before publishing a
+full-commit tag to the private `btcdata-archive` project in the approved Harbor registry.
+CI has project-scoped push/pull access; Kubernetes has a separate pull-only identity.
+Tests run inside a disposable container on an isolated Docker network, without
+published ports or production credentials, including when CI uses a Docker job container.
+Deploy using the published digest, not a mutable tag. Remote: `gitea:magnus/btcdata-archive.git`.
 
 ## Configuration