Looks like I may have figured it out.

I found where I could set the VLAN Interface IP Address to Static, so I set it to 10.1.13.1.  I then updated my DHCP scope default gateway to 'manual' and pointed it to 10.1.13.1.  It appears to work now as expected.

Does this sound right?

nope.  While it routes internally fine, I lost internet.  seems as if there is no route to the outside now.

  @Hank21 Is there not a way to just create a static route on the L3 Switch to handle traffic that is destined outside of my configured VLANs?  

Also, I am using an Omada Controller, and very little in that link matches up to what I am seeing in the Controller interface.

All I really want is the core switch to handle the L3 routing of my VLANs and the router to handle all of the internet traffic.

Before I simplified to the Omada system, I used OSPF between my Cisco 45066E and my Ubiquity Router.  Is something like that an option?  My network is changing quite often (we are a softare company that creates software that runs over the network), so creating static routes for each VLAN is going to be difficult to maintain.

  @Hank21 That URL redirects to https://www.tp-link.com/us/support/faq/4017/, which says it doesn't exist.  i tried removing the 'us', but it still just redirects again.

  @Hank21 So I think I found it at https://www.tp-link.com/en/support/faq/4017/, however, it references in the switch gateway config as the next hop to be 192.168.0.102.  Is this correct?  The switch IP address is 192.168.0.2, and .102 is never referenced other than in the switch gateway config.  Please confirm, and if it is correct, why?  I will need to adapt this to my own topology, so knowing why this is will help.

[EDIT].102 is referenced on the gateway next hop, not switch.  apologies for the error in my text above.  But the question still stands.