Best possible solution:

Land this focused Zalo plugin fix after ordinary maintainer and CI gates, keeping the native getMe fields as the canonical runtime shape.

Do we have a high-confidence way to reproduce the issue?

Yes. Current main reads probe.bot?.name for the startup label while the official getMe sample returns account_name and no name; a mock native response reproduces the missing-label path by source inspection.

Is this the best way to solve the issue?

Yes. Updating the Zalo plugin type and the one startup-label consumer is the narrowest maintainable fix; adding a legacy name normalization shim would preserve a non-native internal shape without a shipped API need.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 9238d9aeae8d.

Label justifications:

• P2: This is a bounded Zalo channel bug fix with limited blast radius and clear source/API-contract evidence.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate does not apply to this maintainer-labeled MEMBER PR; the PR body lists focused local validation as supplemental evidence.

PR surface:

Source +1, Tests +22. Total +23 across 3 files.

What I checked:

• Repository policy read: Root AGENTS.md and extensions/AGENTS.md were read fully; the maintainer label prevents cleanup closing, and the extension policy supports keeping this change inside the Zalo plugin boundary. (AGENTS.md:31, 9238d9aeae8d)
• Current main mismatch: Current main types ZaloBotInfo as id, name, and optional avatar, which does not match the official getMe sample response fields. (extensions/zalo/src/api.ts:22, 9238d9aeae8d)
• Current startup label path: Current main builds the gateway startup label from probe.bot?.name, so a native getMe response with only account_name cannot populate that label. (extensions/zalo/src/channel.runtime.ts:56, 9238d9aeae8d)
• PR implementation: The PR changes ZaloBotInfo to the native account fields, switches the startup label to account_name, and adds a focused getMe response test for the documented shape. (extensions/zalo/src/api.ts:22, 91342b007dbc)
• Official Zalo contract: The official Zalo Bot Platform getMe page returns POST JSON with result.id, result.account_name, result.account_type, and result.can_join_groups.
• Related stacked PR: The related Zalo API-root PR is explicitly stacked on this PR and says it no longer changes ZaloBotInfo or gateway identity labeling, so it is adjacent rather than a replacement.

Likely related people:

• steipete: Commit 5abe3c2 added the Zalo plugin and Bot API client path that this PR updates. (role: introduced behavior; confidence: medium; commits: 5abe3c21456e; files: extensions/zalo/src/api.ts, extensions/zalo/src/channel.runtime.ts, docs/channels/zalo.md)
• darkamenosa: Merged Zalo lifecycle and API type work in PR history around provider startup and API behavior. (role: feature history contributor; confidence: medium; commits: 67b2e81360c4, 608133b4251c; files: extensions/zalo/src/api.ts, extensions/zalo/src/channel.runtime.ts)
• hugenshen: Recently maintained the Zalo API client and tests for bounded Bot API JSON response reads. (role: recent area contributor; confidence: medium; commits: 38ddcef78f07, 798fed7e9c1d; files: extensions/zalo/src/api.ts, extensions/zalo/src/api.test.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.