You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working on the component-switch slice on top of the model-condition and platform benchmark changes. The candidate profile alone will receive explicit, validated switches; existing conflicting values require --force. I will record the effective switch sets, refuse incompatible candidate comparisons, and fail setup before a sweep when the requested configuration cannot pass a bounded readiness probe. Default behavior without switch flags stays unchanged.
The candidate component-switch implementation is ready in #404 (8481d91), stacked on #402 to keep the review diff bounded. It supports repeatable switches, safe/idempotent candidate patching, explicit force/dry-run behavior, composed-config verification and a bounded readiness turn. Reports and sealed arm descriptors retain actual switch facts, and comparisons reject different candidate sets with exit 2 while allowing the baseline's expected empty set.
All twenty benchmark suites passed locally. Ten dedicated checks cover dynamic/legacy config handling, the official host configuration merger, readiness failures, CLI rejection and the rendered panel. Current-head PR CI passed every executed platform and the Node floor: https://github.com/T-Auto/dsh-ops/actions/runs/40114967750.
#207 remains open for Desktop validation; successful headless setup is not presented as that receipt. No model-based token savings or automatic search for an optimal switch combination is claimed.
Activity
Haoming9527 commentedon Oct 24, 2026
Working on the component-switch slice on top of the model-condition and platform benchmark changes. The candidate profile alone will receive explicit, validated switches; existing conflicting values require
--force. I will record the effective switch sets, refuse incompatible candidate comparisons, and fail setup before a sweep when the requested configuration cannot pass a bounded readiness probe. Default behavior without switch flags stays unchanged.Haoming9527 commentedon Oct 24, 2026
The candidate component-switch implementation is ready in #404 (
8481d91), stacked on #402 to keep the review diff bounded. It supports repeatable switches, safe/idempotent candidate patching, explicit force/dry-run behavior, composed-config verification and a bounded readiness turn. Reports and sealed arm descriptors retain actual switch facts, and comparisons reject different candidate sets with exit 2 while allowing the baseline's expected empty set.All twenty benchmark suites passed locally. Ten dedicated checks cover dynamic/legacy config handling, the official host configuration merger, readiness failures, CLI rejection and the rendered panel. Current-head PR CI passed every executed platform and the Node floor: https://github.com/T-Auto/dsh-ops/actions/runs/40114967750.
#207 remains open for Desktop validation; successful headless setup is not presented as that receipt. No model-based token savings or automatic search for an optimal switch combination is claimed.