Are ignored path assertions listed/presented as if they're always found?

[atc0005]

Example from the README file:

C:\Users\Administrator>"C:\Program Files\NSClient++\scripts\custom\check_reboot.exe" --verbose --show-ignored
OK: Reboot not needed (assertions: 15 applied, 0 matched, 1 ignored)

Reboot not required

Assertions ignored:

  - Subkeys for key HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/WindowsUpdate/Services/Pending found
    subkey: 117cab2d-82b1-4b5a-a08c-4d62dbee7782


 | 'errors'=0;;;; 'evaluated_assertions'=15;;;; 'evaluated_file_assertions'=1;;;; 'evaluated_registry_assertions'=14;;;; 'ignored_assertions'=1;;;; 'matched_assertions'=0;;;; 'time'=1ms;;;;

Is this entry always listed? If so, the way it is presented implies that it was found, but ignored. I need to audit the behavior to make sure that it is only listed if it was found and ignored.

If in the ignore list but not matched, we should handle this differently. Perhaps display a list of ignore entries separately.

[atc0005]

Scratch notes from a temporary branch:

func DefaultRebootRequiredIgnoredPaths() []string {
	return []string{

		// FIXME: How are these assertions presented? Are they presented if they're always found?
		/*

				Assertions ignored:

				- Subkeys for key HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/WindowsUpdate/Services/Pending found
				subpath: 117cab2d-82b1-4b5a-a08c-4d62dbee7782


			This is shown on Windows systems where it is questionable that it was actually found.

		*/
		`SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending\117cab2d-82b1-4b5a-a08c-4d62dbee7782`,
	}
}