.addException(
                                new Exception("Build failed due to log statements with a higher severity than allowed. "
                                        + "Fix the logged issues or remove flag --fail-on-severity (-fos)."));
            }

            logResult(event.getSession());

            logStats(event.getSession());

            infoLine('-');
        }
    }

                logForbiddenAPIsOutput(forbiddenApisOutput);
                throw new IllegalStateException(
                    "All excluded classes seem to have no issues. This is sometimes an indication that the check silently failed"
                );
            }
            assertNoPointlessExclusions("are not missing", missingClassExcludes, missingClasses);

If the intention is to gather user feedback on an early prototype, then the experimental property should be used.
If the intention is to allow an issue reporter to get additional local diagnostics when running a build in their proprietary environment, then the internal property is sufficient.

Examples of properties that follow the naming rules:

        }
    }

    @Test
    public void test_mimetypePatternMatching() {
        // Test that MIME type patterns work correctly as regex
        // This verifies the fix for SVG thumbnail generation issue
        // where image/svg+xml was not matching due to unescaped + character

        // SVG MIME type - the + must be escaped in regex
        String svgMimetype = "image/svg+xml";

      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise

      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise

* der Decoder
* kodieren
* dekodieren

* die Exception
* werfen

* der Ausdruck
* die Anweisung

* das Frontend
* das Backend

* die GitHub-Diskussion
* das GitHub-Issue

* die Leistung
* die Leistungsoptimierung

* der Rückgabetyp
* der Rückgabewert

* die Sicherheit
* das Sicherheitsschema

* der Task
* der Hintergrundtask
* die Taskfunktion

      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise

      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise

            }

            // SECURITY WARNING: JWT signature validation is not implemented.
            // This is a critical security vulnerability. The ID token should be validated
            // to ensure it was issued by the expected OpenID Connect provider and has not been tampered with.
            // TODO: Implement JWT signature validation using the provider's public key

            final Map<String, Object> attributes = new HashMap<>();