73db4fad54
Add shared SDK/CLI/MCP byte reads over the existing Kuna data protocol, preserve partial batches and exact u64 ranges, and retain complete source Evidence. Reuse named read lifecycles, bound aggregate hex expansion, and verify stock/native/direct MCP paths plus a shipped-file byte oracle before pinning a table-dispatch model task. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
11 lines
772 B
Plaintext
11 lines
772 B
Plaintext
Analyze {{artifact_path}} statically. In sqlite3GetToken, recover the initial
|
|
byte-classification lookup and the first indirect dispatch it controls.
|
|
For first bytes 0x2d, 0x2f, 0x27, 0x22, 0x3f and 0x80, report the actual stored
|
|
class value and the initial machine dispatch destination. Read the artifact's
|
|
data tables; do not assume the byte value itself is a switch-case number.
|
|
Explain table bases, indexing, displacement width/signedness and target-base
|
|
calculation with supporting instruction addresses and real Evidence references.
|
|
Keep this about initial dispatch, not complete token recognition. Distinguish
|
|
static loaded-image observations from demonstrated runtime feasibility, and do
|
|
not infer final token types or consumed lengths from initial classes alone.
|