Point the integrator at Celilo's merge-gate reference instead of leaving gate behavior undocumented in its guidance #1

New issue

Open

opened 2026-10-28 18:19:07 +00:00 by forgejo-admin · 0 comments

forgejo-admin commented 2026-10-28 18:19:07 +00:00

Owner

Copy link

The integrator's guidance (agents/integrator/guidance/role.md) interprets the merge gate's exit codes (the PASS / FAIL / VOID / PARTIAL table) but never links the Celilo page that explains how the gate decides what to run. When an integrator has to judge why a tier was selected, why a scope was widened, or why a run came back VOID or PARTIAL, it has no pointer to the canonical explanation and must reconstruct it from scripts/merge-gate.ts.

The guidance does not repeat that material today (checked 2026-10-28), so this is a missing link, not a duplication to remove.

Scope

• agents/integrator/guidance/role.md, the verdict table and the gate-reading steps around it.
• Celilo's canonical pages:
  • OpenRig integration gate
  • Tier selection and admission: workspace membership and dependency edges, combined scopes, operator environment variables, the runner's isolated checkout, and load independence.

Acceptance

• Where the guidance interprets a gate verdict, it links the two sections above for how the tier was chosen and what VOID or PARTIAL means.
• The guidance states no tier or admission rule itself; it defers to the Celilo page, so the two cannot drift.

Related

• celilo/celilo#1544 (host-suite coverage across runners)

The integrator's guidance (`agents/integrator/guidance/role.md`) interprets the merge gate's exit codes (the PASS / FAIL / VOID / PARTIAL table) but never links the Celilo page that explains how the gate decides what to run. When an integrator has to judge why a tier was selected, why a scope was widened, or why a run came back VOID or PARTIAL, it has no pointer to the canonical explanation and must reconstruct it from `scripts/merge-gate.ts`. The guidance does not repeat that material today (checked 2026-10-28), so this is a missing link, not a duplication to remove. ## Scope - `agents/integrator/guidance/role.md`, the verdict table and the gate-reading steps around it. - Celilo's canonical pages: - [OpenRig integration gate](https://git.celilo.computer/celilo/celilo/src/branch/main/reference/repository-testing.md#openrig-integration-gate) - [Tier selection and admission](https://git.celilo.computer/celilo/celilo/src/branch/main/reference/repository-testing.md#tier-selection-and-admission): workspace membership and dependency edges, combined scopes, operator environment variables, the runner's isolated checkout, and load independence. ## Acceptance - [ ] Where the guidance interprets a gate verdict, it links the two sections above for how the tier was chosen and what VOID or PARTIAL means. - [ ] The guidance states no tier or admission rule itself; it defers to the Celilo page, so the two cannot drift. ## Related - celilo/celilo#1544 (host-suite coverage across runners)

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

metrics

docs/tasks-slice-8

docs/inbox-rank-full-id

docs/reviewer-seat-reconciliation

docs/tasks-slice-7

docs/jev-project-into-rig

design/reconcile-migration-contract

retool

baseline

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

celilo/rig#1

No description provided.