(v1) Update v1 README links from alpha preview to production on v1 launch

[yamcodes]

Summary

When ArkEnv v1 ships, the root README.md on the v1 branch will point documentation and preview URLs at the alpha preview deployment (https://arkenv-v1.vercel.app). Those links need to be updated to production URLs once v1 is released.

Blocked on v1 launch — see #683.

Current behavior (after #1305)

The v1 branch root README uses alpha/preview URLs for docs, FAQ, quickstart, and related navigation. An alpha callout links to the v1 roadmap.

Desired behavior

After v1 launches and docs are live at production:

• Docs, FAQ, and quickstart links point to https://arkenv.js.org/docs/... (production paths)
• Remove or replace the alpha/pre-release callout with stable-release messaging (or remove it entirely)
• Re-evaluate StackBlitz, GitHub blob links, and CI badge URLs for post-launch branch defaults (main vs v1)
• Confirm install commands reflect the published npm tag (latest vs next)

Acceptance criteria

• All doc navigation links in the v1 root README resolve to production arkenv.js.org URLs
• Alpha/pre-release callout is removed or updated to reflect stable v1
• StackBlitz and GitHub blob links use the correct default branch after launch
• Install commands match the published npm package/tag strategy at launch
• No remaining references to arkenv-v1.vercel.app in the root README unless intentionally kept for a specific reason

Out of scope

• Rewriting README marketing copy beyond URL/target updates
• Changes to packages/arkenv/README.md unless npm publishing requires it
• Fixing the root README stub on main (separate concern)

Related

• (v1) Add root README.md for v1 branch GitHub landing page #1305 — adds the v1 root README with alpha preview links
• v1 Roadmap #683 — v1 roadmap / launch tracking

[pullfrog]

This run croaked 😵

The workflow encountered an error before any progress could be reported. Please check the link below for details.

  ^{｜ Rerun failed job ➔ ｜ View workflow run ｜ via Pullfrog ｜ 𝕏}

[yamcodes]

This was generated by AI during triage.

Expert recommendation

Do this inside the v1 launch PR itself, not as a follow-up. A README pointing at a dead or stale alpha preview during the launch window is exactly the kind of thing that slips when tracked separately.

Concrete suggestions:

1. Make it mechanically verifiable. Add a one-line check to the launch checklist: grep -rn "arkenv-v1.vercel.app" README.md must return nothing. That covers the last acceptance criterion without relying on eyeballing.
2. Decide the npm tag strategy first. The install-command criterion depends on whether v1 ships as latest or next — that decision gates this issue and should be resolved on v1 Roadmap #683 before touching the README.
3. Prefer deleting the alpha callout over rewording it. Stable-release messaging in a callout box ages poorly; the README body should simply describe the stable product.
4. Keep the blocked label until v1 Roadmap #683 resolves; no work is possible before then.

Net: correctly labeled, low risk, ~30 minutes of work once unblocked. The only real decision is the npm tag strategy, which belongs to #683.