Huanqi Cao be4a441ecd ci(windows): non-blocking via continue-on-error; drop the warning wrapper and the demo test ...

The ::warning:: wrapper kept the lane job green on failure — honest
about not gating merges, but a Windows regression was visible only as
an annotation buried in the run summary. GitHub has no yellow job
state, so the choice is green+annotation (too hidden) or a red X on a
non-required job (visible, still non-blocking). Take the red X:
job-level continue-on-error, plain 'Run gates' step, one less wrapper.
The step stays on the runner's native pwsh — never shell: bash — per
the MSYS-parent leak recorded in the windows-support RFC.

Also remove the temporary Windows-only failing demo test that
exercised the wrapper's annotation path (REVERT ME commit a496b9ae).

2026-07-15 18:11:03 +08:00

..

build-exe-for-python-sdk.yml

docs: align prose with runtime contracts

2026-07-14 16:21:41 +08:00

ci.yml

ci(windows): non-blocking via continue-on-error; drop the warning wrapper and the demo test

2026-07-15 18:11:03 +08:00

e2e.yml

Merge remote-tracking branch 'origin/master' into codex/trim-ai-prose

2026-07-14 12:34:14 +08:00

sandbox.yml

feat(sandbox): the confinement seam and the per-platform native runner chains

2026-07-10 15:43:02 +08:00