docs: add community health files (CONTRIBUTING, COC, issue templates)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,24 @@
+---
+name: Bug report
+about: Report something broken in supercut
+title: "bug: "
+labels: bug
+---
+
+## What happened?
+
+## Expected behavior
+
+## Steps to reproduce
+
+1.
+2.
+3.
+
+## Environment
+
+- OS:
+- Node version:
+- supercut version/commit:
+
+## Logs or screenshots

.github/ISSUE_TEMPLATE/demo_request.md

@@ -0,0 +1,24 @@
+---
+name: Demo request
+about: Request or submit a product demo made with supercut
+title: "demo: "
+labels: demo
+---
+
+## Product URL
+
+## Best 3-4 moments to show
+
+1.
+2.
+3.
+4.
+
+## Target audience
+
+## Preferred style
+
+- Fast launch trailer
+- Calm product walkthrough
+- Developer-tool demo
+- Other:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest a new supercut capability
+title: "feat: "
+labels: enhancement
+---
+
+## Problem
+
+What user pain does this solve?
+
+## Proposal
+
+What should supercut do?
+
+## Alternatives considered
+
+## Example output
+
+If this is visual, include a screenshot, mockup, or sample video.

CODE_OF_CONDUCT.md

@@ -0,0 +1,7 @@
+# Code of Conduct
+
+supercut should be a useful, welcoming project for builders, designers, and open-source contributors.
+
+Be respectful, constructive, and specific. Harassment, personal attacks, and discriminatory behavior are not welcome.
+
+If you report a problem, include enough context for maintainers to understand and act on it. Maintainers may remove comments, close issues, or block users who make the project unsafe or unproductive.

CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing to supercut
+
+Thanks for helping build supercut.
+
+## Local setup
+
+```bash
+npm install
+npm run build
+npm run test
+```
+
+## Good first contributions
+
+Good starter tasks usually improve one narrow part of the project:
+
+- add or improve a recipe in `examples/`,
+- add tests for schema validation,
+- improve CLI error messages,
+- document a recorder or renderer edge case,
+- add a small render theme or background asset.
+
+## Pull request checklist
+
+Before opening a PR:
+
+- Run `npm run build`.
+- Run `npm run test`.
+- Keep the PR focused on one change.
+- Add or update tests when behavior changes.
+- Include screenshots, videos, or generated artifacts for visual changes.
+
+## Project principles
+
+- Real product footage beats mockups.
+- The event log is a public contract.
+- Non-AI recorder/render paths should remain useful without an API key.
+- Defaults should produce a launch-ready video, not a raw screen recording.