mirror of
https://github.com/fsolla/teqo.git
synced 2026-11-13 06:43:06 +00:00
c68e1d2394
The /simplify triage produced two live debts, and both are about the same pair of functions the B34+ plan already names in F3, so they landed as F10 of that plan rather than as an escala-dry-pos-b37: the município-side batch actions write one município at a time (findByID + update each — ~870 round trips at the 435 ceiling B37 itself raised, but ~52 at the largest real TI, and no test above a batch of 2), and the two are twins at 2 call sites, one short of the bar. The common trigger is a "select all"/multi-TI affordance or a third batch on that side, and F10 records why the bulk-SQL rewrite is not obviously the answer: it would hand back the scope check that overrideAccess: false gives for free. This delivery also closed B34+ phases outright, which is worth reading in the plan rather than inferring from a diff. F2 is done and its prediction was wrong in a way worth keeping: it stated "o B37 não retira este débito", and B37 read the same evidence the other way — the ~165 measured lines were not deduplicated into useChipRowOverflow, they were deleted when both cells became wrappers of one engine. F9 is done via scopedPortfolioIndex. Half of F3 is done (the three single-id deltas), and the half that stayed out — the set-with-floor form — stayed out because seeing the collapsed code confirmed the plan's own inverted recommendation. F5 and two F6 bullets shrank for the same reason: "written twice across the two surfaces" stopped having two surfaces. Also corrects a comment I got wrong in the previous commit: the batch's sort does not carry the deadlock-avoidance guarantee, since acquireTextAdvisoryLocks sorts its own keys (C8 batched them into one round trip); it only makes the apply order stable. |
||
|---|---|---|
| .. | ||
| design-refs | ||
| plans | ||
| research | ||
| ARCHITECTURE.md | ||
| IMPROVE-APP-PLAN.md | ||
| IMPROVE-CODE-QUALITY-PLAN.md | ||
| roadmap.md | ||
| TECH-DEBT.md | ||
| TESTING.md | ||