Merged PR 2430: Add API grouping facade rollout checkpoint
Add API grouping facade rollout checkpoint Related work items: #23754
This commit is contained in:
@@ -20,6 +20,73 @@ Follow-ups:
|
||||
|
||||
### CL-2026-06-25-API-GROUPING-FACADE-SEARCH-VERTICAL-SLICE: active public search results grouping and service adoption
|
||||
|
||||
### CL-2026-06-25-API-GROUPING-FACADE-ROLLOUT-CHECKPOINT: proven rollout pattern and guardrails checkpoint
|
||||
|
||||
date: 2026-06-25
|
||||
author: Cline
|
||||
scope: `context/api-grouping-adoption-roadmap.md`, `tests/phase22/api-grouping-facade-rollout.test.cjs`, `memory-bank/change-log.md`
|
||||
type: milestone
|
||||
rationale: Record a short checkpoint after the first successful additive API grouping façade slices so the proven rollout pattern, completion criteria, and delay/guardrail criteria are documented before considering more complex API groups.
|
||||
impact: Documentation and characterization only; no runtime behaviour, handler implementation, service URL, route location, payload, contract, auth/session behaviour, or integration behaviour change.
|
||||
status: completed
|
||||
|
||||
Summary:
|
||||
|
||||
- Confirmed the required checkpoint context was read before implementation:
|
||||
- `context/api-grouping-plan.md`
|
||||
- `context/api-grouping-adoption-roadmap.md`
|
||||
- `context/api-route-map.md`
|
||||
- `context/portal-api-platform-assessment.md`
|
||||
- `context/architecture.md`
|
||||
- `memory-bank/change-log.md`
|
||||
- existing façade tests under `tests/phase22`
|
||||
- Confirmed the proven slice pattern now established by the completed façade areas:
|
||||
- `pages/api/subscriptions/*`
|
||||
- `pages/api/documents/*`
|
||||
- `pages/api/search/*`
|
||||
- Recorded the rollout checkpoint in the adoption roadmap with the proven shape:
|
||||
- UI journey
|
||||
- existing service layer
|
||||
- grouped façade route
|
||||
- legacy canonical handler
|
||||
- unchanged integration behaviour
|
||||
- Documented completion criteria for a vertical façade slice, including:
|
||||
- bounded active-journey audit
|
||||
- grouped façade coverage for in-scope active routes only
|
||||
- safe service-layer adoption
|
||||
- retained canonical legacy handlers
|
||||
- explicit out-of-scope treatment for inactive/support routes
|
||||
- characterization proof and scope documentation
|
||||
- Documented “do not group yet” criteria for cases such as:
|
||||
- unclear ownership
|
||||
- missing clear service layer
|
||||
- orchestration-heavy routes
|
||||
- storage + queue + CRM crossing routes
|
||||
- auth/session-critical routes
|
||||
- unproven activity
|
||||
- required frontend refactor
|
||||
- required contract change
|
||||
- Added a lightweight meta-test to characterize the checkpoint structure without introducing a larger framework.
|
||||
|
||||
Validation:
|
||||
|
||||
- Focused validation only for this checkpoint:
|
||||
- `npx eslint tests/phase22/api-grouping-facade-rollout.test.cjs`
|
||||
- `node tests/phase22/api-grouping-facade-rollout.test.cjs`
|
||||
- `node tests/phase22/api-grouping-facade-subscriptions.test.cjs`
|
||||
- `node tests/phase22/api-grouping-facade-documents.test.cjs`
|
||||
- `node tests/phase22/api-grouping-facade-search.test.cjs`
|
||||
- No heavy repo-wide tooling run.
|
||||
|
||||
Follow-ups:
|
||||
|
||||
- Use this checkpoint as the baseline before considering any further façade candidates.
|
||||
- Prefer the next candidate only where the same additive pattern can be proven without route movement, contract change, or orchestration-risk expansion.
|
||||
|
||||
---
|
||||
|
||||
### CL-2026-06-25-API-GROUPING-FACADE-SEARCH-VERTICAL-SLICE: active public search results grouping and service adoption
|
||||
|
||||
date: 2026-06-25
|
||||
author: Cline
|
||||
scope: `pages/api/search/basic-paged.js`, `pages/api/search/advanced.js`, `pages/api/search/advanced-paged.js`, `pages/api/search/basic-details-paged.js`, `actions/services/searchDirectService.js`, `tests/phase22/api-grouping-facade-search.test.cjs`, `context/api-grouping-adoption-roadmap.md`
|
||||
|
||||
Reference in New Issue
Block a user