Skip to content

chore(cli): refine production npm package - #216

Merged
Pepps233 merged 2 commits into
mainfrom
chore/npm-package-presentation
Sep 13, 2026
Merged

Pepps233 merged 2 commits into
mainfrom
chore/npm-package-presentation

Conversation

@Pepps233

@Pepps233 Pepps233 commented Sep 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Prepare the npm package with https://diffex.ai/ as its homepage, no GitHub repository metadata, and an empty README.

Keep the reference documentation Diffex uses, including skills, and hide and reject the repository's /cl prompt in production installations.

Reasoning

An installed CLI can discover repository prompt templates when launched inside a checkout.
Distribution staging now marks the installed package as production independently of NODE_ENV, so /cl remains available during source development while installed copies reject it before inference.
Documentation and license attribution remain available to the runtime and package consumers.

Changes

  • Remove repository and bugs metadata from staged manifests and exclude CONTRIBUTING.md and standalone NOTICE files.
  • Empty the staged README and preserve the 29 referenced documentation pages and their two images.
  • Exclude six unreferenced documentation assets from production: development.md, docs.json, index.md, invocation-traces.md, images/doom-extension.png, and images/exy.png.
  • Consolidate NOTICE attribution into THIRD-PARTY-NOTICES.txt and retain license and component integrity checks.
  • Filter /cl from project, global, and explicit prompt discovery in production and reject direct template invocation.
  • Point the system prompt at the product website and installed reference docs without advertising an empty README or absent example sources.

This PR prepares a future npm release; it does not change published version 0.2.1, npm tags, or the production release announcement.

Testing

  • npm run check and the full isolated ./test.sh suite passed for the runtime changes.
  • After the six documentation exclusions, reran npm run check and all 29 packaging tests, then checked a fresh full CLI tarball: all six exclusions are absent and all 31 retained docs/assets match source bytes.
  • npm run build:offline and actual npm tarball preparation passed.
  • Installed the exact candidate with npm and Bun into fresh consumers outside the repository.
  • Verified homepage, absent repository metadata, empty README, retained reference docs, and absence of AGENTS.md, CONTRIBUTING.md, and standalone NOTICE in the tarball.
  • Verified /cl is absent from installed prompt discovery and both /cl and /cl audit fail before inference using a local fixture provider.
  • Installed CLI smoke tests passed for both consumers: help, version, auth help, model listing, print mode, and interactive startup, prompt response, login navigation, and exit.
  • All inference validation used local fixtures; no real provider calls were made.

- Present the product homepage while preserving runtime documentation and attribution.
- Keep the repository changelog prompt out of installed production command discovery and execution.
@Pepps233 Pepps233 added enhancement New feature or request coding-agent labels Sep 13, 2026
@Pepps233 Pepps233 self-assigned this Sep 13, 2026
- Limit installed documentation to the runtime references and linked assets.
- Verify the actual tarball preserves retained documentation without deleting source files.
@Pepps233
Pepps233 merged commit 06830a9 into main Sep 13, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

coding-agent enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant