feat(federation): wire onPeerActivated into 8 transition sites

Every code location that sets federation_peers.status='active'
now invokes onPeerActivated(peerId, reason). HTTP handler sites
use fire-and-forget (.catch(log)) so the response isn't blocked
by sync-pull pagination. The worker-internal health-check site
awaits the handler since the tick is already async.

Sites: /peer/initiate, /peer/accept (4 branches), /approval-
requests/:id/approve, health check recovery, ensurePeered/
performHandshake.
This commit is contained in:
Jannis Braun
2026-04-22 00:39:58 +02:00
parent 57d7ca66d3
commit 250596c0f6
3 changed files with 26 additions and 1 deletions
@@ -11,7 +11,7 @@ import { getDmMessageWithUser } from '../routes/dm.js';
import { connectionManager } from '../ws/handler.js';
import { generateThumbnail } from './thumbnail.js';
import type { FederationRelayRequest, FederationRelayResponse, FederationRelayEvent } from '@backspace/shared';
import { startupBootstrapSync } from './federationPeerActivation.js';
import { onPeerActivated, startupBootstrapSync } from './federationPeerActivation.js';
import fs from 'node:fs';
import path from 'node:path';
import crypto from 'node:crypto';
@@ -1054,6 +1054,8 @@ async function processHealthCheckTick(): Promise<void> {
console.log(
`[federation-worker] Peer ${peer.origin} recovered — marked active`,
);
await onPeerActivated(peer.id, 'health_check_recovery');
}
// If not ok, leave as unreachable — will check again next cycle
} catch (err) {