v0.3.0

v0.3.0

Five new tools: getDeviceDeclarationState, getDeclarationScope, findObjectReferences,
findGroupDependencies, getComputerGroup.

The theme is coverage. Several tools were stating conclusions more confidently than their
evidence supported, so where a null result cannot be trusted it now carries a field
saying what was actually checked — strength, notChecked, scanComplete,
excludedFromThisAnswer, termsSwept.

Breaking, deliberately: platformRequest no longer accepts method or body, so the
passthrough cannot express a mutation (JPM-0007). requestAll throws on proclassic rather
than returning an empty array.

v0.2.1 — corrections only

v0.2.1 — corrections only

Fixes the retracted Classic path shape wherever it was still published as fact,
most importantly in the platformRequest tool description. Corrects the
pre-JPM-0006 endpoint inventory. Adds JPM-0007 (write-path posture). Bumps CI
actions off deprecated Node 20.

v0.2.0

v0.2.0

Ten tools. Confirmed working routes across six gateway segments: blueprints,
devices, device-groups, pro (Jamf Pro API in full), proclassic (Jamf Pro Classic)
and ddm/report (Declaration Reporting).

New since v0.1.0:
findDeviceGroups, getDeviceGroupMembers — group search and membership resolution
findExpensiveAutomations — audits scripts, extension attributes and policy cadence
getInventoryCollectionSettings — rates inventory options by cost per collection
findCriteriaReferences — establishes whether an inventory field is load-bearing

Contribution rules are now enforced by pre-commit hooks and CI rather than
documented: no live identifiers in tracked files, no captured API responses
committed, committed ADRs immutable.

Known limitation: Compliance Benchmarks returns a gateway-side 500
("Upstream host lookup failed") on its documented path — a fault on Jamf's side.

119 tests, mutation-checked. Upstream API is a public beta with no stability
guarantee, so minor versions may carry breaking changes.