[feat][#16] Re-implement mega-planner as standalone Python script

Makefile

@@ -1,5 +1,5 @@
 # Default target
-.PHONY: test test-shells test-sdk test-cli test-lint test-e2e test-fast help setup pre-commit sandbox-build sandbox-run
+.PHONY: test test-shells test-sdk test-cli test-lint test-e2e test-fast help setup env pre-commit sandbox-build sandbox-run
 
 test:
 	./tests/test-all.sh
@@ -72,6 +72,10 @@ setup:
 	@echo "  2. For persistence, add to your shell RC file:"
 	@echo "     cat setup.sh >> ~/.bashrc  # or ~/.zshrc"
 
+env:
+	@echo 'export AGENTIZE_HOME="$(CURDIR)"'
+	@echo 'export PYTHONPATH="$(CURDIR)/python:$$PYTHONPATH"'
+
 help:
 	@echo "Available targets:"
 	@echo "  make test                - Run all tests (bash only)"
@@ -82,6 +86,7 @@ help:
 	@echo "  make test-e2e            - Run end-to-end integration tests"
 	@echo "  make test-fast           - Run fast tests (sdk + cli + lint)"
 	@echo "  make setup               - Generate local setup.sh for development"
+	@echo "  make env                 - Print environment exports (use: eval $$(make env))"
 	@echo "  make sandbox-build       - Build/rebuild the agentize-sandbox image"
 	@echo "  make sandbox-run         - Run sandbox with volume passthrough (auto-builds if needed)"
 	@echo ""

templates/README.md

@@ -7,9 +7,12 @@ All the templates have:
 - A `Makefile` in the root folder, which defines the following commands:
     - `make setup`: Generates a `setup.sh` script (per-project) to set up environment variables for the SDK.
     - This differs from the agentize repo's `make setup` which generates a cross-project `setup.sh` for `wt` and `agentize` CLI functions.
+    - `make env`: Prints environment export statements to stdout. Usage: `eval $(make env)` to set up the environment in the current shell without generating a file.
+    - `make env-script`: Generates/regenerates `setup.sh` with current paths using `$(CURDIR)` for proper `make -C` handling.
     - `make build`: Builds the SDK.
     - `make clean`: Cleans all the build files.
     - `make test`: Runs the test cases.
+    - `make help`: Displays available targets and usage instructions.
 
 - A `bootstrap.sh` script in the root folder, which initializes the SDK from the template.
     - This makes `make agentize` (see ../Makefile) as simple as copying this script to the target folder and run this script.

templates/c/Makefile

@@ -1,4 +1,4 @@
-.PHONY: setup build clean test pre-commit
+.PHONY: setup build clean test pre-commit env env-script help
 
 pre-commit:
 	@if [ -f scripts/pre-commit ]; then \
@@ -28,6 +28,27 @@ setup:
 	@chmod +x setup.sh
 	@echo "setup.sh generated successfully"
 
+# ============================================================================
+# Environment Setup
+# ============================================================================
+
+env:
+	@echo 'export PROJECT_ROOT="$(CURDIR)"'
+	@echo 'export PATH="$(CURDIR)/build/bin:$$PATH"'
+	@echo 'export C_INCLUDE_PATH="$(CURDIR)/include:$$C_INCLUDE_PATH"'
+	@echo 'export LIBRARY_PATH="$(CURDIR)/build/lib:$$LIBRARY_PATH"'
+
+env-script:
+	@echo "Generating setup.sh..."
+	@echo '#!/bin/bash' > setup.sh
+	@echo '# Generated by make env-script' >> setup.sh
+	@echo 'export PROJECT_ROOT="$(CURDIR)"' >> setup.sh
+	@echo 'export PATH="$$PROJECT_ROOT/build/bin:$$PATH"' >> setup.sh
+	@echo 'export C_INCLUDE_PATH="$$PROJECT_ROOT/include:$$C_INCLUDE_PATH"' >> setup.sh
+	@echo 'export LIBRARY_PATH="$$PROJECT_ROOT/build/lib:$$LIBRARY_PATH"' >> setup.sh
+	@chmod +x setup.sh
+	@echo "Generated setup.sh - run: source setup.sh"
+
 build:
 	cmake -S . -B build && cmake --build build
 
@@ -36,3 +57,13 @@ clean:
 
 test: build
 	cd build && ctest --output-on-failure
+
+help:
+	@echo "Available targets:"
+	@echo "  make pre-commit  - Install pre-commit hook"
+	@echo "  make setup       - Generate setup.sh (legacy)"
+	@echo "  make env         - Print environment exports (use: eval \$$(make env))"
+	@echo "  make env-script  - Generate setup.sh script"
+	@echo "  make build       - Build the project"
+	@echo "  make clean       - Clean build artifacts"
+	@echo "  make test        - Run tests"

templates/cxx/Makefile

@@ -1,4 +1,4 @@
-.PHONY: setup build clean test pre-commit
+.PHONY: setup build clean test pre-commit env env-script help
 
 pre-commit:
 	@if [ -f scripts/pre-commit ]; then \
@@ -28,6 +28,27 @@ setup:
 	@chmod +x setup.sh
 	@echo "setup.sh generated successfully"
 
+# ============================================================================
+# Environment Setup
+# ============================================================================
+
+env:
+	@echo 'export PROJECT_ROOT="$(CURDIR)"'
+	@echo 'export PATH="$(CURDIR)/build/bin:$$PATH"'
+	@echo 'export CPLUS_INCLUDE_PATH="$(CURDIR)/include:$$CPLUS_INCLUDE_PATH"'
+	@echo 'export LIBRARY_PATH="$(CURDIR)/build/lib:$$LIBRARY_PATH"'
+
+env-script:
+	@echo "Generating setup.sh..."
+	@echo '#!/bin/bash' > setup.sh
+	@echo '# Generated by make env-script' >> setup.sh
+	@echo 'export PROJECT_ROOT="$(CURDIR)"' >> setup.sh
+	@echo 'export PATH="$$PROJECT_ROOT/build/bin:$$PATH"' >> setup.sh
+	@echo 'export CPLUS_INCLUDE_PATH="$$PROJECT_ROOT/include:$$CPLUS_INCLUDE_PATH"' >> setup.sh
+	@echo 'export LIBRARY_PATH="$$PROJECT_ROOT/build/lib:$$LIBRARY_PATH"' >> setup.sh
+	@chmod +x setup.sh
+	@echo "Generated setup.sh - run: source setup.sh"
+
 build:
 	cmake -S . -B build && cmake --build build
 
@@ -36,3 +57,13 @@ clean:
 
 test: build
 	cd build && ctest --output-on-failure
+
+help:
+	@echo "Available targets:"
+	@echo "  make pre-commit  - Install pre-commit hook"
+	@echo "  make setup       - Generate setup.sh (legacy)"
+	@echo "  make env         - Print environment exports (use: eval \$$(make env))"
+	@echo "  make env-script  - Generate setup.sh script"
+	@echo "  make build       - Build the project"
+	@echo "  make clean       - Clean build artifacts"
+	@echo "  make test        - Run tests"

templates/python/Makefile

@@ -1,4 +1,4 @@
-.PHONY: setup build clean test pre-commit
+.PHONY: setup build clean test pre-commit env env-script help
 
 pre-commit:
 	@if [ -f scripts/pre-commit ]; then \
@@ -26,6 +26,25 @@ setup:
 	@chmod +x setup.sh
 	@echo "setup.sh generated successfully"
 
+# ============================================================================
+# Environment Setup
+# ============================================================================
+
+env:
+	@echo 'export PROJECT_ROOT="$(CURDIR)"'
+	@echo 'export PATH="$(CURDIR)/build/bin:$$PATH"'
+	@echo 'export PYTHONPATH="$(CURDIR)/src:$$PYTHONPATH"'
+
+env-script:
+	@echo "Generating setup.sh..."
+	@echo '#!/bin/bash' > setup.sh
+	@echo '# Generated by make env-script' >> setup.sh
+	@echo 'export PROJECT_ROOT="$(CURDIR)"' >> setup.sh
+	@echo 'export PATH="$$PROJECT_ROOT/build/bin:$$PATH"' >> setup.sh
+	@echo 'export PYTHONPATH="$$PROJECT_ROOT/src:$$PYTHONPATH"' >> setup.sh
+	@chmod +x setup.sh
+	@echo "Generated setup.sh - run: source setup.sh"
+
 build:
 	@echo "No build needed for Python SDK"
 
@@ -39,3 +58,13 @@ clean:
 test:
 	@echo "Running Python tests..."
 	@python3 tests/test_main.py
+
+help:
+	@echo "Available targets:"
+	@echo "  make pre-commit  - Install pre-commit hook"
+	@echo "  make setup       - Generate setup.sh (legacy)"
+	@echo "  make env         - Print environment exports (use: eval \$$(make env))"
+	@echo "  make env-script  - Generate setup.sh script"
+	@echo "  make build       - Build the project"
+	@echo "  make clean       - Clean build artifacts"
+	@echo "  make test        - Run tests"

tests/lint/test-makefile-env-target.sh

@@ -0,0 +1,37 @@
+#!/usr/bin/env bash
+# Test: Makefile env target prints correct environment exports
+
+source "$(dirname "$0")/../common.sh"
+
+test_info "Makefile env target prints correct environment exports"
+
+cd "$PROJECT_ROOT"
+
+# Clear MAKEFLAGS to avoid jobserver inheritance issues when invoked via make
+unset MAKEFLAGS MAKELEVEL
+
+# Capture make env output
+ENV_OUTPUT=$(make env 2>&1)
+
+# Verify AGENTIZE_HOME export is present with $(CURDIR) resolved
+if ! echo "$ENV_OUTPUT" | grep -q 'export AGENTIZE_HOME='; then
+  test_fail "make env missing AGENTIZE_HOME export"
+fi
+
+# Verify PYTHONPATH export is present
+if ! echo "$ENV_OUTPUT" | grep -q 'export PYTHONPATH='; then
+  test_fail "make env missing PYTHONPATH export"
+fi
+
+# Verify the output is valid shell (can be eval'd without error)
+eval "$ENV_OUTPUT" 2>/dev/null
+if [ $? -ne 0 ]; then
+  test_fail "make env output is not valid shell syntax"
+fi
+
+# Verify AGENTIZE_HOME was actually set after eval
+if [ -z "$AGENTIZE_HOME" ]; then
+  test_fail "AGENTIZE_HOME not set after eval \$(make env)"
+fi
+
+test_pass "make env prints valid environment exports"

tests/lint/test-makefile-help-env-targets.sh

@@ -0,0 +1,26 @@
+#!/usr/bin/env bash
+# Test: Makefile help target documents env targets
+
+source "$(dirname "$0")/../common.sh"
+
+test_info "Makefile help target documents env targets"
+
+cd "$PROJECT_ROOT"
+
+# Clear MAKEFLAGS to avoid jobserver inheritance issues when invoked via make
+unset MAKEFLAGS MAKELEVEL
+
+# Capture make help output
+HELP_OUTPUT=$(make help 2>&1)
+
+# Verify env target is documented in help
+if ! echo "$HELP_OUTPUT" | grep -q "make env"; then
+  test_fail "make help missing 'make env' documentation"
+fi
+
+# Verify eval usage hint is present
+if ! echo "$HELP_OUTPUT" | grep -q "eval"; then
+  test_fail "make help missing eval usage hint for env target"
+fi
+
+test_pass "make help documents env targets"

tests/sdk/test-template-env-targets.sh

@@ -0,0 +1,80 @@
+#!/usr/bin/env bash
+# Test: Template Makefiles have env, env-script, and help targets
+
+source "$(dirname "$0")/../common.sh"
+
+test_info "Template Makefiles have env, env-script, and help targets"
+
+TEMPLATES_DIR="$PROJECT_ROOT/templates"
+FAILED=0
+
+for lang in python c cxx; do
+  MAKEFILE="$TEMPLATES_DIR/$lang/Makefile"
+
+  if [ ! -f "$MAKEFILE" ]; then
+    echo "FAIL: $MAKEFILE not found"
+    FAILED=1
+    continue
+  fi
+
+  # Check env target exists
+  if ! grep -q '^env:' "$MAKEFILE"; then
+    echo "FAIL: $lang/Makefile missing env target"
+    FAILED=1
+  fi
+
+  # Check env-script target exists
+  if ! grep -q '^env-script:' "$MAKEFILE"; then
+    echo "FAIL: $lang/Makefile missing env-script target"
+    FAILED=1
+  fi
+
+  # Check help target exists
+  if ! grep -q '^help:' "$MAKEFILE"; then
+    echo "FAIL: $lang/Makefile missing help target"
+    FAILED=1
+  fi
+
+  # Check env target exports PROJECT_ROOT
+  if ! grep -q 'PROJECT_ROOT' "$MAKEFILE"; then
+    echo "FAIL: $lang/Makefile env target missing PROJECT_ROOT"
+    FAILED=1
+  fi
+
+  # Check env-script generates setup.sh
+  if ! grep -q 'setup.sh' "$MAKEFILE"; then
+    echo "FAIL: $lang/Makefile env-script doesn't generate setup.sh"
+    FAILED=1
+  fi
+
+  # Check .PHONY includes new targets
+  if ! grep -q 'env' "$MAKEFILE" | head -1; then
+    echo "FAIL: $lang/Makefile .PHONY missing env"
+    FAILED=1
+  fi
+done
+
+# Verify language-specific exports
+# Python: PYTHONPATH
+if ! grep -q 'PYTHONPATH' "$TEMPLATES_DIR/python/Makefile"; then
+  echo "FAIL: python/Makefile missing PYTHONPATH in env target"
+  FAILED=1
+fi
+
+# C: C_INCLUDE_PATH
+if ! grep -q 'C_INCLUDE_PATH' "$TEMPLATES_DIR/c/Makefile"; then
+  echo "FAIL: c/Makefile missing C_INCLUDE_PATH in env target"
+  FAILED=1
+fi
+
+# C++: CPLUS_INCLUDE_PATH
+if ! grep -q 'CPLUS_INCLUDE_PATH' "$TEMPLATES_DIR/cxx/Makefile"; then
+  echo "FAIL: cxx/Makefile missing CPLUS_INCLUDE_PATH in env target"
+  FAILED=1
+fi
+
+if [ $FAILED -ne 0 ]; then
+  test_fail "Some template Makefiles missing env/env-script/help targets"
+fi
+
+test_pass "All template Makefiles have env, env-script, and help targets with language-specific exports"