From 19df9602741a6af05e3c9f3dd73d3384d81abaa9 Mon Sep 17 00:00:00 2001 From: variablefate Date: Mon, 11 May 2026 14:55:59 -0700 Subject: [PATCH] docs(tests): retarget stale ADR-0012 ref to ADR-0019 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cleanup miss from PR #113 (`ce0d263`): the parity-regression test added in that PR referenced `ADR-0012` for the roadflared/Universal-Links routing pattern, but the ADR was renumbered to `ADR-0019` in PR #112 (`7c08ac8`) while #113 was in flight. The squash merge auto-resolved existing `ADR-0012` references in this file via 3-way merge, but couldn't catch a brand-new line added on the branch. `decisions/0012-coordinator-ride-identity-cache.md` is now an unrelated ADR, so the stale ref doesn't just point at the wrong number — it points at the wrong subject. Co-Authored-By: Claude Opus 4.7 (1M context) --- RoadFlare/RoadFlareTests/AppState/HandleIncomingURLTests.swift | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RoadFlare/RoadFlareTests/AppState/HandleIncomingURLTests.swift b/RoadFlare/RoadFlareTests/AppState/HandleIncomingURLTests.swift index c0f8d14..7d56014 100644 --- a/RoadFlare/RoadFlareTests/AppState/HandleIncomingURLTests.swift +++ b/RoadFlare/RoadFlareTests/AppState/HandleIncomingURLTests.swift @@ -193,7 +193,7 @@ struct HandleIncomingURLTests { // Cold-start regression parity for Universal Links: same invariant as // `navigationIntentSurvivesIdentityReplacementWhenNoKeypair` above, but // exercised through `handleIncomingUserActivity`. Universal Links are - // the long-term primary share path (per ADR-0012 + issue #63), so the + // the long-term primary share path (per ADR-0019 + issue #63), so the // pre-onboarding tap path needs explicit coverage on this entry point // — not just the `roadflared:` shim. See PR #66 for the precedent of // pinning parallel regression coverage on each new entry seam.