Problem

backend/langgraph.json declares dependencies on . from the backend workspace. This installs the whole backend app rather than exercising deerflow-harness as its own package. Existing boundary tests can pass because the monorepo/backend layout masks standalone harness packaging issues.

Impact

Packaging regressions in packages/harness can be missed until users try to consume the harness package outside the backend source tree.

Suggested Fix

Point LangGraph dependencies at ./packages/harness where appropriate, and add CI that builds/installs deerflow-harness into a temporary environment outside the repo before importing the graph.

Tests

• CI job builds the harness wheel.
• Install the wheel into a clean temporary venv.
• Import/create the graph without relying on backend app package paths.

References

• backend/langgraph.json:4
• backend/pyproject.toml:6
• backend/tests/test_harness_boundary.py:15