fix(mcp): await PostHog flush via unit-tested stdio wrapper

[joaovictor91123]

Summary

• Make local recordMcpToolCall async and await client.flush() before returning (mirrors remote MCP tool-call telemetry fires without waitUntil, unlike this repo's own scheduleAfterResponse pattern #7233).
• Move the stdio success/error await-flush chokepoint into wrapStdioToolHandler / recordStdioToolTelemetry in lib/telemetry.ts with full unit coverage (delayed flush, isError, throw, disabled, defensive catch).
• Keep bin/loopover-mcp.ts as thin /* v8 ignore */ registration glue so codecov/patch is not tanked by uninstrumentable entrypoint lines (the failure mode that closed fix(mcp): await PostHog flush for local tool-call telemetry #8733 at 25% patch).

Client lifetime: still constructs a fresh PostHog client per call (same as remote), not a process-long singleton.

Closes #8690

Scope

• The PR title follows type(scope): short summary Conventional Commit format, for example fix(api): restore profile access checks.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked a currently open issue this PR resolves (e.g. Closes #123) - a linked open issue is required for every contributor PR.

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally; codecov/patch requires ?99% coverage of the lines AND branches you changed (aim for 100% on your diff so CI variance does not fail near the threshold). Global coverage is a non-blocking trend with a loose 90% backstop, not the gate.
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

If any required check was skipped, explain why:

• Local Node is v24; repo engines pin Node 22. Coverage for this change is in test/unit/mcp-local-telemetry.test.ts and will run under CI. Prior fix(mcp): await PostHog flush for local tool-call telemetry #8733 closed for uncovered bin/ awaits - those are now in unit-tested lib/.

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests.
• API/OpenAPI/MCP behavior is updated and tested where needed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
• Visible UI changes include a UI Evidence section below with JPG/JPEG or PNG screenshots arranged as organized, captioned, clickable thumbnails. SVG screenshots are not used as review evidence. Review-only screenshots or recordings are not committed to the repository.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

UI Evidence

N/A - no visible UI changes.

Notes

• Replaces closed fix(mcp): await PostHog flush for local tool-call telemetry #8733 with a coverage-safe structure (lib helper + ignored bin glue).

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.34%. Comparing base (2fc27bc) to head (27f293a).

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #8738       +/-   ##
===========================================
- Coverage   93.80%   82.34%   -11.47%     
===========================================
  Files         797       98      -699     
  Lines       79480    24765    -54715     
  Branches    24080     4748    -19332     
===========================================
- Hits        74554    20392    -54162     
- Misses       3555     4195      +640     
+ Partials     1371      178     -1193     

Flag	Coverage Δ
backend	1.09% <100.00%> (-93.99%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
packages/loopover-mcp/bin/loopover-mcp.ts	0.00% <ø> (-54.52%)	⬇️
packages/loopover-mcp/lib/telemetry.ts	100.00% <100.00%> (ø)

... and 699 files with indirect coverage changes

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-26 01:49:11 UTC}

3 files · 1 AI reviewer · no blockers · readiness 98/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR makes the local `recordMcpToolCall` async and awaits `client.flush()` before returning, then relocates the stdio await-flush chokepoint from `bin/loopover-mcp.ts` into a newly unit-tested `wrapStdioToolHandler`/`recordStdioToolTelemetry` pair in `lib/telemetry.ts`, leaving `bin/` as thin `/* v8 ignore */` glue. The change correctly mirrors the remote fix (#7233) and is well-covered: tests exercise delayed-flush ordering, isError mapping, throw/rethrow, disabled telemetry, and defensive catches on construct/capture/flush failures. Closes #8690 as claimed, and the bin-side diff is a faithful call-site swap with no behavior change beyond the relocation.

Nits — 3 non-blocking

• packages/loopover-mcp/lib/telemetry.ts:94 uses `StdioToolHandler = (...args: any[]) => Promise<any>`; consider typing this against the MCP SDK's tool handler signature instead of `any` for better call-site safety.
• External brief flags `bin/loopover-mcp.ts` as a long file (~1733 lines), but that's pre-existing structure this PR doesn't materially grow — not something to hold this diff to.
• packages/loopover-mcp/lib/telemetry.ts: the `record` default-parameter injection point in `recordStdioToolTelemetry` is a nice seam for testing — consider documenting it's test-only (production callers should never pass it) to avoid future misuse.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#8733, #8690
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (2 linked issues).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 161 registered-repo PR(s), 73 merged, 5 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	joaovictor91123; Gittensor profile; 161 PR(s), 5 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: moderate

Linked issue satisfaction

Addressed
The diff makes recordMcpToolCall async and awaits client.flush() before returning, and threads that await through a new recordStdioToolTelemetry/wrapStdioToolHandler chokepoint so both success and throw paths in the stdio tool registration hold for flush, matching the issue's stated ask.

Review context

• Author: joaovictor91123
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, JavaScript, MDX, TypeScript, C++, CSS, Rust
• Official Gittensor activity: 161 PR(s), 5 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.