zarf destroy doesn't run zarf-clean-* scripts anymore

[WeaponX314]

Environment

Device and OS: linux/amd64
App version: 0.32.3
Kubernetes distro being used: k3s
Other:

Steps to reproduce

1. Init k3s:

# zarf init --components k3s --confirm

2. After install, destroy it.

# zarf destroy --confirm

Expected result

Expect the cluster to be torn down + /opt/zarf/zarf-clean-* scripts to be run

Actual Result

Tear down begins to take place, but the zarf-clean script is not run

Visual Proof (screenshots, videos, text, etc)

Begin install, command use:

[root@node1 test]# zarf init --components k3s --confirm

NOTE Saving log file to /tmp/zarf-2024-01-29-16-52-12-334353752.log

... snip standard zarf k3s install continues, removing for clarity...

📦 ZARF-AGENT COMPONENT

✔ Pushed 1 images to the zarf registry
✔ Starting helm chart generation zarf-agent
✔ Processing helm chart raw-init-zarf-agent-zarf-agent:0.1.1706565132 from Zarf-generated helm chart
✔ Wait for "./zarf tools wait-for pod app=agent-hook Ready -n zarf --..." succeeded
✔ Zarf deployment complete

 Application          | Username  | Password                 | Connect               | Get-Creds Key
 Registry             | zarf-push | fOFO0rs9jAqpnm1nNigjilHF | zarf connect registry | registry
 Registry (read-only) | zarf-pull | s6GWr0AyJ!xZpkuICegdcgf2 | zarf connect registry | registry-readonly

[root@node1 test]# zarf destroy --confirm

NOTE Saving log file to /tmp/zarf-2024-01-29-17-00-04-622128922.log
✔ Waiting for cluster connection (30s timeout)

WARNING Unable to uninstall the chart
✔ Removing Zarf-installed charts
⠋ Deleting the zarf namespace from this cluster (6s)
✔ Removing zarf metadata & secrets from existing namespaces not managed by Zarf

[root@node1 test]#

Severity/Priority

Additional Context

Add any other context or screenshots about the technical debt here.

[WeaponX314]

Just adding my thoughts when looking at cmd/destroy.go:
I didn't poke too deeply, but it looked like it was following the "else" path. Somehow, it determined that it was NOT deployed by zarf and did not need to "burn it all down" as the comment suggests :).
Perhaps a state not being reported correctly?