From 6ebd033dff1116b84a150b751d9d54c780b5c057 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Wed, 11 Nov 2026 07:08:05 +0000 Subject: [PATCH] chore(plugin): regenerate the skill bundle from the authored skill The committed Cursor plugin copy had missed the parameter update mode and the runtime bridge ceiling. --- .../references/connection-and-recovery.md | 12 +++++++----- .../references/native-and-artifacts.md | 3 +-- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/.cursor-plugin/skills/reverse-engineer-anything/references/connection-and-recovery.md b/.cursor-plugin/skills/reverse-engineer-anything/references/connection-and-recovery.md index e2e767411f..a98808414a 100644 --- a/.cursor-plugin/skills/reverse-engineer-anything/references/connection-and-recovery.md +++ b/.cursor-plugin/skills/reverse-engineer-anything/references/connection-and-recovery.md @@ -108,11 +108,13 @@ is not a recommendation to change it. Do not invent a setting. Host memory and - Capacity, when the result is `resource_constraint` and `retryable` is true: wait for the active admission to finish, then retry within the reported limits. Do not restart REA to free the slot. -- `configuration_invalid`: correct the named setting in the environment that - starts REA (the shell or the MCP registration), then restart REA. Run - `rea doctor` to see the `runtime-configuration:` check. Re-run `rea setup` - for that client when the registration must carry the new setting, then - reconnect. +- `configuration_invalid`: when the error reports `update_mode: "runtime"`, + call `update_analysis_settings` for that setting. When it reports + `update_mode: "parameter"`, change that call's argument; the setter does not + accept it. Otherwise correct the named setting in the environment that starts + REA (the shell or the MCP registration) and start REA again. Run `rea doctor` + to see the `runtime-configuration:` check. Re-run `rea setup` for that client + when the registration must carry the new setting, then reconnect. - `invalid_request`: correct the reported fields from the current schema. Do not repeat the unchanged call. diff --git a/.cursor-plugin/skills/reverse-engineer-anything/references/native-and-artifacts.md b/.cursor-plugin/skills/reverse-engineer-anything/references/native-and-artifacts.md index 35c3757f4e..e4d84e2b68 100644 --- a/.cursor-plugin/skills/reverse-engineer-anything/references/native-and-artifacts.md +++ b/.cursor-plugin/skills/reverse-engineer-anything/references/native-and-artifacts.md @@ -539,8 +539,7 @@ the framing LF still fits. Cutter measures, signs, and writes a fitting response in bounded chunks. The bridge searches only the newly read bytes for the framing LF. The client unescapes each socket chunk into one response string before parsing it, so this ceiling does not keep the paged wire frame -and another concatenated copy. Invalid values are configuration errors and do not fall back to 16777216. Set the variable in the environment that starts REA, restart REA, -and start Hopper or Cutter from that same environment. An out-of-band bridge +and another concatenated copy. Invalid values are configuration errors and do not fall back to 16777216. `bridge.max_request_bytes` can be changed at runtime with `update_analysis_settings`. The launch seed is `REA_BRIDGE_MAX_REQUEST_BYTES`. Start Hopper or Cutter from that same environment so the bridge keeps the ceiling it started with until that bridge starts again. An out-of-band bridge without the setting stays at 16777216 bytes. The client reports that mismatch during discovery only after the hello proves a live authenticated bridge, and does not send a status request or the command. A stale descriptor is ignored.