chore: package send recording and capability tests

This commit is contained in:
zhaoyilun
2026-07-10 14:36:15 +08:00
parent 8cdaa3c0bc
commit 89d7f65b45
10 changed files with 1000 additions and 14 deletions

View File

@@ -390,16 +390,57 @@ runs\send-sandbox-gate-package.zip
Send that zip to the online/internal sandbox operator. The operator must follow `OPERATOR-STEPS.md` inside the package:
1. fill `SANDBOX-SEND-INPUTS.json`;
2. run `run-before-recorder.bat`;
2. run `RUN-RECORDING-SUITE.bat` for the guided full flow, or run `01-run-before-recorder.bat`;
3. manually send exactly one sandbox message in the official client;
4. fill `success_ack_or_sent_record`;
5. run `run-after-recorder.bat`;
6. run `make-return-zip.ps1`;
5. continue the guided flow, or run `02-run-after-recorder.bat`;
6. continue the guided flow, or run `03-make-return-zip.bat`;
7. return the generated zip.
The package also contains `RECORDING-PACKAGE-MANIFEST.json`, `run-before-recorder.bat`, `run-after-recorder.bat`, `compute-content-hash.ps1`, `make-return-zip.ps1`, and the read-only recorder under `recorder\`.
Production `isphere_send_message` remains blocked until the returned package is analyzed.
## 14. Troubleshooting
## 14. Offline capability-test package
Use this second package when you want to test the current capability surface without logging in and without any real send.
Build and verify it locally:
```powershell
powershell -NoProfile -ExecutionPolicy Bypass -File scripts\package-send-capability-test.ps1
powershell -NoProfile -ExecutionPolicy Bypass -File scripts\verify-send-capability-test-package.ps1
```
Generated package:
```text
runs\send-capability-test-package.zip
```
Inside the extracted package, run:
```text
run-capability-test.bat
```
Expected final JSON includes:
```json
{
"ok": true,
"tool_count": 9,
"helper_name": "ISphereWinHelper",
"send_preview_tool_present": true,
"production_send_enabled": false,
"local_login_required": false,
"no_real_send": true
}
```
This package includes `isphere-capability-smoke.exe` and `runs\win-helper\ISphereWinHelper.exe`. It verifies the nine-tool MCP surface, fixture-backed receive/search/file-list behavior, send preview, and the production-send block. It does not log in, click, type, upload, hook, inject, or send.
## 15. Troubleshooting
- If C# helper build fails, run `scripts\build-win-helper.ps1` directly and check for missing .NET Framework reference assemblies.
- If `win_helper_version` fails, rerun `powershell -NoProfile -ExecutionPolicy Bypass -File scripts\verify-win-helper.ps1` first.