The Hub routes by the project name in its human-owned routing.md, which
already names this project `internet_control` (the placeholder row from the
Hub brief). The frozen contract requires the /capabilities name to match that
row, so /capabilities now reports `internet_control` as well.
Found while wiring the live Hub (approved confirmation 60b235f3): the Hub
routed the screen-time question to `internet_control` and returned
`no_client` against a project registered as `internet_use_control`. Aligning
the name, rather than editing the Hub repository or its routing file, makes
the end-to-end round-trip work.
Live proof after the rename and the Hub registration:
POST http://192.168.20.13:8788/ask
{"text":"how long have the kids been on screen today?","asker":"sam","source":"console"}
200 {"status":"ok","answer":"The kids have had 1h 22m of screen time today.",
"route":{"kind":"project","project":"internet_control"}}
Repository, module and service names are unchanged; only the Hub-facing
project string changed.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Sam Rolfe
8c42daf4d9