This wiki documents the shared CI architecture centered on jai/trips-ci and downstream caller workflows.

The code-review system now uses 3 reusable workflows in jai/trips-ci:

• code-review-welcome.yaml
• code-review-full.yaml (includes internal ready-automation job)
• code-review-respond.yaml

• Callers are the router (.github/workflows/code-review.yaml in each product repo)
• trips-ci is now reusable-workflow provider only (no middle router)
• post-review automation was folded into code-review-full.yaml to avoid brittle caller-side chaining

Caller-side chaining across multiple reusable workflows caused startup/runtime fragility (startup_failure class issues). Folding ready automation into full removes cross-workflow output plumbing in caller repos.

Caller workflow template source of truth:

• scripts/generate-caller-workflows.sh

See:

• Code-Review Workflow Deep Dive
• Code-Review Test Plan

• Shared repo: jai/trips-ci
  • reusable workflows + common CI primitives
• Downstream repos: callers own event routing and invoke reusable workflows from trips-ci