TT-7583 fix: write the remote artifact type id into phrase BT step settings

[nabalone]

Summary

TT-7583 — PBT Auto Save fails in the Desktop Application.

1. Write the remote artifact type id into phrase BT step settings.
PhraseBackTranslateStepSettings seeded its artifact type from getTypeId, which
returns the local Orbit record id. That value was emitted into the step settings JSON
and persisted verbatim, but every reader decodes settings.artifactTypeId with
remoteIdGuid (and SelectArtifactType hands the other step-settings dialogs remote
ids). The ?? id fallback in those readers hid it locally; once the step synced,
peers could not resolve the GUID.

Now the local id is translated to its remote id when seeding, keeping the local id
when there is no mapping (offline-only artifact types have no remote id).

2. Guard auto-segmentation against two crash paths.
Both are throws hit while auto-segmenting a passage on the way into phrase back
translation, and both are behavior-preserving apart from the crash:

• mergeVerses absorbed a too-short gap into the previous region, but the first
  gap has no previous region — result[result.length - 1].end threw on undefined.
  It now skips that fixup when result is empty, leaving start put so the short
  leading gap folds into the next region (the same outcome as the existing
  fromVerses(start) skip path).
• extractRegions spliced away a too-short trailing region unconditionally, so a
  clip shorter than minRegionLenSeconds was left with an empty array and then threw
  on sRegions[sRegions.length - 1]. It now only drops the trailing region when more
  than one remains, keeping the single segment for a very short clip.

A comment in useGuidedPhraseSegments also records a related case that is not
fixed here: auto-segment can legitimately yield nothing, and returning false leaves
the 250 ms bootstrap poll in PassageDetailGuidedPhraseRecord spinning. Left as a
note rather than a behavior change.

Files touched

• src/renderer/src/components/StepEditor/PhraseBackTranslateStepSettings.tsx — seed with the remote artifact type id
• src/renderer/src/components/StepEditor/PhraseBackTranslateStepSettings.test.tsx — coverage for the translation
• src/renderer/src/crud/useWavesurferRegions.tsx — the two auto-segmentation crash guards
• src/renderer/src/components/PassageDetail/carefulSpeech/useGuidedPhraseSegments.ts — comment only, no behavior change

Test plan

• PhraseBackTranslateStepSettings.test.tsx covers the id translation and the
  offline-only fallback.
• Manual: create a phrase BT step, confirm the persisted artifactTypeId is the
  remote GUID.
• Manual: auto-segment audio whose first gap is shorter than the minimum region
  length, and audio whose whole clip is shorter than the minimum — neither should
  throw; the short clip keeps one segment.

Notes

• The branch also carries TT-7583 fix: only warn of a network issue when the upload never completed and its revert, so those two cancel out and contribute no net
  diff. That work (UploadFailureReason / suggestsConnectionProblem) is not part of
  this PR's behavior — it can be dropped from history or reland separately.
• Rebased onto the latest develop; the earlier duplicate of Retry rejected phrase save on reconnect (already merged as fix: retry rejected phrase save on reconnect #499) was dropped by the rebase.

🤖 Generated with Claude Code

[nabalone]

Seed always uses the Phrase BT slug even for a Retell BT preset

The seed is hard-coded to ArtifactTypeSlug.PhraseBackTranslation, while the comment says the artifact type is fixed by the workflow step preset (Phrase BT vs Retell BT). For a brand-new Retell BT step with empty settings, the dialog will write the Phrase BT artifact type. This is pre-existing behavior (the same hard-coded slug existed before), but the remote-id translation now makes that seeded value durable across peers, so it is worth confirming Retell BT steps always arrive with settings already populated.

[nabalone]

Devin left this comment. Can someone confirm whether this preexisting behavior is intentional?