DeepDrftAPI Rename

DeepDrftManager/Services/CmsTrackService.cs

@@ -8,9 +8,9 @@ using NetBlocks.Models;
 namespace DeepDrftManager.Services;
 
 /// <summary>
-/// HTTP client over the DeepDrftContent API for all CMS track operations. The Manager is
+/// HTTP client over the DeepDrftAPI API for all CMS track operations. The Manager is
 /// InteractiveServer-only and holds no in-process data layer: every track read and write is a
-/// network call to DeepDrftContent, which is the single authority over both the SQL metadata
+/// network call to DeepDrftAPI, which is the single authority over both the SQL metadata
 /// store and the binary audio vault. The ApiKey is baked into the <c>DeepDrft.Content.Cms</c>
 /// named client's default headers.
 /// </summary>
@@ -82,7 +82,7 @@ public class CmsTrackService : ICmsTrackService
                     return ResultContainer<TrackEntity>.CreateFailResult("Upload failed on the content server. Please try again.");
                 }
 
-                // 4xx: body is user-friendly validation text from DeepDrftContent — relay as-is.
+                // 4xx: body is user-friendly validation text from DeepDrftAPI — relay as-is.
                 _logger.LogWarning("Content API rejected upload: {Status} {Body}", statusCode, body);
                 return ResultContainer<TrackEntity>.CreateFailResult(
                     string.IsNullOrWhiteSpace(body) ? $"Upload rejected ({statusCode})." : body);

DeepDrftManager/Services/ICmsTrackService.cs

@@ -6,13 +6,13 @@ namespace DeepDrftManager.Services;
 
 /// <summary>
 /// CMS-side track operations for the Manager host. Every read and write goes over HTTP to the
-/// DeepDrftContent API, which is the single authority over both the SQL metadata store and the
+/// DeepDrftAPI API, which is the single authority over both the SQL metadata store and the
 /// binary audio vault. DeepDrftManager holds no in-process data layer.
 /// </summary>
 public interface ICmsTrackService
 {
     /// <summary>
-    /// Proxy a WAV upload to DeepDrftContent. The Content API owns the dual-database write and
+    /// Proxy a WAV upload to DeepDrftAPI. The Content API owns the dual-database write and
     /// returns the persisted entity carrying the SQL-assigned <c>Id</c>. A vault-without-SQL
     /// orphan is handled and logged server-side; here it surfaces as a failed result.
     /// </summary>