mirror of
https://github.com/morluto/rea.git
synced 2026-11-18 20:53:00 +00:00
* fix(cutter): explain empty discovery when Cutter 2.5.0 rejects the plugin Official Cutter 2.5.0 builds have been observed to reject Python plugins at startup, including Cutter's own sample plugin and REA's bridge (rizinorg/cutter#3659). No session is published, and list_cutter_sessions returns no_live_bridge_found with nothing pointing at the Cutter release. The list_cutter_sessions contract now says what no_live_bridge_found means and names the observed 2.5.0 rejection. The Cutter bridge docs describe installing the plugin, the startup log lines Cutter prints when it rejects it, and that 2.4.1 loaded the bridge in the reported check. A minimal independent plugin fails the same way, so the bridge itself is unchanged. Refs #10299 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cutter): report empty-discovery causes in the shared result The guidance lived only in the MCP tool description, which `rea list-cutter-sessions` never shows. The docs also assumed a known package folder, which npx installations do not have. The discovery result now carries limitations, owned by cutterDiscoveryLimitations in the domain. For no_live_bridge_found they list the causes discovery cannot tell apart, including the observed Cutter 2.5.0 Python-plugin rejection (rizinorg/cutter#3659). CLI and MCP project the same text, and the tool description returns to its previous wording. The docs now take the plugin from the published package of the matching version with npm pack. Refs #10299 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cutter): name failed status probes among no-live causes no_live_bridge_found also covers a published session whose status probe fails: a stale descriptor after Cutter exited, an unresponsive bridge, or an incompatible bridge version. The limitation named only process, plugin-loading and directory causes. It now lists these too, and the dead-status-endpoint test asserts that such a discovery carries it. Refs #10299 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(cutter): give the finalization discovery fixture its limitations commandFinalizationCancellation builds a Cutter discovery through the list_cutter_sessions output schema, which now requires limitations. CI shard 4 failed all five final-close cases with a ZodError. The fixture now takes the owner's empty limitations for sessions_found. Refs #10299 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cutter): count unanswered sessions beside found ones When one session answered and another published session failed its status probe, discovery returned sessions_found with no limitation. The partial result looked complete. The client already throws for live ceiling mismatches, so every other descriptor without a session is a failed probe. It now passes that count to cutterDiscoveryLimitations, which reports the unlisted sessions for sessions_found. The stale-descriptor case in cutterBridgeRequestLimit asserts it. Refs #10299 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cutter): name unpublished bridge sessions among no-live causes When Cutter loads the plugin but the bridge cannot write its session descriptor, for example in an unwritable or full bridge directory, _BridgeServer.run closes the socket without logging. Cutter's log then shows the plugin as loaded, yet discovery finds nothing. The no-live limitation now names that cause and says the bridge does not log it. The Cutter docs say to check the bridge directory when the plugin is loaded but no session appears. Refs #10299 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cutter): count unreadable descriptors among unlisted sessions The descriptor loader dropped filename-matching candidates it could not read before listSessions counted unanswered sessions, so a found session beside a malformed, oversized, non-private or misnamed descriptor reported no limitation. The loader now returns its unreadable count, and the discovery limitation owner reports it beside failed status probes for both sessions_found and no_live_bridge_found. The no-live text keeps only the causes that leave nothing published; published sessions are now counted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cutter): leave session existence unknown for unreadable descriptors A filename-matching candidate the loader could not read does not establish that any session exists: it may be malformed, misnamed or removed while reading. The limitation now counts unreadable descriptor candidates and says whether they describe Cutter sessions is unknown, instead of saying their sessions are not listed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(mcp): record the list_cutter_sessions limitations in the advertised summary Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>