jedarden 4fe25fcfaf docs(bf-3ukb): verify crowd flow API path is in sync across all layers

Investigation confirmed that the crowd flow API path mismatch was already
resolved by commit f042cdf (which closed bf-2jyk). All three layers are
now consistent:
- Backend: /api/analytics/flow
- Frontend: /api/analytics/flow
- Plan spec: /api/analytics/flow

No code changes needed. This commit documents the verification.

2026-07-06 00:13:27 -04:00

1.4 KiB

Raw Blame History

Crowd Flow API Path Verification (bf-3ukb)

Status: ✅ Already In Sync - No Changes Needed

This bead addressed a perceived API path mismatch, but investigation shows the issue was already resolved by commit f042cdf on 2026-07-06 (which closed bead bf-2jyk).

Current State (All Correct)

Backend

File: mothership/internal/analytics/handler.go
Routes registered:
- GET /api/analytics/flow → handleGetFlow
- GET /api/analytics/dwell → handleGetDwell
- GET /api/analytics/corridors → handleGetCorridors

Frontend

File: dashboard/js/crowdflow.js
API calls:
- Line 61: fetch('/api/analytics/flow?...')
- Line 79: fetch('/api/analytics/dwell?...')
- Line 91: fetch('/api/analytics/corridors')

Documentation

File: docs/plan/plan.md
Line 2733: GET /api/analytics/flow (updated from /api/flow in commit f042cdf)

Verification

All three layers are consistent:

Backend serves at /api/analytics/flow ✅
Frontend calls /api/analytics/flow ✅
Plan spec documents /api/analytics/flow ✅

bf-2jyk: Closed by commit f042cdf (updated plan spec)
bf-3f16: Open (same root cause, should be closed as duplicate)
bf-3ukb: This bead (verification only)

Recommendation

No code changes needed. Bead bf-3f16 should be closed as a duplicate of the already-resolved bf-2jyk.

1.4 KiB Raw Blame History