Raven-1/tests/test_proactive_spawn.py
Handsome-wzw 7b45527b5b fix(tools): an array sent as its own JSON is still an array
## Summary

Reported as "deliver_files is broken". It is not: **the tool never ran.**

Every `deliver_files` call on one install was refused before dispatch -- five in a row in a single session -- and nothing was ever delivered:

```
Error: Invalid parameters for tool 'deliver_files': files should be array
```

What the model sent was the array, spelled as a string:

```json
{"files": "[{\"path\": \"...poster.png\", \"title\": \"...\"}]", "message": "..."}
```

`cast_params` already forgives that spelling for every scalar type -- `"3"` for an integer, `"true"` for a boolean -- and did not for arrays or objects, which are exactly the types a model is most likely to stringify.

## Type

- [x] Fix
- [ ] Feature

## The edge of the forgiving is the design

When the value is a string, try `json.loads`, and take the result **only if it is the type the schema asked for**. A string that is not JSON, or is JSON of the wrong shape, is returned unchanged so the validator still names the real problem -- the point is to widen what is accepted, not to swallow a type error.

**Nothing here can raise.** Turning "your argument has the wrong type" into a traceback would be worse than the refusal it replaces, so the parse is wrapped and failure falls through.

**A `type: "string"` field is never parsed.** JSON is ordinary text in a message body or a file's content, and replacing it would hand the tool something it never asked for. Two independent things prevent it today (the string branch returns before the parse is reached, and the parse only wins on a type match), which is why the case pinning it is a tripwire rather than a load-bearing assertion -- said so in its own docstring rather than left to look like coverage.

## Not just deliver_files

Six built-in tools declare an array or object parameter and were all exposed:

| tool | parameter |
|---|---|
| `deliver_files` | `files` |
| `ask_user` | `questions` |
| `image_generate` | `images` |
| `message` | `media` |
| `create_playbook` | `skills` |
| `video_generate` | `params` |

The same failure was already seen from the other side: `acp_client/acp_agent.py` records `update_task_state` and `operations should be array` from a real dispatch.

## Verification

```
make lint-python    ruff check + ruff format --check, 1850 files
make lint-imports   9 contracts kept, 0 broken
pytest tests/       19,699 passed, 7 failed (all pre-existing, see below)
```

- [x] Relevant tests pass locally
- [x] Relevant lint / type checks pass locally
- [ ] User-facing docs or screenshots -- no user-facing string

**End to end, through the real tool**, with the exact payload that failed five times in production:

```
files sent as:            str -> [{"path": ".../poster.png", "title": "..."}]
returned:                 Delivered 1 file(s): poster.png (72 B).
still "should be array":  False
registered in the store:  True
```

Twelve cases, five mutations, each killing at least one:

| mutation | red |
|---|---|
| drop the whole branch (the old behaviour) | 3 |
| raise instead of falling through on a parse failure | 5 |
| accept the parse whatever type it yielded | 1 |
| do not re-cast the parsed value, so items are not cast | 1 |
| widen the tuple to include `string` | **survived -- unreachable** |

The last is worth stating rather than hiding: that mutation cannot change behaviour, because the `type == "string"` branch returns earlier and the type check would refuse the result anyway. I also tried moving the new block above that branch, alone and combined with widening the tuple, and neither reddens anything either. The invariant holds by construction; the case that documents it says so.

**Pre-existing failures, checked against the base.** 7 failed in the full run, all in `tests/test_security_network.py` (`test_a_redirect_to_a_dangerous_address_is_refused` and siblings). Running that file alone on this same tree gives 4 -- the count is order-dependent -- and the change touches only `raven/agent/tools/params.py` plus a new test file, neither of which `raven/security/network.py` imports. The failures are the box's resolver: it returns poisoned answers roughly half the time, which I measured separately (`en.wikipedia.org` came back as `2001::1` on 3 of 6 lookups). Not introduced here, and worth someone's attention on its own.

## Risk

- [x] Security impact considered -- widens what reaches a tool's own validation, not what bypasses it. A parsed value is still validated against the same schema, and a parse that yields the wrong type is refused exactly as before
- [x] Backward compatibility considered -- a call that worked before takes the identical path; the new branch is reached only by a `str` where an array or object is declared, which previously always failed
- [x] Rollback path is clear -- single-commit revert

## Related Issues

N/A

## Swept

`mr-review-patterns` pre-submit sweep, over `git diff origin/main...HEAD`.

- **1 (a write location moved)** -- nothing moved; a branch was added to an existing dispatch on `target_type`. Grepped every caller of `cast_params`: the registry is the only one, and it runs `validate_params` right after, which is the reader this affects.
- **2 (a value with several entry points)** -- the cast is the single funnel every tool argument passes through, which is why the fix belongs here and not in `deliver_files`.
- **3 (a guard)** -- checked both directions: what it wrongly lets through (JSON of the wrong type, non-JSON text -- both refused, with cases) and what it wrongly refuses (a real list, unaffected, with a case).
- **4 (tests)** -- five mutations above, one honestly reported as unreachable. Failing-ID sets diffed against the base rather than counts.
- **6 (stale text)** -- the module docstring enumerated what is coerced ("a string that should be an integer"); it now names arrays and objects too. Grepped the tracked tree for other statements of the rule: none.
- **9 (error handling)** -- the new path adds one way to end and it is caught: `json.loads` raises `ValueError` on bad text and `TypeError` on a non-string, and both fall through to the untouched value.
- **11** -- `git ls-files | grep -c node_modules` is 0; the commit-message gate was run, not eyeballed.

Not applicable, with reasons: **3b, 3c, 3d, 3e** (no tool schema produced, no state moved, one lane, no assertion lost its symbol); **4b, 4c, 4d** (no platform branch, no shell, no rendered number); **5, 5b** (no dependency; `json` is stdlib and already imported across this package); **6b, 6c** (no backup, no generated artifact); **7, 7b** (nothing on disk); **8** (no asset, no secret); **10** (no prompt text).

## Deliberately not fixed

The error text still ends with `[Analyze the error above and try a different approach.]`, and the model plainly did not -- it sent the same shape five times. A message naming the expected spelling (`files must be a JSON array, not a string containing one`) would give it something to act on. That is a change to the registry's error surface, affects every tool, and deserves its own argument.

## Moved from !594

Opened on a compliant source branch. AGENTS.md 2.1 asks for a 3-5 word snake_case description and the previous branch had seven; GitLab cannot change an existing merge request's source branch, so the change moves rather than the name.

Same commits, rebased onto `c2a9768f`. Both code findings from the review on !594 are already in them -- `RecursionError` caught with its regression case, and the implementation comment reduced to the two non-obvious reasons. Nothing else changed, so that review carries.
2026-09-09 15:42:36 +00:00

178 lines
5.7 KiB
Python

"""Unit tests for ProactiveSpawn.
Mocks SubagentManager (real spawn has heavy deps — LLM provider, tool
registry, real workspace). Verifies the gating + wiring contract.
"""
from __future__ import annotations
from datetime import datetime
from unittest.mock import AsyncMock, MagicMock
import pytest
from raven.config.raven import NudgePolicyConfig
from raven.proactive_engine.sentinel.executor.spawn import ProactiveSpawn
from raven.proactive_engine.sentinel.trigger_policy.policy import NudgePolicy
from raven.proactive_engine.sentinel.types import PlannerDecision
def _now():
return datetime(2026, 4, 21, 14, 0, 0)
def _cfg(**overrides) -> NudgePolicyConfig:
defaults = dict(
max_nudges_per_hour=5,
max_nudges_per_day=20,
min_interval_seconds=60,
quiet_hours=(0, 0),
cooldown_on_dismiss_seconds=1800,
high_priority_bypasses_limits=True,
dedup_window_seconds=3600,
inject_ttl_seconds=1800,
inject_max_pending_per_session=3,
defer_idle_threshold_seconds=300,
defer_max_wait_seconds=86400,
)
defaults.update(overrides)
return NudgePolicyConfig(**defaults)
def _decision(**overrides) -> PlannerDecision:
defaults = dict(
action="spawn_agent",
reason="test spawn",
priority="low",
proactivity_score=0.8,
target_session="cli:direct",
spawn_task="run a health check and summarize findings",
)
defaults.update(overrides)
return PlannerDecision(**defaults)
@pytest.fixture
def policy():
return NudgePolicy(_cfg(), now_fn=_now)
@pytest.fixture
def mock_subagent_mgr():
mgr = MagicMock()
mgr.spawn = AsyncMock(return_value="Subagent [foo] started (id: abc123).")
return mgr
@pytest.fixture
def spawner(mock_subagent_mgr, policy):
return ProactiveSpawn(mock_subagent_mgr, policy, now_fn=_now)
# ---------------------------------------------------------------------------
# Happy path
@pytest.mark.asyncio
async def test_dispatch_happy_path(spawner, mock_subagent_mgr):
result = await spawner.dispatch(_decision())
assert result.delivered is True
assert result.reason == "spawned"
assert "task_id" in result.details
mock_subagent_mgr.spawn.assert_awaited_once()
kwargs = mock_subagent_mgr.spawn.await_args.kwargs
assert kwargs["task"] == "run a health check and summarize findings"
assert kwargs["origin_channel"] == "cli"
assert kwargs["origin_chat_id"] == "direct"
assert kwargs["session_key"] == "cli:direct"
assert "sentinel" in kwargs["task_summary"]
@pytest.mark.asyncio
async def test_dispatch_records_in_policy(spawner, policy):
# Before: no history.
assert policy.snapshot_state()["nudges_used_this_hour"] == 0
await spawner.dispatch(_decision())
assert policy.snapshot_state()["nudges_used_this_hour"] == 1
# ---------------------------------------------------------------------------
# Rejection paths
@pytest.mark.asyncio
async def test_dispatch_rejects_wrong_action(spawner, mock_subagent_mgr):
for act in ("skip", "nudge", "nudge_inject", "nudge_defer"):
r = await spawner.dispatch(_decision(action=act))
assert r.delivered is False
assert act in r.reason
mock_subagent_mgr.spawn.assert_not_called()
@pytest.mark.asyncio
async def test_dispatch_rejects_empty_task(spawner):
r = await spawner.dispatch(_decision(spawn_task=None))
assert r.delivered is False
assert r.reason == "empty_spawn_task"
@pytest.mark.asyncio
async def test_dispatch_blocked_by_policy(spawner, policy, mock_subagent_mgr):
# Fill the hour quota on the policy so check() denies.
for i in range(5): # max_nudges_per_hour=5
policy.record_fired("nudge", f"other{i}", f"msg{i}")
r = await spawner.dispatch(_decision(target_session="cli:new"))
assert r.delivered is False
assert "policy" in r.reason
mock_subagent_mgr.spawn.assert_not_called()
# ---------------------------------------------------------------------------
# Error handling
@pytest.mark.asyncio
async def test_dispatch_handles_spawn_exception(policy):
failing_mgr = MagicMock()
failing_mgr.spawn = AsyncMock(side_effect=RuntimeError("boom"))
spawner = ProactiveSpawn(failing_mgr, policy, now_fn=_now)
r = await spawner.dispatch(_decision())
assert r.delivered is False
assert r.reason.startswith("spawn_error:RuntimeError")
# Policy should NOT have recorded — the spawn failed.
assert policy.snapshot_state()["nudges_used_this_hour"] == 0
# ---------------------------------------------------------------------------
# Session parsing
@pytest.mark.asyncio
async def test_dispatch_parses_session_key(spawner, mock_subagent_mgr):
await spawner.dispatch(_decision(target_session="telegram:home:12345"))
kwargs = mock_subagent_mgr.spawn.await_args.kwargs
# split_session_key keeps extra colons in chat_id.
assert kwargs["origin_channel"] == "telegram"
assert kwargs["origin_chat_id"] == "home:12345"
@pytest.mark.asyncio
async def test_dispatch_defaults_missing_target(spawner, mock_subagent_mgr):
await spawner.dispatch(_decision(target_session=None))
kwargs = mock_subagent_mgr.spawn.await_args.kwargs
assert kwargs["origin_channel"] == "sentinel"
# ---------------------------------------------------------------------------
# Details carry task_id
@pytest.mark.asyncio
async def test_result_details_contains_task_id(spawner, mock_subagent_mgr):
mock_subagent_mgr.spawn.return_value = "Subagent [foo] started (id: zzz999)."
r = await spawner.dispatch(_decision())
assert r.details is not None
assert "task_id" in r.details
# Exact content is the full spawn() return message; just ensure non-empty.
assert r.details["task_id"]