@dfm-fi/agent 0.2.823 → 0.2.837

package/dist/cli.js

@@ -54,7 +54,7 @@ function printHelp() {
 }
 async function startMcpServer() {
     // Lazy import so `install`/`help` never pay the cost of building the full
-    // server (loadConfig, 13 tool registrations) and so importing this module
+    // server (loadConfig, 14 tool registrations) and so importing this module
     // never auto-starts the server (mcp-server only auto-starts as an entrypoint).
     const m = await import('./mcp-server.js');
     await m.startServer();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dfm-fi/agent",
-  "version": "0.2.823",
+  "version": "0.2.837",
   "description": "DFM v2 MCP server — drive the full DTF launch → deposit → redeem (+ manage) lifecycle from an AI agent against the live API.",
   "type": "module",
   "bin": {

package/skills.md

@@ -100,8 +100,10 @@ extend expiry. Returns the exact old→new loosening applied.
 
 ### update_vault_assets (write — GATED) — MANAGER
 FULL-REPLACE a vault's basket with new target weights. Only works on a vault YOU
-admin. prepare → sign → submit → confirm. The vault must be in MANUAL rebalance
-mode and outside the 24h config timelock (clear 4xx otherwise).
+admin. prepare → sign → submit → confirm. Every vault is MANUAL (auto-rebalance
+was removed, #35). The config timelock is flag-gated OFF in v1
+(`ENFORCE_DEPOSITOR_GUARDS=false`) — a vault is editable ~10s after create, not
+24h (clear 4xx only if a future deploy re-enables the guard).
 - Input: `vault` (base58), `assets` (1–15, each `{mint,symbol,allocationBps}`;
   allocationBps sum to exactly 10000, no duplicate mints).
 - REMOVING an asset the vault still HOLDS: this tool is order-aware and drains a
@@ -125,18 +127,18 @@ needed for an older vault, one created with rebalancing skipped, or a basket too
 large to bundle the init at create. Reverts on-chain if already initialized.
 - Input: `vault` (base58). Returns the init signature + the `rebalancerConfig` PDA.
 
-### rebalance (write — GATED) — MANAGER
-Execute a rebalance SWAP on a vault the test wallet ADMINS (rebalancer must be
-initialized — bundled into `launch_vault`, or run `init_rebalancer` first). An
-EXPLICIT trade: sell `amountIn` RAW base units of `inputMint` → `outputMint`, BOTH
-already basket assets. One-signature creator-rebalance (approve → execute → revoke).
-On-chain guards are ORACLE-FREE: a measured `min_out` floor + hardcoded velocity
-ceilings (50%/tx, 60s spacing, 48/day) + an output-mint allowlist, so a
-value-leaking route reverts. The API's prepare step still requires fresh
-sponsored Pyth price feeds for both legs (an off-chain quality gate) — on a 503
-"momentarily stale", retry in a few seconds.
-- Input: `vault`, `inputMint`, `outputMint` (base58), `amountIn` (raw base-unit
-  string), optional `slippageBps` (1–300). Returns the rebalance signature.
+### rebalance_to_targets (write — GATED) — MANAGER
+Converge a vault the test wallet ADMINS toward its CURRENT config target weights
+(rebalancer must be initialized — bundled into `launch_vault`, or run
+`init_rebalancer`). The free-form swap tool (`inputMint`/`outputMint`/`amountIn`)
+was REMOVED (#57): a rebalance ONLY converges holdings to the declared targets —
+the config is the source of truth. One-signature creator-rebalance (approve →
+execute → revoke). On-chain guards are ORACLE-FREE: a measured `min_out` floor +
+hardcoded velocity ceilings (50%/tx, **5s** spacing, 48/day) + an output-mint
+allowlist. **No Pyth feed / price-posting gate** — the oracle-free redesign
+removed it; deviations are computed off-chain (Pyth→Switchboard→Jupiter cascade)
+purely to size the converging legs.
+- Input: `vault` (base58), optional `slippageBps` (1–300). Returns the signature(s).
 
 ## Key concepts