Fix Go API and guest memory problems

Start at the host-to-Wasm boundary: import signatures, checked memory ranges, context cancellation, and instance ownership.

Host import mismatch

Create imports with wago.NewImports() and register callbacks with imports.HostFunc(module, name, fn). Module and function names remain separate exact identities. Wago checks the callback and declared signature before guest startup.

Inspect the module first:

wago module imports fib.wasm

Then compare the parameter and result slots with the guest declaration.

Guest memory range failure

Treat pointers as offsets. Validate addition in a wider integer:

end := uint64(ptr) + uint64(length)
if end > uint64(len(memory)) {
	return fmt.Errorf("out of bounds")
}
data := memory[uint64(ptr):end]

Outside host callbacks, prefer checked instance helpers:

data, ok := inst.Read(ptr, length)
if !ok {
	return fmt.Errorf("out of bounds")
}

Caller.Memory(), HostCall, and its raw slot views are valid only during that synchronous callback. Copy bytes that must survive it.

Cancellation does not stop work

Use a context-aware call:

out, err := inst.InvokeValues(ctx, "work", args...)

or the low-level form:

out, err := inst.InvokeContext(ctx, "work", slots...)

The context needs a deadline or cancel function, and the same context must reach Wago. Blocking Go work in a host function needs separate cancellation.

Concurrent instance calls

One instance cannot execute simultaneous public calls. Create separate instances from the same compiled module for parallel guest work.

Report a reduced failure

Include the exact command or Go call, complete error, selected runtime, OS, architecture, module hash, and the smallest reproducer. For memory bugs, include the pointer, length, memory size, and guest signature.