fix(release): republish @mosaicstack/db 0.0.4 with BacklogService; mosaic 0.0.47

mosaic 0.0.46 ships a fleet-backlog command that bare-imports
{ BacklogService, DEFAULT_CLAIM_TTL_SECONDS } from @mosaicstack/db, but
db's version was never bumped after #657 added backlog.ts. The publish
pipeline tolerates "version already exists", so db's new code was never
republished — the registry's db@0.0.3 is the stale pre-#657 artifact with
no BacklogService export. mosaic 0.0.46 (workspace:* -> 0.0.3) therefore
installs the stale db and crashes at CLI entry on every command:

  SyntaxError: The requested module '@mosaicstack/db' does not provide
  an export named 'BacklogService'  (dist/commands/fleet-backlog.js:19)

Verified from registry tarballs: mosaic@0.0.46 declares db as a regular
(non-bundled) dependency at 0.0.3; db@0.0.3 dist exports no BacklogService.
A mosaic-only republish would re-pin 0.0.3 and crash identically, so the
db version bump is mandatory.

Fix: bump @mosaicstack/db 0.0.3 -> 0.0.4 (forces republish WITH
BacklogService past the version-exists gate) and bump mosaic 0.0.46 ->
0.0.47 so workspace:* resolves to db@0.0.4 at publish. pnpm-lock.yaml is
unchanged (workspace deps link by path, not version).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/fleet/north-star.md

@@ -353,6 +353,25 @@ re-evaluate if isolation or write-volume demands it.
 - **Docs as projections:** `docs/TASKS.md` and `MISSION-MANIFEST.md` become generated exports of the DB, not hand-maintained.
 - **Sub-decision pending:** dedicated schema in existing PG instance (recommended) vs. dedicated PG instance. Revisit if isolation or write-volume demands it.
 
+## Decisions of record (2026-06-24, with Jason)
+
+- **Per-agent model switch (operator-configurable, NOT a global lock):** model selection is
+  **per-agent**, never a host-global pin. Claude sessions MUST NOT be locked to a single model in
+  `~/.claude/settings.json`; each agent chooses its model independently. The plumbing already exists —
+  roster `model_hint` → `MOSAIC_AGENT_MODEL` → `start-agent-session.sh` appends `--model <hint>` to that
+  agent's harness (claude or pi); settable today via `mosaic fleet add|edit <agent> --model <hint>`.
+  **North-star target:** surface this as a **per-agent model switch in the webUI** (with CLI/TUI parity
+  per MVP-X1) — read the roster, expose a per-agent model dropdown, write `model_hint` back, and restart
+  that one agent to apply. Unset = inherit the harness default. This **composes with** the budget
+  downgrade ladder (opus → sonnet → haiku, then Claude → Codex): the operator sets the per-agent model
+  _intent/ceiling_; budget pacing may downgrade within policy. Tracked as a Fleet `TASKS.md` entry under
+  the Phase-5 webUI surface.
+- **Orchestrator runtime (confirmed live):** the **orchestrator and enhancer run Claude Opus 4.8 in the
+  Claude Code harness**; only workers (coder/reviewer) run pi/gpt-5.5. Consistent with the 2026-06-20
+  "Claude reserved for Claude Code only" decision (the orchestrator runs _in_ Claude Code, not an
+  alternate Claude harness). Pi/gpt-5.5 as the orchestrator is permitted **only if proven** at least as
+  satisfactory; absent that proof, the orchestrator stays on Claude Opus 4.8.
+
 ## Future enhancements (north-star, post-MVP — not on the MVP track)
 
 - **Mosaic Claude Discord Plugin** — a first-party Mosaic Discord connector that properly

packages/db/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mosaicstack/db",
-  "version": "0.0.3",
+  "version": "0.0.4",
   "repository": {
     "type": "git",
     "url": "https://git.mosaicstack.dev/mosaicstack/stack.git",

packages/mosaic/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mosaicstack/mosaic",
-  "version": "0.0.46",
+  "version": "0.0.47",
   "repository": {
     "type": "git",
     "url": "https://git.mosaicstack.dev/mosaicstack/stack.git",