Update issue templates

Author: HilthonTT

.github/ISSUE_TEMPLATE/-bug-.md

@@ -0,0 +1,58 @@
+---
+name: "[BUG]"
+about: " Report a lexer/parser/typecheck/codegen/VM bug or wrong runtime behavior"
+title: ''
+labels: bug
+assignees: HilthonTT
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+ 
+**Stage / component**
+Where does it go wrong?
+ 
+- [ ] Lexer
+- [ ] Parser
+- [ ] Type checker (gradual types)
+- [ ] Optimizer / bytecode generator
+- [ ] VM (runtime, closures, coroutines, metatables)
+- [ ] Native module (name: `______`)
+- [ ] REPL
+- [ ] Tooling (`fmt` / `build` / `analyze` / `profile`)
+**Minimal reproduction**
+The smallest `.lsc` snippet that triggers it:
+ 
+```lua
+-- your minimal script here
+```
+ 
+**How you ran it**
+```bash
+# e.g. go run ./cmd examples/mycase.lsc
+#      go run ./cmd -dis mycase.lsc   (bytecode dump often helps codegen bugs)
+```
+ 
+**Expected behavior**
+What you expected (output value, or that it should/shouldn't be a compile error).
+ 
+**Actual behavior**
+What actually happened. Paste the full output, including any `type-error:` prefix or Go panic + stack trace.
+ 
+```
+# Paste output here
+```
+ 
+**Mode directive**
+Was the file `--!strict`, `--!nonstrict`, `--!nocheck`, or none (default gradual)?
+ 
+**Environment**
+- Go version (`go version`):
+- OS / arch:
+- Commit / branch:
+- Build tags (e.g. plain, or `-tags luascript_ui`):
+- Relevant env (`LUASCRIPT_LIB`, `package.path` entries) if it's a `require` / module issue:
+**Additional context**
+- Is this behavior different from stock Lua 5.4? If so, how does `lua5.4` handle the same snippet?
+- Note: some things are deliberately out of scope for type-system v1 (generics, intersections, refinements, string-singletons, cross-module type checking, recursive aliases) — see the README "Not in v1" list before filing a typecheck issue.

.github/ISSUE_TEMPLATE/-feature-.md

@@ -0,0 +1,40 @@
+---
+name: "[FEATURE]"
+about: Suggest a language feature, native module, or tooling improvement
+title: ''
+labels: enhancement
+assignees: HilthonTT
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+ 
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+ 
+**Area**
+What does this touch?
+ 
+- [ ] Syntax / parser
+- [ ] Type system
+- [ ] Bytecode / VM semantics
+- [ ] Standard library
+- [ ] Native module (existing or new: `______`)
+- [ ] Tooling (`fmt` / `build` / `analyze` / `profile` / REPL)
+**Prior art**
+How do Lua 5.4 and/or Luau handle this? Link the relevant reference if there is one — the project tracks Lua 5.4 semantics and Luau's type-system shape.
+ 
+**Sketch**
+Example of the proposed syntax or API in `.lsc`:
+ 
+```lua
+-- how it would look
+```
+ 
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+ 
+**Additional context**
+- If this is a type-system feature, note that generics, intersections, refinements, string-singletons, cross-module type checking, and recursive aliases are explicitly deferred past v1 — say whether this is one of those or something new.
+- Anything else: performance implications, whether types can stay fully erased before bytecode, etc.