Improve DevTinder agentic readiness - #3
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7a6fd701a9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -0,0 +1,8 @@ | |||
| import { describe, expect, it } from "vitest"; | |||
There was a problem hiding this comment.
On a clean install this new test imports vitest, but neither package.json nor package-lock.json declares Vitest or a test runner script, while the repo tsconfig.json includes all **/*.ts files. Any build/typecheck/test job that resolves src/app/page.test.ts will fail with an unresolved vitest module before the homepage assertion can run, so add the dev dependency and wiring or remove this test file.
Useful? React with 👍 / 👎.
1 participant
Implements the requested agent-readiness fixes: server-rendered homepage content, public trust pages, recoverable 404s, llms.txt with markdown negotiation and Vary: Accept, richer JSON-LD, and sitemap/robots updates. Note: brand search discoverability still requires indexing/SEO signals and contactPoint email/phone requires product-owned credentials.