From 21d5571b087eca2cd3a41b799572cccdd7e1eba7 Mon Sep 17 00:00:00 2001 From: Dotta Date: Mon, 26 Oct 2026 10:47:33 -0500 Subject: [PATCH] docs(connections): retain route regression and upstream merge evidence Co-Authored-By: Paperclip --- doc/plans/2026-10-13-connection-api-parity.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/plans/2026-10-13-connection-api-parity.md b/doc/plans/2026-10-13-connection-api-parity.md index 692458bdd41..da4c9cfdf91 100644 --- a/doc/plans/2026-10-13-connection-api-parity.md +++ b/doc/plans/2026-10-13-connection-api-parity.md @@ -126,3 +126,6 @@ The implementation was rebased onto `a1f77821b9cd5c9c846fdf7a0fa5cc620ad2b6bb`. - Final assembled-server acceptance after the device-login fix: **32 scenarios passed** in a fresh PostgreSQL database. - Review found that the top-level Apps connect route rejected an `aiLogin`-only handoff before rendering its saved login panel. The new route-policy test failed before the fix; the route now admits a non-empty saved-login ID, leaving owner/session validation to the existing server and panel. Empty IDs remain rejected. The prior component-only tests did not cover this entry gate. + +- Saved-login route policy and Apps connect components: **236 tests passed** after the entry fix; the added route-policy case was red before the fix. Token gates and map validation passed. +- Master advanced during PR qualification. The implementation now merges `5823e9a664`; its already published Copilot v60 identity is preserved byte-for-byte, and the combined connection guidance is declared as v61. Generated TypeScript/Rust identity checks and all **58 Copilot installation tests passed**. These checks do not imply a new live provider qualification.