## Summary

- Recreates the release PR that the failed v2.9.13 workflow never
opened.
- Advances `version.txt` to `2.9.14-canary.0` so the next release does
not retry `2.9.13`.
- Keeps package and Turborepo skill metadata aligned with the attempted
`2.9.13` release state.

## Context

The v2.9.13 release failed during npm publishing after a partial native
package publish. This PR only moves repository state forward; it does
not create a `v2.9.13` tag or complete the npm publish.

## Changes Since v2.9.12

- release(turborepo): 2.9.12 (#12774) (`c1f923a`)
- fix: Restore docs mobile menu (#12782) (`859c629`)
- ci: Use `pull_request` for PR title linting (#12787) (`4cf9fab`)
- ci: Scope GitHub Actions caches by branch (#12788) (`5fcb960`)
- test: Validate lockfiles without dependency downloads (#12789)
(`71f8c90`)
- Removed unneeded import form hash creation script in docs (#12799)
(`1779ad7`)
- fix: Validate auth callback state (#12802) (`84f4508`)
- fix: Harden VS Code extension command execution (#12800) (`91c90cb`)
- fix: Avoid project-local Yarn during detection (#12801) (`e8e629d`)

## Release v2.9.14

> [!CAUTION]
> Versioned docs aliasing FAILED. [View
logs](https://github.com/vercel/turborepo/actions/runs/25882155729)

### Changes

- release(turborepo): 2.9.12 (#12774) (`c1f923a`)
- fix: Restore docs mobile menu (#12782) (`859c629`)
- ci: Use `pull_request` for PR title linting (#12787) (`4cf9fab`)
- ci: Scope GitHub Actions caches by branch (#12788) (`5fcb960`)
- test: Validate lockfiles without dependency downloads (#12789)
(`71f8c90`)
- Removed unneeded import form hash creation script in docs (#12799)
(`1779ad7`)
- fix: Validate auth callback state (#12802) (`84f4508`)
- fix: Harden VS Code extension command execution (#12800) (`91c90cb`)
- fix: Avoid project-local Yarn during detection (#12801) (`e8e629d`)
- chore: Release 2.9.13 (#12803) (`fb8c9ae`)

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>