Fix Glama MCP build and tool introspection

[AjnasNB]

What changed

• add root glama.json maintainer metadata for repository ownership verification
• add a digest-pinned Dockerfile.glama that starts the native stdio MCP process instead of the HTTP daemon
• add npm run check:glama, which performs a real MCP initialize and tools/list exchange and requires all eight public tools
• exercise both the local process and the built Glama container in CI
• document the separate Glama build path in the generated MCP manual and discovery surfaces

Why

Glama was building the repository's root daemon image. That image correctly starts the authenticated HTTP browser daemon, but Glama expects a stdio MCP process for protocol introspection, so the listing reported zero tools and could not produce a Glama release.

Impact

The normal daemon Docker image and runtime behavior are unchanged. Glama maintainers can select Dockerfile.glama with the repository root as build context, deploy it, and inspect the MCP schema without a secret. Daemon-backed tool calls still require the documented URL and token.

Validation

• local npm run check passed
• 65 tests passed, 1 browser smoke test skipped locally by its existing environment guard
• GitHub CI built Dockerfile.glama, initialized MCP inside the container, and discovered all 8 registered tools
• Node 22, 24, and 26; Chromium smoke; packed consumer; hardened daemon container; dependency review; and CodeQL all passed
• package, site, audit, and tarball gates passed with 0 runtime vulnerabilities

Branch migration

This PR replaces #36 only because its legacy head ref used the retired �gent/ prefix. The source tree and commit history are unchanged: $(System.Collections.Hashtable.oldBranch) and $(System.Collections.Hashtable.newBranch) both point to exact head $(System.Collections.Hashtable.sha) at migration time. Review and merge protection remain required.