Repository navigation
chore: add open-source community files - #5
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.
What / why
Adds the standard open-source community scaffolding so contributors know how to engage: CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, issue/PR templates, and a CI workflow. Also enriches package.json metadata and README with contributing, security-reporting, and license sections plus CI/license badges.
Spec / issue
n/a — docs/config-only change, no behavior change (per CONTRIBUTING.md, trivial changes may skip the spec).
Verification
npm run typechecknpm run lintnpm test(32 files, 254 tests passed) + build passednpm run buildPre-push checks ran green on the branch before pushing. No src/ changes; CI workflow repeats these on the PR.
Docs updated
This PR is docs/config: CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, README.md sections. No architecture change, no decisions.md update needed.