ADR 0025: origin-first forge resolution and host-keyed credentials (tracking) #30
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements docs/adr/0025-origin-first-forge-resolution.md on branch
adr/0025-origin-first-forge-resolution.Landed on the branch (with review):
ParseRemoteHost/forgeHost/OriginForgeURL/runGitDir(5b01e432) · T2 host-keyed TokenStore v2 across keychain/pass/systemd-creds (e516ec7b, fix 6fce6df3) · T3 resolver: host-keyed lookup + migrate-on-first-use, signatureresolveSecureOrGitToken(ctx, cleanURL, gitUser) (token, user, source string, secureErr error)(fdaf007a) · T4 the origin-first chain in getConfigFromGit/GetCredentials/GetCredentialsWithSource + migrate-gate rework (0b787929).Remaining: the sub-issues below. Order: #A ∥ #B (disjoint files), then #C, then #D ∥ #E, then #F, then #G (gate + merge).
Exit criterion: full ./scripts/gate.sh green on the branch; a repo whose origin names forge X can never be queried against forge Y; one credential per forge host; repo-less calls resolve a session forge or fail closed; ADR status flipped to Accepted.
Sub-issues:
Follow-on (not gating this epic):
All sub-issues T5–T11 (#31–#37) are closed and the branch merged to main via PR #41 (merge commit
7f874f80). Exit criteria verified: ADR status is Accepted (docs/adr/0025-origin-first-forge-resolution.md:3), full gate ran as T11 (#37), host-keyed credentials + origin-first chain + session-forge scan + dir= forge routing all on main. The body checklist predates the sub-issue closes and is stale; the closed children are the record. Follow-on #59 (dir= on the API plane) remains open by design.