Goal: Queued CI/CD Adoption

Bring operations, common-module, and infrastructure onto the Queued CI/CD model — GitHub merge queue with ALLGREEN grouping, changelog entries authored in the PR body, and post-merge assembly into CHANGELOG.md — so that independent pull requests can land concurrently instead of serializing on a shared file.

Why now

Every merge to main in these repositories edits CHANGELOG.md. Measured over the 90 days to 2026-08-04:

Repository	First-parent commits on `main`	Of those, touching `CHANGELOG.md`
`operations`	50	50
`common-module`	29	29

The rate is 100%, and it is structural rather than incidental: CHANGELOG.md is where the version lives, so a release is an edit to that file. Two open PRs therefore conflict by construction, and the second one to merge always rebases. The queued model removes the conflict class outright — PRs never touch the file, so the queue can batch them.

Linear Tickets

PDEV-1408 — Adopt queued CI/CD and PR-body changelog in the Kotlin and IaC repositories: parent; records the structural obstacle and the chosen direction.
PDEV-1409 — Shared build actions: support merge_group and assembly-commit publishing: the enabler; blocks the three per-repository tickets.
PDEV-1410 — operations
PDEV-1411 — common-module
PDEV-1412 — infrastructure

Repositories

Repository	Role	Planned Changes
`qualify-build-action`	Shared build qualification	Classify `merge_group` as a test build; resolve the feature-build path
`gradle-build-pipeline-action`	Shared Gradle build + publish	Inherit the new qualification; retire the `operations` `@v1.3.7` pin
`common-module`	Pilot repository (library)	Gates, assembly, PR template, CODEOWNERS, ruleset, `cicd.yaml` rewiring
`operations`	Backend service	Same, plus the four-partition deploy chain
`infrastructure`	IaC	Same, adapted to `ci.yaml` and the `validate-release` check name
`documentation`	This project’s artifacts	Design, decision log, and updates to the Queued CI/CD specification
`workspace`	Agent rules	`rules/changelog.md` repo list — deferred; see Out of Scope

Scope

In scope. The five workflow groups of the queued model in each of the three repositories; the shared-action changes that make assembly-first ordering possible; the ruleset changes; the contributor documentation.

Out of scope. Changing what gets published, how it is versioned, or where it is deployed. The artifact coordinates, the semver semantics, and the deploy topology are all unchanged by this project — only the order of assembly and build moves.

Constraints

CHANGELOG.md is the version source for all three repositories and must stay so. The project changes who writes it and when, not what reads it.
Published artifact versions, tags, and GitHub Release shapes must be indistinguishable from today’s after the change.
infrastructure’s deploy matrix reaches production. Its cutover must follow two proven ones.
All four .github/clq/changemap.json files are already identical across documentation, operations, common-module, and infrastructure, so the version-bump semantics port unchanged.

Success Criteria

A PR that edits CHANGELOG.md is rejected in all three repositories unless it carries the manual-changelog label.
A PR without a valid ## CHANGELOG body section is rejected.
Two independent PRs land in a single ALLGREEN batch with no changelog conflict.
The version, tag, Docker image tag, Helm chart version, Maven coordinates, and GitHub Release produced by an assembled release match the pre-migration shape exactly.
operations’ dev → stage → demo → prod chain and infrastructure’s four-partition chain each fire once, in order.
arda-changelog-bot is the sole bypass actor on all three rulesets.

Reference Documents

Design — the adapted pipeline.
Decision Log — the five decisions and their rejected alternatives.
Queued CI/CD — the model being adopted.