docs: queue outstanding-issue for recurring shared-shell testid duplication

docs/outstanding-issues-inbox/4008efd4-b116-42a2-a4e1-f7b3ed9590f7.json

@@ -0,0 +1,10 @@
+{
+  "version": 2,
+  "id": "4008efd4-b116-42a2-a4e1-f7b3ed9590f7",
+  "createdOn": "2026-09-04",
+  "action": "cancel",
+  "payload": {
+    "requestId": "97f270b0-f713-45ae-8b04-0e1982db2518",
+    "reason": "Overstated an unverified detail (claimed the duplicate element was nested inside mobile-composer-reserve-pad by analogy with two earlier occurrences); the actual job log for this instance only shows two sibling matches for the same testid, with no nesting evidence pulled. Replacing with a corrected entry that doesn't overstate what was verified."
+  }
+}

docs/outstanding-issues-inbox/4cc4b95c-8dcb-4772-a157-b7ae2980c033.json

@@ -0,0 +1,13 @@
+{
+  "version": 2,
+  "id": "4cc4b95c-8dcb-4772-a157-b7ae2980c033",
+  "createdOn": "2026-09-04",
+  "action": "add",
+  "payload": {
+    "pri": "P2",
+    "type": "issue",
+    "summary": "Shared-shell testid duplicates under Playwright strict mode: service-actions-trigger (PR #2536) and sources-topics-main (PR #2591) both resolve to 2 elements, one nested inside GlobalSearchShell's mobile-composer-reserve-pad wrapper and one outside it",
+    "detail": "Recurring, reproducible 'Production UI critical' failure, not a random flake: strict-mode violation on getByTestId resolving to 2 elements — one aka mobile-composer-reserve-pad.getByTestId(x), one aka getByTestId(x).nth(1). Seen on tests/ui-tools.spec.ts (service-actions-trigger, PR #2536 precedent) and tests/ui-sources.spec.ts:88 (sources-topics-main, PR #2591, run 33868983554). Confirmed unrelated to either PR's own diff (files touched by those PRs don't include global-search-shell.tsx, sources-browse-client.tsx, or mode-home-template.tsx). Root cause not yet isolated — likely a hydration-timing or route-transition double-render inside the GlobalSearchShell/PageSecondaryNavigation tree. GlobalSearchShell is a 'one owner' contract component (AGENTS.md Search chrome behaviour) — a fix needs docs/search-chrome-behaviour.md read first and its own focused PR + npm run verify:phone-chrome, not a rushed patch riding an unrelated PR.",
+    "issueUlid": "01M1P472CHJAEKM4CFC2PR8C20"
+  }
+}

docs/outstanding-issues-inbox/97f270b0-f713-45ae-8b04-0e1982db2518.json

@@ -0,0 +1,13 @@
+{
+  "version": 2,
+  "id": "97f270b0-f713-45ae-8b04-0e1982db2518",
+  "createdOn": "2026-09-04",
+  "action": "add",
+  "payload": {
+    "pri": "P2",
+    "type": "issue",
+    "summary": "Third confirmed occurrence of the shared-shell duplicate-testid Playwright strict-mode bug, now in Caring Contacts workspace (caring-contacts-phone-dock, PR #2600)",
+    "detail": "Same shape as the two occurrences already logged (see the outstanding-issue queued alongside PR #2613): getByTestId resolves to 2 elements, once inside a shared layout wrapper and once outside it. This time: tests/ui-caring-contacts-workspace.spec.ts:1992, 'Template detail at 390px: the phone dock does not own navigation', getByTestId('caring-contacts-phone-dock') resolved to 2 <nav aria-label=\"Phone workspace\"> elements (PR #2600 run 33868074584, job 101007656433). Confirmed unrelated to PR #2600's own diff (a documents/medications routing consolidation, not Caring Contacts). Three occurrences across three unrelated PRs and three different testids now strongly suggests a systemic layout-duplication bug (possibly a hydration or route-transition double-mount) rather than three independent flakes — worth escalating priority when the originally-queued investigation is picked up.",
+    "issueUlid": "01M1P6RP04D1D6PEPQNF1QB3QP"
+  }
+}

docs/outstanding-issues-inbox/ab278e5a-b081-4959-906f-2f7ca72b0aac.json

@@ -0,0 +1,13 @@
+{
+  "version": 2,
+  "id": "ab278e5a-b081-4959-906f-2f7ca72b0aac",
+  "createdOn": "2026-09-04",
+  "action": "add",
+  "payload": {
+    "pri": "P2",
+    "type": "issue",
+    "summary": "Third confirmed occurrence of the shared-shell duplicate-testid Playwright strict-mode bug, now in Caring Contacts workspace (caring-contacts-phone-dock, PR #2600)",
+    "detail": "Same error shape as the two occurrences already logged (see the outstanding-issue queued alongside PR #2613): getByTestId resolves to 2 elements for the same testid. This time: tests/ui-caring-contacts-workspace.spec.ts:1992, 'Template detail at 390px: the phone dock does not own navigation', getByTestId('caring-contacts-phone-dock') resolved to 2 identical <nav aria-label=\"Phone workspace\"> elements (PR #2600 run 33868074584, job 101007656433, shard 2). Confirmed unrelated to PR #2600's own diff (a documents/medications routing consolidation, not Caring Contacts). Correction: an earlier version of this note claimed one copy was nested inside GlobalSearchShell's mobile-composer-reserve-pad wrapper by analogy with the first two occurrences (service-actions-trigger, sources-topics-main) — that specific nesting detail was NOT verified for this third instance; the job log only shows two sibling matches (.first() and getByRole equivalent), not where in the DOM tree the second copy actually lives. Root cause (single vs. multiple mechanisms) is still open. Three occurrences across three unrelated PRs and three different testids still strongly suggests a systemic layout-duplication bug rather than three independent flakes.",
+    "issueUlid": "01M1P7G8RDXXH42KG1RKCXZTFN"
+  }
+}