Bug: add_resource API does not move temp file to target path (v0.3.3)

[MuBeiGe]

Bug: add_resource API does not move temp file to target path (v0.3.3)

Environment:

• OpenViking v0.3.3
• Data path: ~/.openviking/data
• Backend: local filesystem

Reproduction steps:

1. Start OpenViking server v0.3.3
2. Call POST /api/v1/resources/temp_upload to upload a file, get temp_file_id
3. Call POST /api/v1/resources with {"temp_file_id": "...", "to": "viking://resources/test/file.md", "wait": false}
4. API returns success, but file stays in ~/.openviking/data/temp/upload/ directory
5. GET /api/v1/fs/stat?uri=viking://resources/test/file.md returns NOT_FOUND

Expected: File should be moved to ~/.openviking/data/viking/{account}/resources/test/file.md

Actual: File remains in ~/.openviking/data/temp/upload/{temp_file_id}

Temporary workaround (V28.1 Hermes): Write directly to local filesystem {data_path}/viking/{account}/{scope}/{path} instead of using the API.

[MaojiaSheng]

please use "add-resource --wait" if you need all data files prepared.