Moving status reads into a program does not solve everything if each execution still carries a long conversation and explanation. While connecting the existing cafe and YouTube runners, I defined a small capsule containing only the current task data. This changes the execution input; it does not delete or prune the host conversation.
A rich conversation can produce a small execution input
Earlier corrections and context matter while interpreting what a person wants. Once the destination and task are known, however, the executor may need only content, time and scope. Treating those as the same material makes past conversation follow every execution even when the program cannot use it. I separated judgment context from inputs to an established procedure.
The compact runner accepts exactly version, scope and deliveries at the top level. Scope identifies the project and profile; each delivery carries its platform, content and a selected video when needed. There is no accepted field for chat history or long instructions. A general intention to send less became a concrete set of fields and a validation function.
Unknown fields are rejected rather than silently ignored
The keys check rejects unknown fields. Content has length and shape bounds, and the supported platforms and number of deliveries are bounded. The supported scope of this particular entrance is explicit. Its batch-size bound is not a limit on the number of articles in a content project; it is a contract for a specific execution interface.
Silently dropping an unknown field can make a caller believe an instruction was applied. An invented public-visibility field, for example, must not be ignored behind an apparently successful response. Rejecting unsupported input with a short error helps locate the mismatch. Reducing input should not be implemented by discarding meaning unnoticed.
The compact entrance does not replace the whole plugin
In this compact route, YouTube is constrained to private upload or a dated preview. That differs from the existing plugin path for an explicitly requested public schedule. Cafe items also have the date condition expected by this entrance. I do not describe the compact wrapper as replacing every choice supported by the original plugins.
The selected video is connected through the existing selection procedure after its name and hash are checked. Naming a selected video is different from granting arbitrary filesystem access. This runner also follows the G-drive path contract chosen for this PC. Another machine needs a deliberate decision about storage locations and trusted boundaries.
Compare the current input with its retained receipt
Even a small input must not reuse one result folder for a different request. A fingerprint of scope and delivery is compared with the saved intent. A completed receipt can be returned; an intent without a run ID remains uncertain. Shortening the request did not remove the protection against resubmission.
A video can change bytes while keeping its name. The saved selection hash must agree with the current file before an earlier handle is reused. These checks move material-identity work into the local program rather than supplying the model with more explanation. A hash establishes byte identity, not authorship or permission to publish.
The output should serve the next decision
Detailed context and status responses remain in local records; the final summary returns status, verification and bounded execution metrics. Request and response bytes are measured separately. A smaller transfer can be observed, but bytes cannot be relabeled as model tokens. The surrounding host's system context is not controlled by this runner.
The historical report records one execution with 1,003 input bytes and 579 output bytes. Those are the sizes for that execution, not a promise about every future request or its cost. Actual token use is retained separately. Distinguishing the part I reduced from the accumulated conversation managed by the host lets a reader assess the scope of the improvement.
Find the small contract inside another program
When revising an automation, I would inspect which fields the executor actually reads. Does it need the entire conversation? Where do verified environment defaults come from? Will an unsupported extra instruction be rejected? If the lifetime and responsibility of each field can be explained, another agent can use the entrance without another long briefing.
This article comes from the actual shared runner and its historical measurement record. It did not send new customer material to an external service or reactivate the embedded model. The benefit of a compact contract depends on an established procedure with known checks. I finish the necessary judgment first and then reduce execution data, rather than compress an unknown workflow into an unjustified shortcut.