dsh-agy-link 0.4.70 → 0.4.74

package/docs/KNOWN-GAPS.md

@@ -107,9 +107,32 @@ reference-counted slot is the strongest isolation the plugin can provide.
 - **DSH tools to agy (reverse MCP bridge)** - available since v0.2 behind the
   `mcpBridge` config flag (experimental): the plugin runs a loopback-only,
   token-guarded HTTP endpoint and registers a zero-dependency stdio MCP
-  server (`dsh-tools`) in the workspace `.mcp.json` (merged in, restored on
-  disable). `run_code` and `agy_ask` are never bridged; `mcpToolAllowlist`
-  restricts the set further.
+  server in the MCP registry (`~/.gemini/config/mcp_config.json` by default,
+  where `agy` 1.4+ actually reads it, merged in and restored on disable).
+  Bridged calls carry caller identity via `DSH_MCP_SESSION` so identity-enforcing
+  tools (such as `agent_teams`) function correctly. `run_code` and `agy_ask`
+  are never bridged; `mcpToolAllowlist` restricts the set further.
+  Every bridged call is audit-logged as `mcp call <tool> [<outcome>] <ms>` with
+  the caller class and the failure text (never the arguments), so a failed run
+  is visible in journald instead of only in transcripts.
+- **DSH `send_message` from an agy child** - DSH's sub-agent runtime appends a
+  footer telling the child to report with `send_message({ agent_id: <parent> })`.
+  In an agy run that name resolves to agy's **own** `send_message`, which does
+  not know DSH agent ids and fails with `recipient "..." not found`. The DSH
+  tool itself is bridgeable - add `send_message` to `mcpToolAllowlist` and call
+  it explicitly on the `dsh-tools-<port>` MCP server (agy dispatches MCP calls
+  by server + tool name, so there is no collision with the native tool). The
+  footer still names the native one, so an agy member should report through
+  `agent_teams_send_message` (or an explicit instruction) instead. Root cause is
+  upstream in `@deepseek-ai/dsh-subagent`, which assumes a DSH-native child.
+- **Weekly quota auto-warmup is opt-in (v0.4.74+)** - `autoWarmup` defaults to
+  `false` because the feature deliberately bypasses the CLI-first quota path and
+  sends minimal `loadCodeAssist` + `generateContent` probes straight to Google's
+  internal endpoints. When enabled it scans every 5 minutes, only targets rows
+  whose `weeklyFraction` is explicitly >= 99.9%, records a 30-minute failure
+  backoff, skips accounts in cooldown / auth quarantine, and never guesses a
+  missing `cloudaicompanionProject` (no shared fallback project id). The manual
+  "Warmup" buttons still work while auto mode is off.
 - **Full tool args / diff cards (v0.4.28+)** - the bridge reads agy's
   conversation SQLite DB via the `sqlite3` CLI to recover arguments that
   `filterToolParameters` strips from stream-json. When `sqlite3` is missing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-agy-link",
-  "version": "0.4.70",
+  "version": "0.4.74",
   "description": "Google Antigravity (agy CLI) models for DeepSeek Harness — stream Gemini/Claude/GPT-OSS subscriptions into DSH with thinking, tool activity, token usage and in-GUI Google OAuth login.",
   "type": "module",
   "license": "MIT",