Merged PR 2429: Add public search API grouping facade slice

Add public search API grouping facade slice

Related work items: #23754

context/api-grouping-adoption-roadmap.md

@@ -13,6 +13,9 @@ Pilot status update (2026-06-25):
 - active published-document metadata consumer (`actions/services/searchDirectService.js`) now targets grouped documents façade routes for details, paged details, and document-type reads
 - published document download remains on the existing grouped runtime path `pages/api/documents/download/[id].js`
 - legacy document metadata endpoint routes remain canonical and stable behind the additive façade wrappers
+- third additive grouping façade vertical slice implemented for the active Public Search results journey under `pages/api/search/`
+- active public search consumer (`actions/services/searchDirectService.js`) now targets grouped search façade routes for the proven in-scope public results path
+- legacy public search endpoint routes remain canonical and stable behind the additive façade wrappers
 - legacy watched-case endpoint routes remain canonical and stable
 - no old route removal or migration has occurred
 - runtime behaviour is intended to remain unchanged because the grouped routes delegate to the existing handlers
@@ -218,6 +221,44 @@ It means:
     - download behaviour remains unchanged
     - no route migration, deletion, or contract change has occurred
 
+#### Additional vertical-slice proof point — Public Search
+
+- The active Public Search journey now has a third complete additive grouping slice for the bounded public results path:
+    - grouped façade routes exist under `pages/api/search/` for the proven active service calls:
+        - `basic-paged`
+        - `advanced`
+        - `advanced-paged`
+        - `basic-details-paged`
+    - `actions/services/searchDirectService.js` targets those grouped routes for:
+        - `getBasicSearchPaged`
+        - `getAdvancedSearch`
+        - `getAdvancedSearchPaged`
+        - `getBasicSearchDetailsPaged`
+    - legacy endpoint handlers remain present and canonical behind the façade:
+        - `pages/api/endpoint/getbasicsearchpaged_api.js`
+        - `pages/api/endpoint/getadvancedsearch_api.js`
+        - `pages/api/endpoint/getadvancedsearchpaged_api.js`
+        - `pages/api/endpoint/getbasicsearchdetailspaged_api.js`
+    - runtime behaviour remains unchanged through direct delegation and unchanged service-layer query contracts
+- The bounded public-search audit also established that:
+    - the active public results UI is driven through `components/search/searchresults.js`
+    - the common service layer is `actions/services/searchDirectService.js`
+    - paged basic results are active in the public results path
+    - advanced search is in scope because `pages/advancedsearchresults.js` actively uses the advanced bootstrap route and the shared results UI actively uses the advanced paged route
+    - paged search-detail expansion is in scope because the active results UI uses `getSearchDetailsPaged(...)`, which calls `getBasicSearchDetailsPaged(...)`
+    - the following routes remain outside this grouped adoption scope because they belong to adjacent or excluded journeys rather than the active bounded public results path:
+        - `getbasicsearch_api.js` (used for adjacent case-detail bootstrap and other non-results contexts)
+        - `getbasicsearchdetails_api.js` (used for adjacent case-detail/bootstrap detail expansion)
+        - address-search variants
+        - DNS search variants
+        - myportal search pages
+- For this Public Search slice, a complete vertical grouping slice means:
+    - active public results journey calls have grouped façade routes
+    - the active common service layer uses those grouped routes
+    - legacy handlers remain present and canonical
+    - excluded adjacent search journeys remain unchanged
+    - no route migration, deletion, or contract change has occurred
+
 ---
 
 ### Stage 3 — Documentation Maturity