GeezerVison

filename should not have spaces ideally please change to stackql_release_process.md

Renamed to docs/stackql_release_process.md in 625b20a.

Also updated the three references to the old name so nothing is left dangling: the header comments in mcp-packaging.yml and mcp-registry-publish.yml, and packaging/mcpb/CLAUDE.md.

Move this to robot

Done in 27f1c4d. The step is removed; the check is the robot scenario Sqlite Extension Functions Smoke Working in stackql_mocked_from_cmd_line.robot, which this job already runs via build.py --robot-test.

The scenario previously used a weaker aws_policy_equal comparison than this step did, so I moved the step's arguments (Version plus scalar-vs-array Resource) into the scenario so nothing is lost in the move. I ran the scenario's exact SQL against a CGO_ENABLED=0 build of this branch and the output matches the expected table.

move this to robot

Removed in 27f1c4d, with one thing to flag.

This job has no robot harness: no checkout and no Python, it only downloads the amd64 exe from winbuild and runs it under x64 emulation. So after this change the extension functions are no longer exercised under emulation. The same binary is covered by the robot scenario in winbuild.

If you want emulation coverage kept, the options are wiring a minimal robot run into this job, or keeping a workflow-level check in this job only. Let me know which you prefer and I will add it.

I also dropped the stale "cgo" wording from the comment just above, since this PR makes it incorrect.

move this to robot

Removed in 27f1c4d. linuxbuild does not run robot itself, but linuxtest needs it and runs the functional suite against this job's artifact, so the robot scenario Sqlite Extension Functions Smoke Working covers the linux amd64 binary there.

move this to robot

Removed in 27f1c4d. This job runs the functional suite in-job, so the robot scenario Sqlite Extension Functions Smoke Working covers the native linux arm64 binary.

move this to robot

Removed in 27f1c4d. This job runs the functional suite in-job, so the robot scenario Sqlite Extension Functions Smoke Working covers the darwin intel binary.

move this to robot

Removed in 27f1c4d, with the same flag as on the winarmsmoke thread.

This job builds and uploads the darwin arm64 binary but does not run robot, so after this change the extension functions are not exercised on darwin arm64. macOS coverage comes from macosbuild (intel).

Adding a full robot run here would take this job from roughly 3 minutes to something like the 30 minutes of the intel job, so I have not done that unprompted. Let me know if you want it.

This requires an assertion, at the conclusion of all shards, that every single test is run on each db and platform. Failure to verify both the total count and the presence of any expected line item must fail

Added in c645a2b as a new dockertestverify job. It needs dockertest, so it runs once every shard has concluded. dockermerge now needs it as well, so an image cannot be pushed past a failed verification.

How it works:

• Every robot-running dockertest leg uploads its output.xml. The unsharded sqlite leg uploads as shard 1 of 1, so both db backends go through the same check.
• The verifier lives in robot_shard.py next to the shard modifier. It parses test/robot/functional with no modifier applied to get the expected tests, then compares that as a multiset against the union of the shard reports for each (platform, db) group. The total count and each line item are checked independently.
• Failure to verify fails the job: an absent shard, an absent output.xml, inconsistent shard counts, a NOT RUN test, an expected group with no reports, or reports from a group that is not in the expected list. That last one means a new robot-running leg cannot be added without also being verified.

Testing: run locally against real output.xml files produced by dry-run shards (146 + 159 + 170 + 176 = 651, matching the unsharded 651). 13 mutated cases all exit 1. One of them renames a test so the count is still 651 but a line item is wrong, which shows the two checks are independent. actionlint 1.6.23 with shellcheck passes.

Scoping notes:

• The linux/arm64 docker leg is not an expected group because it has never run the robot suite. The matrix.platform == 'linux/amd64' condition is on main and predates this PR. Native linux arm64 robot coverage is in linuxarmbuild.
• Only the docker postgres leg is sharded. The other platforms run the suite unsharded through build.py --robot-test with no modifier, so there is nothing to reassemble there.
• The job skips verification under the same conditions where dockertest skips robot (fork and Dependabot PRs, build-elide refs, express tags). That condition is duplicated rather than shared. If the two drift, this job expects reports that do not exist and fails, which is the safe direction.

This has not run in CI yet. The artifact upload and download directory layout is the one part I could not exercise locally, so the first run on this push is the real test of it.