TaskRequest.Payload

I have some questions about the task submission process.

1. When I run devkit avs call , is it calling TaskMailBox contract?

2. why in the example on website, the call is devkit avs call -- signature="(uint256,string)" args='(5,"hello")' , while HelloWorld.sol functions take as input only a string?

3. I am going through the hourglass template, and in cmd/main.go I see HandleTask function, with input t *performerV1.TaskRequest, which is defined as

type TaskRequest struct {
	state         protoimpl.MessageState
	sizeCache     protoimpl.SizeCache
	unknownFields protoimpl.UnknownFields

	TaskId  []byte `protobuf:"bytes,1,opt,name=task_id,json=taskId,proto3" json:"task_id,omitempty"`
	Payload []byte `protobuf:"bytes,2,opt,name=payload,proto3" json:"payload,omitempty"`
}

from what I see, Payload is Abi encoded, for the example on the github with hello world, this is abi encoding of (5, "hello") arguments?

4. And does anyone has a sample go function that actually does something (like squaring a number) and return it? It would be helpful for me.

Start with cmd/main.go's HandleTask, the hourglass template, and the devkit avs call example referenced in the issue. Trace how TaskRequest.Payload is used and compare the documented HelloWorld.sol inputs with the CLI signature example. Done means the submission flow and ABI payload are explained and a working Go example for a simple computation is included.