The dashboard builds with Temurin 25 and carries a runtime jlinked from it, as ADR 0001 decides.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
werkrevisor: YELLOW / HUMAN_REVIEW for f5b12b0371f049836afd2f03e5ebf246aa58702d.
The result comment of werkrevisor holds the details.
werkrevisor: YELLOW / HUMAN_REVIEW for `f5b12b0371f049836afd2f03e5ebf246aa58702d`.
The result comment of werkrevisor holds the details.
<!-- werkrevisor-review:f5b12b0371f049836afd2f03e5ebf246aa58702d -->
Stale JDK reference, severity unknown, counted as medium (werkrevisor)
hint; Jev: real 0.87, severity 1.1 of 3
The PR moves the dashboard from JDK 21 to Temurin 25 and ticks the corresponding step under #ops.jdk, but the description of #ops.deps still claims "JDK 21 stays, as Werkator's." This line, added in PR#6, is now stale and contradicts the new state established under #ops.jdk in the same file. As the rest of the PR is about aligning the project's JDK claims with Temurin 25, this contradictory note should be updated or removed in the same change.
**Stale JDK reference**, severity unknown, counted as medium (werkrevisor)
hint; Jev: real 0.87, severity 1.1 of 3
The PR moves the dashboard from JDK 21 to Temurin 25 and ticks the corresponding step under `#ops.jdk`, but the description of `#ops.deps` still claims "JDK 21 stays, as Werkator's." This line, added in PR#6, is now stale and contradicts the new state established under `#ops.jdk` in the same file. As the rest of the PR is about aligning the project's JDK claims with Temurin 25, this contradictory note should be updated or removed in the same change.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The dashboard builds with Temurin 25 and carries a runtime jlinked from it, as ADR 0001 decides.
🤖 Generated with Claude Code
🟡 werkrevisor: YELLOW / HUMAN_REVIEW
Change kind:
mixed.Reasons
Findings
doc/werkregie.werkbaum:101, severity unknown, counted as medium, hint, as a line commentClassifier
4 of 4 units passed all questions (1 PR document(s)).
Usage: model `openrouter/minimax/minimax-m3`, LLM done, tokens counted before the call 12155, calls 1, tokens in 11673 / out 18946 (reasoning included in out), duration 169.6 s, cost 0.0262 USD (reported), classifier `jev-1.13.0` calls 4, tokens in 2733, cost 0.0001 USD, finding judge `jev-1.13.0` calls 1, tokens in 2541, cost 0.0001 USD, build file judge `jev-1.13.0` calls 4, tokens in 3328, cost 0.0001 USD, phases: path_judge 0.3 s, classifier 0.3 s, context 1.1 s, model_review 166.2 s, finding_judge 0.3 s, config: defaults + host + repository (.werkrevisor.toml at main801c910).Reviewed head `f5b12b0371f049836afd2f03e5ebf246aa58702d` against base `801c9109d1d79e4c937ceaf06b45dd2b4cae3ad5`, werkrevisor 0.32.7.
werkrevisor: YELLOW / HUMAN_REVIEW for
f5b12b0371f049836afd2f03e5ebf246aa58702d.The result comment of werkrevisor holds the details.
@@ -97,5 +97,5 @@device of its own, because many rooms are end-to-end encrypted and only adevice of the account can read them. It runs in the relay, so the devicekeys stay on the user's machine.The homeserver is configured; there is no default, and no real homeserverStale JDK reference, severity unknown, counted as medium (werkrevisor)
hint; Jev: real 0.87, severity 1.1 of 3
The PR moves the dashboard from JDK 21 to Temurin 25 and ticks the corresponding step under
#ops.jdk, but the description of#ops.depsstill claims "JDK 21 stays, as Werkator's." This line, added in PR#6, is now stale and contradicts the new state established under#ops.jdkin the same file. As the rest of the PR is about aligning the project's JDK claims with Temurin 25, this contradictory note should be updated or removed in the same change.Fixed in
273c9f7:#ops.depspoints to#ops.jdknow.Correction:
273c9f7reached this branch only after the merge, so it is not onmain. werkregie PR#26 carries the fix tomain.