mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-21 09:31:12 +00:00
Oleksandr Bezdieniezhnykh
5ae352c68d
AZ-897 ("Build the first operator-facing UI for the GPS-denied
onboard system") was wrong-shop: the spec named React + Tailwind
but assumed it would land in gps-denied-onboard. The Azaion suite
already has a single React 19 SPA front-end at ../ui per
ui/README.md; spinning up a second React toolchain inside this
repo would have been parallel-pipeline duplication forbidden by
coderule.mdc.
Per user 2026-05-29 directive:
- Jira AZ-897 summary + description rewritten to UI-only scope in
../ui (adapted to take CSV + nadir-camera video uploads aligned
with the AZ-894 CSV path). Full audit comment attached.
- Local AZ-897 spec deleted from this repo's todo/ and re-authored
into ../ui/_docs/02_tasks/todo/AZ-897_replay_ui_web_form.md
(left uncommitted there — ../ui repo's next autodev cycle picks
it up).
- Filed AZ-959 (3 SP, todo/) to extend replay_api POST /replay to
accept (video, csv) multipart + add GET /static/example-csv.
Without this endpoint the relocated AZ-897 UI cannot drive the
CSV-replay path.
- Linked AZ-959 'is blocked by' against AZ-897 Jira-side (verified
via read-back: AZ-897 issuelinks now includes AZ-959 as blocker
alongside the existing AZ-894 + AZ-896 dependency links).
Cycle-4 in-repo effort: −5 SP (AZ-897) + 3 SP (AZ-959) = −2 SP
net. AZ-897 itself remains open and active; its 5 SP now belong
to ../ui's cycle (the Jira ticket stays AZ-897 — no renumbering,
no duplicate, no Won't-Fix; just a scope + repo-home correction).
Touches: _docs/02_tasks/_dependencies_table.md (preamble third
bump narrative + AZ-959 row + totals to 184 / 584), _autodev
state pivots to AZ-959 as next implement-batch target. The
../ui-side spec write is intentionally uncommitted in that repo;
surface flagged in the chat summary.
Co-authored-by: Cursor <cursoragent@cursor.com>