Fix Alibaba Personal/Solo workspace authorization - #351
Conversation
|
Thermo-nuclear review: FIX requested before approval. Behavior is correct and focused, no file crosses the 1k threshold because mod.rs was already >1k on main, and the shared nested-error parser is in the canonical Alibaba layer. One structural issue remains: sec_token is threaded through multiple already parameter-heavy Personal helper signatures. Upstream steipete#2533 intentionally collapsed the same request state into a Personal API context. I am refactoring that internal orchestration now so the change does not add argument plumbing/spaghetti while keeping the pure form builder directly testable. No other blocker found. |
|
Thermo-nuclear follow-up: PASS. The one structural finding is resolved by PersonalApiContext, which removes repeated request-state argument plumbing while preserving the pure form builder for direct regression coverage. Final checks on head 9f91619: hosted Rust format PASS, workspace Clippy PASS, full workspace Rust tests PASS, frontend tests PASS, frontend typecheck/build PASS, interaction guards PASS. Local focused Alibaba suite remains 13/13 PASS. No remaining thermo blocker found. |
Fixes #350 by porting the applicable behavior from upstream CodexBar steipete#2533 into the Windows Rust provider.
Ported
Skipped
Deferred
Verification