Add Glama ownership manifest

[kriptoburak]

Summary

• add Glama's repository-native ownership manifest
• identify the authenticated Xquik maintainer for the organization claim flow

Validation

• manifest assertion

x-developer@2.6.0 test
node --test --experimental-test-coverage --test-coverage-branches=80 --test-coverage-functions=90 --test-coverage-lines=90 tests/*.test.mjs

✔ accepts the complete policy (1.321417ms)
✔ rejects missing frontmatter (0.095667ms)
✔ rejects unclosed frontmatter (0.03775ms)
✔ rejects unsupported frontmatter syntax (0.039333ms)
✔ rejects a changed nested scalar (0.076583ms)
✔ rejects a missing array value (0.045916ms)
✔ accepts quoted scalars and block arrays (0.061292ms)
✔ accepts blank lines and false values (0.054208ms)
✔ reports missing scalars and invalid enums (0.058791ms)
✔ packaged MCP entry supports the offline quickstart workflow (38.730875ms)
All surfaces at 2.6.0
✔ validates every package contract surface (35.229625ms)
✔ fuzzes arbitrary JSON lines without invalid responses (26.145375ms)
✔ fuzzes unknown methods while preserving JSON-RPC identifiers (35.131125ms)
✔ handles every supported JSON-RPC message (1.851ms)
✔ ignores malformed, non-object, and oversized input (0.111ms)
✔ connects the stdio server to supplied streams (1.93125ms)
ℹ tests 16
ℹ suites 0
ℹ pass 16
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 129.189375
ℹ start of coverage report
ℹ --------------------------------------------------------------------------------------------------------------------------------------
ℹ file | line % | branch % | funcs % | uncovered lines
ℹ --------------------------------------------------------------------------------------------------------------------------------------
ℹ scripts | | | |
ℹ check-versions.mjs | 76.19 | 50.00 | 100.00 | 15-19
ℹ release-guard | | | |
ℹ content-policy.mjs | 100.00 | 100.00 | 100.00 |
ℹ context.mjs | 93.44 | 95.45 | 91.67 | 28-29 50-51
ℹ frontmatter.mjs | 100.00 | 96.55 | 100.00 |
ℹ policy-checks.mjs | 86.57 | 72.73 | 100.00 | 30-33 45-46 54-57 97-98 100-101 113-114 119-120
ℹ policy.mjs | 100.00 | 85.71 | 100.00 |
ℹ repository-checks.mjs | 89.06 | 77.36 | 100.00 | 98-99 114-117 132-135 159-160 184-185 188-189 204-207 226-227 236-237 239-242
ℹ stub-server.mjs | 100.00 | 100.00 | 100.00 |
ℹ --------------------------------------------------------------------------------------------------------------------------------------
ℹ all files | 96.33 | 87.62 | 98.53 |
ℹ --------------------------------------------------------------------------------------------------------------------------------------
ℹ end of coverage report

x-developer@2.6.0 check:reproducible
node scripts/check-reproducible.mjs

x-developer-2.6.0.tgz
x-developer-2.6.0.tgz
Package archives are reproducible.

x-developer@2.6.0 check-versions
node scripts/check-versions.mjs

All surfaces at 2.6.0

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

---

Summary by cubic

Add glama.json ownership manifest to declare repository maintainers and enable the Glama organization claim flow. Sets kriptoburak as the authenticated maintainer per the Glama MCP schema.

^{Written for commit ce9e6bd. Summary will update on new commits.}

Note

Add Glama ownership manifest for MCP server

Adds glama.json to declare the Glama MCP server maintainer (kriptoburak) using the Glama manifest schema.

^{Macroscope summarized ce9e6bd.}

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Warning

Review limit reached

@kriptoburak, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 846e84be-1391-4a0b-adf4-003cce8ae108

📥 Commits

Reviewing files that changed from the base of the PR and between 39dec29 and ce9e6bd.

📒 Files selected for processing (1)

• glama.json

---

_{Comment @coderabbitai help to get the list of available commands.}