Remove unnecessary full_status and snapshot API endpoints

docs/API.md

@@ -281,29 +281,6 @@ Known callers:
 
 - `RenderServerProxy.get_status()`
 
-### `GET /api/snapshot`
-
-Returns local status, all jobs, and a timestamp.
-
-Known callers:
-
-- `full_status()` internally.
-
-Review note: no direct in-repo HTTP callers were found. It overlaps with
-`/api/status` plus `/api/jobs`.
-
-### `GET /api/full_status`
-
-Returns a multi-server shaped status payload with the local server populated.
-
-Known callers:
-
-- `RenderServerProxy.get_full_status()`
-- `dashboard.py`
-
-Review note: this currently reports only the local server. The response shape
-suggests an intended future aggregation point.
-
 ### `GET /api/presets`
 
 Returns `config/presets.yaml`.
@@ -492,10 +469,6 @@ Review note: development/debug only.
 
 ## Redundancy and Cleanup Review
 
-Likely redundant or overlapping routes:
-
-- `/api/snapshot` overlaps with `/api/status` and `/api/jobs`. It is currently
-  used internally by `/api/full_status`.
 Routes with no in-repo callers found:
 
 - `GET /api/jobs/status/<status_val>`

docs/api.html

@@ -406,18 +406,6 @@
         <p>Returns local system and queue status, including operating system, CPU, memory, job counts, hostname, port, app version, and API version.</p>
       </article>
 
-      <article class="endpoint">
-        <div class="endpoint-header"><span class="method get">GET</span><span class="path">/api/snapshot</span></div>
-        <p>Returns local status, all jobs, and a timestamp.</p>
-        <div class="note">No direct in-repo HTTP callers were found. It overlaps with <code>/api/status</code> plus <code>/api/jobs</code> and is used internally by <code>/api/full_status</code>.</div>
-      </article>
-
-      <article class="endpoint">
-        <div class="endpoint-header"><span class="method get">GET</span><span class="path">/api/full_status</span></div>
-        <p>Returns a multi-server shaped status payload with the local server populated. Used by <code>RenderServerProxy.get_full_status()</code> and <code>dashboard.py</code>.</p>
-        <div class="note">The response shape suggests an intended future aggregation point, but it currently reports only the local server.</div>
-      </article>
-
       <article class="endpoint">
         <div class="endpoint-header"><span class="method get">GET</span><span class="path">/api/presets</span></div>
         <p>Returns <code>config/presets.yaml</code>.</p>
@@ -562,13 +550,6 @@
     <section id="cleanup">
       <h2>Cleanup Review</h2>
       <div class="panel">
-        <h3>Likely Redundant Or Overlapping Routes</h3>
-        <ul>
-          <li><code>/api/snapshot</code> overlaps with <code>/api/status</code> and <code>/api/jobs</code>. It is currently used internally by <code>/api/full_status</code>.</li>
-        </ul>
-      </div>
-
-      <div class="panel" style="margin-top: 14px;">
         <h3>Routes With No In-Repo Callers Found</h3>
         <ul>
           <li><code>GET /api/jobs/status/&lt;status_val&gt;</code></li>