Config sync uploads {} instead of actual config content

[Defiant-Engineer]

Description

When using Tabby with rtabby-web-api, config sync appears to succeed (HTTP 200), but the content field is always saved as {}.

Steps to reproduce

1. Configure Tabby sync:

   configSync:
     host: https://<instance>
     token: <token>

2. Add a profile in Tabby

3. Click “Upload as a new config”

4. Check DB:

   SELECT id, name, content FROM configs ORDER BY id DESC LIMIT 1;

Actual result

content = {}

Expected result

Config content (profiles, etc.) should be stored instead of {}

Notes

• Tested with Tabby 1.0.215 and 1.0.230
• rtabby-web-api v0.4.5