Follow-up from PR #1049 review (inline comments on .tool-versions and .github/workflows/test.yml).
Current state after #1049:
- The Spin release-build job compiles the wasm32-wasip1 artifact but no CI workflow proves it boots;
scripts/smoke-spin.sh is manual-only.
spin is not pinned in .tool-versions, while every other runtime tool is, and the refresh evidence record notes the smoke ran with Spin 4.1.0, newer than EdgeZero's verified major-version range.
Work:
- Determine the EdgeZero-verified Spin version range and pick a pin.
- Add
spin <version> to .tool-versions and emit it from scripts/read-tool-versions.sh.
- Add
spin to the adapter-first-success-smokes matrix so CI runs scripts/smoke-spin.sh against the pinned CLI.
The gap is also recorded in docs/internal/audits/documentation-refresh-decisions.md under "Adapter smoke and logging decisions".
Follow-up from PR #1049 review (inline comments on
.tool-versionsand.github/workflows/test.yml).Current state after #1049:
scripts/smoke-spin.shis manual-only.spinis not pinned in.tool-versions, while every other runtime tool is, and the refresh evidence record notes the smoke ran with Spin 4.1.0, newer than EdgeZero's verified major-version range.Work:
spin <version>to.tool-versionsand emit it fromscripts/read-tool-versions.sh.spinto theadapter-first-success-smokesmatrix so CI runsscripts/smoke-spin.shagainst the pinned CLI.The gap is also recorded in
docs/internal/audits/documentation-refresh-decisions.mdunder "Adapter smoke and logging decisions".