feat(release): prepare TechScript 2.0 public open source release

- freeze TechScript 2.0 canonical syntax

- migrate repository to final syntax

- update compiler, parser and documentation

- modernize installer and setup tooling

- setup CI/CD pipeline and release packaging workflows

- clean legacy cache, build and temporary artifacts

Author: Tcode-Motion

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,37 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully receiving constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best for the overall community, not just the individual
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and unwelcome sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate, fair corrective action in response to any behavior they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers at **support@techscript.is-a.dev**. All complaints will be reviewed and investigated promptly and fairly.

.github/CONTRIBUTING.md

@@ -0,0 +1,105 @@
+# Contributing to TechScript
+
+Thank you for deciding to contribute to TechScript! As an open-source project aiming to build a human-first programming language, we value your help in expanding the language features, stabilizing the VM, updating documentation, and building developer tools.
+
+---
+
+## 🛠️ Setting Up Your Development Environment
+
+TechScript is written entirely in **Rust** as a Cargo workspace. To get started, make sure you have the following installed:
+
+1. **Rust Toolchain**: Install via rustup:
+   ```bash
+   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
+   ```
+2. **Git**: For version control.
+3. **Clang/LLVM** (Optional, required for LLVM-backend contributions):
+   * **Ubuntu/Debian**: `sudo apt install llvm-dev libclang-dev`
+   * **macOS**: Installed via Xcode CLI tools or homebrew (`brew install llvm`).
+   * **Windows**: Download the LLVM installer or use `winget install LLVM.LLVM`.
+
+### Fork & Clone
+1. Fork the TechScript repository on GitHub.
+2. Clone your fork locally:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/techscript.git
+   cd techscript
+   ```
+3. Add the upstream remote:
+   ```bash
+   git remote add upstream https://github.com/Tcode-Motion/techscript.git
+   ```
+
+---
+
+## 📂 Repository Structure Overview
+
+The codebase is organized like Rust and Zig to keep compilation, execution, and tools clean:
+
+* `compiler/` - Lexer, parser, semantic analyzer, AST, IR, optimizer, and LLVM backend.
+* `runtime/` - Virtual Machine (VM), Tree-walking interpreter, garbage collector, and native runtime.
+* `stdlib/` - Standard library written in TechScript and Rust.
+* `cli/` - The unified `tech` command-line executable.
+* `tools/` - Formatter, linter, LSP, and package manager.
+* `examples/` - Working demonstration scripts.
+* `tests/` - System integration and language regression tests.
+* `benchmarks/` - Scripts and suites for testing engine performance.
+
+---
+
+## 🔄 Development & Git Workflow
+
+We use a standard branching model. Always make changes on a descriptive branch, not on the `main` branch.
+
+### 1. Create a Branch
+```bash
+git checkout -b feature/my-cool-feature
+# or
+git checkout -b fix/issue-123
+```
+
+### 2. Make Edits & Run Linting
+We enforce strict styling and quality rules. Run these commands locally before committing:
+```bash
+# Verify formatting
+cargo fmt --all -- --check
+
+# Run linter
+cargo clippy --workspace --all-targets -- -D warnings
+
+# Build all workspace targets
+cargo build --workspace
+```
+
+### 3. Run Tests
+Verify both Rust internal tests and TechScript integration tests pass:
+```bash
+cargo test --workspace
+```
+
+### 4. Committing Changes
+We follow [Conventional Commits](https://www.conventionalcommits.org/):
+* `feat: ...` for new features or syntax.
+* `fix: ...` for compiler/runtime bug fixes.
+* `docs: ...` for documentation changes.
+* `style: ...` for formatting updates.
+* `refactor: ...` for code restructurings.
+* `test: ...` for adding/updating tests.
+
+Example:
+```bash
+git commit -m "feat: add support for pattern matching default keyword"
+```
+
+---
+
+## 📝 Pull Request Checklist
+
+Before submitting a Pull Request:
+- [ ] Ensure all code compiles without warning.
+- [ ] Run `cargo fmt` and `cargo clippy`.
+- [ ] Add corresponding documentation in `docs/` if modifying syntax, CLI flags, or standard libraries.
+- [ ] Add regression tests inside `tests/` or examples in `examples/`.
+- [ ] Link the issue you are fixing in the PR description (e.g., `Fixes #123`).
+
+Once submitted, our CI workflow will run automated checks on Windows, Linux, and macOS. A maintainer will review your code and request adjustments if necessary.

.github/DISCUSSION_TEMPLATE.md

@@ -0,0 +1,19 @@
+# Discussion Proposal
+
+## Summary
+A concise overview of the topic you want to discuss with the community.
+
+## Purpose
+Why is this discussion important? What decisions are we trying to make or what opinions are we seeking?
+
+## Key Points of Discussion
+- **Point 1**: [Describe first aspect]
+- **Point 2**: [Describe second aspect]
+- **Point 3**: [Describe third aspect]
+
+## Proposed Solutions / Implementation Ideas
+If applicable, outline how you envision this being addressed or designed.
+
+```txs
+# Code mockups or syntax layouts if relevant
+```

.github/FUNDING.yml

@@ -0,0 +1,6 @@
+# Funding configurations
+
+github: [Tcode-Motion]
+patreon: tcodemotion
+ko_fi: tcodemotion
+custom: ['https://techscript.is-a.dev/sponsor']

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,26 +1,38 @@
 ---
-name: Bug Report
-about: Create a report to help us improve TechScript 2.0
-title: '[BUG] '
+name: 🐛 Bug Report
+about: Create a report to help us improve TechScript.
+title: "[BUG] "
 labels: bug
-assignees: ''
-
+assignees: ""
 ---
 
 **Describe the bug**
 A clear and concise description of what the bug is.
 
 **To Reproduce**
-Steps to reproduce the behavior:
-1. Provide a minimal TechScript code sample (`.txs`).
-2. Run command: `tech run <filename>.txs`
-3. See error details.
+Steps to reproduce the behavior, including a minimal TechScript code sample.
+
+```txs
+# Paste minimal TechScript code sample here
+```
+
+**Command Run**
+What CLI command did you execute? (e.g. `tech run main.txs`)
 
-**Expected behavior**
+**Expected Behavior**
 A clear and concise description of what you expected to happen.
 
-**Diagnostics and Environment Output**
-- OS: [e.g. Windows, Ubuntu, macOS]
-- Rust Compiler Version: [e.g. `rustc --version`]
-- Tech CLI version: [e.g. `tech version`]
-- Emitted Diagnostics: [Paste terminal print details here]
+**Actual Output / Error Log**
+If applicable, paste the exact error message or stack trace you received.
+
+```
+# Paste logs/errors here
+```
+
+**Environment Info:**
+ - OS: [e.g. Windows 11, Ubuntu 24.04, macOS Sonoma]
+ - TechScript Version: [e.g. v2.0.0]
+ - CLI Wrapper Version: [e.g. pip techscript-lang v1.0.8]
+
+**Additional Context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,26 @@
 ---
-name: Feature Request
-about: Propose a new language feature, tool, or syntax addition
-title: '[FEAT] '
+name: 🚀 Feature Request
+about: Propose an idea or syntax extension for TechScript.
+title: "[FEATURE] "
 labels: enhancement
-assignees: ''
-
+assignees: ""
 ---
 
 **Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. E.g. "I'm frustrated when..."
+A clear and concise description of what the problem is. (e.g. "I'm frustrated when I try to...")
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen. Provide proposed syntax examples where applicable.
+A clear and concise description of what you want to happen. Mention proposed syntax, keywords, or stdlib additions.
+
+**Example Code (TechScript)**
+Show what the syntax should look like:
+
+```txs
+# Proposed syntax example
+```
 
 **Describe alternatives you've considered**
 A clear and concise description of any alternative solutions or workarounds you've considered.
 
-**Additional context**
-Add any other context, designs, or mockups about the feature request here.
+**Additional Context**
+Add any other context or mockups about the feature request here.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,23 @@
+---
+name: ❓ Question / Support Request
+about: Ask a question about syntax, features, installation, or documentation.
+title: "[QUESTION] "
+labels: question
+assignees: ""
+---
+
+**What is your question?**
+State your question clearly.
+
+**What have you tried so far?**
+If you are troubleshooting a specific snippet of code or command, share it here.
+
+```txs
+# Share your code if applicable
+```
+
+**Relevant Documentation**
+Did you check the docs? If so, which page? (e.g., [Language Guide](docs/LanguageGuide.md))
+
+**Additional Context**
+Add any other screenshots or details that could help us answer your question.

.github/SECURITY.md

@@ -0,0 +1,24 @@
+# Security Policy
+
+## Supported Versions
+
+Only the latest release of TechScript receives security updates. If you find a security issue, please update to the newest stable release.
+
+| Version | Supported |
+| ------- | --------- |
+| v2.0.x  | ✅ Yes    |
+| v1.0.x  | ❌ No     |
+| < v1.0  | ❌ No     |
+
+## Reporting a Vulnerability
+
+We take the security of TechScript seriously. If you discover a vulnerability, please do **NOT** open a public GitHub issue. Instead, report it privately to our security team.
+
+### How to report:
+1. Email us at **security@techscript.is-a.dev** with details of the vulnerability.
+2. Include:
+   * A description of the vulnerability and its potential impact.
+   * Step-by-step instructions or proof-of-concept (PoC) code to reproduce it.
+   * Your GitHub username if you wish to be credited.
+
+We will acknowledge receipt of your report within 48 hours and work with you to patch the issue before making a public disclosure.

.github/SUPPORT.md

@@ -0,0 +1,29 @@
+# Support Guide
+
+If you need help with TechScript, please review the resources below before opening an issue.
+
+---
+
+## 📖 Official Documentation
+Our official documentation is the best place to find answers:
+* **Getting Started**: [getting-started.md](../docs/getting-started.md)
+* **Syntax Reference**: [syntax.md](../docs/syntax.md)
+* **Standard Library**: [Stdlib Reference](../docs/StdlibReference.md)
+* **Website**: [https://techscript.is-a.dev](https://techscript.is-a.dev)
+
+---
+
+## 💬 Community Channels
+
+For general help, advice, and chatting:
+* **GitHub Discussions**: [https://github.com/Tcode-Motion/techscript/discussions](https://github.com/Tcode-Motion/techscript/discussions)
+* **Discord Community**: Join our chat to discuss bugs, features, and show off your projects (Discord link is available on our website).
+
+---
+
+## 🐞 Reporting Bugs & Requesting Features
+If you've verified a bug or want to suggest a new feature:
+1. Search active and closed [GitHub Issues](https://github.com/Tcode-Motion/techscript/issues) to see if it has already been reported.
+2. If not, open a new issue using the appropriate template:
+   * [Bug Report](https://github.com/Tcode-Motion/techscript/issues/new?template=bug_report.md)
+   * [Feature Request](https://github.com/Tcode-Motion/techscript/issues/new?template=feature_request.md)

.github/dependabot.yml

@@ -0,0 +1,16 @@
+# dependabot.yml config
+version: 2
+updates:
+  - package-ecosystem: "cargo"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    groups:
+      rust-dependencies:
+        patterns:
+          - "*"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"