Skip to main content

Helpifyr Warp Compatibility

This compatibility page is generated from canonical repo-owned source material in JaddaHelpifyr/jhf-warp.

Documentation Map​

Compatibility Sources​

  • docs/OSS_INVENTORY.md
  • docs/OSS_INVENTORY_VERSION_TRUTH.md

Derived from OSS Inventory, Version Truth, and Upgrade Readiness​

OSS Inventory, Version Truth, and Upgrade Readiness

This document defines the repo-owned contract for OSS inventory and version truth in jhf-warp.

Canonical Machine-Readable Sources​

  • maintenance/oss-inventory.json
  • maintenance/oss-version-truth.json
  • maintenance/oss-upgrade-policy.json

These files are the only repo-owned truth for:

  • relevant OSS components used by runtime, CI, and packaging paths
  • component pinning posture (tag-pinned, major-track, external-floating-classified)
  • external owner classification where this repo does not own the upstream release train
  • upgrade readiness blockers that are outside this repository

Verification Path​

Run:

python scripts/verify_oss_inventory.py

The verifier fails closed when:

  • an observed OSS surface is missing from inventory truth
  • observed refs drift from inventory truth
  • a repo-owned container ref is floating (latest or untagged)
  • pyproject dependency truth drifts from maintenance/oss-version-truth.json
  • required external blocker references drift from maintenance/oss-upgrade-policy.json

Policy Summary​

  • Repo-owned container/runtime tooling refs must be explicit and non-floating.
  • Runner labels may stay *-latest only when explicitly classified as external owner scope.
  • Python dependencies must remain bounded by explicit version ranges.
  • External cross-repo upgrade blockers are tracked in machine-readable policy truth and must not be hidden by local workarounds.

Compatibility Note​

docs/OSS_VERSION_GOVERNANCE.md remains as a compatibility alias and points to this canonical document.

License​

AGPLv3. See ../LICENSE (LICENSE).

Learn more at helpifyr.com.