docs: record the gate-expansion decisions in an ADR #589

New issue

Open

opened 2026-09-22 17:11:17 +00:00 by hexajon · 0 comments

hexajon commented

2026-09-22 17:11:17 +00:00

Owner

Context

The gate expansion made several decisions worth recording as one ADR, written
as-implemented.

What

Write one ADR. A working title is "Gate expansion: additive linting,
formatting, and vulnerability checks". Cover:

Why golangci-lint is the runner for the four linters (one type-checked pass)
while their standalone binaries stay installed.
Why the revive ruleset excludes the comment-style classes.
Why osv-scanner is kept alongside govulncheck: ecosystem coverage, since it
caught the npm harness vulnerabilities.
Why nancy is credential-gated rather than dropped: the 401 evidence, and that
fork CI cannot hold secrets (per ADR 0035).
gofumpt adoption and the deliberate format-last sequencing.

Follow the house ADR rules (verified against ADR 0037): required front matter
(status, date, decision-makers), the three required MADR sections in order, and
an index row appended to docs/decisions/README.md. Create it with
madtea adr new, then validate with madtea adr check. Cite this tracking
issue in the record per the check rules.

Acceptance

madtea adr check returns OK, with the record count incremented by one and
the index row present and matching.

## Context The gate expansion made several decisions worth recording as one ADR, written as-implemented. ## What Write one ADR. A working title is "Gate expansion: additive linting, formatting, and vulnerability checks". Cover: - Why golangci-lint is the runner for the four linters (one type-checked pass) while their standalone binaries stay installed. - Why the revive ruleset excludes the comment-style classes. - Why osv-scanner is kept alongside govulncheck: ecosystem coverage, since it caught the npm harness vulnerabilities. - Why nancy is credential-gated rather than dropped: the 401 evidence, and that fork CI cannot hold secrets (per ADR 0035). - gofumpt adoption and the deliberate format-last sequencing. Follow the house ADR rules (verified against ADR 0037): required front matter (status, date, decision-makers), the three required MADR sections in order, and an index row appended to `docs/decisions/README.md`. Create it with `madtea adr new`, then validate with `madtea adr check`. Cite this tracking issue in the record per the check rules. ## Acceptance - `madtea adr check` returns OK, with the record count incremented by one and the index row present and matching.

hexajon added the

documentation

label

2026-09-22 17:11:17 +00:00

No milestone

No project

No assignees

1 participant

Notifications

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

sixfold-space/madtea#589

No description provided.

Rows
Columns