fix: re-enable pre-commit in devcontainer

[prql-bot]

Summary

• Re-enables pre-commit installation in the devcontainer postCreateCommand, which was disabled due to Field Report from using Vite build... #3709 (now closed)
• The install-python-deps command now runs task install-maturin && task install-pre-commit && pre-commit install-hooks as originally intended

Closes #5768

🤖 Generated with Claude Code

[prql-bot]

task install-pre-commit doesn't exist — there's no such task defined in Taskfile.yaml (or anywhere else in the repo). The original commented-out line had this same nonexistent command, so re-enabling it as-is will cause the postCreateCommand to fail during devcontainer setup.

The setup-dev task (Taskfile.yaml:89) runs pre-commit install-hooks directly — no wrapper task. The devcontainer line should probably just do the same.

[max-sixty]

@prql-bot why doesn't CI test for the devcontainer? can we adjust this so it does?

[prql-bot]

The build-devcontainer job only triggers when Dockerfiles, the build workflow, or Taskfile.yaml change — devcontainer.json itself isn't in the trigger list. So changes to postCreateCommand (like this PR) don't get tested.

The existing smoke test in build-devcontainer.yaml builds the base Docker image and runs cargo test + mdbook build inside it, but never exercises the postCreateCommand steps from devcontainer.json.

Two options to fix this:

Option A — Add devcontainer.json to the trigger paths and test postCreateCommand in the base image. Add .devcontainer/devcontainer.json to the devcontainer-build path filter, then add a step that runs the postCreateCommand commands (task install-maturin && uv tool install pre-commit, task install-npm-dependencies) inside the base image container. This is lightweight but doesn't test devcontainer features (Python, Node, go-task, etc. are installed via features, not the base image).

Option B — Use devcontainers/ci to build the full devcontainer. The devcontainers/ci action can build and run the full devcontainer including features and postCreateCommand. This tests the actual developer experience but is heavier (installs all features from scratch each time).

I'd lean toward Option A as a pragmatic first step — it would have caught the task install-pre-commit issue in this PR. Want me to implement one of these?

[max-sixty]

can we try B?

[prql-bot]

Done — added a test-devcontainer job that uses devcontainers/ci to build the full devcontainer (base image + features + postCreateCommand) and verify that key tools are available (task, pre-commit, cargo, node). Also added devcontainer.json to the path filter so changes to it trigger the test.

[prql-bot]

The test-devcontainer job failed because uv isn't installed in the devcontainer — task install-maturin calls uv tool install maturin but no feature provides uv. This was a pre-existing issue (the install-maturin step would also fail without uv), just not caught because the existing build-devcontainer job doesn't exercise postCreateCommand.

Pushed a fix that installs uv via pip install uv before running the tasks that need it.