chore: prepare v0.1.0 release

- Add hero image for pi package gallery
- Update CHANGELOG with release date
- Update README with npm install instructions
- Add assets/ to npm package files
- Add CONTRIBUTING.md and GitHub templates
- Add CI workflow for typecheck and pack validation

2 files changed, 63 insertions, 0 deletions

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..87023dc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Report a reproducible problem with pi-browser-harness
+title: "[Bug]: "
+labels: bug
+assignees: ""
+---
+
+## Description
+
+Describe the problem clearly. Include what browser action or pi tool failed, if applicable.
+
+## Steps to Reproduce
+
+1.
+2.
+3.
+
+Please include the exact prompt, command, or tool call sequence when possible.
+
+## Expected Behavior
+
+What did you expect to happen?
+
+## Actual Behavior
+
+What happened instead? Include error messages, screenshots, or relevant logs if available.
+
+## Environment
+
+- OS:
+- Node version (`node --version`):
+- Chrome / Chromium / Edge version:
+- pi version:
+- pi-browser-harness version or commit:
+- Install method (`npm`, `git`, local path):
+
+## Additional Context
+
+Add any other context that may help diagnose the issue, such as whether Chrome remote debugging was enabled through `chrome://inspect/#remote-debugging` or launched with `--remote-debugging-port=9222`.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 0000000..4944eed
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an improvement or new browser-control capability
+title: "[Feature]: "
+labels: enhancement
+assignees: ""
+---
+
+## Problem Statement
+
+What problem are you trying to solve? Describe the workflow, limitation, or browser-control gap.
+
+## Proposed Solution
+
+Describe the behavior you would like to see. If this is a new browser tool, include the proposed `browser_*` name, inputs, and expected output if you have a preference.
+
+## Alternatives Considered
+
+What alternatives or workarounds have you tried? For example, could this be handled with `browser_execute_js`, `browser_http_get`, or `browser_run_script` today?
+
+## Additional Context
+
+Add examples, screenshots, links, or related Chrome DevTools Protocol details that would help explain the request.