build: bump to 1.0.0-beta.4 and migrate checkForUpdates to InstalledPluginRef

[bigpuritz]

Context

Upstream PR plugwerk/plugwerk#506 (closes plugwerk/plugwerk#504) is a breaking SPI change shipping in 1.0.0-beta.4:

PlugwerkUpdateChecker.checkForUpdates now takes List<InstalledPluginRef> instead of Map<String, String>. The wire-API is unchanged — only the SPI input shape changes.

Affected files in this repo

gh search code found two call sites:

• plugwerk-java-cli-example/plugwerk-java-cli-example-app/src/main/java/io/plugwerk/example/cli/command/UpdateCommand.java
• plugwerk-springboot-thymeleaf-example/src/main/java/io/plugwerk/example/webapp/controller/PluginInstalledController.java

Both call marketplace.updateChecker().checkForUpdates(installed) where installed is a Map<String, String>. After the bump the parameter must be a List<InstalledPluginRef>.

Migration

// before
Map<String, String> installed = pluginManager.getPlugins().stream()
    .collect(Collectors.toMap(p -> p.getPluginId(), p -> p.getDescriptor().getVersion()));
List<UpdateInfo> updates = marketplace.updateChecker().checkForUpdates(installed);

// after
import io.plugwerk.spi.model.InstalledPluginRef;

List<InstalledPluginRef> installed = pluginManager.getPlugins().stream()
    .map(p -> new InstalledPluginRef(p.getPluginId(), p.getDescriptor().getVersion()))
    .toList();
List<UpdateInfo> updates = marketplace.updateChecker().checkForUpdates(installed);

Tasks

• Bump the Plugwerk dependency version to 1.0.0-beta.4 (in whichever gradle/libs.versions.toml / pom.xml / equivalent the examples use)
• Migrate UpdateCommand.java (CLI example)
• Migrate PluginInstalledController.java (Spring Boot Thymeleaf example)
• Update any README snippets that still show the Map<String, String> shape (grep -RIn 'checkForUpdates' .)
• Verify both example projects build and run against the new beta

Why a separate issue

The breaking change must land in the main repo first (PR #506). Once 1.0.0-beta.4 is published, this repo can pick up the new artifact and migrate. Doing it in lockstep avoids a window where examples don't compile.

Source

Upstream: plugwerk/plugwerk#504 (issue), plugwerk/plugwerk#506 (PR).

[bigpuritz]

Closing — substantively done.

• Migrate UpdateCommand.java (CLI) — done in fix(sdk): adapt to PlugwerkUpdateChecker.checkForUpdates(List<InstalledPluginRef>) signature #43
• Migrate PluginInstalledController.java (Spring) — done in fix(sdk): adapt to PlugwerkUpdateChecker.checkForUpdates(List<InstalledPluginRef>) signature #43
• Update README snippets — grep -RIn 'checkForUpdates' . returns nothing in *.md / *.html / *.txt, no doc references need touching
• Verify both example projects build & run — main is green on the current SNAPSHOT post-fix(sdk): adapt to PlugwerkUpdateChecker.checkForUpdates(List<InstalledPluginRef>) signature #43 (CI runs dcc9de8 succeeded); the SNAPSHOT contains the new List<InstalledPluginRef> signature
• Bump the Plugwerk dependency to 1.0.0-beta.4 — intentionally not done

On the version pin: both examples stay on plugwerk = "1.0.0-SNAPSHOT" by convention so day-to-day development tests against the latest server build. Pinning to a fixed release (1.0.0-beta.4, 1.0.0-beta.5, …) is reserved for when an examples-repo release of the same name is cut. The migration the issue actually depended on (Task 1's "once beta.4 is published this repo can pick up the new artifact and migrate") was achieved transparently — Gradle resolves the SNAPSHOT, which already carries the new SPI.

Closing rather than partially leaving open because the only remaining checkbox is a deliberate non-action.