From ae22379668b34cde6f0ce8e5ad0bc5ec98934852 Mon Sep 17 00:00:00 2001 From: amankumarsingh77 Date: Sat, 2 May 2026 00:08:22 +0530 Subject: 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 --- .github/ISSUE_TEMPLATE/feature_request.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md (limited to '.github/ISSUE_TEMPLATE/feature_request.md') 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. -- cgit v1.2.3