v0.4.1 — entry points actually ship
forge v0.4.1 — entry points actually ship
A packaging fix, no functional change. Found while verifying v0.4.0's published artifact: installing
from the tag put only main.py into site-packages, so a pip install could not run the two entry
points the docs tell you to run — you had to clone the repo.
Fixed
executor_agent.py(#17 client executor) anddevice_sim.py(#16 device-side simulator) are now
installed with the package- two console scripts join
forge:forge-executor --center http://<centre>:8080 --token <KEY> --id pc-01 --root D:/work— the
executor to run on a controlled PCforge-device-sim --transport socket --port 9130— the hardware simulator that speaks protocol v1
Verified
- v0.4.0's artifact (installed from the tag):
/healthzand/api/statusreport 0.4.0,/docsis
up, and all six/api/executor/*routes are present - v0.4.1's artifact (installed from the tag): version 0.4.1 in both places,
forge-executorand
forge-device-simon PATH, andforge executor --list-capsreporting the machine's real
capabilities
Upgrading
pip install --upgrade "handcraft-agent[server,device] @ git+https://github.com/musokean/forge.git@v0.4.1"