chore(cli): put weaver on PATH and scope the package name

[SunkenInTime]

What

Two changes from the render-loop cadence experiment's open items.

npm run link puts weaver on PATH. npx --no-install weaver works only inside the repository tree; from a widget directory anywhere else, npm walks up, finds no workspace, and consults the registry:

npm error npx canceled due to missing packages and no YES option: ["weaver@0.3.1"]

That is not our package. Public npm weaver is an "Interactive process management system" last published 2022-06-28. Without --no-install it would be downloaded and run. Several agents read this error as a widget problem, and weaver init's "Next: weaver check

" hint named a binary that was not on PATH. The root script link runs npm link --workspace cli; the README quickstart uses it and invokes weaver … directly (14 node cli/bin/weaver.js invocations replaced).

The CLI package is @weaver/cli. A scoped name no one else can claim; @weaver/cli, @weaver/sdk, and @weaver/weaver all return 404 on the registry today. The bin stays weaver, the workspace is referenced by path, and nothing in scripts or CI referenced the old name.

Verified

• After npm run link: which weaver → global bin symlink → lib/node_modules/@weaver/cli/bin/weaver.js.
• From /tmp: weaver check <out-of-tree widget> passes.
• npm test 117 passed.

Companion: #81 changes the conjure skill to invoke weaver … and states the npx caveat.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[greptile-apps]

Greptile Summary

This change lets developers link the repository’s CLI once and invoke it as weaver, scopes the CLI package as @weaver/cli, and updates shell quickstart commands.

Using isolated writable npm prefixes, the linked command was verified from outside the repository. It was unavailable before linking, then resolved to the local CLI wrapper after linking; weaver init completed successfully and created a widget.

Confidence Score: 5/5

Safe to merge for the verified local CLI linking workflow.

The two relevant user-facing failures were exercised using writable npm prefixes: linking selected the intended workspace, and invoking the installed command from outside the repository reached the expected entry point and initialized a widget successfully.

Files Needing Attention: No files need follow-up for the verified linking behavior.

T-Rex Logs

What T-Rex did

• Validated that starting from an empty npm prefix, the repository link script resolves through @weaver/cli to the repository's cli/bin/weaver.js.
• Linked the CLI into a separate prefix and ran weaver init linked-entrypoint-proof outside the repo, creating the requested widget.
• Verified the PATH-based resolution and that after linking, the installed CLI maps to the repository script, and that weaver status runs but exits due to Linux support limitations, confirming the command is present.
• Captured the end-to-end linking and entrypoint generation, showing the wrapper resolution and widget.tsx creation as part of the linked-entrypoint-proof workflow.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore(cli): put `weaver` on PATH and sco..." | Re-trigger Greptile}