Approve/reject DO need round_no-aware query filtering (the row_order+1
lookup and the reject index-walk have no is_state guard and would
collide across rounds) - the initial draft's "no changes needed" claim
was wrong. Also: migration auto-applies via Database.Migrate() on
startup, remark_historys round_no can be stamped client-side (no PUT
handler changes needed), and frontend's hasActiveStep()/approveStatus()
need round-scoping too.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MNN1mgyALe9skewgUDSMLK
Design for letting users submit a fresh approval round when a
budget-year/faculty/area's request_expense has already been fully
approved but new line items need to go through approval too.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MNN1mgyALe9skewgUDSMLK
Nut.ไปเรื่อย