depends: the two bindings, measured again on the tree facts and not taken

constrains: a field Odoo cannot trigger on is asked for by its inputs

depends: a name assigned records, measured and not taken

ondelete: a read through mapped(), measured and not taken

depends: a read straight off a call that keeps the records is a read

artifacts: the measurements move out of the repository's root

depends: a read through a method's own output, measured and kept exempt

depends: what a file says a method computes is its output; a lambda stays unread

depends: what a string names and what a subscript picks are reads

constrains: a dotted name is read, not matched

onchange: the same check made again on the server backs it

onchange: backed by a constraint on its field, refused only when taken back

onchange: a dead _sql_constraints backs nothing on 19

depends: a mapped() path is a read

sudo: a public page reading what it publishes is re-scoped

sudo: a domain on records the caller already holds is re-scoped

rule: _sql_constraints is ignored from Odoo 19

datetime: the rule sees where the value goes

depends-unread: an override that calls super() adds triggers for the chain

narrow: the last three named false-positive classes, and one weakness found on the way

xml: read the data files, and ask noupdate the question per record

recursion: ask whether the ORM already refuses the cycle, and whether it can form one

precision: read the named false positives, and the misses that named themselves

review: a pass over the tool itself, and the silence it was keeping

triggers: the two conditional rules learn to ask the tree

rules: except-order ships advisory, and advisory grows a second ground

semantics: narrow the two worst-aimed rules, at no cost to recall

checkers: two more move to AST, and the OCA findings are classified

tests: pytest suite seeded from the fixed defects