jsfeatNext is not drop-in compatible with jsfeat: consumers must unwrap jsfeatNext.jsfeatNext (double namespace), algorithm modules require new (instance methods) vs jsfeat static namespace functions, and each instance allocates its own cache pool. Decide the compatibility strategy (static facade / dual API) and fix the export shape. See docs/jsfeat-parity-and-refactor-audit.md (Axis 2).
jsfeatNext is not drop-in compatible with jsfeat: consumers must unwrap jsfeatNext.jsfeatNext (double namespace), algorithm modules require new (instance methods) vs jsfeat static namespace functions, and each instance allocates its own cache pool. Decide the compatibility strategy (static facade / dual API) and fix the export shape. See docs/jsfeat-parity-and-refactor-audit.md (Axis 2).