#3041 digitalocean codegen leaves an orphaned security_secret.ts model file after its endpoint left the spec

Problem

In swamp-extensions, model/digitalocean/extensions/models/security_secret.ts is still in the repository, but the /v2/security/secrets endpoint is no longer in the DigitalOcean OpenAPI spec. The generator no longer produces the file and manifest.yaml no longer lists it, so it is never regenerated and never published. Nothing removes it.

Found during swamp-club#3030: every regenerated model picked up the new sensitive meta except this file, whose ResourceSchema still has a plain secret field, because the generator never rewrites it. It is the only model file in the directory that the manifest does not list.

Expected

deno task generate:digitalocean deletes model files that the current run did not produce, or the stale file is removed once and the pipeline guards against leaving new ones behind.

Notes

Last touched by the regenerate commit 4b3399d3a (#85). Other providers may have the same gap.