Files
isphere-ai-bridge/docs/source-discovery/2026-07-12-login-reachability-probe-package.md
2026-07-12 12:55:53 +08:00

96 lines
3.2 KiB
Markdown

# Login Reachability Probe Package
Date: 2026-07-12
## Business purpose
This package turns the login validation schema into an operator-runnable package for the 2026-07-13 logged-in environment.
It is for B-route evidence collection. It does not enable production send.
## Generated artifacts
- Package script: `scripts/package-login-reachability-probe.ps1`
- Verification script: `scripts/verify-login-reachability-probe-package.ps1`
- Package directory: `runs/login-reachability-probe-package`
- Package zip: `runs/login-reachability-probe-package.zip`
- Downloads copy: `C:\Users\zhaoy\Downloads\login-reachability-probe-package-20260712-125451.zip`
## What the package contains
- `recorder/ISphereLiveProbeRecorder.exe`
- `tools/isphere-capability-smoke.exe`
- `LOGIN-REACHABILITY-INPUTS.template.json`
- `LOGIN-REACHABILITY-INPUTS.schema.json`
- `CREATE-RETURN-ZIP.ps1`
- `RUN-LOGIN-REACHABILITY-SUITE.bat`
- numbered operator steps:
- `00-prepare-inputs.bat`
- `01-run-before-recorder.bat`
- `02-run-after-text-recorder.bat`
- `03-run-after-file-recorder.bat`
- `04-create-return-zip.bat`
- copied reference docs:
- `docs/login-reachability-validation-items.md`
- `docs/send-upload-deep-dive.md`
## Operator flow
1. Run only on a machine where iSphere/IMPlatformClient is visibly logged in.
2. Fill `LOGIN-REACHABILITY-INPUTS.json` from the template.
3. Run before-recorder.
4. If text test is enabled, manually send exactly one text message in the official client, then run after-text-recorder.
5. If file test is enabled, manually send exactly one safe small file in the official client, then run after-file-recorder.
6. Run `CREATE-RETURN-ZIP.ps1` or `04-create-return-zip.bat`.
7. Return `isphere-login-reachability-return-*.zip`.
## Required returned schema
The return script writes `LOGIN-REACHABILITY-OUTPUT.json` with these top-level sections:
- `run`
- `targets`
- `runtime`
- `reachability`
- `server_auth`
- `snapshots`
- `attempts`
- `failures`
- `correlation`
## Safety and route status
- `NO_AUTOMATIC_SEND=true`: the package does not send text or files automatically.
- `production_send_enabled=false`
- `production_file_send_enabled=false`
- A-route/RPA remains `backup_only`.
- B-route remains blocked until returned evidence proves logged-in reachability and sent-record/ack correlation.
## Verification
Fresh verification command:
```powershell
powershell -NoProfile -ExecutionPolicy Bypass -File scripts\verify-login-reachability-probe-package.ps1
```
Verified result:
```json
{
"ok": true,
"required_file_count": 21,
"synthetic_return_verified": true,
"online_login_required": true,
"no_automatic_send": true,
"production_send_enabled": false,
"production_file_send_enabled": false
}
```
## Next decision after returned zip
- If text evidence includes one-shot target, before/after sent-record source, content hash, and ack/ref correlation, move text B-route from contract/probe toward production connector design.
- If file evidence includes FileUploadPara/server/auth data, IFileTransfer reachability, FileUploadResult/FileID or structured failure, and file sent-record/ack correlation, move file B-route to upload connector design.
- If reachability fails with structured reasons, continue offline reverse against the failed step.