Online pages supply action metadata that the client binds to buttons and counters. The original V2 browser path includes favourite, star and stop-favourite decisions, colour availability and counter updates. A visible star count is part of a document tree as well as a server state; the client can update one before a later fetch confirms the other. [1][2]
Two star paths
The archive star action rewrites a .ppm URL and sends a count header. A document metadata action can instead use a page-provided URL and an empty POST body. These paths should not be collapsed into one rule, even though the user sees a similar star button. [1]
Colour and count handling
The traced V2 document code reads colour-specific action URLs, stock and deltas, then updates nested counter nodes. That establishes client-side behaviour for the studied route, not the original service's validation or persistence policy. If a displayed count differs after navigation, compare the action response, the document mutation and the next page fetch. [1]
Reproduce one action
Capture the source page metadata, press the control once, record method/path/headers/body, capture the response and observe the resulting page. Repeat from a cold page load to separate cache effects from server effects. Use a client build label with the capture. [1][2]