Handoff: Finish hosted verification of the UrlResolver structured exception rebase

Written 2026-10-21 22:24 UTC.

RE-VERIFY: This is a write-time snapshot. Re-check https://github.com/CodexCoder21Organization/UrlResolver/pull/1116 with gh pr view <full URL> --json state,mergeStateStatus,statusCheckRollup,mergedAt,headRefOid, the listed Actions runs and git ls-remote before acting.

Design decisions in force

User requirements, 2026-10-21: “Bring https://github.com/CodexCoder21Organization/UrlResolver/pull/1116 up to date with current main and carry it to a landable, verified head (or show it is superseded).” “Keep the PR's existing WHY paragraph at the top of its description, unchanged in substance.” “No local builds or test runs (hosted shards only).” “PROHIBITED ... merging, enqueueing into the merge queue, gh pr merge, publishing artifacts ... deploying anything, restarting any service, changing any timeout, re-running CI to see whether a failure goes away.”

Acceptance: 129 PR-new scenarios three times each; the related family (1240 exact scripts); full suite once on the final source head with usual sorted [shard::32] partition (2463 scripts). Hosted jobs have unchanged40-minute deadlines, fail-fast:false, git installed before checkout and fetch-depth:0. Never weaken/delete/skip tests, lower iterations, raise budgets, add sleeps/polls or remove main files. Every non-green must be class(a)PR-owned with a proved repair, class(b)exact-main-owned with native baseline evidence, or class(c)zero-test infrastructure with at most one re-drive. That single infrastructure redrive was already consumed. PR branch must be pushed FIRST before WIP mirrors of the same source SHA. No lane notes in the PR source tree. End description and commits with the original Claude session footers, already present. Preserve the first647-character WHY exactly; saved in evidence branch.

Mission and remaining work

The owner wanted this idle PR raced toward landing. It is still needed, and rebased source is pushed, but the final-head gates have not completed. Do not call it landable, merge it, or assume the last build-only repair is proved. The90-minute lane time box prevents finishing long hosted jobs here. Collect the existing runs first; do not blindly retry.

What was found and done

1. Main ed50a6b1bfd096fba1fd272a4a7758eb4873cb6f lacks ServiceInvocationBoundary/RemoteExceptionContext and structured service-only attribution. Audited81new main commits,48overlapping paths (38behavior and10docs/build); all relevant patches and retained anchors are in the durable audit. Not superseded.
2. Squashed and rebased141old commits. Retained main's effect delivery worker, terminal stream cleanup, projection/observable ownership, provider admission, correlated relay diagnostics, deadlines and persistent/shared writes, adding origin records around current operations. Restored three old relay hooks lost in manual port after a hosted compilation failure. Main's extracted cache tests were not resurrected. README keeps all main content plus attribution docs.
3. Removed1806old test-pin churn changes:1784restored to main and22cache tests absent on main not resurrected. Diff now has129newtests plus6behavioral test edits. All129new scenario bodies match original after dependency annotations. Aligned protocol0.0.1429, libp2p snapshot-32, Observable0.3.25; clocks0.0.16/cache0.0.1 retained. Changed pins' POMs returned200. No publication. Resolver coordinate stays0.0.1328.
4. 8957c45's hosted selected attempt failed compilation during preparation: exactly96native failed records(time0),0passes,3receipts; missing relay hooks repaired in44b21. Its remaining requested tests have no receipt.
5. 44b21selected/family and full attempts each reached40-minute job deadlines, with20/20 and32/32artifacts collected respectively and0XMLreceipts. Logs have no compile-error strings but repeatedly successfully compile the identical Kotlin key (24MISS/24STORED/0HIT in one selected shard). No runtime scenario failure is asserted. Hypothesis/mechanism: original PR replaced main's artifact-level cached buildSimpleKotlinMavenArtifact with raw BuildKotlinJar/manual assembly, so each scenario dependency preparation rebuilds classes. Published build-kotlin-jvm0.0.33 helper bytecode confirms simpleCache wraps Kotlin compile+artifact construction.
6. Final source ca18d5e35b09a1533ee81df2ace157c6797a6cf8 restores that public cached helper for a thin internal Kotlin artifact while preserving the Java connection-entry shim and final combined jar/POM. Source was pushed PR-FIRST, then mirrored and verified. This build-only repair has dedicated code review but is NOT YET PROVED by a completed hosted build/receipt. Exact-main two-unchanged-case probe has2native records,2passes,0failures (effect/stream handler getImplementationJar); the44candidate comparison later completed with2native records,2passes,0failures; its same Kotlin key was recomputed twice.
7. Final selected/family and32fullshard workflows launched on explicit ca18source. No final XML artifacts yet as of22:21UTC. Final automatic bld-build is still in build step. A requested gh pr checks read at22:14UTC, more than2minutesafterpush, showed bld-build pending. Do not repeat it unnecessarily.
8. Remote service checks on44failed before upload: upload sessions0, attempts0, RECOVERING_LOCAL_STATE,0tests. One allowed dispatch re-drive was used; do not re-drive again. Direct enforced main rules show only bld-build required (ruleset11352029), contradicting the brief's remote-only required-check premise. Evidence retained. REST quota ran out once; waited until header reset21:41:46UTC before any retry. Respect the next reset if exhausted.
9. PR body patched at22:17 and updated with exact-main2/2; exact opening WHY retained, current conflicts/pins/pending counts/run links included, required footer retained. Condensed historical helper table into its existing evidence link to fit65536-character body limit. No main deletions or lane notes in PR source tree.

Relevant PRs and refs

No artifacts were published, nothing deployed, no service restarted, and no PR merged/enqueued in this session. Checked commands/history and current PR state. No worktrees or stashes carry unpushed source. Only one fresh clone was used. The initial rebase80e295push failed, and a shell mistakenly checkpointed that old source WIP-first; superseded by a new PR-FIRST source8957revision before gates. The mistake and evidence are in FINDINGS.

Run links and actual counts

Next steps

1. Re-verify PR/head/main/run state first; do not overwrite other work. Clone only into workspace, --depth300, configure clone-local git identity from last author. Read README. Follow user's hosted-only constraint; no local compiler/test.
2. Download final run artifacts with gh run download and parse runner-native XML using the evidence parser; each manifest must exactly match receipt file names, full expected counts and all three new-case receipts. Record first-attempt counts, distinguish preparation failures from executed scenario results, retain complete error text. Collect the remaining candidate44comparison result too.
3. Verify the cached-helper repair actually compiles and reuses preparation; if it fails, use exact error and public test path to repair (no budget changes), push PR-FIRST then mirror, and gate the new final head. A source change requires re-gating; never merely retry a code-test failure.
4. For any actual runtime failure, reproduce its exact scenario on current main hosted at the same baseline before labeling main-owned. The existing2/2mainprobe proves only those two unchanged cases, not all unexecuted family/full tests.
5. Update the rebase section in the PR body with actual native counts and links while keeping original WHY first and footer exact. Use gh api PATCH -F body=@file; gh pr edit is broken. Final body is currently~46kchars after historical-table condensation.
6. Throwaway refs wip/gha-run/rf3-1 throughrf3-5 were deleted after preserving their workflow files on the evidence branch. Re-check that cleanup succeeded. Branch deletion does not cancel already-running Actions; do not cancel sibling jobs merely because one fails. Re-check whether this lane already removed them at its final checkpoint. Evidence generator reconstructs the exact final workflows; source SHA and baseline are explicit.
7. Leave the PR open for owner approval. No merging, queueing, publishing, deployment or service restarts authorized. Update this handoff/report and release claim when finished or stopping.

Reusable operational knowledge

Evidence lives under rf3-evidence/ on the dedicated evidence branch, never the PR source tree. Local mandatory FINDINGS path was /tmp/claude-1000/-code/cab71c69-9604-400a-a7b5-cdb15e018076/scratchpad/lanes/out/rRF3-findings.md; it is ephemeral, so use durable copy. All workflows install git/curl/python before checkout, fetch-depth0, checkout source candidate, fetch/rebase main and assert candidate unchanged. A baseline advance must be resolved explicitly. Sorted full partition is files[shard::32]. Final workflow commit68a4f7a635bdbc5088eca06208928f02d87d437c has separately named selected/full YAML. Throwaway branch MUST start wip/gha-run/rf3-; other names flood automatic remote CI. No rg executable here; used Python/git fallback. gh pr checks is TSV, no --json, maxonce/minute. Do not use pgrep-f/pkill-f. Stop only explicitly identified local watchers. Coursier executable is /home/christian/bin/cs; handoff health returned {"status":"OK"}. Its deprecation warning is unrelated.

The paired probe completed on both sides: 2/2 native passes on main and 2/2 on44b21. Main compiled/assembled once per key;44recomputed its same Kotlin and merged-jar key twice (2MISS/2STORED/0HIT). This supports the preparation composition diagnosis; finalca18repair proof is still pending. All five throwaway refs were deleted and verified absent; no Actions job was cancelled. Workflow copies and native receipts are preserved on the evidence branch.