Updating Screenshots for Three.js Examples

Based on the information available about TeapotGeometry in Three.js, I can provide some guidance on updating screenshots for the automated checks, though the specific process isn't detailed in the documentation I have access to.

For Three.js pull requests that modify examples and require screenshot updates, there's typically a process to follow:

1. The Three.js repository likely has a screenshot generation tool or script that maintains consistency across example screenshots.

2. You should check the Three.js contribution guidelines or developer documentation for specific instructions on updating screenshots.

3. In many projects with automated visual testing, there's often a command you can run locally to regenerate the reference screenshots.

4. You might need to add a comment on your PR asking maintainers to update the screenshot, as this might be a protected process.

5. Some projects use flags like [update screenshots] in commit messages to trigger automated screenshot updates.

Since you're working specifically with the TeapotGeometry example, make sure your fix correctly renders the glossy shader as intended before attempting to update the screenshot.

I recommend checking the Three.js repository's README, CONTRIBUTING.md, or developer documentation for specific instructions on updating example screenshots, or asking directly in your PR for guidance from the maintainers.