Retire lightpanda from the profiles; ego-browser takes the slot

[NagyVikt]

Follow-up to #126, which merged before these commits landed on it — it carried
only the submodule bump, so main still declares a skill that no longer exists
upstream.

What's wrong on main right now

opencue/skills#20 deleted browser/lightpanda. main's core profile still
declares it, and main's skills pin (ba3d06d) predates the deletion. The two
agree with each other, so nothing is broken — they are just both stale, and any
checkout that advances the submodule gets SKILL_NOT_FOUND.

Why lightpanda is going

#121 removed the lightpanda MCP from every profile that pinned it, but left
the skill. Of the 29 skill→MCP requirements in the tree, browser/lightpanda
was the only one with no provider at all — it could not run, yet core shipped
it to every session and the smart-loader kept offering it, annotated (needs MCP: lightpanda).

ego-browser covers the same ground — headless navigation, scraping, DOM
extraction — and also paints pixels, which was the gap that forced the old
two-engine handoff in the first place.

Changes

• core and browser no longer declare browser/lightpanda.
• Four personas that routed agents to it now route to ego-browser: browser
  (its "default browser engine" section), commerce and webshop (their "which
  browser when" tables), plus stale MCP-inheritance comments in gstack and
  x-growth-bot. agent-browser and webwright keep their entries — the
  persistent Rust daemon and the long-horizon mission workflow are still theirs.
• resources/skills → 752aef4 (Retire the lightpanda skill skills#20: the deletion plus the four
  in-repo references it left dangling, including verify-council's visual-proof
  lane, which had been told to drive a dead MCP).

Note on summon.test.ts

I had rewritten it here against a hardcoded deployment/coolify + backend
pair. #127 landed a better fix on main — deriving a still-valid pairing
from live profile data via findMcpGatedPair() — so I dropped mine and kept
main's during the cherry-pick. Nothing from this branch touches that file.

Verification

Full suite on this branch, with the skill gone from disk and from every profile:
3077 pass, 0 fail (3078 across 231 files, 1 skip).

grep -rn lightpanda profiles/ returns one deliberate line — a note in gstack
recording that core used to ship the MCP, so the next reader knows it went away
rather than never existed.

[NagyVikt]

Automated review — verdict: no blocking findings. 0 CRITICAL, 0 HIGH, 0 MEDIUM, 0 LOW.

Three things worth checking on a change that deletes a skill out from under a
profile; all three hold.

Nothing else references the skill. grep -rn lightpanda profiles/ src/ is
clean apart from one deliberate note in gstack recording that core used to
ship the MCP. The four in-repo references inside the skills submodule
(verify-council's visual-proof lane, agent-browser's overlap note,
cue-dashboard's sample output) were repointed in opencue/skills#20, which this
bump pulls in — so no dangling instruction survives on either side.

The persona claims about ego-browser are accurate, not aspirational. The
rewritten sections say it paints pixels (page.screenshot()), that it is
Chromium-only, and that playwright stays for Firefox/WebKit. Checked against the
skill's own SKILL.md rather than asserted.

The bump does not lose anything. resources/skills moves to 752aef4; the
only removal in that range is browser/lightpanda itself, and ego-browser,
agent-browser and playwright all survive.

Verification

Check	Result
CI — test	Pass — and main's latest CI run is green too, so this clears an actually-green baseline, not a red one
CI — lint, configured	Pass
CI — Profiles e2e (ubuntu + macos)	Pass
CI — validate	Fail, pre-existing and unrelated: E3 (missing reference): MCP "openaiDeveloperDocs", and nothing else. profiles/research declares that MCP, it is registered in no config in the mcps repo, and it is not installed on this machine. #121 failed the same check and merged; the job is pull_request-only so it has no main baseline
Local full suite	3077 pass, 0 fail (3078 across 231 files, 1 skip)

Note

I had also rewritten summon.test.ts here against a hardcoded
deployment/coolify + backend pair. #127 landed a better fix on main —
deriving a still-valid pairing from live profile data via findMcpGatedPair() —
so mine was dropped during the cherry-pick. This branch does not touch that file.