Bump version to 2.13.0 (spec v158)

[sameh-farouk]

Release 2.13.0 — spec_version 157 → 158 (runtime upgrade required).

Version bumped across all components via make version-bump type=minor: runtime/Cargo, tfchain-client-js, activation-service, scripts, fork-off-substrate, and the three Helm charts. Verified consistent — all five package versions at 2.13.0, all three charts at 2.13.0, spec_version: 158.

Highlights since 2.12.0

Bridge — reliability & fund safety

• Crash-safe idempotency for withdraws and refunds (feat(bridge): crash-safe idempotency for withdraws and refunds #1096)
• Quarantine undeliverable refunds instead of crashlooping (fix(bridge): quarantine undeliverable refunds instead of crashlooping #1092)
• Pallet: reject creating an already-executed refund (fix(pallet-tft-bridge): reject creating an already-executed refund #1093) — drives the spec bump
• Correct Stellar deposit asset/issuer validation (fix(bridge): correct Stellar deposit asset validation #1094)
• Error wrapping / trace_id / log fixes (fix(bridge): correct error wrapping, trace_id key, and a log message #1095)
• Reset expiry timer on burn/refund re-proposal (fix(bridge): reset expiry timer on re-proposal after burn/refund expiry #1081)
• Fetch tx operations once in processTransaction (perf(bridge): fetch transaction operations once in processTransaction #1098)
• Support multiple substrate URLs for redundancy (Support multiple substrate URLs #1028)

Pallet / runtime

• Enforce node_certification in farming-policy limits (fix(pallet-tfgrid): enforce node_certification in farming policy limits #1087) — changes which default farming policy a node receives

activation-service

• Migrated to @threefold/tfchain_client (fix(activation-service): migrate to @threefold/tfchain_client #1105) — fixes hanging at startup when the chain is unreachable, and failed funding transfers no longer report success
• Removed the unauthenticated /create-entity route (fix(activation-service): remove unauthenticated /create-entity route (crash + wallet-drain) #1103) — crash + wallet-drain surface
• Stopped returning internal error messages to callers; dropped the unused KYC_PUBLIC_KEY requirement (fix(activation-service): stop leaking internal errors, drop unused KYC_PUBLIC_KEY #1109)
• Dependency upgrades: pino, jsonschema, http-errors (chore(activation-service): upgrade pino, jsonschema, http-errors #1085); express 4.17.1 → 4.21.2 ([Snyk] Upgrade express from 4.17.1 to 4.21.2 #1031)

Clients

• tfchain-client-js: resolve types from runtime metadata v14/v15, drop static types.json (fix(tfchain-client-js): remove static types.json, use metadata v14/v15 for type resolution #1078)
• tfchain-client-js: fix stale runtime assumptions in read wrappers — twin ip, entity storage, null crashes (fix(tfchain-client-js): fix stale runtime assumptions in read wrappers (twin ip, entity storage, null crashes) #1101)
• tfchain-client-js: fix the test script for Node ≥ 22, drop the stale lock file (chore(tfchain-client-js): fix the test script and drop the stale lock file #1106)
• go-client: resolve errors from runtime metadata instead of a hardcoded list (fix(go-client): resolve errors from runtime metadata instead of hardcoded list #1086)

Infra / docs

• CI: only build substrate when substrate changed, supersede stale runs (ci: only build substrate when substrate changed, and supersede stale runs #1108)
• CI: bridge lint on Go 1.21 (fix(ci): update bridge lint workflow for Go 1.21 #1083); weights workflow safe.directory fix (fix(ci): correct git safe.directory path in benchmark weights workflow #1091)
• Validator migration guide (Add validator migration guide #1082)
• Apache LICENSE with TFTech NV copyright; README re-framing and repository rename references

Runtime upgrade

spec_version 158 is required by the pallet-tft-bridge refund guard (#1093) and the farming-policy change (#1087).

transaction_version stays at 2: there are no extrinsic surface changes in this release — no call_index or call-signature changes anywhere under substrate-node/pallets. Outside of weights and tests, the only pallet source changes are pallet-tfgrid/src/pricing.rs and pallet-tft-bridge/src/tft_bridge.rs, both logic inside existing calls.

⚠️ Operator notes — read before deploying activation-service

1. ACTIVATION_AMOUNT is now read. It has been required by bin/www since the service was written while nothing consumed it; the amount was hardcoded to 0.1 TFT. It is honoured again, in whole TFT, as readme.md and the chart always documented. The chart default is set to 0.1 so an un-overridden deploy funds exactly what it funds today — but if your values file sets activation_amount: 1, this release will fund 1 TFT per activation instead of 0.1. Check the deployed value.
2. The service now refuses to start if ACTIVATION_AMOUNT is malformed or below the chain's existential deposit (500 base units), and exits 1 when the chain is unreachable instead of hanging silently before ever listening. A misconfigured deployment will crashloop visibly rather than appear healthy — intended, but it changes what a bad config looks like.
3. Error responses changed shape to { message }, and 5xx no longer carry internal detail (it goes to the log). The bundled frontend renders a fixed string and never reads the body, so the UI is unaffected.
4. kyc_public_key was removed from the chart. Values files still setting it are unaffected; the value is simply unused.
5. The activation-service image base moved to node:22, required by @polkadot/api 15.x.

Not in this release

• feat(bridge): batch withdraw/refund proposals (force_batch API + E2E harness) #1104 (bridge batching) is deliberately excluded — its own description marks it as draft with four open correctness items.
• tfgrid-api-client is not published to npm; those credentials remain lost (Publish tfgrid-api-client 2.13.0 to npm #1099, closed). activation-service no longer needs it, but clients/tfchain-client-js stays the only JS client exposing the V3 billing opt-out surface, so it is not retired.

After merge

Follow the remaining steps in docs/production/releases.md: tag v2.13.0, publish the release, then the image workflows fire on release: published.