feat(cli): default static registry for lousho add out of the box (M7b, #230)

[LinuxDevil]

Closes #230

Summary

• lousho add works out of the box: with neither --registry nor LOUSHO_REGISTRY it reads DEFAULT_REGISTRY (https://registry.lousho.com/index.json, the issue's recommended option a) instead of failing with "no registry configured; there is no hosted registry yet".
• New registry/ folder with the five starter items — open-meteo-weather and github-issues tools, changelog and code-review skills, generic-webhook channel — each an item.json plus source files, and the committed generated registry/dist/ (index.json + one document per item).
• scripts/build-registry.ts validates every item with the now-exported IndexSchema/ItemSchema, the planFiles path rules and M7a's checkItem(), then writes deterministic sorted output. npm run registry:build regenerates it; the new npm run registry:check (wired into the CI job) fails when dist is stale.
• Precedence is --registry > LOUSHO_REGISTRY > default; --registry none / LOUSHO_REGISTRY=none disables the registry and preserves the LOUSHO_CONFIG_INVALID "no registry configured" error.
• Offline tests: src/cli/defaultRegistry.test.ts installs all five committed items via runAdd and loads the agent directory with resolveAgentDir() (tools and skills resolve, the channel default-exports a channel). add.test.ts covers the default fetch, none and both overrides.
• docs/registry.md, README.md, CHANGELOG.md and regenerated llms-full.txt.

Design decisions

• One constant for the hosting answer: DEFAULT_REGISTRY in src/cli/registry.ts is the single place the URL lives, so the owner's pending choice between options (a)/(b)/(c) is a one-line change. Set to the recommended https://registry.lousho.com/index.json.
• No Pages workflow yet: hosting is the owner's call, so no deployment workflow is added; committed registry/dist/ works with any of the three options, including github.com/ghraw as-is.
• Source folders + committed static JSON: registry/<name>/ folders stay maintainable while consumers only read static JSON — the registry source is never executed by lousho add.
• none sentinel: an explicit opt-out for offline or locked-down use that keeps the previous error path and code byte-for-byte.
• Shared validation: the build reuses ItemSchema, planFiles and checkItem, so an item cannot pass the registry build and then fail lousho add.
• Package boundary preserved: package.json files is untouched; registry/ is not shipped in the npm tarball.
• Fallow: scripts/build-registry.ts carries the same // fallow-ignore-file complexity as the other scripts, and registry/** joins health.ignore — installed item code is not exercised by repo coverage, so its CRAP score would only be noise.

Tests

• npx tsc --noEmit — clean
• npm run lint — clean
• npm run build, npm run build --workspace=packages/create-lousho-agent — clean
• npm run test:types — 79 pass
• npm run test:coverage — 4230 pass / 8 skipped, including the new defaultRegistry.test.ts
• npm run docs:verify-snippets — 258 snippets type-check (8 run cleanly)
• npm run docs:llms:check, npm run registry:check — clean
• Agent Forge: typecheck, typecheck:server, vitest run (119 tests), test:server (133 tests) — all pass

Pre-existing failures (identical on baseline, unrelated):

• npm run pack-smoke: tarball unpacked size 16,982,166 exceeds the 16,777,216 cap; baseline is 16,976,834 and already over (this change adds ~5 KB; registry/ is not shipped).
• npm run fallow: 10 circular dependencies, 5 clone groups and 6 complexity findings, all in pre-existing files — this change adds no findings.

Live test spend: none — the ticket has no live test and all new tests are offline.

🤖 Generated with Devin