AFTER | 79b586f276a2
REAL SERVER OUTPUT EXCERPTS + READ-ONLY SQLITE CHECKS
Environment: Linux, Node server, isolated synthetic database

Case A: ledger ends at 069; schema already includes 070-072.
migrations: [
    '70_PeerLinks',
    '71_PeerLinkFence',
    '72_WaitingLinkRequestIndex',
    '73_ActiveTurnItemIndexes',
    '74_ExcludeAttachmentPlaceholdersFromSearch',
    '75_SubagentDeliveryState',
    '76_ProjectionProjectsPinArchive',
    '77_RepairBooleanSettledOverride',
    '78_DropOrchestrationEventCorrelationIndex',
    '79_DelegatedRecoveryIndexes',
    '80_ScheduledTaskThreadMode'
  ]
[08:55:50.325] INFO (#626): Listening on http://127.0.0.1:18432
SQL: max(effect_sql_migrations.migration_id) = 80
SQL: synthetic peer row unchanged = True
SQL: synthetic peer fenced = 1
SQL: PRAGMA integrity_check = ok

Case B: same schema; ledger ends at 071 (isolates migration 072).
migrations: [
    '72_WaitingLinkRequestIndex',
    '73_ActiveTurnItemIndexes',
    '74_ExcludeAttachmentPlaceholdersFromSearch',
    '75_SubagentDeliveryState',
    '76_ProjectionProjectsPinArchive',
    '77_RepairBooleanSettledOverride',
    '78_DropOrchestrationEventCorrelationIndex',
    '79_DelegatedRecoveryIndexes',
    '80_ScheduledTaskThreadMode'
  ]
[08:56:13.380] INFO (#623): Listening on http://127.0.0.1:18435
SQL: max(effect_sql_migrations.migration_id) = 80
SQL: synthetic peer row unchanged = True
SQL: synthetic peer fenced = 1
SQL: PRAGMA integrity_check = ok

Seed peer-row SHA256 (same on all four databases):
e5608f8cfe0c2d68527c7c2668c616d626b08fd2efce1f78a7a7d67d4b4a28cc

Additional observed client checks:
CLI project add completed successfully through the running server.
Chromium web client paired and loaded the chat view (1280 x 800).