chore: park batch 24 plan; AZ-300 blocked on [inference] extras

batch 23 (AZ-332) is committed + pushed; AZ-332 transitioned to In
Testing. Batch 24 next-task computation revealed AZ-300 (C7
PytorchFp16Runtime) cannot proceed without `pip install -e .[inference]`
(torch + torchvision + onnxruntime). State file now reflects this gate
so the next /autodev invocation knows the explicit Choose A/B/C is
queued.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-05-12 10:00:08 +03:00
parent 1ebab29a4f
commit fce80290bc
+3 -3
View File
@@ -6,9 +6,9 @@ step: 7
name: Implement
status: in_progress
sub_step:
phase: 13
name: archive-and-loop
detail: "batch 23/cycle1 complete: AZ-332 → In Testing, archived to done/. Next: recompute batch 24 (AZ-345 still gated; product-tasks queue may be near-empty — Step 15 Product Implementation Completeness Gate is the expected next stop)."
phase: 3
name: compute-next-batch
detail: "batch 24/cycle1 computed but BLOCKED on env: AZ-300 (C7 PytorchFp16Runtime, 2pt) needs the [inference] optional extra (torch>=2.2 + torchvision>=0.17 + onnxruntime>=1.17, ~700 MB on macOS). Dev venv currently only has [dev]. Resolve: either (a) pip install -e .[inference] before resuming, or (b) skip AZ-300 in this cycle (move it to backlog) and pick the next-smallest ready task that does not need torch — AZ-301 EngineGate (3pt, no torch dep), AZ-302 ThermalState Publisher (3pt, jetson-stats/pynvml — also heavy but tier2-only), AZ-304 C6 Postgres schema (2pt, no native deps). 18 tasks total ready overall."
retry_count: 0
cycle: 1
tracker: jira