Allow networkx install on older Python runtimes

[DevOpsMadDog]

Summary

• add Python-version markers so networkx falls back to 3.2.x on Python <3.10
• keep networkx 3.5+ for Python 3.10 and newer

Testing

• not run (not requested)

---

Codex Task

---

Note

Adds Python-versioned constraints for networkx and replaces the interactive setup wizard with a non-interactive one-click script that writes defaults and builds/starts Docker.

• Setup:
  • scripts/setup-wizard.sh: Replaces interactive prompts with a non-interactive one-click flow that:
    • Backs up existing .env, writes fresh defaults (env, API token, LLM flags, service secrets, optional integration vars, COMPOSE_FILE).
    • Verifies Docker, runs scripts/bootstrap.sh, then docker compose build and up -d using COMPOSE_FILE.
    • Updates script messaging and defaults (DEPLOYMENT_MODE, COMPOSE_FILE).
• Dependencies:
  • requirements.txt: Adds Python-version markers for networkx (>=3.5,<4.0 for Python >=3.10; >=3.2.1,<3.5 for Python <3.10).

^{Written by Cursor Bugbot for commit 9ed25ac. This will update automatically on new commits. Configure here.}

---

Summary by cubic

Allows NetworkX to install on Python <3.10 and streamlines deployment with a one-click, non-interactive setup that builds and starts the stack automatically.

• Dependencies

  • Pin NetworkX to 3.5+ for Python >=3.10 and 3.2.x for Python <3.10.

• Refactors

  • Replaces interactive wizard with one-click setup: backs up existing .env and writes safe defaults with generated secrets.
  • Uses deterministic LLM config by default; reads optional provider keys from env if present.
  • Runs bootstrap, builds images, and starts Docker Compose (defaults to docker-compose.demo.yml).
  • Checks for Docker before proceeding and exits with a clear message if missing.

^{Written for commit 9ed25ac. Summary will update automatically on new commits.}

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (all 1 issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="scripts/setup-wizard.sh">

<violation number="1" location="scripts/setup-wizard.sh:80">
P2: The wizard always invokes `docker compose` but never falls back to the documented `docker-compose` binary, so it fails outright on systems without the Compose v2 plugin.</violation>
</file>

_{Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR}

[cubic-dev-ai]

P2: The wizard always invokes docker compose but never falls back to the documented docker-compose binary, so it fails outright on systems without the Compose v2 plugin.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At scripts/setup-wizard.sh, line 80:

<comment>The wizard always invokes `docker compose` but never falls back to the documented `docker-compose` binary, so it fails outright on systems without the Compose v2 plugin.</comment>

<file context>
@@ -11,166 +11,84 @@ YELLOW=&#39;\033[1;33m&#39;
+&quot;$ROOT_DIR/scripts/bootstrap.sh&quot;
+
+echo &quot;🐳 Building FixOps Docker image using $COMPOSE_FILE ...&quot;
+docker compose -f &quot;$ROOT_DIR/$COMPOSE_FILE&quot; build
+
+echo &quot;🚀 Starting FixOps stack...&quot;
</file context>

Suggested change

	docker compose -f "$ROOT_DIR/$COMPOSE_FILE" build
	echo "🚀 Starting FixOps stack..."
	docker compose -f "$ROOT_DIR/$COMPOSE_FILE" up -d
	echo "🐳 Building FixOps Docker image using $COMPOSE_FILE ..."
	if docker compose version &> /dev/null; then
	DOCKER_COMPOSE_CMD="docker compose"
	elif command -v docker-compose &> /dev/null; then
	DOCKER_COMPOSE_CMD="docker-compose"
	else
	echo -e "${RED}❌ Docker Compose (v2 plugin or docker-compose binary) is required.${NC}"
	exit 1
	fi
	$DOCKER_COMPOSE_CMD -f "$ROOT_DIR/$COMPOSE_FILE" build
	echo "🚀 Starting FixOps stack..."
	$DOCKER_COMPOSE_CMD -f "$ROOT_DIR/$COMPOSE_FILE" up -d