fix: point Playground and example links at v1

[yamcodes]

Summary

Hardcoded stale branch URLs still sent living product surfaces to the v0 archive (main) or a deleted branch (dev). Production docs track Option A / v1.

Changes

• Site Nav Playground → StackBlitz on v1 (apps/www/lib/stackblitz.ts)
• Root + @arkenv/core READMEs, examples/README.md, community MDX, acknowledgements → v1 blob/tree links
• CLI RegistryClient fetches examples/registry.json from v1 (patch changeset)
• Docs “Edit this page” / example-card GitHub fallback branch: dev → v1
• Footer MIT License: blob/dev → blob/v1 (Playwright + AGENTS.md learned fact)
• @arkenv/core test badge: tests-badge.yml → test.yml (match root README; mirror was gated on deleted dev)
• .changeset/config.json baseBranch: dev → v1
• Playwright homepage assert Playground href includes /tree/v1/examples/stackblitz

Left intentional main mentions in branching/launch docs that describe the v0 archive.

Test plan

• pnpm exec vitest run apps/www/lib/utils/github.test.ts
• Confirm raw.githubusercontent.com/.../v1/examples/registry.json returns 200
• Local www: Playground href + footer MIT License use v1
• CI

  

[changeset-bot]

🦋 Changeset detected

Latest commit: 4b242e1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
arkenv	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

@arkenv/agent-plugin

npm i https://pkg.pr.new/@arkenv/agent-plugin@1903

arkenv

npm i https://pkg.pr.new/arkenv@1903

@arkenv/build

npm i https://pkg.pr.new/@arkenv/build@1903

@arkenv/bun-plugin

npm i https://pkg.pr.new/@arkenv/bun-plugin@1903

@arkenv/core

npm i https://pkg.pr.new/@arkenv/core@1903

@arkenv/fumadocs-ui

npm i https://pkg.pr.new/@arkenv/fumadocs-ui@1903

@arkenv/nextjs

npm i https://pkg.pr.new/@arkenv/nextjs@1903

@arkenv/nuxt

npm i https://pkg.pr.new/@arkenv/nuxt@1903

@arkenv/rsbuild-plugin

npm i https://pkg.pr.new/@arkenv/rsbuild-plugin@1903

@arkenv/standard

npm i https://pkg.pr.new/@arkenv/standard@1903

@arkenv/tanstack-addon

npm i https://pkg.pr.new/@arkenv/tanstack-addon@1903

@arkenv/vite-plugin

npm i https://pkg.pr.new/@arkenv/vite-plugin@1903

commit: 4b242e1

[pullfrog]

Important

The repoint itself is correct, but this PR's whole purpose — getting living surfaces off stale branches — misses the footer's MIT License link, which still targets the deleted dev branch (404), and the packages/core badge now renders no status.

Reviewed changes

• StackBlitz Playground → v1 — apps/www/lib/stackblitz.ts points the interactive example at tree/v1/examples/stackblitz; the Playwright homepage assertion was updated to match.
• Docs "Edit this page" fallback → v1 — apps/www/lib/utils/github.ts falls back to v1 instead of dev, with apps/www/.env.example and github.test.ts updated in step.
• CLI registry fetch → v1 — packages/arkenv/src/shared/clients/registry.client.ts loads examples/registry.json from v1 (verified 200), with a top-level patch changeset.
• README / community / examples repoint — root and @arkenv/core READMEs, community.mdx, ACKNOWLEDGEMENTS.md, and examples/README.md now use v1 blob/tree URLs.

⚠️ The footer still links the MIT License at a branch that no longer exists

apps/www/components/site-footer.tsx:158 builds the footer license link from a hardcoded blob/dev/LICENSE. The dev branch is gone — the branches API returns 404 for it, and raw.githubusercontent.com/yamcodes/arkenv/dev/LICENSE 404s — so the "MIT License" link on every homepage and docs footer is broken. Because this PR exists to move living surfaces onto v1, this is the one stale branch pointer it should have caught, and the Playwright test currently pins the broken value instead of catching it.

Technical details

# Stale `dev` references after the v1 repoint

## Affected sites
- `apps/www/components/site-footer.tsx:158` — `${githubRepoUrl}/blob/dev/LICENSE`; `dev` is not a branch on `yamcodes/arkenv` (branches API → 404, raw file → 404). Renders a 404 from the live footer.
- `apps/playwright-www/tests/docs-toc.test.ts:149` — asserts the same `blob/dev/LICENSE` href, so the suite keeps passing while the link is dead.
- `AGENTS.md` — the "Learned Workspace Facts" note documents `blob/dev/LICENSE`; stale if the branch stays gone.
- `.github/workflows/tests-badge.yml:19` — mirror gated on `head_branch == 'dev'`, which can never match now (root cause of the `packages/core` badge showing "no status").

## Required outcome
- Branch pointers on living surfaces resolve against a branch that exists. Point the footer (and its assertion) at `v1`, or confirm `dev` is coming back.

## Open questions for the human
- `.changeset/config.json` still sets `baseBranch: "dev"`. Since this PR adds a changeset consumed by the `v1` release flow, is that base branch still valid for changesets, or does it need to become `v1`?

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}

[cursor]

Addressed Pullfrog review on 4b242e1:

1. Footer MIT License — site-footer.tsx + Playwright docs-toc assertion + AGENTS.md learned fact now use blob/v1/LICENSE (dev 404s).
2. Core README badge — src aligned with root README: test.yml/badge.svg?branch=v1 (no longer the dead tests-badge.yml mirror).
3. Changeset baseBranch — set to v1 in .changeset/config.json. Option A release line already uses changeset-release/v1 → v1 (e.g. Version Packages (rc) #1885); dev is gone.

[pullfrog]

✅ No new issues found.

Reviewed changes

This run reviewed 4b242e1e (plus the two earlier commits for context) — the delta since the prior pullfrog review at 2573dd37. It finishes the stale-branch cleanup raised there:

• Footer MIT License → v1 — apps/www/components/site-footer.tsx:158 now builds ${githubRepoUrl}/blob/v1/LICENSE, and the Playwright assertion at apps/playwright-www/tests/docs-toc.test.ts:149 was retargeted to match, so the suite no longer pins the dead link.
• @arkenv/core badge fixed — packages/core/README.md:8 now points at test.yml/badge.svg?branch=v1 (matching the root README) instead of the dev-gated tests-badge.yml mirror.
• Changesets base branch → v1 — .changeset/config.json baseBranch is now v1, the repo's actual default branch (confirmed via the API; dev 404s), answering the prior open question.
• AGENTS.md learned fact updated — the footer license-link note now records blob/v1/LICENSE.

A repo-wide grep confirms no remaining yamcodes/arkenv/{blob,tree,edit}/dev|main pointers on living surfaces; the remaining main references are third-party links, test fixtures, or the intentional v0-archive docs.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}