Preserve tested Verify source, authoritative READY checks, bounded bridge retries, diagnostics and failure-only reporting. Include 336-test suite and packaging assets; exclude live Mentor samples, field logs, backups and distributions.
5.4 KiB
Native CBB Verify Probe Implementation Plan
For agentic workers: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task with verification checkpoints.
Goal: Determine whether the EE7.9 native CLibServer::VerifyRCCells(int) path can verify one CBB safely on an isolated .lmc copy and persist a READY state.
Architecture: Keep production Python/UI code unchanged. Use static analysis to recover the caller sequence and ABI, then build a separate x86 C++ probe with Mentor's runtime DLLs. The probe will operate only on a copied library, emit JSONL evidence, and be accepted only when the existing read-only status bridge reports READY after the probe process exits.
Tech Stack: Windows PowerShell, MSVC x86, LibManagerDBPI.dll, LMCDLL70.dll, existing CbbStatusBridge32.exe, objdump/dumpbin, JSONL evidence.
Spec: docs/superpowers/specs/2026-09-20-bridge-execution-and-unc-design.md
Global Constraints
- Never call write exports against the production center library.
- Use
diagnostics/Mentor_lib_EE7.9-cleanor a newly-created copy as the only write target. - Do not use physical mouse, keyboard injection,
SendInput, or foreground switching. - Do not claim success unless the post-exit status bridge returns
READYfor the same CBB and.lmc. - Preserve raw return codes, DLL paths, process architecture, and before/after status in JSONL.
Task 1: Establish a clean isolated fixture and baseline
Files:
- Create:
diagnostics/native-verify-probe-20260925/README.md - Create:
diagnostics/native-verify-probe-20260925/baseline.json
Interfaces:
-
Consumes: the existing clean EE7.9 center-library copy and
CbbStatusBridge32.exe. -
Produces: an immutable fixture path, target CBB identity, and a recorded pre-probe status.
-
Step 1: Resolve the clean fixture and target CBB without opening production files.
-
Step 2: Run the existing status bridge in read-only mode for exactly one target.
-
Step 3: Record the response, file hashes, and process/DLL architecture in
baseline.json. -
Step 4: Stop if the target is already
READYor if the fixture identity cannot be proven.
Task 2: Recover the native call sequence
Files:
- Create:
diagnostics/native-verify-probe-20260925/static-analysis.md - Create:
diagnostics/native-verify-probe-20260925/call-sites.txt
Interfaces:
-
Consumes:
LibManagerDBPI.dll, Mentor executables/DLLs, and existing exported-symbol records. -
Produces: disassembly evidence for constructor,
Load,Init,SetVerifyRCCellsFlag,VerifyRCCells,Save, andClosecall sites. -
Step 1: Enumerate x86 exports and decorated names with
objdumpordumpbin. -
Step 2: Search Mentor binaries for references to the decorated
VerifyRCCellssymbol and nearby string/resource references. -
Step 3: Disassemble each caller and record register/stack argument setup and return-code checks.
-
Step 4: Identify whether the caller opens a partition, sets a flag, saves, or requires an application context.
Task 3: Build a read-only ABI sanity probe
Files:
- Create:
tools/native_verify_probe/NativeVerifyProbe32.cpp - Create:
tools/native_verify_probe/CMakeLists.txt - Create:
tools/native_verify_probe/README.md
Interfaces:
-
Consumes: the recovered constructor/load signatures and a fixture
.lmcpath. -
Produces: JSONL describing object creation, load/init results, and no-write dry-run checks.
-
Step 1: Write a probe that loads Mentor DLLs but does not call Verify/Save.
-
Step 2: Compile it as Win32 with the available MSVC toolchain.
-
Step 3: Run it against the fixture and verify clean process exit with no production file changes.
Task 4: Run one isolated native verify experiment
Files:
- Create:
diagnostics/native-verify-probe-20260925/experiment.jsonl - Modify:
tools/native_verify_probe/NativeVerifyProbe32.cpponly if Task 3 and static evidence agree.
Interfaces:
-
Consumes: one isolated fixture and one target CBB.
-
Produces: a single experiment record with before status, call sequence, return codes, save result, process exit, and after status.
-
Step 1: Add an explicit
--write-isolated-copyguard; refuse any path outside the fixture directory. -
Step 2: Execute only one parameter combination inferred from static evidence.
-
Step 3: Save/close the isolated library and allow the probe process to exit naturally.
-
Step 4: Re-read the target using
CbbStatusBridge32.exeafter process exit. -
Step 5: Classify the result as
READY,PENDING,ERROR, orABI_UNSAFE; do not retry with guessed parameters.
Task 5: Document the decision and keep production unchanged
Files:
- Create:
diagnostics/native-verify-probe-20260925/conclusion.md - Modify:
API-FINDINGS.mdonly with evidence-backed results.
Interfaces:
-
Consumes: static-analysis and experiment JSONL.
-
Produces: a go/no-go decision for production integration.
-
Step 1: Require a post-exit
READYstatus before calling the native path viable. -
Step 2: If viable, document exact ABI and guard requirements without wiring production yet.
-
Step 3: If not viable, document the blocking evidence and retain the existing safe status-only bridge.
-
Step 4: Run repository tests that do not launch Mentor and verify no production source changes were introduced.