The template’s quad shader

The platformer template's DrawQuadSprite plugin (its QuadTextureMatPropBlock material draws the interaction prompt, the E keycap over a box in reach, through Graphics.RenderMesh and a MaterialPropertyBlock; not the dash's after-images) failed on GetAbsolutePositionWS, which Tassix's URP core lacked. URP doesn't render camera-relative, so it (and GetCameraRelativePositionWS) returns its argument.
A shaderlab test compiles a billboard written the same way (a texture declared in UnityPerMaterial, the ShaderGraph ShaderPass.hlsl include, the model matrix's rows, UNITY_MATRIX_I_V, absolute world positions); the template's own file compiles too.
Checked in the template over MCP: a virtual gamepad joins the player (PlayerInputManager), the stick walks it beside a box, and the screenshot shows the prompt, billboarded and drawn over everything, its texture from the property block.
Next: rumble (SetMotorSpeeds); URP render features; humanoid avatars and retargeting.