circuitforge-orch must not be a hard install dependency — it is Paid+ only #56
Labels
No labels
accessibility
backlog
browser-pool
bug
cloud
enhancement
feature
infra
paid-tier
performance
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Circuit-Forge/snipe#56
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
snipecurrently declarescircuitforge-orch>=0.1.0as a hard dependency inpyproject.toml. This means a plainpip install snipe(orpip install -e .) will fail unlesscircuitforge-orchis also installed — butcircuitforge-orchis not published to PyPI and is a Paid+ tier feature.Free tier users attempting a local install will hit:
Fix
Move
circuitforge-orchto an optional extras group so it is never a hard install requirement:The tier gate should be enforced at runtime (in
tiers.pyor the feature entry point), not at install time. Free tier users should be able to install and run snipe without orch; the orchestration features simply stay locked behind the tier check.Principle
This follows the CF licensing model: MIT discovery/pipeline layers install cleanly for everyone; BSL/Paid features are runtime-gated, not install-gated. A hard install dep on a paid-only package is a violation of that boundary.
Discovered
2026-05-21, during xanderland.tv per-service venv setup.