jared/cc-os

Watch

Fork 0

os-sdlc: amend ADR-0112 lint-retry text to match shipped retries: 0 #348

New issue

Closed

opened 2026-08-11 22:12:47 +00:00 by jared · 2 comments

jared commented

2026-08-11 22:12:47 +00:00

Owner

Context

ADR-0112 says lint retries default to "~10"; plugins/os-sdlc/maps/default.yaml:47 ships retries: 0. The 0 was a deliberate in-pipeline review round-3 change during #341 — the lint gate runs the same in-process rubocop with no agent in between retries, so 10 identical attempts cannot produce a different result. The post-#341 spec review flagged the mismatch: either the ADR text or the map is wrong, and right now the ADR misdescribes shipped behavior.

Correct approach

The map is right; the ADR text is stale. Amend ADR-0112 via /os-adr:create-style amendment convention (an amendment note in the existing ADR, not a new ADR — this is a parameter correction, not a reversed decision): state that gate rows with no agent between attempts (automated rows) default to retries: 0 because identical deterministic re-runs cannot change outcome, and that the original "~10" presumed an agent-mediated fix loop, which the lint row does not have in the default map. If a future map routes lint failures through a fixer agent (on_failure.route to an agent row), a nonzero cap becomes meaningful — the amendment should say the cap belongs to the map author, per map.

Scope

IN: text amendment to docs/adr/0112-*.md only; regenerate the ADR index if the tooling requires it.
OUT: any code or map change; retry semantics.

Acceptance criteria

ADR-0112 no longer states "~10" for lint unqualified; it documents the retries: 0 rationale and the agent-mediated exception.
Amendment carries today's absolute date and does not rewrite the original decision text (append-style amendment, matching the existing ADR amendment convention in docs/adr/).
No other file changed.

## Context ADR-0112 says lint retries default to "~10"; `plugins/os-sdlc/maps/default.yaml:47` ships `retries: 0`. The 0 was a deliberate in-pipeline review round-3 change during #341 — the lint gate runs the same in-process rubocop with no agent in between retries, so 10 identical attempts cannot produce a different result. The post-#341 spec review flagged the mismatch: either the ADR text or the map is wrong, and right now the ADR misdescribes shipped behavior. ## Correct approach The map is right; the ADR text is stale. Amend ADR-0112 via `/os-adr:create`-style amendment convention (an amendment note in the existing ADR, not a new ADR — this is a parameter correction, not a reversed decision): state that gate rows with no agent between attempts (automated rows) default to `retries: 0` because identical deterministic re-runs cannot change outcome, and that the original "~10" presumed an agent-mediated fix loop, which the lint row does not have in the default map. If a future map routes lint failures through a fixer agent (`on_failure.route` to an agent row), a nonzero cap becomes meaningful — the amendment should say the cap belongs to the map author, per map. ## Scope - IN: text amendment to docs/adr/0112-*.md only; regenerate the ADR index if the tooling requires it. - OUT: any code or map change; retry semantics. ## Acceptance criteria 1. ADR-0112 no longer states "~10" for lint unqualified; it documents the retries: 0 rationale and the agent-mediated exception. 2. Amendment carries today's absolute date and does not rewrite the original decision text (append-style amendment, matching the existing ADR amendment convention in docs/adr/). 3. No other file changed.

jared added the

label

2026-08-11 22:12:47 +00:00

jared commented

2026-08-11 23:16:21 +00:00

Author

Owner

Shipped in b6f55fe: ADR-0112 amended (2026-08-11) — agentless automated rows default retries: 0; ~10 presumed an agent-mediated fix loop.

Shipped in b6f55fe: ADR-0112 amended (2026-08-11) — agentless automated rows default retries: 0; ~10 presumed an agent-mediated fix loop.

jared commented

2026-08-12 14:24:21 +00:00

Author

Owner

Resolution

Done: Amended ADR-0112 with date 2026-08-11: agentless automated rows (no agent between retries) default retries: 0; original ~10 presumed an agent-mediated fix loop which lint gate lacks.

Evidence: b6f55fe

Follow-ups: none

Approved-by: jared

## Resolution **Done:** Amended ADR-0112 with date 2026-08-11: agentless automated rows (no agent between retries) default retries: 0; original ~10 presumed an agent-mediated fix loop which lint gate lacks. **Evidence:** b6f55fe **Follow-ups:** none Approved-by: jared

jared closed this issue

2026-08-12 14:24:21 +00:00

jared referenced this issue from a commit

2026-08-13 15:08:12 +00:00

docs(adr): amend 0112 — lint retries: 0 rationale for agentless automated rows (#348)

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

jared/cc-os#348

No description provided.

Rows
Columns