Residual bp.sbcB5 files remain in Steam Cloud after deleting blueprints in-game

After deleting cloud blueprints from the in-game Blueprints screen, several bp.sbcB5 files remain in the Steam Cloud and in the local Steam userdata folder. They cannot be removed by normal means: deleting them manually from disk causes Steam to restore them from the cloud on the next sync.

Observed behavior

1. I deleted several blueprints (saved to Cloud) from the in-game Blueprints screen (F10). They disappeared from the UI.
2. 4 .sbcB5 files remained under:
   C:\Program Files (x86)\Steam\userdata\<SteamID>\244850\remote\Blueprints\cloud\<BlueprintName>\bp.sbcB5
3. Deleting these files manually from disk did not help. They were restored by Steam on the next sync (including after running cloud_sync_up 244850 in the Steam console).
4. These blueprints no longer exist in the game UI, so they cannot be deleted from there.
   Workaround that worked
   For each residual Blue-Print folder (example: MAKO):
   Launch the game with Steam running. Create a new blueprint with exactly the same name (MAKO), saved to Cloud. Delete that blueprint from the in-game Blueprints screen. Exit the game and wait for Steam Cloud status to show “Up to date”. After this, the residual Blueprints\cloud\MAKO\bp.sbcB5 file was gone and was not restored.
   Expected behavior
   Deleting a cloud blueprint in-game should remove the corresponding bp.sbcB5 file from Steam Cloud, so no orphaned files remain.
   Notes
   I don’t know the root cause. It looks like the deletion is not propagated to Steam Cloud in some cases, leaving orphaned files that the UI no longer lists. Recreating a blueprint with the same path seems to re-register the file with the game so that the deletion goes through the normal path. I’m sharing this in case it helps others, and in case the team can look at how cloud blueprint deletion is handled.