chore: complete package.json metadata for npm discovery

[beogip]

Priority: P0 (blocking for the announcement)
Source: pre-announcement LinkedIn review note (marketer, 2026-06-03), approved 2026-06-07.

Why

Anyone searching npmjs or landing on the package page sees this metadata. It's currently incomplete, which hurts discoverability and the perception of maturity right when the announcement drives traffic.

Verified current state

• The keywords field is missing entirely.
• Weak description: "Code-first agent tool definitions with Zod schemas". The GitHub repo's one is much better and they should be aligned.
• homepage is missing.
• bugs is missing.

Tasks

1. Add keywords (5 to 8): e.g. ai-agents, llm-tools, tool-use, zod, cli-tools, structured-output, deterministic-tools, code-first-agents. Align with the repo's existing topics.
2. Align description with the GitHub repo's (the rich one: "A code-first framework for building deterministic CLI tools that LLM agents can discover, validate, and invoke with zero guesswork...").
3. Add homepage pointing to the canonical URL (see the canonical URL issue, ideally code-first-agents.com).
4. Add bugs with the repo's issues URL.
5. Version bump (patch) so the new metadata reaches npm.

[claude]

Claude finished @beogip's task in 2m 18s —— View job • claude/issue-24-20260607-1604 • [Create PR ➔](https://github.com/beogip/code-first-agents-tool/compare/main...claude/issue-24-20260607-1604?quick_pull=1&title=Issue%20%2324%3A%20Changes%20from%20Claude&body=This%20PR%20addresses%20issue%20%2324%0A%0AGenerated%20with%20%5BClaude%20Code%5D(https%3A%2F%2Fclaude.ai%2Fcode)

---

Completing package.json metadata for npm discovery ✅

All tasks done. PR opened: #31

• Read current package.json and gather repo metadata/topics
• Add keywords (8, aligned with repo topics)
• Align description with the GitHub repo's rich description
• Add homepage
• Add bugs
• Handle version bump (via release-triggering commit)
• Run checks — biome ✅, tsc ✅, bun test 113 pass ✅
• Commit, push, open PR

Changes to package.json

Field	Change
description	Aligned with the repo's rich description: "A code-first framework for building deterministic CLI tools that LLM agents can discover, validate, and invoke with zero guesswork. Powered by Zod schemas and structured output contracts."
keywords	Added: ai-agents, llm-tools, tool-use, zod, cli-tools, structured-output, deterministic-tools, code-first-agents
homepage	https://github.com/beogip/code-first-agents-tool#readme
bugs	https://github.com/beogip/code-first-agents-tool/issues

Two decisions worth your eyes

1. Version bump (task [#1] feat: export public API via barrel file #5): This repo publishes via semantic-release, which owns the version field and commits it as a release asset. Hand-editing version would fight the automation, so I made this a fix: commit — semantic-release will cut a patch on merge to main and carry the new metadata to npm. (A chore: commit would not trigger a publish, so the metadata wouldn't reach npm.)

2. homepage: The issue mentions an ideal canonical code-first-agents.com, pending the separate canonical-URL issue. Until that's decided I pointed homepage at the GitHub repo #readme — safe and non-speculative, trivial to swap once the domain is finalized.
   • PR #31 • branch claude/issue-24-20260607-1604

[github-actions]

🎉 This issue has been resolved in version 0.1.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀