Repository navigation
Description
GitLab becomes a parallel execution lane for t27 CI. GitHub stays the merge authority: a green GitLab result never authorizes a merge by itself. This issue is piece 1 of the owner's order of 2026-11-15 (GITLAB_PARALLEL_LANE_TRIGIT_INTEGRATION_PLANNED): the contract as pure t27 functions with tests, no I/O, no network, no pipeline file.
Reuses, never copies: specs/ci/runner_policy.t27 (trigger trust), specs/tri/lab/dispatch.t27 (sha check), specs/lab/job_kind.t27 (gate codes), specs/queen/agent_registry.t27 (domain code of letter G, T27G, slug governance).
Out of scope: any .gitlab-ci.yml or other hand-written non-t27 file (a pipeline file must later be generated from this spec), any new tri subcommand arm, the trigit event publishing itself (next piece), runner provisioning (owner's side).
Boundary
- specs/ci/gitlab_lane.t27
User Scenarios
- Given a GitLab job is green and GitHub required checks are green when the owner has not accepted then merge_allowed is false.
- Given a job record lacks RUNNER_ID when it is submitted then it is refused.
- Given a (COMMIT, JOB_KIND) pipeline is already dispatched when a second dispatch arrives then it is refused.
- Given free disk is 7 GiB when a window build is dispatched then it is refused.
- Given a job fails when its outcome is read then a FIX_REQUIRED queue item is produced.
Requirements
- FR-001: merge_allowed MUST be independent of the GitLab result.
- FR-002: A job record MUST carry COMMIT, PIPELINE_ID, JOB_ID and RUNNER_ID, or be refused.
- FR-003: Dispatch MUST refuse a duplicate (COMMIT, JOB_KIND), a seal job without a changed or stale seal, a heavy job under 8 GiB free, and screenshots before renderer draft acceptance.
- FR-004: A spec path MUST map to exactly one of five shards.
- FR-005: A failed job MUST yield a FIX_REQUIRED item and a passed job MUST yield none.
- FR-006: Each job outcome MUST map to exactly one of ten named events.
- FR-007: The lane MUST refuse merge from CI, review approval, force-push, release tag, fork code with secrets, and a seal not produced by CI.
- FR-008: Every rule MUST be held by a test with a negative control (10 or more test blocks).
Success Criteria
- 10 or more test blocks in
specs/ci/gitlab_lane.t27, all passing in CI. - 1 file changed, checked with
git diff --stat origin/master.
Activity
ci: gitlab lane drops owner gate, adds pilot kinds, retry rule, agent…
ci: GitLab parallel lane contract (Refs #13907) (#13909)
gHashTag commentedon Nov 17, 2026
Spec created: specs/ci/gitlab_parallel_lane.t27 (typecheck OK, 1 test pass).
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Spec exists and passes typecheck + tests. M4 milestone complete.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.