mcptools vs tulpa

tulpa is the C++/R inference engine sitting under a family of ecological occupancy packages, tagging releases several times a week in the 0.0.x range. The current window splits cleanly in two: an API move that turns its calibration and goodness-of-fit entry points into S3 generics, and a run of numerical-correctness work in the nested-Laplace grid. A notable share of releases exist to record a measurement that produced no code change at all.

The generics conversion and the new cross-Hessian return value point the same way: the engine is being reshaped into something downstream packages extend rather than wrap, with the extension points made explicit. The correctness fixes cluster tightly on the joint nested-Laplace driver — indefinite Hessians hitting negative pivots, chunk counts read from live machine load, grid cells silently dropped from a fit — which is where the remaining risk visibly sits. Reported numbers have moved more than once in this window, so the project is still finding cases where earlier answers were wrong rather than merely imprecise.

Expect the rest of the diagnostics layer to finish migrating onto generics, and continued hardening of the batched joint driver's dense path, which is the one route that recently diverged from its own single-species equivalent.