Dockge Removal

Removed dockge from the app as it is not required due to the manager page picking up most of its abilities.

manager/src/app/dashboard/layout.tsx

@@ -2,8 +2,6 @@ import Link from "next/link";
 import { logoutAction } from "./logout-action";
 
 export default function DashboardLayout({ children }: { children: React.ReactNode }) {
-  const dockgeUrl = process.env.DOCKGE_URL;
-
   return (
     <div className="min-h-screen">
       <header className="flex items-center justify-between border-b border-line bg-surface px-6 py-4">
@@ -14,11 +12,6 @@ export default function DashboardLayout({ children }: { children: React.ReactNod
           <Link href="/dashboard/settings" className="text-muted hover:text-ink">
             Settings
           </Link>
-          {dockgeUrl && (
-            <a href={dockgeUrl} target="_blank" rel="noreferrer" className="text-muted hover:text-ink">
-              Dockge ↗
-            </a>
-          )}
           <form action={logoutAction}>
             <button type="submit" className="text-muted hover:text-ink">
               Sign out

manager/src/lib/docker.ts

@@ -7,9 +7,8 @@ const execFileAsync = promisify(execFile);
  * Every call here runs `docker compose` with `cwd` set to a stack's own
  * directory (stacks/<slug>/) rather than passing explicit -f/--env-file
  * flags — compose already auto-loads `compose.yaml` and `.env` from the
- * current directory, and this is the same convention Dockge itself uses,
- * so a stack behaves identically whether it's started by this app, by
- * Dockge, or by hand from the command line.
+ * current directory, so a stack behaves identically whether it's started
+ * by this app or by hand from the command line.
  *
  * This app's own container needs the Docker socket mounted and the
  * `docker compose` CLI installed (see manager/Dockerfile) — these calls