fix(portable): Gemini keys, Telegram pairing UI, and config durability

Improve first-run and channel setup for non-technical users: detect newer
Gemini key formats, pin Node 22.22.3, add Control Panel Telegram approve
flow, and keep channels/models when config is rewritten. Persist uclaw
wizard state via uclaw-meta.json so restarts skip language/persona prompts.

Co-authored-by: Cursor <cursoragent@cursor.com>

portable/skills/en/linkedin-post/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: linkedin-post
+description: "LinkedIn posts - hooks, structure and formatting for the feed, without the LinkedIn voice everyone hates"
+metadata: { "openclaw": { "emoji": "💼" } }
+---
+
+# LinkedIn Posts
+
+Write posts that read like a person wrote them.
+
+## The one rule
+
+LinkedIn has a house style — the one-line paragraphs, the fake-humble opener, the
+"Agree?" sign-off, the 🧵 emoji ladder. Readers are tired of it, and it now reads
+as low effort. **Write like you would to a colleague who respects you.**
+
+Specifically, avoid: "I'm humbled to announce", "Let that sink in", a story about
+a taxi driver that turns out to be a business lesson, and anything that opens with
+a one-word line for drama.
+
+## Structure
+
+```
+Hook        First two lines. Everything else is behind "…see more".
+Substance   The actual point, with something concrete in it
+Close       What you want — a reply, a click, or nothing at all
+```
+
+The hook is the whole game: the feed shows about 200 characters. A hook that
+withholds ("Here's what nobody tells you…") gets scrolled past now. A hook that
+states something specific gets read.
+
+| Weak | Better |
+|---|---|
+| "Some thoughts on hiring." | "We stopped asking for CVs. Applications went up 4x." |
+| "Excited to share our new feature!" | "Our users kept exporting to CSV to do one thing. So we built it." |
+
+## Formatting
+
+- Short paragraphs, but not one line each — two or three lines reads as human
+- No hashtag wall. Three at most, and only if they are real communities
+- Links kill reach on LinkedIn; put yours in the first comment and say so
+- Native images and documents outperform link previews
+
+## Length
+
+Roughly 150–400 words for a normal post. Below that it reads thin; above that
+almost nobody expands it unless the hook earned it.
+
+## Example prompts
+
+```
+Turn this product update into a post — the angle is why we built it, not what it does
+```
+
+```
+Rewrite this so it sounds like me and not like LinkedIn
+```
+
+```
+Five hook options for a post about our hiring change, no clickbait
+```
+
+## Working notes
+
+- Ask what the person actually wants from the post. "More engagement" is not a
+  goal; a reply from hiring managers is.
+- If they give you a real number, a real mistake or a real customer, build the
+  post around it. Posts without anything concrete are the ones that get ignored.
+- Singapore context: the audience is regional. Explain local references that a
+  reader in KL or Jakarta would not have.