chore: clean npm tarball, restructure README for sellability, add July metrics#74
Merged
Merged
Conversation
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
.opencode/package-lock.jsonand.opencode/package.jsonno longer ship in the npm tarball. These dev-only plugin dependency files were scanned by Socket.dev, which flagged Apache-2.0 transitive deps and docked the license score to 70 despite MIT licensing. Fixed by replacing the wildcard"files": [".opencode"]with explicit subdirectories.<details>, trimmed verbose behavior notes, moved permission YAML into<details>, and rewrote the agent "Best For" column from role labels to action+outcome.Validation
npm run doctor— 17/17 passednpm run lint:md— cleannpm pack --dry-run— 105 files (was 107), 104.3 kB (was 108.8 kB), dev lock files excludedAgent Behavior & Policy Impact
Risk & Rollback
508009a. README changes are cosmetic. The tarballfileschange is additive — it removes files that were never consumed at install/runtime, so no functional regression is possible.