Add browsergnome

[xavi-999]

browsergnome is a JS web performance skill/CLI: It centralizes all JS web performance knowledge into one agentic tool workflow. It can profile a page's load (LCP, bundle composition, dependency graph) and propose improvements based off the latest up to date JS web performance insights.

browsergnome can be used locally on the user's LLM, or run on CI as part of an automated performance continuous integration protocol.

Maintenance: a few cross-file invariants (chrome-devtools-mcp version pin, stack-catalog filenames, depPulse config, Guidance IDs).

[pgom]

The description is pretty minimal. Worth adding a few lines about:

• What browsergnome is (the perf loop, measurements, etc.)
• Why it's being brought into this org/repo
• Any key maintenance assumptions (single maintainer, invariants that need coordinating, etc.)

This helps future reviewers understand scope when it shows up in blame/history.

[pgom]

CLAUDE.md documents some fragile cross-file invariants (chrome-devtools-mcp pin in 3 places, stack-catalog filenames, depPulse config duplication, Guidance IDs). These "silently drift" if only one side gets updated.

Might be worth documenting a checklist or a linting rule to catch these on future updates? Right now they're just a knowledge requirement for maintainers.

[pgom]

CONTRIBUTING.md notes this is a single-maintainer project with variable response times. Also, each script has its own selfTest() rather than using a shared test framework.

For a production skill, you might want to clarify:

• Escalation path if Xavier becomes unavailable?
• Plan to integrate these tests into CI in a way that's runnable/debuggable by the team?