Repository navigation
Document milestone-led Windows parity gates - #837
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: f5e73246-b6e0-47b1-8580-032d1ff5bced Signed-off-by: Colin Neilens <coneilen@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: f5e73246-b6e0-47b1-8580-032d1ff5bced Signed-off-by: Colin Neilens <coneilen@microsoft.com>
coneilen
force-pushed
the
coneilen-milestone-policy-retrospective
branch
from
October 16, 2026 02:17
1ad0d78 to
c4e793e
Compare
coneilen
marked this pull request as ready for review
October 16, 2026 02:24
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
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.
Summary
Replace failure-count escalation for new Windows parity work with observable milestones, fresh-eyes handoffs and hard cost ceilings, while preserving historical stops. Reconcile environment traps and source/capture receipts without promoting any parity row or granting new execution.
Refs #764, #826, #833, #834.
Changes
Test plan
RED: git --no-pager grep -n -F '60 AI credits' badcf51 -- investigation\windows-parity-lane-kickoff.md -> exit 1; zero matching lines; STATIC immutable-document policy absence, not behavioural RED or test-first evidence
GREEN: git --no-pager grep -n -F '60 AI credits' -- investigation\windows-parity-lane-kickoff.md -> exit 0; one matching policy line; STATIC source presence only, not runtime evidence
REGRESSION: git --no-pager diff --check -> exit 0; static source-whitespace check only; separate git --no-pager diff --numstat returned exactly 3 changed Markdown paths, not runtime regression
The baseline comparison ran after documentation authoring. The expected no-match exit establishes only absence of the policy token in the fixed baseline; it is not a passing empty test query, product-behaviour failure or test-first contract. The working-tree comparison returned one actual matching line. Original console output and separate command/exit/count receipts are retained in the owning session's
files\m2-*artifacts.Direct matrix diff inspection confirms no canonical row or crosswalk edit.
git ls-files --eolreturned three paths: kickoff/matrix retain LF and the orchestration plan retains its committed CRLF.Not verified: product behaviour, native execution, compilation, GUI, screenshots, image privacy clearance, paired visual fidelity, daemon cleanup, runtime parity, and full Windows/macOS regression. Tracked changes are limited to the three documentation files; execution is limited to existing static Git checks and the existing PR-body gate, not product/native tests or images. No stopped owner or capture lease is resumed by this documentation.
At documentation freeze
2026-10-16T01:14:57.815Z, the coordinator-verified original CI for draft #836/head359a033ba749a9bcf2648ba8b96ee424ad8f398ais blocked: port run 38832369751, job 116753854474, failedVerifyValidationRunnerbefore Swift/real-zmx tests on amp-start.identitysharing violation in unchanged source already using an atomic pending-file move; holder/cause are unknown. Hardening run 38832369710 Windows 2025 job 116753830293 executed 59 cases, 57 passed/2 failed (target-nonzero Failure/release/EOF evidence missing; report gate refused the failed rehearsal), underlying cause unknown. Windows 2022 job 116753830273 logged 59/59/0, still stubbed/no-desktop and not real-zmx/GUI proof. These original failed results do not establish all nine required status contexts as passing, Ready/merge or a #834 lease. The operator separately authorized one diagnostic rerun of only failed jobs on unchanged359a033ba749a9bcf2648ba8b96ee424ad8f398a, in runs 38832369751 and 38832369710 (attempt 2), not a source fix or reset. This document grants no additional rerun, new fix owner, native/GUI/capture execution. Wrapper publication/head/merge remain unknown/pending, and no offscreen GREEN/PNG/vision has been accepted.Checklist
git commit -s) per the DCOmake test)make check)