gate: each check states what it proves and what it needs, and the skip flags become derived #770

New issue

Open

opened 2026-10-14 20:15:36 +00:00 by hexajon · 0 comments

hexajon commented

2026-10-14 20:15:36 +00:00

Owner

What to build

Each check carries what it proves and what it needs (its environment), so the
gate output reads as a list of guarantees.
The negative skip flags (--no-forge, --no-conformance,
--skip-remote-issues) become derived from what a stage can run, not hand-set
names that hide the check.

Acceptance

The gate output names each check and what it proves.
A reader can tell from the gate what the forge test, the MCP schema
conformance check, and the issue-state check each do and need, without reading
the script body.
No stage is configured by a bare negative flag that hides the check; the stage
selects by what it can run.

Needs #769 (the scoped-target structure). Part of #767.

## What to build - Each check carries what it proves and what it needs (its environment), so the gate output reads as a list of guarantees. - The negative skip flags (`--no-forge`, `--no-conformance`, `--skip-remote-issues`) become derived from what a stage can run, not hand-set names that hide the check. ## Acceptance - The gate output names each check and what it proves. - A reader can tell from the gate what the forge test, the MCP schema conformance check, and the issue-state check each do and need, without reading the script body. - No stage is configured by a bare negative flag that hides the check; the stage selects by what it can run. Needs #769 (the scoped-target structure). Part of #767.

hexajon added a new dependency

2026-10-14 20:16:14 +00:00

#767 epic: the gate scopes to the change, runs heavy tests as their own stage, and reads as a list of guarantees

hexajon added a new dependency

2026-10-14 20:16:15 +00:00

#769 gate: split into scoped targets that fail closed when the diff exceeds their scope