data-set terminate: confirm skipProvider as the default termination path

[SgtPooki]

data-set terminate calls synapse.storage.terminateService({ dataSetId, skipProvider: true }) (src/data-set/run.ts:314). skipProvider: true is filecoin-pin's explicit choice, not the SDK default. This issue tracks confirming it as the right default.

Both paths invoke the same on-chain call, FWSS.terminateService(dataSetId), so the fund wind-down (endEpoch, lockup-period settlement) is identical:

• skipProvider: true (current): the owner wallet submits the tx directly and always returns a tx hash.
• provider-relayed (SDK default): the owner signs an EIP-712 payload, the provider submits the same tx, and the SDK refuses when the account cannot settle its lockup in full (debt > 0).

Differences that matter for the CLI:

1. Gas: direct, the owner pays; relayed, the provider pays.
2. Debt gate: relayed refuses under outstanding lockup debt; direct always runs.
3. Reliability: relayed needs the provider's HTTP endpoint up and willing; direct only needs the chain.
4. tx hash: direct returns one immediately (the --wait UX depends on it); relayed polls the provider status endpoint and can come back empty.

For a self-service CLI, direct is the deterministic, provider-independent path that always yields a confirmable tx hash, so it stays the default. The one thing it gives up is letting the provider cover termination gas.

Decision to confirm: keep skipProvider: true as the default, and optionally expose provider-relayed termination behind a flag for users who want gasless wind-down.

Verified against synapse-sdk v1.0.1 and synapse-core v0.7.0 (storage/terminate.js, warm-storage/terminate-service.js, sp/terminate-service.js).

Context: PR #574 review thread #574 (comment) (noted as an out-of-scope follow-up in the PR body).

cc @juliangruber

[SgtPooki]

@rvagg @juliangruber I think we just need to decide whether we like the default here, or if we need a fallback to use provider in the cli/lib.

[rvagg]

Default should be skipProvider: false, it should go through the provider because then when it lands in FWSS we get immediate termination rather than having to wait 30 days for lockup; but there should be an override, --skip-provider would be a good option to add I think. The whole point of skipProvider is that you could potentially have an uncooperative SP that doesnt' want to submit your termination msg, so you can side-step them to get the termination to land on chain but you have to pay the gas for submitting the message.

Both paths invoke the same on-chain call, FWSS.terminateService(dataSetId), so the fund wind-down (endEpoch, lockup-period settlement) is identical

This isn't quite correct. The key part is here: https://github.com/FilOzone/filecoin-services/blob/d1d67d1cea352ff746225936593b56ed1f1d66e5/service_contracts/src/FilecoinWarmStorageService.sol#L1033 - when you go through an SP, extraData contains the EIP-712 validation that it's the client, in that case both client and SP are agreeing so therefore we go through to immediate termination. With skipProvider: true we don't hit that branch.

[BigLep]

Triage comment from 2026 FOC Board Triage (Post GA): easy fix, should do