fix(rig): respect parked/docked status in gt up and gt rig start

Previously, `gt up` and `gt rig start` would start witnesses and
refineries for parked/docked rigs, bypassing the operational status
protection. Only the daemon respected the wisp config status.

Now both commands check wisp config status before starting agents:
- `gt up` shows "skipped (rig parked)" for parked/docked rigs
- `gt rig start` warns and skips parked/docked rigs

This prevents accidentally bringing parked/docked rigs back online
when running routine commands.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

internal/cmd/rig.go

@@ -825,6 +825,15 @@ func runRigStart(cmd *cobra.Command, args []string) error {
 			continue
 		}
 
+		// Check if rig is parked or docked
+		cfg := wisp.NewConfig(townRoot, rigName)
+		status := cfg.GetString("status")
+		if status == "parked" || status == "docked" {
+			fmt.Printf("%s Rig '%s' is %s - skipping (use 'gt rig unpark' or 'gt rig undock' first)\n",
+				style.Warning.Render("⚠"), rigName, status)
+			continue
+		}
+
 		fmt.Printf("Starting rig %s...\n", style.Bold.Render(rigName))
 
 		var started []string