Formalising this future enhancement into an issue

Problem

When using Dynamic Client Registration (RFC 7591) for remote MCP servers, client credentials are not persisted across restarts. This causes:

1. New OAuth client registered on every thv run execution
2. Orphaned client registrations accumulate in OAuth providers
3. Risk of rate limiting from excessive registration requests

Acceptance Criteria

• DCR credentials (client_id, client_secret) persisted after registration
• DCR metadata (client_secret_expires_at, registration_access_token) stored
• Credentials reused across thv run restarts
• Expired credentials trigger automatic re-registration
• thv secret list shows persisted DCR secrets
• thv secret rm can remove persisted credentials
• Backward compatibility maintained for existing configs
• Documentation updated

References

• https://datatracker.ietf.org/doc/html/rfc7591