Hugs
Asking
Building
cliq hug build names the file and the rule it breaks: a binary file (inline it — the build inlines assets by
default), an outside URL, too many files or bytes, a missing hug.json or definition.mjs. cliq team publish
refuses a team hug whose dist/ is out of date — cliq hug build hugs/<name>, or publish with --build.
On the page
Errors a page’s code can see (HugError, with a code):
An answer isn’t accepted: the agent checks every answer with the definition. One that fails isn’t counted — the
run’s log says why (“the answer from Ann couldn’t be used — …”), and the page shows “1 answer couldn’t be used;
waiting for a valid one”. The page and the agent use the same definition, so this usually means the answer didn’t come
through the page (a script, an older bundle).
The page is blank: open the browser’s console on the Hug page. A page that loads anything from outside its bundle
is blocked by its Content Security Policy;
cliq hug dev reports the same.