Adopt

llms.txtlists every page for an agent

plunge stack adopt --json --stack dev        # classify, write nothing
plunge stack adopt --json --yes --stack dev  # adopt

Each object keeps its ID and gets a record. The next plunge up adds both labels to metadata.labels in place (Migrate).

Helm releases and YAML and Kustomize resources have no metadata of their own and stay unmarked. A provider setting hiding plunge- labels is refused by name.

Leaving

Back out with plunge stack export and a stock pulumi stack import.

Optional: hand this page to your coding agentThe steps work by hand too.

Follow https://intentius.io/plunge/kubernetes/adopt/. Run `plunge stack adopt --json --stack <stack>` without --yes and report the status and every refusal.
Never run `plunge up`, `plunge destroy` or `plunge stack adopt --yes`, approve or apply a saved plan, or merge; never edit or remove a plunge-stack or plunge-urn tag or label by hand.

plunge