Put Worktui on every agent trail

[woltspace-jerpint]

Agent shells could see the Worktui skill but could not invoke wt: the command only existed as a .bashrc function, non-interactive bash returned before sourcing it, and the function resolved ~/worktui against each wolt-scoped HOME. The map pointed to a tool that was not actually on the trail.

What changed

• add an executable container/bin/wt entry point, already covered by every session PATH
• resolve the image-owned Worktui install at /home/node/worktui without depending on wolt HOME
• retain the interactive shell function for its directory-switching convenience
• update the derived skill contract and add regression coverage for executable mode and HOME-independent resolution

Verification

• uv run --extra test pytest -q test/test_wolts.py — 47 passed
• container/bin/wt list --json — succeeds from a wolt-scoped non-interactive shell
• bash -n container/bin/wt
• git diff --check

The agents can follow the Worktui trail again. 🦝

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
woltspace	Ready	Preview, Comment	Jul 23, 2026 9:19pm