Skip to content

docs(readme): pare the root README down to a human-written overview - #54

Merged
ScriptedAlchemy merged 4 commits into
mainfrom
docs/readme-pare-down
Aug 31, 2026
Merged

docs(readme): pare the root README down to a human-written overview#54
ScriptedAlchemy merged 4 commits into
mainfrom
docs/readme-pare-down

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Summary

Closes #53.

The root README read like generated marketing text: 325 lines of dense capability prose, an install instruction that doesn't work, and deep reference material duplicated from the package README and docs. This pares it down to ~75 lines a newcomer can read in under a minute: what the tool is, how to install it today, a verified quickstart, the command list, the examples table, and pointers to the docs that own the detail.

What changed

  • Install section corrected. The old README led with npm install --save-dev agent-bundle — that npm name currently belongs to an unrelated project (yujiachen-y/agent-bundle, last published v0.1.2), so the instruction installed the wrong package. The new README leads with the pkg.pr.new preview URL and says so plainly.
  • Quickstart verified end-to-end in a clean temp project: npm i -D https://pkg.pr.new/ScriptedAlchemy/agent-bundle/agent-bundle@6427206 (plain npm, no --legacy-peer-deps), minimal agent-bundle.config.ts + one skill, npx agent-bundle build --root . --output distdist/plugin/ with .claude-plugin/, .codex-plugin/, .cursor-plugin/, and the generated AGENTS.md install matrix.
  • feat(build): agent-bundle owns the package build — bin/lib, entry conventions, stdio entry shell, tools hatch, mcp run (RFC #50 Phase 1) #52 reconciled. After it merged, main was merged in and its "One config" story is folded into the quickstart as one paragraph (bin/lib, entry conventions, framework stdio lifecycle, tools escape hatch) linking to docs/entry-conventions.md; mcp run joined the command list.
  • Cut, not lost: the workbench/Agent API detail, configuration semantics, artifact contract, and host-install matrix all remain owned by packages/agent-bundle/README.md (ships to npm), docs/preview-packages.md, the architecture doc, and each built bundle's generated AGENTS.md. The root now links instead of duplicating.
  • One docs-contract test re-targeted. api.test.ts > documents a versioned MCP App resource URI accepted by source validation grepped the root README for a resourceUri: '…' example that only existed inside the removed configuration wall. The pin now reads the real documented example, examples/mcp-app/agent-bundle.config.ts, and fails loudly if that example ever loses its resourceUri. The behavioral assertion (documented URI passes source validation) is unchanged.
  • Command list checked against agent-bundle --help from a fresh workspace build.
  • Added an honest Status section: pre-release, final npm name and license not yet chosen (there is no LICENSE file; the release docs say this is deliberate).

Not changed

  • Package READMEs (npm-facing, self-contained) and docs/ are untouched.

Gates

pnpm typecheck, pnpm lint (0 errors/warnings), pnpm test:unit (all pass), and the re-targeted integration test file run locally on the merged tree.

Closes #53. Replace the 325-line generated-reading README with a short
overview: honest description, the pkg.pr.new install path (the npm
`agent-bundle` name belongs to an unrelated project), a verified
quickstart, a command list, the examples table, and pointers to the
package README and docs that own the deep detail.
@changeset-bot

changeset-bot Bot commented Aug 31, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7f58fb4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-31T02:11:32.386770Z 8256ead PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8256eadfd3

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

Comment thread README.md Outdated
No version has been published to npm yet. Until the first release is cut,
install the identical preview package CI publishes for every commit and pull
request — see [Preview packages](docs/preview-packages.md).
Any `main` commit SHA or PR number works. See [Preview packages](docs/preview-packages.md) for pinning and details.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Qualify which SHAs have preview tarballs

This overstates preview availability: a main commit whose package-preview workflow failed, or a PR without a successful preview run, has no tarball at this URL and produces a 404. The detailed guidance in docs/preview-packages.md correctly limits SHA installs to commits that had a package-preview run, so mirror that qualification here rather than promising that any SHA or PR number works.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in 7fe5280: the install line now says to use a PR number or the SHA of a commit whose package-preview run succeeded, mirroring docs/preview-packages.md.

@pkg-pr-new

pkg-pr-new Bot commented Aug 31, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle@54
npm i https://pkg.pr.new/ScriptedAlchemy/agent-bundle/@agent-bundle/rsc-runtime@54

commit: 7f58fb4

@ScriptedAlchemy
ScriptedAlchemy merged commit f5c3b0d into main Aug 31, 2026
9 checks passed
@ScriptedAlchemy
ScriptedAlchemy deleted the docs/readme-pare-down branch August 31, 2026 02:49
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.

Unslop the README?

1 participant