Validate opt-in W&B and S3 telemetry publication on real targets #10

Vendor synchronization delivered on Windows — 2026-09-27

The vendor synchronization is merged in PR #20, merge 41bbb64a52e51c83feb548a8204c4c7ea0102b7e, verified SSH-signed source a58cb6443fc122c2a4920002667c81d0abf80670. The adapter/provider and two regression files exactly match the pinned Overwatch PR #1 source blobs. All five PR checks and all five post-merge main checks passed. Primary Layev main is clean and synced, divergence 0/0.

Windows validation: 16 installer/pinning cases passed, including an external-process rerun of the same 94 guard cases against temporary installer output; the 94 bundled guards also passed directly. Full Layev suite with verified pinned tokenizer snapshot: 790 passed, 11 explicit skips. Compilation, staged-source audit (161 files), pinned critical Ruff, lock and whitespace checks passed. Review fixed CRLF handling in the frozen test patch and updated historical cold-start test inputs to None; the four copied Overwatch blobs remain exact, and installer/revision/hash allowlist behavior is unchanged.

This satisfies only the additional vendor source-delivery gate below. The four original live W&B/S3 acceptance boxes remain unchecked, this issue remains OPEN, and Overwatch PR #1 remains draft pending its authenticated backend and live integration gates. No live remote publication or service deployment was performed.

Windows source repair delivery — 2026-09-27

The W&B publisher retry guard was merged in PR #19 at 9fa074d4926cac35ecaef16d62295acb3e5e922f; source commit b2e8ce6a3758a975fbcd4b2ab5765e0310d47c47 has a valid verified SSH signature. All five PR checks passed. On the primary Windows checkout, the full source suite passed 774/11 with the verified pinned tokenizer snapshot; the focused publication cases passed 22/22. The source audit, critical lint, compilation, lock check, CPU numerical audit and local resume/calibration exercise passed. This delivers source robustness only: it does not establish an authorized live W&B/S3 exchange, remote readback, request/rate accounting or cross-writer atomicity. All live acceptance boxes below remain unchecked; keep this issue OPEN.

The issue was briefly auto-closed during PR merge because the original PR description contained an issue-closing keyword in a negated sentence. That text was corrected and the issue was reopened immediately; the live acceptance evidence has not changed. The independent vendor synchronization candidate recorded below was not integrated by PR #19.

Independent installer-payload repair — 2026-09-27; source candidate, not delivered

The live Layev main readback is 6a99afde9df06be616a2ac75fb63e4e933bdfd96. Its bundled Overwatch payload still contains adapter blob 6df6d81c974a8b8db70bf0178d36d82859ef2e46 and provider blob 19c5d510130537a6153bcafdc1ec4cc56b6b6dab: the old malformed-cache-version and W&B pagination/response-ownership defects. The corresponding repairs already exist in the single draft Overwatch PR #1, at verified SSH-signed head 5a7e4418bcebee9c9ceccca4837e04f881d57ecf. This session observed that workstation delivery; it did not author or push it.

A seven-file uncommitted Layev synchronization candidate copies the two repaired modules and their two regression files byte-for-byte from that head, adds an LF/CRLF-aware pinning and installer-output test, its exact predecessor fixture diff, and provenance/limitation documentation. The repaired blobs are 99e5a25c1047f89750d7b12f6427307c7af7575d and 9c08ed6b759429043e4ff25859caa97bb47e0730. No new Overwatch implementation or duplicate integration PR is created. apply.py, both historical hash manifests, core-file transformations, accepted base revision, schemas, model code and publisher behavior are unchanged. Both old payload hashes were already allowed; the allowlist is not expanded.

Patch: layev-overwatch-vendor-sync.patch, SHA-256 5f131803a5dc808ba73ad3c67216f7172f02cc4457d6ca27eb55229625c44570, supplied in the accompanying execution-response bundle. It must not be confused with an already signed, pushed or merged change.

Measured in this isolated Linux/Python 3.13.5 runtime: the same 94 synthetic cache/transport regressions give 48 failed / 46 passed on the exact old payload and 94 passed / zero skipped on the candidate. The new installer/pinning suite gives 16 passed, including an external-process rerun of those same 94 cases against temporary installer output whose import paths are verified. Those repeated 94 cases are not additional distinct coverage. Added-file fixtures verify exact-predecessor upgrade, CRLF, backups, idempotence, preservation/refusal of unrelated and post-preflight edits, rollback, and unchanged revision/worktree refusal conditions. They deliberately exclude the eight core-file transformations and any actual primary-checkout/service acceptance.

Compilation, strict whitespace patch check/application, reverse check, all seven postimage comparisons and an overlapping-preimage refusal passed. The four recovered installer/manifest support files were matched to current Git blobs before use. Full repository/locked tests, Ruff, supported Overwatch backend, native weights/CUDA, genuine producer-to-visible-UI and live remote exchanges were not run for this candidate. The runtime is below Overwatch's supported minimum. Source checks do not satisfy the original live gates below.

Current Overwatch run 36332662610 has frontend success and backend failure. The decoded backend job 108657460948 confirms Python 3.13.12 setup succeeds, then missing_authorized_tscore_index_token exits 2 before locked installation/lint/tests. Keep PR #1 draft. The original remote gates still require explicitly authorized existing W&B run/S3 targets and usable credentials; none was obtained, inferred or called here.

Additional source-delivery gate

• Review the vendor synchronization against the actual current checkout, run the complete required suites, and deliver with the configured verified SSH signer, hosted checks and post-merge synchronization. Do not force the base-pinned installer onto the integration branch or reapply the already-pushed Overwatch repairs.

This session cannot access the Windows primary checkouts, running service or configured SSH signer. No source commit, push, merge, issue closure, run-identity change or WSL operation was performed. Related collector acceptance remains Overwatch #4 and #5; branch-policy enforcement remains Layev #8.

Gap and evidence

STAGE3_CORRECTNESS.md says opt-in W&B publishing updates an existing run and real publication remains unverified. Publishing tests use injected doubles for W&B and S3. This optional remote telemetry path is not required for local model inference, but it is part of the documented Overwatch transport design. Collector-side live validation is tracked in CompleteDotTech/Overwatch#5.

Acceptance

• With explicit authorization and disposable remote targets, publish a bounded, content-free telemetry snapshot to an existing W&B run and to S3; verify the observable config/summary/object readback and exact run identity.
• Confirm opt-in disabled mode makes no remote calls, W&B publication never creates/finishes an owned run, and a remote write failure increments monitoring warnings without aborting local optimization/checkpoint durability.
• Record remote SDK/version, snapshot hash, rate/size limits and credential-safe reproduction; do not place credentials or request/response content in artifacts.
• If authorized remote access is unavailable, leave this gate open and state the missing prerequisite rather than treating injected doubles as production proof.