By the way, if you don’t mind, I have been looking into using real CKB protocols as maturity benchmarks for CellScript, and your iCKB seems like a natural stress test candidate.
The idea is not to make any production-equivalence claim, but to use normalised differential fixtures to expose weak spots in the language model under realistic DAO/xUDT/accounting-heavy scenarios.
In practice, this would mean comparing behaviour under the same semantic inputs, capacities, output data, deps, headers and witnesses where relevant, allowing only the script-under-test code cell/hash to differ, and then executing both sides in CKB VM/testtool with pass/pass and fail/fail alignment, plus explicit evidence: hashes, exit codes, cycles, named failure modes, etc.
I will likely start putting this together properly around the end of next month. If you are interested, I would really value your perspective when it reaches a more concrete stage.