docs: add community health files

Author: DKFuH

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Report incorrect behavior in the OrgScript language, CLI, exporters, editor support, or docs
+title: "[Bug] "
+labels: bug
+assignees: ""
+---
+
+## Summary
+
+Describe the bug clearly and briefly.
+
+## Steps to reproduce
+
+1. 
+2. 
+3. 
+
+## Expected behavior
+
+What should have happened?
+
+## Actual behavior
+
+What happened instead?
+
+## Reproduction input
+
+If relevant, include:
+
+- the `.orgs` file or a minimal snippet
+- the command you ran
+- the diagnostics or output you received
+
+## Environment
+
+- OrgScript version:
+- Node.js version:
+- OS:
+
+## Additional context
+
+Add any other context, screenshots, or notes here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: OrgScript contribution guide
+    url: https://github.com/DKFuH/OrgScript/blob/main/CONTRIBUTING.md
+    about: Read the contribution guidelines before proposing larger language or tooling changes.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,36 @@
+---
+name: Feature request
+about: Suggest an improvement to the language, tooling, docs, or ecosystem
+title: "[Feature] "
+labels: enhancement
+assignees: ""
+---
+
+## Summary
+
+Describe the idea in one or two sentences.
+
+## Problem
+
+What problem does this solve?
+
+## Proposed direction
+
+Describe the smallest useful version of the idea.
+
+## Why this fits OrgScript
+
+Explain how the idea aligns with:
+
+- clarity over cleverness
+- explicit semantics over shorthand
+- human readability and machine parseability
+- small, composable language growth
+
+## Alternatives considered
+
+What alternatives or workarounds exist today?
+
+## Additional context
+
+Add any examples, links, sketches, or prior discussion here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+## Description
+
+Please include a summary of the change and any relevant issue links.
+
+## Type of change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Documentation update
+- [ ] Refactor or maintenance change
+
+## Validation
+
+- [ ] I ran the relevant checks locally
+- [ ] I updated tests or fixtures where needed
+- [ ] I updated docs if the change affects user-facing behavior
+
+## Notes
+
+Anything reviewers should pay special attention to.

CODE_OF_CONDUCT.md

@@ -0,0 +1,54 @@
+# Code of Conduct
+
+OrgScript is committed to a respectful, constructive, and professional community.
+
+## Our standards
+
+Examples of behavior that help create a positive environment include:
+
+- being respectful in language, tone, and intent
+- giving actionable, specific, and kind feedback
+- assuming good faith while still discussing tradeoffs honestly
+- welcoming people with different backgrounds, skill levels, and perspectives
+- focusing on what helps the language, tooling, and community move forward
+
+Examples of unacceptable behavior include:
+
+- harassment, intimidation, or personal attacks
+- hateful, discriminatory, or demeaning language
+- bad-faith arguments, trolling, or deliberate derailment
+- publishing other people's private information without permission
+- repeated dismissive or hostile behavior after being asked to stop
+
+## Scope
+
+This Code of Conduct applies in OrgScript spaces, including:
+
+- GitHub issues
+- pull requests
+- discussions
+- release threads
+- other project communication channels managed by the maintainers
+
+## Enforcement
+
+Project maintainers may remove, edit, or reject comments, issues, pull requests, or other contributions that violate this Code of Conduct.
+
+Maintainers may also take any action they consider appropriate, including temporary or permanent bans from project spaces.
+
+## Reporting
+
+If you experience or witness unacceptable behavior, please contact the maintainers through the repository owner contact listed on GitHub or via the project's published contact route.
+
+When reporting, include:
+
+- what happened
+- where it happened
+- links or screenshots if available
+- any relevant surrounding context
+
+Reports will be reviewed as promptly and fairly as possible.
+
+## Attribution
+
+This Code of Conduct is informed by the Contributor Covenant spirit, adapted to fit OrgScript's project size and governance style.

README.md

@@ -233,6 +233,12 @@ npm run demo:generate
 - Language evolution: [docs/language-evolution.md](./docs/language-evolution.md)
 - Changelog: [CHANGELOG.md](./CHANGELOG.md)
 
+## Community
+
+- Contributing guide: [CONTRIBUTING.md](./CONTRIBUTING.md)
+- Code of Conduct: [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md)
+- Security policy: [SECURITY.md](./SECURITY.md)
+
 ## License
 
 Apache-2.0

SECURITY.md

@@ -0,0 +1,29 @@
+# Security Policy
+
+## Supported versions
+
+OrgScript is still evolving quickly. In practice, the latest released version is the supported version for security fixes.
+
+## Reporting a vulnerability
+
+Please do not open a public GitHub issue for a suspected security vulnerability.
+
+Instead, report it privately to the maintainer through the repository owner's GitHub contact route or the published repository contact information.
+
+When possible, include:
+
+- a short description of the issue
+- affected version or commit
+- steps to reproduce
+- expected impact
+- any suggested mitigation if known
+
+We will review the report, reproduce it where possible, and determine the appropriate fix and disclosure path.
+
+## Disclosure approach
+
+OrgScript aims for responsible disclosure:
+
+- acknowledge valid reports
+- work on a fix before broad public disclosure when practical
+- publish relevant release notes once a fix is available