Skip to content

fix(test): publish process markers atomically - #2455

Merged
chubes4 merged 2 commits into
mainfrom
fix/2454-atomic-process-markers
Sep 1, 2026
Merged

fix(test): publish process markers atomically#2455
chubes4 merged 2 commits into
mainfrom
fix/2454-atomic-process-markers

Conversation

@chubes4

@chubes4 chubes4 commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • publish the native interruption pause marker through a same-directory atomic rename
  • publish the archive-cache child readiness marker through the same complete-payload contract
  • prevent existence-based readers from observing empty or partial readiness payloads under concurrent smoke load

Evidence

Verification

  • npx tsx tests/playground-custom-archive-cache-process.test.ts
  • node tests/execute-native-agent-task-interruption.test.mjs
  • npm run build
  • npm run check (342 commands, concurrency 8)

Fixes #2454.

AI assistance

OpenAI GPT-5.6 Sol via OpenCode correlated the two release-blocking failures, identified the shared readiness-publication race, implemented the atomic marker protocol, and ran focused and full concurrent verification. Chris Huber directed and owns the work.

@chubes4
chubes4 merged commit 6d92681 into main Sep 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Concurrent smoke process markers are observable before writes complete

1 participant