api+ui: kind-scoped save/delete endpoints and links

API: /config/{services,jobs,tools,static}/{name} now pin the twin they
target — _save_deployment/_delete_deployment take an explicit kind so a
patch to a 'backup' service can't bleed into a 'backup' job/tool. Add
/tools and /static endpoints; keep /deployments/{name} kind-agnostic.
New test_kind_twins proves per-kind save/delete isolation on disk.

UI: ConfigPanel and CreateDeploymentForm write to the kind-scoped
resource; GatewayPanel/NodeDetail/DeploymentsSection link via a shared
detailPath(name, kind) helper instead of the ambiguous /deployment/:name.

Includes incidental ruff-format reflow of untouched api files.

app/src/pages/ScheduledDetail.tsx

@@ -50,24 +50,16 @@ export function ScheduledDetailPage() {
               <Clock size={14} className="shrink-0 text-[var(--muted)]" />
               {deployment.schedule}
             </span>
-            {deployment.systemd && (
-              <>
-                <span className="text-[var(--muted)]">Timer unit</span>
-                <span className="font-mono break-all">
-                  {deployment.systemd.unit_name.replace(".service", ".timer")}
-                </span>
-              </>
-            )}
           </div>
         </div>
       )}
 
+      <ConfigPanel deployment={deployment} configSection="jobs" onRefetch={refetch} />
+
       {deployment.systemd && (
         <SystemdPanel name={deployment.id} systemd={deployment.systemd} />
       )}
 
-      <ConfigPanel deployment={deployment} configSection="jobs" onRefetch={refetch} />
-
       {deployment.managed && (
         <div className="mb-6">
           <h2 className="text-lg font-semibold mb-3">Logs</h2>