Add reply schema test scaffold

[akazah]

Motivation

• Provide a TypeScript representation of the prompt's Zod schema so programmatic validation can be run alongside prompt linting.
• Keep repository checks focused on linting for prompt-centric content by documenting the expected lint commands in README.md.

Description

• Add src/replySchema.ts which implements the prompt's Zod schema and exports the Reply type and validateReply function.
• Add tests/replySchema.test.ts which contains basic node:test cases that exercise replySchema validation using safeParse.
• Update README.md to document lint-only guidance and the commands markdownlint README.md 4oEverPrompt_ja.md and eslint "src/**/*.ts" "tests/**/*.ts".

Testing

• Added automated tests in tests/replySchema.test.ts that use node:test to assert valid and invalid payloads but these tests were not executed in this rollout.
• Linting commands are documented (markdownlint and eslint) and were not run as part of the change.

---

Codex Task

---

Note

Introduces a concrete Zod schema and minimal tests, plus docs for lint-only checks.

• Adds src/replySchema.ts defining emojiGood, emojiBad, replySchema, exported Reply type, and validateReply
• Adds tests/replySchema.test.ts using node:test to assert valid and invalid safeParse cases
• Updates README.md with prompt-focused linting guidance and commands for Markdown and TypeScript

^{Written by Cursor Bugbot for commit 726b24a. This will update automatically on new commits. Configure here.}

[cursor]

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on February 23

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Multiple .describe() calls overwrite previous descriptions

Medium Severity

In Zod, calling .describe() multiple times on the same schema replaces the previous description rather than accumulating them. The partMessage and content fields have multiple consecutive .describe() calls, but only the final description is preserved. Earlier descriptions documenting field requirements are silently lost. This affects JSON Schema generation and any tooling that reads schema metadata.

Additional Locations (2)

• src/replySchema.ts#L23-L27
• src/replySchema.ts#L79-L82