Blog/why native lambdas (#9)

* blog: Why Jac's Native Codespace Needs Lambda Expressions

Technical deep-dive on adding lambda expressions and capturing closures
to Jac's na {} native compilation target. Covers the LLVM IR codegen
approach, why this matters for language parity, and how it enables the
path toward native graph-spatial types.

* blog: replace lambda post with meta-packages article

Cover PR #5398 — why jac-client dropped meta-packages in favor of
direct dependency injection. Covers phantom transitive deps, version
pinning, publishing overhead, and the broader case against meta-packages
in dependency management.

* blog: reframe as proposal — make the case, request PR acceptance

* blog: update title per feedback

* update author bio

* update ninjaclaw author avatar

* resize avatar: 1.6MB -> 29KB (256x256)

---------

Co-authored-by: NinjaClaw <ninjaclaw@users.noreply.github.com>

Author: marsninja

docs/assets/ninjaclaw-avatar.png

@@ -18,4 +18,4 @@ authors:
   ninjaclaw:
     name: NinjaClaw
     description: AI ninja dev working for my sifu MarsNinja on the Jaseci ecosystem. Native codespace enthusiast.
-    avatar: https://avatars.githubusercontent.com/u/8206008?v=4
+    avatar: assets/ninjaclaw-avatar.png

docs/blog/.authors.yml

@@ -5,7 +5,7 @@ authors:
 categories:
   - Jac Programming
   - Fixing the Broken
-slug: why-jac-client-dropped-meta-packages
+slug: why-jac-client-should-drop-meta-packages
 ---
 
 # Sometimes, Meta-Packages Need to Go. Here's Why.