Repository navigation
chore(cli): refine production npm package - #216
Merged
Merged
Conversation
- Present the product homepage while preserving runtime documentation and attribution. - Keep the repository changelog prompt out of installed production command discovery and execution.
- Limit installed documentation to the runtime references and linked assets. - Verify the actual tarball preserves retained documentation without deleting source files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
/clprompt 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/clremains available during source development while installed copies reject it before inference.Documentation and license attribution remain available to the runtime and package consumers.
Changes
CONTRIBUTING.mdand standaloneNOTICEfiles.development.md,docs.json,index.md,invocation-traces.md,images/doom-extension.png, andimages/exy.png.THIRD-PARTY-NOTICES.txtand retain license and component integrity checks./clfrom project, global, and explicit prompt discovery in production and reject direct template invocation.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 checkand the full isolated./test.shsuite passed for the runtime changes.npm run checkand 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:offlineand actual npm tarball preparation passed.AGENTS.md,CONTRIBUTING.md, and standaloneNOTICEin the tarball./clis absent from installed prompt discovery and both/cland/cl auditfail before inference using a local fixture provider.