Pre-existing yamllint failures in workflow files (develop branch)

[wphillipmoore]

Summary

st-finalize-repo post-finalization validation fails on develop due to yamllint errors in the GitHub Actions workflow files. These are pre-existing failures left behind because validation was being run outside of st-docker-run — yamllint is a container-side tool and does not run correctly on the host.

These will be resolved automatically once the fleet-wide Docker caching fix lands (vergil-project/vergil-tooling#453) and validation is consistently run inside the container.

Failing files and errors

.github/workflows/ci.yml — 11 line-length errors (worst: line 12 at 434 chars, line 142 at 480 chars), plus missing document start "---" and truthy warnings on on: trigger.

.github/workflows/docs.yml — 1 line-length error (line 34, 142 chars), plus missing document start "---" and truthy warning.

.github/workflows/publish.yml — 3 line-length errors, plus missing document start "---" and truthy warning.

All five YAML workflow files have missing document start "---" and truthy warnings. The line-length errors (not warnings) are what cause validation to exit non-zero.

Root cause

Agents have been running st-validate-local directly on the host rather than via st-docker-run. Since yamllint is a container-side tool, these errors were never surfaced during PR validation cycles, allowing them to accumulate on develop undetected.

Ref vergil-project/vergil-tooling#453

Resolution

1. Once the Docker caching fix ships and st-docker-run works correctly for Python repos end-to-end, run st-finalize-repo — the yamllint errors will surface in the post-finalization validation output.
2. Fix each workflow file: add --- document start, shorten long lines, and address truthy warnings on on: triggers.
3. Confirm st-finalize-repo exits cleanly.