feat(logistics): cutover to MAF runtime

[Cataldir]

Problem statement

Migrate the logistics-* bounded context (4 services: carrier-selection, eta-computation, returns-support, route-issue-detection) from the legacy BaseRetailAgent runtime internals to the MAF-backed runtime introduced in #981.

This is a hard sunset: legacy runtime imports are deleted in the same PR. There is no coexistence flag.

Required change

For each of logistics-carrier-selection, logistics-eta-computation, logistics-returns-support, logistics-route-issue-detection:

• Replace usage of lib/src/holiday_peak_lib/agents/ internals with the public surface backed by the MAF runtime from feat(lib): MAF runtime adapter behind the existing BaseRetailAgent surface #981.
• Update each main.py and the agent definition to use the MAF-backed seam.
• MCP tool registrations via FastAPIMCPServer remain unchanged in signature; only the underlying runtime changes.
• REST endpoints remain unchanged in shape; migration is internal.
• Per-service Foundry config (FOUNDRY_AGENT_ID_FAST, MODEL_DEPLOYMENT_NAME_FAST, FOUNDRY_AGENT_ID_RICH, MODEL_DEPLOYMENT_NAME_RICH, FOUNDRY_STREAM, PROJECT_ENDPOINT) wired via Helm values + Key Vault refs.
• Three-tier memory bound per ADR-032 (PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978).
• MCP-only A2A enforced (ADR-030, PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978); hop counter wired.
• Delete pre-MAF imports across all four services in the same PR.

Affected components

• apps/logistics-carrier-selection
• apps/logistics-eta-computation
• apps/logistics-returns-support
• apps/logistics-route-issue-detection

Acceptance criteria (per spec — Acceptance gate per bounded context)

• Contract tests in lib/tests pass.
• All apps/logistics-* unit and integration tests pass.
• Continuous eval baseline (per ADR-028 final schema, PR Add continuous agent evaluation engine #974) within maxDeltaPercent for each agent in this context (advisory until PR Add continuous agent evaluation engine #974 merges).
• AGC canary 5 → 25 → 50 → 100 succeeds in dev, then in staging (per ADR-029, PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978).
• No A2A HTTP detected by scripts/ci/lint_no_a2a_http.py (per ADR-030, PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978).
• Span attribute contract validated by App Insights workbook query (per ADR-031, PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978).
• No pre-MAF imports remain in apps/logistics-carrier-selection, apps/logistics-eta-computation, apps/logistics-returns-support, apps/logistics-route-issue-detection.
• Per-service Foundry config wired via Helm values + Key Vault refs for all four services.
• 24-hour steady-state hold satisfied before the next context's PR opens.

Risks and dependencies

Risk	Mitigation
ETA / carrier-selection regressions degrade promised delivery dates surfaced to the UI.	Eval baselines explicitly cover ETA accuracy and carrier-selection scoring; outside tolerance halts the canary.
Returns-support regressions cause incorrect refund / RMA handling.	Contract tests cover returns flows; eval baselines cover refund/RMA decision quality.
MCP A2A introduces extra latency on multi-hop logistics flows.	Measured pre/post per service; tolerance P95 within 10 %.
Reach-throughs into BaseRetailAgent internals from any of the 4 services.	Pre-flight grep blocks cutover until refactored.
Foundry agent ID provisioning fails for any of the 4 services.	Provisioning runs ahead of this PR; failure halts this context.

Blocked by:

• feat(lib): MAF runtime adapter behind the existing BaseRetailAgent surface #981 (lib MAF runtime seam).
• feat(inventory): cutover to MAF runtime #986 (inventory-* cutover — preceding context per the R1 cutover order).

Blocks: the next context (ecommerce-*) per the R1 sequencing rule.

Evidence links

• apps/logistics-carrier-selection
• apps/logistics-eta-computation
• apps/logistics-returns-support
• apps/logistics-route-issue-detection
• apps/logistics-carrier-selection/src
• apps/logistics-eta-computation/src
• apps/logistics-returns-support/src
• apps/logistics-route-issue-detection/src
• lib/src/holiday_peak_lib/agents/base_agent.py

ADR impact

• ADR-007 (memory tiers) — refined by ADR-032 (PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978).
• ADR-024 → ADR-030 (PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978): MCP-only A2A enforced.
• ADR-029 (PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978): AGC canary gates the cutover.
• ADR-031 (PR docs(adr): ADR-029..033 - architecture contracts (canary, MCP A2A, OTEL, memory, UI on SWA) #978): span attribute contract validated.

Branch convention

feature/<issue-id>-logistics-maf-cutover (per ADR-018).

BPMN process

%%{init: {'theme':'base', 'themeVariables': {
  'primaryColor':'#FFB3BA',
  'primaryTextColor':'#000',
  'primaryBorderColor':'#FF8B94',
  'lineColor':'#BAE1FF',
  'secondaryColor':'#BAE1FF',
  'tertiaryColor':'#FFFFFF'
}}}%%
flowchart LR
  A[Analyze Current Code] --> B[Design Change]
  B --> C[Implement on Issue Branch]
  C --> D[Open PR]
  D --> E[Validation and Fixes]
  E --> F[Merge to Main]
  F --> G[Monitor Workflows]
  G --> H[Close Issue and Cleanup]

Loading