backend stage patches

Pipeline Demo

Each backend stage owns a processing-instruction range in the streamed shell. The server writes a <template for> chunk for the stage as soon as that work is complete.

stream evidence

server route sketch

enqueue(shellWithProcessingInstructions);
await stageDone("fetch");
enqueue('<template for="fetch">...</template>');
await stageDone("transform");
enqueue('<template for="transform">...</template>');

why this is different

The old page animated a client-side transform pipeline. This version demonstrates the platform primitive: server-produced HTML chunks patch existing document ranges directly.

references

ChromeStatus entry
Declarative partial updates explainer

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗