mcp-workbay-handoff

# WorkBay Handoff MCP > **Component of the `workbay` stack.** You usually install `workbay`, not this package directly. Portable MCP server for agent handoff state, review findings, exports, close checks, and lane-scoped worker/orchestrator coordination. ## Scope This package owns handoff state and related workflow primitives: - task state, decisions, blockers, and next actions - review findings and review runs - generated `CURRENT_TASK.json` snapshots - lane registration, lane activity, worker reports, and lane messages - artifact indexing and derived metrics snapshots It does not include unrelated repo-intel or UI helpers. ## Runtime State By default, runtime state lives under the workspace you point the CLI at: - SQLite DB: `.task-state/handoff.db` - exports: `.task-state/exports/` - generated markdown: `CURRENT_TASK.json` Override these with CLI flags or `WORKBAY_HANDOFF_*` environment variables. Legacy pre-rebrand names are still read for one release. ### Tuning compaction thresholds The compaction advisory (`get_handoff_state(sections="identity").compaction_advisory`) compares observed token and char totals against thresholds. The single source of truth for the canonical defaults is the `compaction:` block of `docs/workbay/contracts/harness-protocol.yaml` (`threshold_tokens`, `threshold_chars`); see that file for the current values and the rationale comment above them. Per-deployment overrides resolve with precedence **env > overlay > contract**, per knob, every call (no module-level cache): 1. **Environment variables**: - `WORKBAY_HANDOFF_COMPACTION_THRESHOLD_TOKENS=<int>` - `WORKBAY_HANDOFF_COMPACTION_THRESHOLD_CHARS=<int>` 2. **`.workbay-bootstrap.json`** at the workspace root, via the `compaction.thresholds` key (`tokens` and `chars` must be non-negative integers; the legacy `.workbay-overlay.json` name is still read as a fallback; the values below are illustrative overrides, not required values): ```json { "compa…