docs: absorb implemented plans into ADRs, architecture and design docs #114
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-docs!114
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "docs/absorb-implemented-plans"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
What
Record decisions that were implemented but only written down in working notes.
ent_renovate, Write collaborator up to a per-tier cap, empty autodiscover filter, per-repo opt-out, why opt-in). Records that the range-only default was not adopted.paidquota replaced the per-tier LFS groups (bitborg-infra#184). Per-org quotas are now enforced (org-default,org-unlimited).design/authentication-factors.md: no SMS or email OTP, credential matrix, recovery paths. Linked from ADR 0014.design/identity-field-validation.md: Forgejo email domain lists, name normalisation on first sign-in, Kanidm error shapes.architecture.md: hourly hot backup (ADR 0041) and object-locked off-site copies.contributing/issue-tracking.md: the Forgejo limits behind the scheme.Why
These facts lived only in notes that are being retired. The ADRs and design docs are the durable record.