Enhance CI robustness and test coverage

[avrabe]

Problem

After the successful rules_rust 0.65.0 upgrade, we've identified several areas where CI and testing can be improved:

Opportunities for Enhancement

1. Expanded test coverage - Some complex examples currently excluded from CI
2. Better error handling - Improve graceful degradation when optional features fail
3. Documentation updates - Update docs to reflect known limitations and workarounds
4. Platform compatibility - Ensure all features work consistently across macOS, Linux, Windows

Current State

• Core functionality: ✅ All working
• Integration tests: ✅ 6/6 passing
• Registry tests: ✅ 7/7 passing
• Basic examples: ✅ All building successfully
• CI smoke tests: ✅ Passing

Requirements for Enhancement

• Add more comprehensive integration tests for complex scenarios
• Improve error messages and user guidance
• Add Windows CI testing
• Create automated testing for known-working subset of examples
• Enhance documentation with troubleshooting guides

Priority

Low - Current functionality is stable, these are quality-of-life improvements

Related Issues

• Builds on Signing toolchain improvements needed #127 (Signing improvements)
• Builds on Improve Go component dependency resolution #128 (Go component improvements)
• Builds on WKG integration toolchain issues #129 (WKG integration improvements)

Context

This issue tracks general improvements after the successful 2.0.0 upgrade to official rules_rust 0.65.0.

[avrabe]

Progress in commit 64afac2: Added Windows CI testing (experimental, continue-on-error). Also added Bazel 9 compatibility documentation. Remaining items: expand test coverage for complex scenarios, add troubleshooting guides.

[avrabe]

Progress Update

Windows CI Testing Added ✅

Added experimental Windows CI testing to the CI workflow:

• Runs on windows-latest with continue-on-error: true
• Tests core targets: //examples/basic:hello_component, //rust/..., //providers/...
• Current status: 12/14 targets building successfully

The Windows test is marked experimental because some targets still fail due to:

• Path handling differences
• Platform-specific toolchain issues

This provides early detection of Windows compatibility regressions without blocking PRs.

Remaining Items

• Add more comprehensive integration tests for complex scenarios
• Improve error messages and user guidance
• Create automated testing for known-working subset of examples
• Enhance documentation with troubleshooting guides

The Windows CI checkbox can be checked off as the experimental test is now in place.

[avrabe]

Significant progress (2026-03-23)

CI is now 26/26 green on all platforms for the first time:

• Windows: Fixed LNK1181 via --output_base=D:\_b (MAX_PATH), fixed bash-vs-cmd in debug_windows.bzl
• Ubuntu/macOS: Fixed docs-site build (Node.js 20→24 for Astro 6)
• P2/P3 tests: Both WASI versions tested in CI via //test/p3:all
• STPA safety analysis: 26 artifacts with 100% coverage tracking supply chain risks

Remaining work for this issue:

• Version-removal detection in weekly CI auto-merge (STPA CC-002)
• Integration test for the unified extension

[avrabe]

Closing — CI is now 26/26 green on all platforms (Ubuntu, macOS, Windows). All major CI issues resolved:

• Windows LNK1181 (--output_base fix)
• docs-site Astro 6 (Node.js 24)
• Rolling release breakage (lazy loading)
• P2/P3 both tested in CI
• STPA CC-002 version-removal detection added to weekly CI