Release v2026.5.62#119
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… case-insensitivity fix)
On case-insensitive filesystems (macOS), existsSync('verify-T9003.mjs') returns
true even when the file is named 'verify-t9003.mjs', causing the function to
return the wrong path. Real scripts use lowercase by convention (verify-t9230.mjs),
so put lowercase candidates first in the search order.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…owercase convention resolveVerifierScript now checks lowercase candidates first, matching the real-world script naming convention (verify-t9232.mjs, not verify-T9232.mjs). Tests updated to create lowercase fixture files so they pass on case-insensitive macOS and case-sensitive Linux alike. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…identity
Adds a .mailmap at the repo root that remaps the three observed surface
variants of the polluted `test@example.com` identity to the project
owner's canonical GitHub identity:
Test <test@example.com>
test <test@example.com>
Drift Test <test@example.com>
-> kryptobaseddev <kryptobaseddev@users.noreply.github.com>
Display-only fix: git log, git blame, git shortlog, git check-mailmap,
and GitHub's contributor pages all honour this without touching the
underlying commit objects. Zero history rewrite, zero force-push, zero
broken evidence atoms (commit:<sha> stays valid because SHAs don't move).
Pairs with the two defensive layers already in main:
- vitest.setup.ts identity-pollution guard (14a25eb)
- .github/workflows/identity-pollution-check.yml CI gate (79cd832)
Legitimate fixture identities (cleo-test, CLEO Test, cleo-agent,
cleo-subagent, test@cleo.test, test@test.com) are intentionally left
unmapped — those are scoped fixture identities, not owner impersonation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v2026.5.62 (T9232)
Campaign 2026-05-11/12 — multi-agent infrastructure fixes and improvements.
What's included
Note
worker-omega initially reused v2026.5.61 (already published pre-session). This PR correctly ships v2026.5.62 as the canonical campaign release.
🤖 Generated with Claude Code