feat: manage local website previews through one guided workflow #150

Summary

Please provide a consistent way to start, find, inspect, and stop a local website or web application preview.

Problem or workflow

Enthusiasts and small businesses building websites often lose track of which preview is running, where to open it, or why it failed. Repeated starts can create conflicting previews, and stopping the wrong one can disrupt another project.

Affected area

Local project previews and website workflows.

Proposed behavior

Let users start a preview for a selected project, receive a clear address, inspect its status and recent problems, and stop that project's preview when finished. Reuse a working preview where appropriate, keep its address consistent when possible, and explain conflicts or missing requirements. Keep local previews private to the user's computer by default, and protect unrelated projects when stopping or restarting one.

For example, a business owner reviewing two website projects should be able to open the correct preview and close one without affecting the other.

Please fit this into the existing project workflows, with implementation and supported project types decided by the maintainer.