Skip to content

Update READMEs for npm - #291

Merged
chiragjn merged 3 commits into
mainfrom
cj-npm-packages-readmes
Aug 16, 2026
Merged

Update READMEs for npm#291
chiragjn merged 3 commits into
mainfrom
cj-npm-packages-readmes

Conversation

@chiragjn

@chiragjn chiragjn commented Aug 16, 2026

Copy link
Copy Markdown
Member

Note

Low Risk
Documentation, npm metadata, and packaging comments only; no application or library runtime logic changes.

Overview
Improves how TrueForge packages look on npm and in docs by adding package READMEs, shipping them in tarballs, and aligning branding with trueforge.dev.

New READMEs for @truefoundry/trueforge-core and @truefoundry/trueforge (quick start, links to docs, related packages). @truefoundry/trueforge-sdk README gains a Documentation section pointing to the API reference.

npm tarballs for trueforge-core and trueforge now include README.md via files; RELEASING.md, AGENTS.md, and check-dist.mjs comments are updated to match.

Metadata: homepage for core and trueforge packages moves from GitHub tree URLs to https://trueforge.dev; descriptions use “Agent Harness” wording. Root README adds a row of npm version badges for the four published packages.

Fern generators.yml sets apiName: TrueForge, apiReferenceLink, and the same Agent Harness intro text. A changeset records a patch bump for @truefoundry/trueforge-sdk from OpenAPI regeneration (no SDK source diff in this PR beyond README).

Reviewed by Cursor Bugbot for commit 29551c5. Bugbot is set up for automated code reviews on this repo. Configure here.

@chiragjn
chiragjn merged commit 5100c59 into main Aug 16, 2026
10 checks passed
@chiragjn
chiragjn deleted the cj-npm-packages-readmes branch August 16, 2026 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant