fix: rename all packages from @mosaic/* to @mosaicstack/*

- Updated all package.json name fields and dependency references
- Updated all TypeScript/JavaScript imports
- Updated .woodpecker/publish.yml filters and registry paths
- Updated tools/install.sh scope default
- Updated .npmrc registry paths (worktree + host)
- Enhanced update-checker.ts with checkForAllUpdates() multi-package support
- Updated CLI update command to show table of all packages
- Added KNOWN_PACKAGES, formatAllPackagesTable, getInstallAllCommand
- Marked checkForUpdate() with @deprecated JSDoc

Closes #391

docs/reviews/consolidation-board-memo.md

@@ -302,7 +302,7 @@ a fully open-source, self-contained AI development pipeline
 framework. The Forge pipeline, MACP protocol, and credential
 resolver together form a complete agentic development system.
 Packaged correctly, this could be published as
-@mosaic/forge + @mosaic/macp — reusable by any team building
+@mosaicstack/forge + @mosaicstack/macp — reusable by any team building
 AI-native development workflows. The mosaic-stack repo becomes
 a reference implementation. Other organizations adopt the
 protocol. MACP becomes a standard.
@@ -335,7 +335,7 @@ runtime; packages/forge becomes the brain. These should be
 designed as separable concerns from the start.
 
 DEFERRED OPPORTUNITIES:
-- Publish @mosaic/forge to npm (after consolidation stabilizes)
+- Publish @mosaicstack/forge to npm (after consolidation stabilizes)
 - MACP as an open protocol spec with multiple implementations
 - Forge pipeline as a configurable product (enterprise personas,
   custom stage sequences, SLA-based gate configuration)
@@ -539,7 +539,7 @@ is listed in WP2's scope (`learning_capture.py` + `learning_recall.py`).
 If OpenBrain's interface is undefined, why is it in WP2 either?
 Cut it from both WP2 and WP1. Make it a separate brief.
 
-To the Moonshot: The "publish @mosaic/forge to npm" idea is
+To the Moonshot: The "publish @mosaicstack/forge to npm" idea is
 premature. Publishing a package externally means committing to
 a public API and semver guarantees. Mosaic's pipeline is
 actively evolving. Publishing now creates external consumers
@@ -1223,7 +1223,7 @@ consideration. They are NOT in scope for this consolidation.
   memory capture/recall. Requires a standalone brief once
   the interface is defined. High long-term value.
 
-- @mosaic/forge external publication: After the consolidated
+- @mosaicstack/forge external publication: After the consolidated
   package stabilizes, evaluate publishing as an open-source
   framework. Requires API freeze and semver commitment.