What problem does it solve? In a SolidStart production build, every 'use server' function is addressed by its file hash and its position in the file, not by its name. Removing, reordering, or changing the parameters of an existing server function causes stale browser tabs to call the wrong function with the wrong arguments, which has already caused real production bugs like players being teleported to wrong coordinates. ## Core Features & Use Cases - Positional Stability Rules: New server functions go at the end of the file; existing ones are never removed, reordered, or given different parameters. - Deprecation Pattern: Unused functions keep their slot, stay exported, and answer their old arguments sensibly instead of being deleted. - Verification Workflow: Compare the ordered list of 'use server' functions before and after a change (e.g., with git show HEAD:<file>) to confirm every function kept its position. - Use Case: When adding a new server action to a SolidStart file, place it after the last existing function and verify no existing function moved, so tabs loaded before the deploy keep calling the correct endpoints. ## Quick Start Review my changes to this file containing 'use server' functions and confirm that no existing server function was removed, reordered, or given different parameters.
