chore: switch devcontainer to node-agentic, drop Python

[pofallon]

The backend is Bun + TypeScript, so python-agentic no longer matches the stack. Rebased on node-agentic, keeping this repo's two local customizations on top: CLAUDE_CONFIG_DIR and the ~/.claude + ~/.config/gh credential mounts.

Bun

Comes from the template's node-dev-tools feature. Its default installs everything, so bun would arrive either way, but it's named explicitly since it's this project's runtime, test runner and package manager rather than an optional extra:

"ghcr.io/get2knowio/devcontainer-features/node-dev-tools:2": {
    "install": "typescript,bundlers,linters,watchers,bun"
}

postCreateCommand now runs bun --version too, so a broken install fails the build instead of surfacing later.

Dropping Python

Nothing here needs it — no .py files, no pyproject.toml / requirements.txt / Pipfile / poetry.lock, and nothing in the workflows or scripts shells out to Python.

There's exactly one Python consumer: Spec Kit's agent-context hook, enabled in .specify/extensions.yml, which needs a python3 that can import yaml. python-tools was never satisfying it. In a container built from the old config, with both python and python-tools installed:

$ python3 -c "import yaml"
ModuleNotFoundError: No module named 'yaml'

That feature installs uv/Poetry/ruff/mypy, none of which put PyYAML on the system interpreter, and PEP 668 blocks a plain pip install into it. The hook has been silently skipping — and because it exits 0, it read as "nothing to do" rather than "broken."

Fixing the hook

The script honors $SPECKIT_PYTHON, and the uv tool venv specify itself lives in already ships PyYAML 6.0.3, so containerEnv now points at it. The hook goes from skipping to:

$ bash .specify/extensions/agent-context/scripts/bash/update-agent-context.sh
agent-context: updated CLAUDE.md

If that interpreter ever goes missing the script falls through to python3/python and skips cleanly, so it can't hard-fail. This is a local workaround for get2knowio/devcontainer-features#77 — ai-clis installs Specify with uv tool install, which isolates the venv, and should expose the interpreter itself. This line can be dropped once that ships.

CLAUDE.md

Turning the hook on for the first time exposed a latent problem: the hand-written "Key design artifacts" list sat inside the <!-- SPECKIT START/END --> markers, so the generator wiped it on first run. Moved below the markers with a comment explaining why, and verified a re-run now leaves it intact.

Left as-is, the first /speckit-plan or /speckit-specify after a rebuild would have quietly deleted it.

Also

node_modules/ was missing from .gitignore entirely — it showed as untracked and was one git add . away from being committed. Added, and replaced the now-dead Python ignore entries (__pycache__, .mypy_cache, .ruff_cache, .venv, …), keeping dist/ and build/ which apply to Node too.

README updated — it still described the container as python-agentic with "Python tooling: uv, Poetry, ruff, mypy".

Testing note

The container this was authored in was built from the old config, so the new one hasn't been built end to end yet — worth a Rebuild Container before merging. The JSONC parses, and the SPECKIT_PYTHON path and hook behavior were verified live.

🤖 Generated with Claude Code

https://claude.ai/code/session_013CvCDKqHEKtVjg1hMbWdv7