fix(blog): repair 27 broken links across 14 posts (#8094)

- Strip wrong /blog prefix from 20 internal cross-post links: the blog
  app serves under basePath "/blog", so prefixed hrefs rendered as
  /blog/blog/<slug> and 404ed in production
- Fix case in 2 Remix-series links (part 1 and 4 slugs are lowercase)
- Add https:// scheme to 4 scheme-less pris.ly short links
- Replace mangled cors middleware link with the expressjs/cors README
  configuration-options anchor

pnpm --filter blog lint:links now exits 0 (was 27 errors, 14 files).

Author: nurul3101

apps/blog/content/blog/app-hosting-compute-platforms-for-ai-agents-2026/index.mdx

@@ -29,9 +29,9 @@ So, here is a field guide to who shipped what recently, and how close they get t
 
 <TweetColumns tweetId="2064674357075759281" side="left">
 
-[Prisma Compute](/blog/launching-prisma-compute-public-beta) is TypeScript app hosting that runs in the same regions as [Prisma Postgres](https://www.prisma.io/postgres), so app-to-database queries stay low-latency. It targets the workloads typical serverless still struggles with: WebSockets, background jobs, cron tasks (first-class in `prisma.config.ts`), and agents that need to stay warm and stateful.
+[Prisma Compute](/launching-prisma-compute-public-beta) is TypeScript app hosting that runs in the same regions as [Prisma Postgres](https://www.prisma.io/postgres), so app-to-database queries stay low-latency. It targets the workloads typical serverless still struggles with: WebSockets, background jobs, cron tasks (first-class in `prisma.config.ts`), and agents that need to stay warm and stateful.
 
-Deployments are versioned with preview URLs. [Prisma Next](/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app) (early access) adds a contract-first ORM with a machine-readable `contract.json`, so the ORM, Postgres, and Compute now share one schema.
+Deployments are versioned with preview URLs. [Prisma Next](/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app) (early access) adds a contract-first ORM with a machine-readable `contract.json`, so the ORM, Postgres, and Compute now share one schema.
 
 On the agent side, `SKILL.md` files, agent rules, and native MCP support give the AI a clean interface for the full loop: init, schema changes, data access, deploy, logs, and redeploy. pgvector and extensions make feeding structured context easier with less manual ETL.
 
@@ -121,4 +121,4 @@ A unified stack attacks both at once: keep code, schema, data, and runtime coher
 
 ---
 
-_Disclosure: I work at Prisma, so I had a front-row seat for one of these launches, which is also why I think the integration story matters more than raw speed. If you want to feel what "one coherent system" is like, [Prisma Compute](/blog/launching-prisma-compute-public-beta) runs your app next to [Prisma Postgres](https://www.prisma.io/postgres) in a single project._
+_Disclosure: I work at Prisma, so I had a front-row seat for one of these launches, which is also why I think the integration story matters more than raw speed. If you want to feel what "one coherent system" is like, [Prisma Compute](/launching-prisma-compute-public-beta) runs your app next to [Prisma Postgres](https://www.prisma.io/postgres) in a single project._

apps/blog/content/blog/bringing-prisma-orm-to-react-native-and-expo/index.mdx

@@ -56,7 +56,7 @@ This line initially returns an empty array and then re-renders the component as
 ```ts
 prisma.transactions.useFindMany({ orderBy: { date: "desc" }})
 ```
-> It is customary for hooks in React to be free standing functions - for example `useFindManyTransactions()`. To conform with the regular Prisma ORM API, we have chosen the alternative format `prisma.transactions.useFindMany()`. During this Early Access period, we are soliciting feedback on this decision. Please share your thoughts on [Discord](pris.ly/discord).
+> It is customary for hooks in React to be free standing functions - for example `useFindManyTransactions()`. To conform with the regular Prisma ORM API, we have chosen the alternative format `prisma.transactions.useFindMany()`. During this Early Access period, we are soliciting feedback on this decision. Please share your thoughts on [Discord](https://pris.ly/discord).
 
 In the `LongPress` handler, the database row is deleted, automatically triggering a re-render of the component. It’s important to note that data changes can happen anywhere in your application, and it will trigger a re-render of any active component that relies on that data.
 
@@ -67,7 +67,7 @@ By taking advantage of Reactive Queries, many applications can be refactored to
 
 ## Prisma ORM in your Expo App today
 
-Prisma ORM is ready to be used in your Expo and React Native app today. Keep in mind this is an Early Access release, so please help us test it out and share your experience with us [on Discord](pris.ly/discord). To get started, follow the [instructions in the readme](https://github.com/prisma/react-native-prisma).
+Prisma ORM is ready to be used in your Expo and React Native app today. Keep in mind this is an Early Access release, so please help us test it out and share your experience with us [on Discord](https://pris.ly/discord). To get started, follow the [instructions in the readme](https://github.com/prisma/react-native-prisma).
 
 ### A Local-First experiment
 

apps/blog/content/blog/building-open-chat/index.mdx

@@ -144,7 +144,7 @@ That typed Postgres data comes from [Prisma Next](https://www.prisma.io/blog/pri
 
 ## Prisma Compute: two apps, one project, one command each
 
-The part that surprised me: production is this exact repo, deployed twice (the chat server and the Durable Streams service) side by side in one [Prisma Compute](/blog/launching-prisma-compute-public-beta) project, next to the [Prisma Postgres](https://www.prisma.io/postgres) database they share.
+The part that surprised me: production is this exact repo, deployed twice (the chat server and the Durable Streams service) side by side in one [Prisma Compute](/launching-prisma-compute-public-beta) project, next to the [Prisma Postgres](https://www.prisma.io/postgres) database they share.
 
 ![The whole production setup in the Prisma Console: the open-chat project on its main branch, with the Streams app, the open-chat app, and the primary database](/building-open-chat/imgs/tour-console.webp)
 
@@ -183,4 +183,4 @@ Then read the code. The whole app is about 6,000 lines and built to be read. The
 
 I set out to fix one tiny annoyance: a chat that drops its tail when you look away. What I ended up with is a small demonstration that durable, resumable streaming doesn't have to be exotic infrastructure. It can be an append-only log, a typed database, a live query, and one deploy command. Never dropping a token turned out to be the easy path, as long as you let the log be the truth.
 
-The reason it stayed simple is that the app, the streaming service, and the database all live in one place. That's what [Prisma Compute](/blog/launching-prisma-compute-public-beta) and [Prisma Postgres](https://www.prisma.io/postgres) are for: your app runs next to your data, deploys in one command, and is free to try while Compute is in public beta. If you want the rest of the story, see how we [launched Compute](/blog/launching-prisma-compute-public-beta), why it [runs on Bun's Rust rewrite](/blog/bun-rust-rewrite-prisma-compute), and how it handles [image transformations](/blog/image-transformations-with-bun-on-prisma-compute) and [custom domains](/blog/prisma-compute-custom-domains). Come build with us in [#prisma-compute](https://pris.ly/discord-compute) on Discord.
+The reason it stayed simple is that the app, the streaming service, and the database all live in one place. That's what [Prisma Compute](/launching-prisma-compute-public-beta) and [Prisma Postgres](https://www.prisma.io/postgres) are for: your app runs next to your data, deploys in one command, and is free to try while Compute is in public beta. If you want the rest of the story, see how we [launched Compute](/launching-prisma-compute-public-beta), why it [runs on Bun's Rust rewrite](/bun-rust-rewrite-prisma-compute), and how it handles [image transformations](/image-transformations-with-bun-on-prisma-compute) and [custom domains](/prisma-compute-custom-domains). Come build with us in [#prisma-compute](https://pris.ly/discord-compute) on Discord.

apps/blog/content/blog/create-prisma-deploy-prisma-compute/index.mdx

@@ -18,7 +18,7 @@ tags:
   - "prisma-postgres"
 ---
 
-`create-prisma` now scaffolds apps that deploy to [Prisma Compute](/blog/launching-prisma-compute-public-beta) out of the box.
+`create-prisma` now scaffolds apps that deploy to [Prisma Compute](/launching-prisma-compute-public-beta) out of the box.
 
 Run the initializer, pick a Compute-ready template, and the generated project can include:
 
@@ -53,7 +53,7 @@ export default defineComputeConfig({
 });
 ```
 
-That file is the whole deploy contract. For a closer look at it, including how it scales to monorepos, see [Configure Prisma Compute deploys in TypeScript](/blog/prisma-compute-config-file).
+That file is the whole deploy contract. For a closer look at it, including how it scales to monorepos, see [Configure Prisma Compute deploys in TypeScript](/prisma-compute-config-file).
 
 ## Add-ons that set your agent up
 
@@ -84,7 +84,7 @@ bunx @prisma/cli@latest app deploy
 
 `create-prisma` gets you from nothing to a deployed app and database in one command, with the config already wired up. From here:
 
-- Read [Configure Prisma Compute deploys in TypeScript](/blog/prisma-compute-config-file) to understand `prisma.compute.ts` and monorepo deploys in depth.
+- Read [Configure Prisma Compute deploys in TypeScript](/prisma-compute-config-file) to understand `prisma.compute.ts` and monorepo deploys in depth.
 - Follow the [deploy quickstart](https://docs.prisma.io/docs/prisma-compute/deploy) to take the generated app to a live URL.
 - Browse the [Prisma Compute docs](https://docs.prisma.io/docs/compute) for branching, environment variables, and the full CLI reference.
 

apps/blog/content/blog/enabling-cors-for-express-graphql-apollo-server-1ef999bfb38d/index.mdx

@@ -137,7 +137,7 @@ The problem is that neither `express-graphql` nor `apollo-server` accept HTTP re
 
 > [Here](https://github.com/graphql/express-graphql/issues/14) is the GitHub discussion on `express-graphql` where this issue first came up**.**
 
-Luckily, the solution is very simple. As `express-graphql` and `apollo-server` are both based on [express.js](https://github.com/expressjs), you can simply use its standard [cors](/enabling-cors-for-express-graphql-apollo-server-1ef999bfb38d/imgs/cors#configuration-options) middleware to fix the issue.
+Luckily, the solution is very simple. As `express-graphql` and `apollo-server` are both based on [express.js](https://github.com/expressjs), you can simply use its standard [cors](https://github.com/expressjs/cors#configuration-options) middleware to fix the issue.
 
 Uncommenting [line 23](https://github.com/nikolasburk/graphql-cors-example/blob/master/server/index.js#L23) in `server.js` will enable the cors middleware for your express server: `app.use(cors())`. Having the middleware enabled ensures your express server sets the proper HTTP header, enabling your React app to load data from it:
 

apps/blog/content/blog/evaluating-object-storage-providers-for-prisma-compute/index.mdx

@@ -16,7 +16,7 @@ series: prisma-compute
 seriesIndex: 10
 ---
 
-We built [Prisma Compute](https://www.prisma.io/docs/compute), now in [public beta](/blog/launching-prisma-compute-public-beta), because existing serverless compute offerings felt too limited. It runs [Bun](https://bun.sh/) in microVMs and uses automatic memory snapshotting, so it gives much of the feel of a long-running server with the pricing model of serverless.
+We built [Prisma Compute](https://www.prisma.io/docs/compute), now in [public beta](/launching-prisma-compute-public-beta), because existing serverless compute offerings felt too limited. It runs [Bun](https://bun.sh/) in microVMs and uses automatic memory snapshotting, so it gives much of the feel of a long-running server with the pricing model of serverless.
 
 Bun's batteries-included approach inspired us too. Over time, we want Prisma Compute to offer integrated solutions for email, auth, object storage, and more. This post is about one of those pieces: object storage.
 

apps/blog/content/blog/fullstack-remix-prisma-mongodb-2-ZTmOy58p4re8/index.mdx

@@ -46,7 +46,7 @@ Welcome to the second article of this series where you are learning how to build
 
 ## Introduction
 
-In the [last part](/fullstack-remix-prisma-mongodb-1-7D0BfTXBmB6r) of this series you set up your Remix project and got a MongoDB database up and running. You also configured TailwindCSS and Prisma and began to model out a `User` collection in your `schema.prisma` file.
+In the [last part](/fullstack-remix-prisma-mongodb-1-7d0bftxbmb6r) of this series you set up your Remix project and got a MongoDB database up and running. You also configured TailwindCSS and Prisma and began to model out a `User` collection in your `schema.prisma` file.
 
 In this part you will implement authentication in your application, allowing a user to create an account and sign in via sign in and sign up forms.
 

apps/blog/content/blog/fullstack-remix-prisma-mongodb-5-gOhQsnfUPXSx/index.mdx

@@ -32,7 +32,7 @@ Welcome to the last article of this series where you are learning how to build a
 
 ## Introduction
 
-In the [last part](/fullstack-remix-prisma-mongodb-4-l3MwEp4ZLIm2) of this series you wrapped up development on the Kudos application by giving your users a way to update their profile settings, add a profile picture, and delete their account and related data.
+In the [last part](/fullstack-remix-prisma-mongodb-4-l3mwep4zlim2) of this series you wrapped up development on the Kudos application by giving your users a way to update their profile settings, add a profile picture, and delete their account and related data.
 
 In this part you will deploy your application to your users using Vercel.
 

apps/blog/content/blog/image-transformations-with-bun-on-prisma-compute/index.mdx

@@ -22,7 +22,7 @@ You host the app in one place and store the images in another. Then every thumbn
 
 Prisma Compute runs on Bun, so Bun's [native image transformations](https://bun.com/docs/runtime/image) come with the runtime, at no extra charge, with no external service to manage.
 
-There is no Prisma image product to switch on, no transformation quota to track, and no second dashboard. You write a route, deploy it to [Prisma Compute](/blog/launching-prisma-compute-public-beta) next to everything else, and pay for the ordinary work your app does: requests, CPU, memory while it runs, and bytes on the way out.
+There is no Prisma image product to switch on, no transformation quota to track, and no second dashboard. You write a route, deploy it to [Prisma Compute](/launching-prisma-compute-public-beta) next to everything else, and pay for the ordinary work your app does: requests, CPU, memory while it runs, and bytes on the way out.
 
 ## Most of it is just app logic
 
@@ -406,4 +406,4 @@ bunx @prisma/cli@latest auth login
 
 Then point your agent at your project and let it write the route, deploy it, and watch the logs in the same loop it uses for the rest of your app.
 
-The [Image Transformations docs](https://docs.prisma.io/docs/compute/image-transformations) have the full feature mapping, the security checklist, and the deployment steps. For the bigger picture, see how we [launched Compute in public beta](/blog/launching-prisma-compute-public-beta), why it [runs on Bun's Rust rewrite](/blog/bun-rust-rewrite-prisma-compute), and how an [agent deploys to it from `create-prisma`](/blog/create-prisma-deploy-prisma-compute). Tell us what you build, or what breaks, in [`#prisma-compute`](https://pris.ly/discord-compute) channel on Discord.
+The [Image Transformations docs](https://docs.prisma.io/docs/compute/image-transformations) have the full feature mapping, the security checklist, and the deployment steps. For the bigger picture, see how we [launched Compute in public beta](/launching-prisma-compute-public-beta), why it [runs on Bun's Rust rewrite](/bun-rust-rewrite-prisma-compute), and how an [agent deploys to it from `create-prisma`](/create-prisma-deploy-prisma-compute). Tell us what you build, or what breaks, in [`#prisma-compute`](https://pris.ly/discord-compute) channel on Discord.

apps/blog/content/blog/prisma-compute-config-file/index.mdx

@@ -149,7 +149,7 @@ Drop a `prisma.compute.ts` next to your app, or one at your monorepo root, and d
 bunx @prisma/cli@latest app deploy
 ```
 
-Starting fresh? [`create-prisma`](/blog/create-prisma-deploy-prisma-compute) scaffolds a Compute-ready app with `prisma.compute.ts` already wired up.
+Starting fresh? [`create-prisma`](/create-prisma-deploy-prisma-compute) scaffolds a Compute-ready app with `prisma.compute.ts` already wired up.
 
 For the full field reference, see the [configuration docs](https://docs.prisma.io/docs/compute/configuration). For everything else about deploying on Compute, start with the [quickstart](https://docs.prisma.io/docs/prisma-compute/deploy).