[codex] ship toolcraft help renderer release

[kamilio]

Summary

• Bump @poe-code/design-system metadata to 0.0.2 and checked-in toolcraft metadata to 0.0.4.
• Align toolcraft-openapi workspace dependency ranges with the bumped design-system/toolcraft metadata so npm ci can resolve local workspaces.
• Change generated root help from Global options to Options, keeping commander -h, --help out of generated option rows.
• Update focused CLI help snapshots/assertions for the new output.

Validation

• npm run build -w @poe-code/design-system
• npm run build -w toolcraft
• npm run test -w toolcraft -- packages/toolcraft/src/cli.test.ts packages/toolcraft/src/renderer.test.ts
• npm ci --ignore-scripts --no-audit --no-fund in a clean worktree
• GitHub trusted-publishing workflow run 25862723867
• ashby smoke against published toolcraft@0.0.16: root/calendar help commands plus todo lists --yes

Release note

Trusted publishing ran from GitHub Actions and published toolcraft, toolcraft-schema, and toolcraft-openapi at 0.0.16. I did not publish from local.

[poe-code-agent]

Requested changes: npm ci no longer resolves workspace dependencies.

[poe-code-agent]

This version bump leaves packages/toolcraft-openapi/package.json pinned to @poe-code/design-system ^0.0.1. Since the workspace package is now 0.0.2, npm no longer satisfies that range locally and falls back to the registry; npm ci fails with a 404 for @poe-code/design-system@^0.0.1. Please update that workspace dependency and regenerate package-lock.json, or keep this package at 0.0.1.

[poe-code-agent]

Requested changes: npm ci still cannot resolve toolcraft-openapi's workspace dependency.

[poe-code-agent]

toolcraft was bumped to 0.0.4, but this workspace still depends on ^0.0.1 (which only accepts <0.0.2), so npm ci --ignore-scripts fails with Missing: toolcraft@0.0.1 from lock file. Please update this range and refresh package-lock.json.

Suggested change

	"toolcraft": "^0.0.4",
	"toolcraft": "^0.0.4",

[poe-code-agent]

LGTM