[onedr0p]

Overview

Collapses lint.yaml, tests.yaml and e2e.yaml into a single ci.yaml whose
jobs fan in to a Build Success job, so a ruleset can require branches to be up
to date before merge.

All six job bodies and their names are unchanged — only the trigger and the new
fan-in job are new.

Additional information

GitHub rejects strict_required_status_checks_policy unless at least one check
is required, and the individual jobs are unsafe to require: they are skipped for
release-please PRs, and a required check that never reports blocks the PR
permanently. Build Success runs on !cancelled(), so it reports whether its
dependencies pass or skip.

The pull request trigger drops paths-ignore for the same reason. Those filters
covered **.md and .release-please-manifest.json — the release-please PR
footprint that the per-job conditions from #320 already skip.

The e2e jobs keep their previous trigger scope through an event guard rather than
a separate file, since they build an image and stand up a kind cluster.

The cache-poisoning ignore follows the job into ci.yaml; the rationale is
unchanged, as the e2e image is loaded into kind and never pushed.

Still to confirm on this run: that Build Success reports green when its
dependencies are skipped, which is the case the fan-in exists for.

Requirements

• I have read and agree with the contributing guidelines
• AI usage disclosure: YES — the workflow changes and this description were
  written by an AI agent (Claude Code) under maintainer direction, as part of a
  wider branch-protection rollout. Static validation only: actionlint,
  zizmor, oxfmt, plus a scripted check that every job body is byte-identical
  to origin/main. Per the AI Usage Policy this exceeds assistive use and needs
  maintainer review before merge.

[greptile-apps]

Greptile Summary

Consolidates pull-request validation into one CI workflow.

• Moves the existing lint, test, and end-to-end job bodies into .github/workflows/ci.yaml.
• Adds the Build Success fan-in job as the single required status check.
• Preserves the prior e2e trigger scope with job-level event guards.
• Updates the Zizmor cache-poisoning exception to reference the consolidated workflow.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains within the scope of this follow-up review.

T-Rex Logs

What T-Rex did

• The contract validation captured the Before state with legacy workflows skipping all six release-please jobs and no Build Success fan-in.
• The contract validation captured the After state where six skipped dependency results make !cancelled() true, the failure step false, the pass-or-skipped step true, and Build Success is achieved.
• The static subset check verified YAML syntax passed and that migrated bodies are byte-identical to the originals.
• Artifacts were collected and inspected to support the results, including Python scripts and multiple logs.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
.github/workflows/ci.yaml	Consolidates six existing validation jobs and adds the Build Success fan-in check.
.github/workflows/e2e.yaml	Removes the standalone e2e workflow after its jobs were transferred to the consolidated workflow.
.github/workflows/lint.yaml	Removes the standalone lint workflow after its jobs were transferred to the consolidated workflow.
.github/workflows/tests.yaml	Removes the standalone test workflow after its jobs were transferred to the consolidated workflow.
.github/zizmor.yml	Retargets the existing cache-poisoning exclusion to ci.yaml.

_{Reviews (3): Last reviewed commit: "ci: gate pull requests on a single Build..." | Re-trigger Greptile}