-
Notifications
You must be signed in to change notification settings - Fork 0
Run native macOS and Windows runtime smoke tests on hosted runners #59
Copy link
Copy link
Open
Labels
area:runtimeTerminal lifecycle, events, input, cancellation, and effectsTerminal lifecycle, events, input, cancellation, and effectspriority:p2Normal milestone priorityNormal milestone priorityrigor-upliftRepository hygiene, CI, release, or governance hardeningRepository hygiene, CI, release, or governance hardeningtype:verificationExecutable compatibility, testing or release verificationExecutable compatibility, testing or release verification
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area:runtimeTerminal lifecycle, events, input, cancellation, and effectsTerminal lifecycle, events, input, cancellation, and effectspriority:p2Normal milestone priorityNormal milestone priorityrigor-upliftRepository hygiene, CI, release, or governance hardeningRepository hygiene, CI, release, or governance hardeningtype:verificationExecutable compatibility, testing or release verificationExecutable compatibility, testing or release verification
Outcome
Synthetic persona: Erin — cross-platform CLI integrator. Job: Trust that terminal startup, cancellation and degraded output work on the actual OS where consumers run.
This is a repository-grounded improvement hypothesis from a synthetic workflow exercise, not validated customer demand.
Evidence
Baseline: 64b0d0d96954 / v1.0.0-rc.2.
Bounded scope
Add a bounded native hosted-runner matrix for public root-module runtime/capability smoke tests. Extend the workflow guard narrowly for the exact approved hosted runner labels, while preserving no self-hosted/reusable/local-composite escalation. Limit native jobs to root-module smoke packages, set explicit timeouts, avoid duplicating the full benchmark/adapter suite, and document expected runner-minute cost.
Acceptance checks
Compatibility and dependencies
Preserve the v1 root API and wire meanings. Additive tooling/docs or behavior-preserving validation; no root dependency or minimum-Go increase is implied.
Dependencies: #39
Milestone plan and shared release prerequisites: #38. Priority: P2. Required verification must preserve existing gates; completing this issue does not itself authorize a release.