docs(adr-0035): correct the repo name and the tracking issue #61

Sammanfogat

supernaut sammanfogade 1 incheckning från docs/adr-0035-corrections in i main

2026-07-31 01:23:54 +00:00

supernaut kommenterad

2026-07-31 00:55:43 +00:00

Ägare

Two factual errors in ADR 0035 on main, both confirmed against bitborg-infra#226:

Field	On `main`	Correct
Extracted repo	`gitborg/reconciler`	`gitborg/gitborg-auth-reconciler`
Tracking issue	`bitborg-infra#202`	`bitborg-infra#226`

The repo genuinely exists under bitborg-auth-reconciler — that is what bitborg-infra pins images
from. And issue #226 states outright:

Supersedes the erroneous bitborg-infra#202 reference in ADR 0035 and the reconciler PRs — #202
is an unrelated merged PR. ADR 0035 (docs PR #48) and PR #221 are being corrected to point here.

So the correction was intended, but never reached main.

Why a fresh branch

The fix was originally written on the local adr-0035-extract-reconciler branch, which was never
merged. That branch is 47 commits behind main, so opening a PR from it would have merged far more
than the fix:

decisions/0036-signup-trial-and-downgrade.md          | 104 ------
decisions/0037-reconciler-event-driven-work-queue.md  | 180 ------
default.json                                          |  37 ---
renovate.json, package.json, pnpm-lock.yaml           | reverted

Deleting two shipped ADRs to correct a repo name is not a trade worth making, so the two-line change
was reapplied on a branch cut from current main. The stale branch should be deleted, not merged
— everything of value in it is now here.

Why it matters

ADR 0035's subject shipped: the container has been the sole reconciler since 2026-07-28 (bash removed,
#226 closed). An ADR that describes delivered infrastructure while naming a repository that does not
exist sends the next reader looking for gitborg/reconciler. The ISMS cites decisions/ as the
auditable decision trail for control A.8.32, so a wrong repo name and a wrong issue link are exactly
the kind of defect that trail cannot afford.

Two factual errors in ADR 0035 on `main`, both confirmed against bitborg-infra#226: | Field | On `main` | Correct | | --- | --- | --- | | Extracted repo | `gitborg/reconciler` | **`gitborg/gitborg-auth-reconciler`** | | Tracking issue | `bitborg-infra#202` | **`bitborg-infra#226`** | The repo genuinely exists under `bitborg-auth-reconciler` — that is what bitborg-infra pins images from. And issue #226 states outright: > Supersedes the erroneous `bitborg-infra#202` reference in ADR 0035 and the reconciler PRs — `#202` > is an unrelated merged PR. ADR 0035 (docs PR #48) and PR #221 are being corrected to point here. So the correction was *intended*, but never reached `main`. ## Why a fresh branch The fix was originally written on the local `adr-0035-extract-reconciler` branch, which was never merged. That branch is **47 commits behind main**, so opening a PR from it would have merged far more than the fix: ``` decisions/0036-signup-trial-and-downgrade.md | 104 ------ decisions/0037-reconciler-event-driven-work-queue.md | 180 ------ default.json | 37 --- renovate.json, package.json, pnpm-lock.yaml | reverted ``` Deleting two shipped ADRs to correct a repo name is not a trade worth making, so the two-line change was reapplied on a branch cut from current `main`. The stale branch should be **deleted, not merged** — everything of value in it is now here. ## Why it matters ADR 0035's subject shipped: the container has been the sole reconciler since 2026-07-28 (bash removed, #226 closed). An ADR that describes delivered infrastructure while naming a repository that does not exist sends the next reader looking for `gitborg/reconciler`. The ISMS cites `decisions/` as the auditable decision trail for control A.8.32, so a wrong repo name and a wrong issue link are exactly the kind of defect that trail cannot afford.

supernaut lade till 1 incheckning

2026-07-31 00:55:43 +00:00

docs(adr-0035): correct the repo name and the tracking issue

ci / ci (pull_request) Successful in 13s

Detaljer

1fa6b910bb

Two factual errors on main, both confirmed against gitborg-infra#226:

- The extracted repo is `gitborg/gitborg-auth-reconciler`, not `gitborg/reconciler`.
  The real repo exists under that name and its images are what gitborg-infra pins.
- It implements gitborg-infra#226, not #202. Issue #226 says outright that #202 is
  "an unrelated merged PR" and that ADR 0035 was to be corrected to point at it.

That correction was written on the stale `adr-0035-extract-reconciler` branch and
never landed: the branch is 47 commits behind, so merging it would also have
deleted ADRs 0036 and 0037 and reverted the renovate and package changes. Applied
the two-line fix on a fresh branch off main instead, leaving the stale branch to be
deleted rather than merged.

Matters because ADR 0035's subject shipped — the container is the sole reconciler
since 2026-07-28 — so the ADR describing it named a repo that does not exist.