Workflow and Source Panels
Client and Worker Contracts
Replay one PHP execution where a client request includes a worker response file.
Project Entry
request_client.php
<?php
$command = ;
$label = $command;
if ($command === "refresh") {
$label = "cache";
} elseif ($command === "archive") {
$label = "records";
}
require_once __DIR__ . "/request_worker.php";
$response = handle_request($command);
$ticket = 40 + strlen($command);
echo "label=" . $label . "\n";
echo "ticket=" . $ticket . "\n";
echo $response . "\n";
<?php
$command = ;
$label = $command;
if ($command === "refresh") {
$label = "cache";
} elseif ($command === "archive") {
$label = "records";
}
require_once __DIR__ . "/request_worker.php";
$response = handle_request($command);
$ticket = 40 + strlen($command);
echo "label=" . $label . "\n";
echo "ticket=" . $ticket . "\n";
echo $response . "\n";
<?php
$command = ;
$label = $command;
if ($command === "refresh") {
$label = "cache";
} elseif ($command === "archive") {
$label = "records";
}
require_once __DIR__ . "/request_worker.php";
$response = handle_request($command);
$ticket = 40 + strlen($command);
echo "label=" . $label . "\n";
echo "ticket=" . $ticket . "\n";
echo $response . "\n";
source panels
When an example has more than one source file, replay keeps each file in its own panel while preserving one ordered trace stream. The Variables panel follows the actual `require_once` call into the worker file and the returned response back to the client.
boundary
The client owns the selected command and visible output. The worker owns the response rule for that command.