ci(template-delivery-e2e): run on registry.go (the reconcile trigger) #3003
Reference in New Issue
Block a user
Delete Branch "ci/template-delivery-e2e-include-registry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds
workspace-server/internal/handlers/registry.goto thetemplate-delivery-e2epath filter (bothpushandpull_request).The post-online declared-plugin reconcile (RFC#2843 #32) fires from the heartbeat handler in registry.go, but registry.go was absent from this gate's path filter — so the exact change class that fixes (or could regress) "reconcile never fires" did not trigger its own CI mirror. Companion to PR #3002 (the reconcile-trigger fix), which is exactly such a change.
Touches the reserved
.gitea/workflows/path, so reserved-path-review applies (distinct non-author approver + merger). Kept separate from #3002 so the root-cause code fix isn't gated on the reserved-path dance.Root-cause not symptom
Root-cause: the
template-delivery-e2egate's path filter omittedregistry.go, the file that owns the reconcile trigger — so a change to the trigger logic (e.g. #3002) would not exercise its own integration mirror. This adds the file to the filter; it is the gap, not a symptom.No backwards-compat shim / dead code added
No shim, no dead code. A two-line additive change to an existing workflow's
pathslists (push + pull_request). Nothing removed, no compat layer.Comprehensive testing performed
CI-config-only change. Correctness is self-evidencing: the gate itself runs on this PR. All five branch-protection-required contexts (CI / all-required, E2E API Smoke, Handlers Postgres, E2E Peer Visibility, Secret scan) are green on the head. No application code touched, so no unit/integration surface to add.
Local-postgres E2E run
N/A — pure CI workflow path-filter change; no Go/DB code touched. Local-postgres E2E is unaffected and continues to pass on the head.
Staging-smoke verified or pending
N/A — no runtime/image change; this only widens which file diffs trigger the template-delivery-e2e CI mirror. Nothing to roll to staging.
Five-Axis review walked
Correctness (adds the precise file that owns the reconcile trigger), readability (mirrors the existing path-list entries), architecture (keeps the gate's path filter in sync with the code it guards), security (touches reserved
.gitea/workflows/→ reserved-path-review enforced, distinct non-author approver), performance (no runtime effect; only changes CI trigger scope).Memory consulted
Consulted:
reference_serving_e2e_gate,reference_cf_tunnel_drift_gate_is_code_drift(keep gate path-filters in sync with guarded code),feedback_no_such_thing_as_flakes,project_rfc2843_rollout_authorization.🤖 Generated with Claude Code
QA: CI path-filter add for registry.go; gate runs on this PR; required CI green. Approving.
Security: reserved .gitea/workflows/ change, additive path filter only, no token/secret surface. Distinct non-author approve. Approving.
/sop-ack comprehensive-testing verified — CI path-filter add (registry.go → template-delivery-e2e); required CI green on head.
/sop-ack local-postgres-e2e verified — CI path-filter add (registry.go → template-delivery-e2e); required CI green on head.
/sop-ack staging-smoke verified — CI path-filter add (registry.go → template-delivery-e2e); required CI green on head.
/sop-ack root-cause verified — CI path-filter add (registry.go → template-delivery-e2e); required CI green on head.
/sop-ack five-axis-review verified — CI path-filter add (registry.go → template-delivery-e2e); required CI green on head.
/sop-ack no-backwards-compat verified — CI path-filter add (registry.go → template-delivery-e2e); required CI green on head.
/sop-ack memory-consulted verified — CI path-filter add (registry.go → template-delivery-e2e); required CI green on head.
QA re-approve on rebased head; CI path-filter add. Approving.
Security re-approve on rebased head; reserved workflow path-filter only. Approving.