Tree-Mendous 1.1.1

Tree-Mendous 1.1.1

Tree-Mendous 1.1.1 is a documentation and packaging-metadata patch. It does not
change the stable RangeSet API, the stable treemendous.exact_batch API,
backend selection, application-engine behavior, or experimental
multidimensional runtime behavior.

User documentation

The PyPI landing page now leads with a task-oriented API choice:

• use RangeSet for general queries, allocation, snapshots, and payloads;
• use treemendous.exact_batch for ordered, whole-batch-atomic geometry only;
• use treemendous.applications for one of 50 concrete process-local scenario
  engines;
• use treemendous.multidimensional only as an explicit experiment.

New maintained guides cover choosing an interface,
application patterns, and
performance. The performance guide records scoped local
standard measurements, links the hosted 1.1.0 exact-batch evidence, defines the
timed layers, and gives a gated optimization roadmap without claiming new
runtime work. The 1.1.0 GitHub release now carries durable JSON, Markdown, and
SHA-256 assets for both the standard RangeSet profile and hosted exact-batch
evidence linked by that guide.

Two new executable patterns live outside the 50-engine example directory:

• atomic port-pool reconciliation
  uses exact batch but intentionally supplies no lease identity, TTL, or
  fencing;
• spatiotemporal geofences
  uses experimental, process-local BoxIndex3D.

Exact batch is not integrated into the 50 engines. The radio-spectrum engine
is the existing generic multidimensional integration: it wraps experimental
BoxIndex(2) behind application-specific channel/time reservation semantics.
The Morton geospatial catalog does not use BoxIndex; it uses one-dimensional
Morton candidate bands with exact Cartesian filtering.

Packaging metadata

The project description now reflects the stable Python/C++ range-set backends,
atomic native batch API, experimental multidimensional indexes, and 50
application engines. PyPI metadata adds search keywords and explicit homepage,
documentation, repository, issue, and release links. The version is 1.1.1 and
the lock file is regenerated.

twine>=6.2.0 is part of the build extra. Release source, platform-wheel, and
aggregate artifact jobs run python -m twine check --strict before upload or
publication. The existing pinned Actions, OIDC trusted publication, single
publisher, and job timeouts remain in place.

The source-distribution content policy now requires all new guides and examples.
Documentation contracts execute both patterns from an unrelated working
directory and verify that README repository links are absolute and PyPI-safe.

Compatibility

Version 1.0.0 established RangeSet, BackendRegistry, and
create_range_set as the stable package-root API. Version 1.1.0 added the
contained stable treemendous.exact_batch module without root, backend, or
protocol integration. Those release statements and contracts remain unchanged
in 1.1.1. Existing 1.0.0 and 1.1.0 applications require no migration.