Enable Hostinger-ready static deploy output (relative asset base) and document import flow

[Copilot]

This PR addresses the Hostinger import/deploy requirement by making the Vite build output pathing compatible with static file hosting and adding explicit deployment instructions for Hostinger.

• Build config: static-host compatible asset paths

  • Updated Vite config to emit relative asset URLs so the generated dist/ can be uploaded directly to Hostinger without root-path assumptions.
  • Change:

  // vite.config.ts
  export default defineConfig(({ mode }) => ({
    base: './',
    // ...
  }));

• Docs: Hostinger deployment/import instructions

  • Added a focused README section (Deploy to Hostinger) describing the required publish flow:
    • build with npm run build
    • upload dist/ contents to public_html
    • replace old files on updates

This keeps the app deployment model unchanged while ensuring the generated static bundle is portable to Hostinger’s file-manager based hosting workflow.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.