fix: activate dataset and persist clearing account config in demo compose (#1250)

* fix: wire deposit/withdrawal saga orchestration in unified binary

The unified binary's wireCurrentAccount used the basic NewService()
constructor which creates a Service without deposit/withdrawal
orchestrators, causing nil pointer panics on ExecuteDeposit calls.

Switch to NewServiceWithExistingClients() with loopback gRPC clients
for position-keeping and financial-accounting, enabling full Starlark
saga orchestration within the unified binary.

Also:
- Copy saga script assets into Docker image (SAGA_ASSET_DIR=/app)
- Fix init-databases.sql: meridian_internal_account → meridian_internal_bank_account

* fix: load clearing account config from env for deposit double-entry

Without a clearing account, the deposit saga only creates a CREDIT
posting (to customer). FA rejects the unbalanced booking log. Load
AccountConfig from DEPOSIT_CLEARING_ACCOUNT_ID env var so the saga
creates both DEBIT (clearing) and CREDIT (customer) postings.

Gracefully falls back to nil when env var is unset.

* fix: fail fast on invalid clearing account config

Differentiate "env var not set" (graceful skip) from "env var set but
invalid" (hard error) to avoid silently falling back to single-sided
postings when config is misconfigured.

* fix: use account_id for PK position logs in deposit and withdrawal sagas

The Starlark deposit and withdrawal scripts were passing
external_identifier (e.g. VE-GBP-010) as the position_id to
position_keeping.initiate_log, but the post-deposit balance query
uses account_id (e.g. ACC-xxx). This mismatch caused PK balance
lookups to fail with "no position logs found for account".

* fix: add required CEL expressions to seed-demo dataset registration

RegisterDataSet now requires validation_expression and
resolution_key_expression fields. Add appropriate CEL expressions
for the wholesale energy price dataset.

* fix: activate dataset before recording observations and persist clearing account config

- seed-demo: call ActivateDataSet after RegisterDataSet to transition
  from DRAFT to ACTIVE before recording observations
- docker-compose: add DEPOSIT_CLEARING_ACCOUNT_ID env var passthrough
  so it persists across deployments
- .env.demo.example: document the clearing account config

---------

Co-authored-by: Ben Coombs <bjcoombs@users.noreply.github.com>

Author: bjcoombs

cmd/seed-demo/main.go

@@ -471,6 +471,16 @@ func seedMarketData(ctx context.Context, conn *grpc.ClientConn) error {
 		fmt.Println("  Registered dataset: WHOLESALE_ENERGY_GBP_KWH")
 	}
 
+	// Activate dataset so observations can be recorded
+	_, err = client.ActivateDataSet(ctx, &marketv1.ActivateDataSetRequest{
+		Code: "WHOLESALE_ENERGY_GBP_KWH",
+	})
+	if err == nil {
+		fmt.Println("  Activated dataset: WHOLESALE_ENERGY_GBP_KWH")
+	} else if st, ok := status.FromError(err); !ok || st.Code() != codes.FailedPrecondition {
+		return fmt.Errorf("activate dataset: %w", err)
+	}
+
 	// Seed 30 days of wholesale prices.
 	// UK wholesale prices vary between 15-35p/kWh with daily volatility.
 	rng := rand.New(rand.NewSource(42)) //nolint:gosec

deploy/demo/.env.demo.example

@@ -148,6 +148,11 @@ KAFKA_ENABLED=false
 # [OPTIONAL] Internal master tenant identifier used by the market-information service.
 MASTER_TENANT_ID=meridian_master
 
+# [OPTIONAL] Clearing account ID for deposit double-entry postings.
+# When set, deposits create both a DEBIT posting to this clearing account
+# and a CREDIT posting to the customer account.
+DEPOSIT_CLEARING_ACCOUNT_ID=CLEARING-GBP-001
+
 # ---------------------------------------------------------------------------
 # Observability (OpenTelemetry)
 # ---------------------------------------------------------------------------

deploy/demo/docker-compose.yml

@@ -98,6 +98,9 @@ services:
       # --- Multi-tenancy ---
       MASTER_TENANT_ID: ${MASTER_TENANT_ID:-meridian_master}
 
+      # --- Clearing accounts ---
+      DEPOSIT_CLEARING_ACCOUNT_ID: ${DEPOSIT_CLEARING_ACCOUNT_ID:-}
+
       # --- Connection pool ---
       DB_MAX_OPEN_CONNS: ${DB_MAX_OPEN_CONNS:-25}
       DB_MAX_IDLE_CONNS: ${DB_MAX_IDLE_CONNS:-5}