pynchy-development

# Pynchy Development Run commands directly—don't tell the user to run them. ## Am I on pynchy? Check `hostname` and compare it with the deployment-specific live host from local memory, environment, or the operator. If you are on that host, access services at `localhost`. Otherwise, reach Pynchy over SSH or Tailscale using that configured host. ## Commands ```bash uv run pynchy # Run the app uv run pytest tests/ # Run tests uv run ruff check --fix src/ # Lint + autofix uv run ruff format src/ # Format uvx prek run --all-files # Run all repository hooks ./src/pynchy/agent/build.sh # Rebuild agent container ``` ## Isolated feature runtimes Use `new-feature` from the control checkout when a feature needs an isolated Pynchy runtime. See [the feature-runtime workflow](../../../docs/contributing/new-feature.md) for create, merge, restart, and teardown commands. Do not use raw `git worktree` commands for managed features. Install or verify its host dependencies with `./scripts/install_new_feature_dependencies.py`. ## Documentation Lookup When you need documentation for a library or framework, use the context7 MCP server to get up-to-date docs. Don't rely on training data for API details that may have changed. ## Testing Philosophy Write tests that validate **actual business logic**, not just line coverage. See [references/testing-philosophy.md](references/testing-philosophy.md) for what makes a good test vs. coverage theater. ## Known Issues - ...