← Priority list

Publish a UrlResolver release compatible with protocol 0.0.427

No published resolver through 0.0.680 implements the abstract GossipHandler method required by protocol 0.0.427. Update UrlResolver, test it against 0.0.427, and publish a compatible release before the ContainerNursery pin verification can continue.

hf-2026-07-30-publish-a-urlresolver-release-compatible-with-protocol-0-0-427

Edit handoff

Add dependency

Complete this handoff

Moves it out of every priority list and into ArchiveArea.

Handoff document

Markdown

Handoff: Publish a UrlResolver release compatible with protocol 0.0.427

Written: 2026-07-30 04:23 UTC

RE-VERIFY: This is a write-time snapshot. Before acting, re-read the live resolver index at https://kotlin.directory/foundation/url/resolver/, inspect the candidate resolver JAR with javap, and check UrlResolver main with GitHub. A newly published release supersedes the version list below.

Mission summary

ContainerNursery needs protocol 0.0.427 for 256 KiB request and response write chunking, but no published UrlResolver release can start with that protocol. Publish the lowest resolver release that implements the protocol's current GossipHandler contract and is tested against protocol 0.0.427.

What was found and done

  1. Protocol 0.0.427 declares GossipHandler.authenticatedInteractionSeverity(Object) as an abstract method returning PeerInteractionSeverity.
  2. ContainerNursery clean-cache tests with resolver 0.0.653, 0.0.655, 0.0.670, and 0.0.680 all compiled and then failed at facade startup with AbstractMethodError because foundation.url.resolver.UrlProtocol2 does not implement that method.
  3. Resolver JARs 0.0.671, 0.0.672, 0.0.673, and 0.0.677 through 0.0.680 were inspected with javap; none implements the method.
  4. No resolver newer than 0.0.680 was published at write time.
  5. UrlResolver main at https://github.com/CodexCoder21Organization/UrlResolver/commit/086927a2c8be309c61b2a5bff551e278ece6dec1 still pins protocol 0.0.409 and its UrlProtocol2 source lacks the method.

Relevant PRs / refs

| Item | Write-time state | |---|---| | ContainerNursery verification branch | Pushed at faa35a6f7d8745c245e187200b4689143fdb9f1b: https://github.com/CodexCoder21Organization/ContainerNursery/tree/verify/facade-fix-on-newer-protocol | | Verification findings | https://github.com/CodexCoder21Organization/ContainerNursery/blob/verify/facade-fix-on-newer-protocol/verification/facade-protocol-0427-findings.md | | UrlResolver main snapshot | https://github.com/CodexCoder21Organization/UrlResolver/commit/086927a2c8be309c61b2a5bff551e278ece6dec1 |

No pull request was opened for this blocker.

Next steps

  1. Re-verify the published resolver index and UrlResolver main first.
  2. Update UrlResolver to protocol 0.0.427.
  3. Implement GossipHandler.authenticatedInteractionSeverity(Object) on UrlProtocol2 with the intended interaction classification.
  4. Add end-to-end coverage that starts the resolver with protocol 0.0.427 and exercises facade RPC traffic.
  5. Run the UrlResolver suite, open an unmerged pull request, and take its CI green.
  6. After approval and merge, publish the resolver artifact.
  7. Confirm the published POM targets protocol 0.0.427 and the published JAR contains the required method.

Reusable / operational knowledge

  • Do not trust ContainerNursery's existing Kompile result cache after changing only dependency pins. A stale result reused protocol 0.0.397 after build.kts named 0.0.427. Use a fresh --cache-location and confirm JAR names in build output.
  • The full evidence is on the linked ContainerNursery verification branch.