wsr

Java E2E worker progress

flowchart LR
    I[Recorded inputs] --> C[Checkpoint evidence]
    C --> L[Limits and pending work]
    L --> N[Next verified action]

Current checkpoint — November 5, 2026

Design documentation is merged on main at 031b583e60ce93b6b0af3b41afdec02b393aedff (PR #17). Refresh live state before work; historical branch names and dirty-document lists below describe their original sessions.

The selected source remains junit-team/junit-examples at 5bd6594a2336f1eff52527733ba28682a3215d83, subproject junit-jupiter-starter-maven. Last recorded prerequisite results are wrapper bootstrap and a partial 51-artifact dependency repository. Native Maven success, the intended assertion failure, JAR checks and WSR execution remain unverified. Liberica 25 / clean verify evidence below is an adapted reference; the Java walkthrough requests Temurin 21 / verify and requires separately matching evidence.

The owner stopped smoke-test implementation during the subsequent design discussion. This document does not resume that work. Before implementation resumes, reconcile the live owner instruction and external worker prompt with the current architecture, verify the required orchestrator model, and settle the next bounded behavior. Documentation-only approval does not resume the Java milestone.

After explicit resumption, verify existing fixture/artifact identities and qualify the chosen reference path before running workloads. Do not select another project or repeat completed source selection. Acquire live checkout ownership and preserve unrelated edits.

All target/wsr-tests paths below are ignored, machine-local evidence/preparation. They are not included in a clean clone. The historical Python scripts and their exact resume commands apply only if those files and their recorded hashes are present. A fresh checkout requires documented input reconstruction and verified source/tool acquisition before any execution claim.

Historical checkpoints

Dated entries below preserve observations and their original next-action suggestions. The current checkpoint above is authoritative for handoff; later evidence must be added with its own date.

Initial checkpoint — November 1, 2026

Historical initial next invocation

Inspect the live checkout and prerequisites, acquire exclusive ownership, then select and pin a small Maven/GHA reference project. Record its license, workflow/actions, toolchain requirements, and safe native reference environment. Prepare a bounded inspection/translation contract from the actual inputs; if unresolved, record the smallest decision needed before implementation. Do not start by installing/running arbitrary upstream build scripts on the host.

Per-run checkpoint fields

Record run time/branch/revision and dirty-work ownership; selected source/action/tool identities; current behavior and prerequisite decisions; exact commands; observed red/green/regression evidence; raw-result locations; changes made; blockers; next action. Keep implementation evidence indexed in docs/testing/coverage.md; this file tracks worker continuity, not duplicate coverage claims.

November 2 prerequisite checkpoint

Runtime metadata confirms GPT-6 Astra orchestration. Read-only reference review assigned to GPT-6.1 Sol agent java_reference_review with a self-contained handoff. No product implementation or native workload was run. Branch and owner edits remain preserved.

Docker CLI is present and selects desktop-linux, but docker info fails because its daemon socket is absent. No podman, colima, limactl or orb command was found on PATH. A usable isolated Linux reference environment is not yet established. Options: (A) start and qualify the existing Docker Desktop Linux environment with restricted mounts/credentials and resource limits (recommended); (B) supply an independently managed disposable Linux environment. Neither has been started or provisioned. Next action: finish the pinned Maven fixture review, then qualify the chosen Linux environment before any upstream script execution. No red/green claim.

Sol read-only review selected junit-team/junit-examples at 5bd6594a2336f1eff52527733ba28682a3215d83, subproject junit-jupiter-starter-maven. License EPL-2.0; wrapper Apache-2.0. Wrapper 3.3.4 downloads Maven 3.10.0 without an upstream distribution checksum. POM declares compiler release 17, JUnit 6.1.3, compiler plugin 3.16.0 and Surefire 3.6.1. Upstream build-all-examples.yml uses Liberica JDK25, checkout 3d3c42e5aac5ba805825da76410c181273ba90b1 and setup-java b843ebf9b913146b38da2eaa7aeddf76074ae1ad (both node24 declarations, not Bun proof). Review source at https://github.com/junit-team/junit-examples/tree/5bd6594a2336f1eff52527733ba28682a3215d83/junit-jupiter-starter-maven .

Next preparation must preserve licenses, independently verify Maven/JDK/image digests, and record an adapted manual-only workflow selecting only this Maven subproject, with credentials disabled and explicit cache omission. Upstream runs multiple ecosystems through Builder.java; this reduction is not unchanged upstream compatibility. Inside the qualified disposable Linux environment, run ./mvnw --batch-mode --no-transfer-progress -Dmaven.repo.local=/workspace/maven-repository clean verify. Expect five test invocations and the project JAR containing Calculator.class; all remain unexecuted. In a second disposable copy change the addsTwoNumbers expected result from 2 to 3, rerun the same command, and require a real JUnit assertion failure plus Surefire XML. No source has been downloaded or executed. Exact next action: qualify the reference-only Linux environment and pin its image/JDK/Maven identities before these commands.

November 2 manual preparation — downloaded inputs only

November 3 Linux reference prerequisite qualification

November 4 Maven input preparation — no workload execution

Validation for this slice: cargo xtask ci exit 0 (format, locked compilation/Clippy, workspace tests and strict docs); git diff --check passed. Logs/results remain in the ignored evidence root. This is repository regression evidence only; no Java behavioral red/green claim.

November 4 dependency preparation — bounded offline discovery