Refactor authored tooling to TypeScript

[JustineDevs]

Summary

• migrate tests and operational scripts from JavaScript to TypeScript
• compile test and script entrypoints for Node 18 execution
• use the TypeScript Next config and keep PostCSS in its supported config format

Verification

• pnpm check
• pnpm --filter agent-compat-docs build
• 53 tests and 41 adapter conformance cases passed

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agents	Ready	Preview	Aug 22, 2026 8:29pm

[chatgpt-codex-connector]

💡 Codex Review

agent-compat/packages/agents/package.json

Lines 33 to 34 in 5b5d36d

	"files": [
	"dist",

Stage the compiled distribution for GitHub Packages

When the tag-triggered github-package.yml workflow runs pnpm publish:github, the staging script still copies only src, while this new files allowlist and the package entry points require dist. Consequently, npm excludes the staged source and publishes a package containing only package.json, README, and LICENSE, so importing @JustineDevs/agents fails. Copy the built dist directory into the staging area instead.

---

agent-compat/packages/agents/src/index.ts

Line 2 in 5b5d36d

export type * from "./types.js";

Preserve the public result types in generated declarations

This re-export now exposes only the reduced set in types.ts, dropping previously public types such as DetectionResult, CompileResult, ValidationResult, ValidationReport, and RuntimeVerification (as well as the testing ConformanceResult). The implementation also lacks corresponding return annotations, so the generated declaration infers validate() with results: {}; ordinary consumer code such as report.results.cursor no longer type-checks, which is why the converted internal tests and smoke script now cast these values to any. Restore the public interfaces and use them to annotate the exported functions.

ℹ️ 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".