chore: bump version to 8.1.1 and overhaul documentation with patriotism section

[AnkanSaha]

Summary

This PR updates the versioning across the entire ecosystem from 8.1.0 to 8.1.1 and introduces a new patriotic marketing section to the documentation.

Changes

• Versioning: Updated package.json, package-lock.json, VERSION, main.go, and repl.go to version 8.1.1.
• Documentation: Added PatriotismSection.tsx to the home page featuring cultural pride, empowerment, and Bengali philosophy.
• Extension: Massive update to the VS Code Extension README with detailed installation guides, code snippets, and feature highlights.
• Links: Updated official documentation URL from banglacode.dev to banglacode.nexoral.in.

Verification

• Manually verified the documentation build.
• Checked CLI version output using banglacode --version.
• Verified README rendering on GitHub/Marketplace.

[github-actions]

🤖 Review Buddy - General Code Review

👥 Attention: @AnkanSaha

Oye @AnkanSaha! Ye kya bawasir bana diye ho? Matlab patriotism ke naam pe code ka balidaan de doge?

1. Version Control ya Version Circus?: Bhai, 2024 chal raha hai aur tum manually 5-6 jagah version bump kar rahe ho? main.go, repl.go, VERSION, package.json... kya ye tumhari hobby hai? Automation naam ki bhi koi cheez hoti hai, mere bhai!
2. Documentation Bloat: Ye Extension ka README hai ya Mahabharat? 500 line ka README kaun padhega? User ko coding sikhani hai ya apni life history batani hai?
3. Hardcoding ki Seema: Pura PatriotismSection.tsx hardcoded Bengali strings se bhara pada hai. Kal ko agar kisi ko Sylheti mein chahiye toh kya pura component firse likhoge? i18n ka naam suna hai kabhi?

Code Quality Score: 3/10 - Bhai logic toh thik hai, par manage karne ka tarika ekdum '90s wala hai.

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

⚡ Review Buddy - Performance Analysis

👥 Attention: @AnkanSaha

Bhai, performance analysis sun ke teri rooh kaanp jayegi. Dekh, tune jo ye PatriotismSection.tsx banaya hai na, ye basically browser ke liye ek 'torture chamber' hai.

1. Tailwind Layering Ka Kaand:
   Tune blur-3xl aur opacity-20 wale elements ko aise pel diya hai jaise free ka maal ho. Ye CSS blur filters GPU pe itna load daalte hain ki purane laptops toh dhuaan chhod denge. Oopar se bg-gradient-to-b aur via-accent/5... bhai, GPU ko thoda saans lene de!

2. Animation Overkill:
   animate-fade-in-up har ek grid item pe? Aur wo bhi staggered delay ke saath (index * 0.1s)? Jab page load hoga, browser ka main thread 'Aila, ye kya ho gaya!' chillayega. Har ek element ka layout recalculation aur paint trigger hoga. React ki reconciliation engine ko tune mazak bana rakha hai. Kam se kam memo toh use kar leta agar ye list static hai toh.

3. Lucide Icons Ki Bheed:
   Globe, Heart, Zap, Users - sab ek saath import kar liye. Tree-shaking ho rahi hai ya nahi, ye check kiya hai? Agar tera bundle size badh gaya toh users bolenge 'Humse na ho payega'.

4. Go Code Ka Garbage:
   main.go mein wo jo ASCII art tune print kiya hai na, wo har baar static memory allocate kar raha hai. Maana ki Go fast hai, par faltu ki string concatenation aur printing se binary ka size aur execution time dono pe thoda toh asar padta hi hai.

5. README Size vs Bandwidth:
   GitHub README itna bada kar diya hai ki slow internet wale toh page load hone ka intezaar karte-karte budhe ho jayenge. Images aur links ka itna bheed... thoda clean rakho bhai.

6. React Component Complexity:
   Ek hi file mein 180 lines ka component? Isko split karne mein tera kya ja raha tha? Har re-render pe ye pura tree evaluate hoga.

7. Next.js Image Optimization Missing:
   Tune icons toh use kar liye, par agar kal ko yahan images aayi aur tune yahi approach rakhi, toh LCP (Largest Contentful Paint) ka 'The End' ho jayega.

8. Memory Allocation in Loops:
   Go REPL mein version constant baar-baar print ho raha hai. Isko global load pe rakhna chahiye tha na ki functional call ke andar.

9. CSS Over-engineering:
   backdrop-blur-sm, shadow-xl, hover:-translate-y-1... bhai, ye portfolio website hai ya high-performance compiler? Itne transitions se frame rate drop hota hai.

10. Recommendation:

• Static data ko component se bahar phenko.
• Versioning ke liye ek hi source of truth rakho (ldflags use karo Go mein).
• Animations ko Intersection Observer se trigger karo, sab ek saath mat chalao.
• Tailwind blurs ko avoid karo agar performance chahiye toh.

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

🔐 Review Buddy - Security Audit

👥 Attention: @AnkanSaha

Bhai, security ke naam pe tune toh darwaaje khulle chhod diye hain.

1. Domain Migration Risk:
   banglacode.dev se banglacode.nexoral.in pe move kar rahe ho. Purane links agar hijack ho gaye toh users phishing ke shikaar ho sakte hain. Redirection logic kahan hai?
   Severity: Medium | Location: README.md

2. Dependency Management:
   Documentation/package-lock.json mein version 0.1.0 se seedha 8.1.0? Beech mein koi vulnerability check ki? npm audit gaya tel lene?
   Severity: High | Location: package-lock.json

3. Hardcoded URLs:
   Pure documentation mein hardcoded URLs hain. Agar nexoral.in down gaya ya hijack hua, toh tera pura documentation compromised hai.
   Severity: Low | Location: Multiple files

4. Input Sanitization in REPL:
   Bhai, version print karne ke liye tune escape sequences (\033[1;36m) use kiye hain. Agar koi user input inject kar de toh terminal escape injection ho sakta hai.
   Severity: Low | Location: main.go

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

📊 Review Buddy - Code Quality & Maintainability Analysis

👥 Attention: @AnkanSaha

🎯 Overall Benchmark: 45/100 (Poor)

Ankan, tera code dekh ke lagta hai ki tu 'Copy-Paste' ka king hai par 'Clean Code' ka dushman.

1. DRY (Don't Repeat Yourself) Ka Murder:
   Tune version string 8.1.1 ko kam se kam 6 jagah likha hai. Ek file mein change karna bhul gaya toh tera compiler bolega 8.1.1 aur extension bolega 8.1.0. Aise kaun kaam karta hai bhai? Git tags ya environment variables naam ki cheez pata hai?

2. Component Structure Bawasir:
   PatriotismSection.tsx ek giant monolith hai. Ismein initiatives ka data hai, UI logic hai, animations hain. Isko InitiativeCard, ImpactMetric, PhilosophyQuote jaise sub-components mein kyun nahi toda? Modular programming tere syllabus mein nahi thi kya?

3. Inconsistent Package-Lock:
   package.json mein version 8.1.1 hai par package-lock.json mein 8.1.0? Bhai, lock file aur main file sync mein nahi hain. Production mein build fail hoga toh mat rona.

4. Magic Strings Everywhere:
   Bengali text ko direct components mein hardcode kar diya. Kal ko agar support badhana hua toh? Ek constants/locales.ts bana aur saara text wahan daal.

5. Manual ASCII Art:
   main.go mein manual padding de kar ASCII art align kar rahe ho? Agar version 8.1.1 se 8.1.10 ho gaya toh tera alignment bigad jayega. Dynamic padding sikh le thoda.

6. README Content Density:
   Extension ka README ab 500 lines ka hai. Content repetition hai. 'Features' section aur 'Key Features' section mein difference kya hai? Documentation redundancy is technical debt.

7. Inline Styles in Tailwind:
   style={{ animationDelay: '${index * 0.1}s' }} - Bhai, Tailwind use kar raha hai toh arbitrary values use kar le ya CSS variables. React inline styles avoid kar.

8. Error Handling Absent:
   Documentation build scripts mein koi error handling nahi dikh rahi version mismatch ke liye.

9. Naming Conventions:
   PatriotismSection... thoda zyada emotional nahi ho gaya? AboutSection ya MissionSection rakhta toh zyada professional lagta.

10. Refactoring Suggestion:

    • Ek version.go bana Go ke liye.
    • initiatives.json bana documentation ke liye.
    • Sync script likh jo saare package.json ko update kare.

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

💡 Review Buddy - Best Practices & Alternative Suggestions

👥 Attention: @AnkanSaha

Bhai, ye dekh thoda sudhar ja:

1. Manual Versioning vs Single Source of Truth

Current Code (Bawasir):
Manual updates in main.go, package.json, VERSION...

Better Alternative:
Use a single VERSION file and read it in Go using //go:embed VERSION or via ldflags during build.

// main.go
var version string // set by -ldflags

Why: Ek jagah change karo, sab jagah reflect hoga. Dimag kam lagega.

2. Hardcoded Bengali Strings

Current Code:

<h3 className="text-3xl font-bold">আমাদের দর্শন</h3>

Better Alternative:

import { STRINGS } from '@/constants/bn';
// ...
<h3>{STRINGS.philosophy_title}</h3>

Why: Scalability, mere bhai! Internationalization (i18n) ke liye prepare raho.

3. Component Decomposition

Current Code:
One giant 180-line PatriotismSection.

Better Alternative:
Split into InitiativeCard.tsx, HeroBanner.tsx, etc.
Why: Readable rahega aur testing mein asani hogi. Abhi toh ye khichdi hai.

---

Generated by Review Buddy | Tone: roast | Language: hinglish

[github-actions]

⚠️ Review Buddy - Final Recommendation

👥 Attention: @AnkanSaha

Recommendation: REQUEST CHANGES

Changes chahiye, bhai! Abhi approve nahi kar sakte.

Reasoning:

• Manual versioning across 6 files is a maintenance nightmare waiting to happen.
• Package-lock.json version (8.1.0) is out of sync with package.json (8.1.1).
• Massive code bloat in PatriotismSection.tsx without modularization.
• Hardcoded UI strings make future localization impossible.
• README redundancy in the Extension folder needs pruning.

---

📋 Review Checklist for Reviewers:

• Code changes align with the PR description
• No security vulnerabilities introduced
• Performance considerations addressed
• Code follows project conventions
• Tests are adequate (if applicable)
• Documentation updated (if needed)

🎯 Next Steps:

⚠️ Pehle suggestions address karo, phir approve karna.

Generated by Review Buddy | Tone: roast | Language: hinglish