PWSS Libraries Update & Backend Alignment

[pwgit-create]

---

PWSS Libraries Update & Backend Alignment

Overview

This PR updates selected PWSS library dependencies to their latest stable patch versions and applies those updates to the File-Integrity Scanner backend. The goal is to improve stability, maintain compatibility with the current Spring Boot ecosystem, and ensure documentation accurately reflects the updated versions.

All changes are patch-level only and are not expected to introduce any breaking behavior.

---

PWSS Libraries Affected

The following private PWSS libraries were updated to bump their JUnit and Logback versions:

1. PWSS-DirectoryNav
   aka directory_nav

2. PWSS-FileQuarantine
   aka file-quarantine

3. literate-octo-guacamole
   aka algorithm-hash-extraction

These libraries now align on the same updated testing and logging stack.

---

Dependency Updates

Logging

Upgrade logback-classic from 1.5.23 → 1.5.26

This update includes multiple bug fixes and internal improvements, such as:

• Improved modularity and internal optimizations
• Better handling of fat/shaded JARs
• Fixes in composite converters and exception handling
• Removal of unused dependencies
• General performance and reliability improvements

No functional or breaking changes are expected.

Release notes:
https://logback.qos.ch/news.html

---

Testing

Upgrade junit-jupiter-api from 6.0.1 → 6.0.2

This is a patch-level release that provides minor fixes and improvements while remaining fully backward compatible. No test behavior changes are expected.

Release notes:
https://repo1.maven.org/maven2/org/junit/jupiter/junit-jupiter-api/6.0.2/

---

Backend Updates

• Applied the updated PWSS library versions to the File-Integrity Scanner backend
• Verified that existing functionality continues to work as expected
• No obsolete exclusions or temporary workarounds were required after the upgrade

---

Documentation

• Updated Java/Javadoc documentation to reflect the new library versions
• Ensured configuration and dependency references are consistent with the upgraded stack

---

Notes on Library Visibility

The PWSS libraries are intentionally kept private, solely for the purpose of protecting the license key mechanism.

Making these libraries public would significantly lower the barrier for bypassing or overriding the license key security system. While such circumvention may still be technically possible (and is not recommended), keeping the libraries private provides an important additional layer of protection.

To maintain transparency:

• Complete JavaDoc documentation for all PWSS libraries is publicly available
• Screen-sharing walkthroughs of the full source code are offered on request for anyone who would like to review the implementation before using the libraries

---

Verification

• Application builds successfully with updated dependencies
• File-Integrity Scanner backend runs without regressions
• No breaking changes observed in existing functionality

---

[lilstiffy]

Great! 💯 🥇