Skip to content

Adopt cooperative Windows harness execution #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
drafael merged 1 commit into from
Aug 31, 2026
Merged

Adopt cooperative Windows harness execution #20

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
109 changes: 0 additions & 109 deletions .github/workflows/autopilot-windows-helper.yml
View file
Open in desktop

This file was deleted.

2 changes: 1 addition & 1 deletion skills/autopilot/docs/2026-08-30-continuity-evidence-implementation-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -556,7 +556,7 @@ Validate modified Markdown links and balanced fences with the repository's estab

### Windows validation evidence

GitHub Actions run [33335872725](https://github.com/drafael/coding-harness/actions/runs/33335872725) passed Node 24 typecheck, lint, format check, the 162-test suite, and deterministic generated-artifact checks on both `ubuntu-latest` and `windows-latest` at merge commit `b511331`. The Windows runs exposed and then verified fixes for unsupported directory fsync, direct governed-hook execution, portable fake CLI fixtures, descendant process-tree cancellation, CRLF-neutral restack assertions, and bounded Git worktree administration paths. Windows writes still do not claim POSIX-equivalent sudden-power-loss directory metadata durability because Node.js cannot fsync a Windows directory handle. A source-controlled x64 Job Object helper, manifest verification, and a pinned Windows bootstrap workflow now define the restart boundary, but the capability remains disabled until that workflow produces a reproducible artifact, real fault-injection tests pass, and the reviewed binary and digest are checked into the package.
GitHub Actions run [33335872725](https://github.com/drafael/coding-harness/actions/runs/33335872725) passed Node 24 typecheck, lint, format check, the 162-test suite, and deterministic generated-artifact checks on both `ubuntu-latest` and `windows-latest` at merge commit `b511331`. The Windows runs exposed and then verified fixes for unsupported directory fsync, direct governed-hook execution, portable fake CLI fixtures, descendant process-tree cancellation, CRLF-neutral restack assertions, and bounded Git worktree administration paths. Windows writes still do not claim POSIX-equivalent sudden-power-loss directory metadata durability because Node.js cannot fsync a Windows directory handle. Later protected run [33353702353](https://github.com/drafael/coding-harness/actions/runs/33353702353) passed the full 179-test partition and produced a reviewed reproducible x64 Job Object artifact. [ADR 0002](adr/0002-use-cooperative-harness-execution-on-windows.md) records the decision not to package that artifact because of the native executable's antivirus and application-reputation surface. Windows restart reattachment therefore remains disabled while the cooperative harness execution plan is implemented.

### Direct Pi validation evidence

Expand Down
Loading