Should editor consider code actions that are not listed in `codeActionKinds`?

Server can specify code actions that it supports through the codeActionProvider.codeActionKinds server capability. The spec says this about it:

	/**
	 * CodeActionKinds that this server may return.
	 *
	 * The list of kinds may be generic, such as `CodeActionKind.Refactor`,
	 * or the server may list out every specific kind they provide.
	 */
	codeActionKinds?: CodeActionKind[];

My questions are:

• Should editor only allow code actions specified in codeActionProvider.codeActionKinds to be run as part of the "code actions on save" functionality? I know that "Code actions on save" are not really part of the spec but maybe you have opinion as someone who works with the "reference implementation" (VSCode).
• Besides "code actions on save", what was the thinking behind introducing this capability? What practical effect should it have on the client from the LSP perspective?

Start by reviewing the codeActionProvider.codeActionKinds capability definition and the issue's questions about code actions on save. Compare the stated capability wording with the relevant LSP behavior and record a clear decision or clarification for clients; the issue is done when the expected client effect is documented.