Append CI queue wake smoke marker to README.md
Intent: Force a new commit on the branch to wake or trigger a queue-based CI system. The marker includes a UTC timestamp so each wake event produces a unique, traceable diff that does not alter any functional content.
Affected files: README.md
@@ -196,3 +196,4 @@ Useful starting points for new contributors:
## License
[MIT](LICENSE)
+ci queue wake smoke 2026-03-20T17:02:28Z
A single line is appended after the existing [MIT](LICENSE) license reference at the bottom of README.md:
ci queue wake smoke 2026-03-20T17:02:28Z
Why this pattern exists
Some CI systems (e.g., Mergify merge queues, GitHub merge queues, or custom queue runners) require a fresh commit on a branch before they will pick it up for processing. When a previous queue run was cancelled or the branch fell out of the queue, pushing a trivial commit like this "wakes" the queue and re-enqueues the branch.
Key details
- No functional change — the marker sits outside any code or configuration block and does not affect build output.
- Timestamp provides uniqueness — the ISO-8601 timestamp (
2026-03-20T17:02:28Z) ensures the commit hash differs from any prior wake attempts, which is necessary for CI systems that de-duplicate by tree hash. - Branch naming convention — the branch name
ci-queue-fix-1774026139encodes a Unix-epoch identifier, linking this wake commit back to the specific queue event it is intended to remediate.