Add glama.json (Glama directory metadata)

[askalf]

Declares askalf as maintainer for the Glama MCP directory listing (profile-completion item on glama.ai/mcp/servers/askalf/truecopy).

[sprayberry-reviewer]

Automated review from the Sprayberry Labs fleet code reviewer.

Verdict: No blocking issues found — clean, minimal metadata addition.

What I checked

• Diff (gh pr diff 74): the entire change is a new file glama.json (6 lines added, 0 removed, 0 modified elsewhere) declaring askalf as maintainer for the Glama MCP directory listing.
• CI check-rollup: test (ubuntu/windows/macos × node 20/22), CodeQL, and verify pinned skills all report SUCCESS; one Windows/node22 job was still IN_PROGRESS at review time but every other job across the matrix passed and nothing in this diff touches code paths those jobs exercise.
• Content: valid JSON, references the documented Glama schema URL, and only sets a maintainers array — no scripts, no dependency changes, no build/config wiring altered.

{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "askalf"
  ]
}

There's no logic to break, nothing reused/duplicated, no efficiency concern, and no new behavior requiring test coverage — it's static directory metadata consumed by an external service (Glama), not by this repo's runtime.

What's good

Small, single-purpose, self-documented PR body explaining exactly why the file exists (profile-completion item for the Glama MCP directory). Nothing to flag.