feat(pages): serve install scripts from custom domain

[amh1k]

Description

Serve the OCR installation scripts from the project’s custom domain.

The Pages deployment now publishes install.sh and install.ps1 at:

• https://open-codereview.ai/install.sh
• https://open-codereview.ai/install.ps1

All installer documentation and usage comments were updated to use the shorter URLs. The existing installer and release-download logic remains unchanged.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring (no functional changes)
• Documentation update
• CI / Build / Tooling

How Has This Been Tested?

• make test passes locally
• Manual testing:
  • sh -n install.sh
  • npm run typecheck
  • npm run build
  • Verified both scripts are copied into the deployment artifact
  • Verified copied scripts match the repository versions with cmp
  • Verified no old installer URLs remain
  • make check
  • git diff --check

Checklist

• My code follows the project's coding style (go fmt, go vet)
• I have performed a self-review of my code
• I have added tests that prove my fix is effective or my feature works
• New and existing unit tests pass locally with my changes
• I have updated the documentation accordingly
• I have signed the CLA

Related Issues

Closes #411

[github-actions]

✅ OpenCodeReview: Review complete: 0 finding(s) across 3 selected item(s).

[wu21-web]

This implementation is neat and great! Thank you.
Russian docs are still pending for changes: pages/src/content/docs/ru/installation.md

[wu21-web]

Suggested change

	test -f _site/install.sh
	test -f _site/install.ps1
	cmp install.sh _site/install.sh
	cmp install.ps1 _site/install.ps1
	test -f _site/install.sh
	test -f _site/install.ps1
	sh -n _site/install.sh
	cmp install.sh _site/install.sh
	cmp install.ps1 _site/install.ps1

Scripts not justified by /bin/sh. After that, consider also linting the pwsh script.

[lizhengfeng101]

LGTM

[wu21-web]

Why not add a job to justify the .ps1 too?

[lizhengfeng101]

Good call — I actually tried this out. Added a separate verify-ps1 job with mcr.microsoft.com/powershell:lts-debian-12 to run [scriptblock]::Create(...) as a parse check, then reverted it.

The cost just doesn't justify the value here: pulling a ~200MB PowerShell container image on every deploy for a single parse check on a file that rarely changes feels like overkill. The sh -n check for install.sh is essentially free (sh is already in the build container), but there's no equivalent zero-cost option for .ps1 in our current setup.

If the script grows more complex or changes frequently in the future we can revisit, but for now I'll leave it as-is.

[wu21-web]

Do your require all jobs to run on self-hosted runners, even if a job proceeds for a relatively short amount of time (2sec) and uses a cheap runner (ubuntu-latest: $0.006/min)?