Claimed and verified library: admin Title/Description not applied after a full re-parse (/baldurhq/baldur)

Library: https://context7.com/baldurhq/baldur (/baldurhq/baldur) — claimed, and verified today.

Problem

The title and description shown in search results are the auto-generated ones. Neither the context7.json values nor the values I saved in the admin Configuration tab were applied, even though a full re-parse ran afterwards.

	Value I set	Value the index serves
title	Baldur - Python Resilience Framework (Circuit Breaker, Retry, DLQ)	Baldur
description	Self-healing reliability layer for Python: circuit breaker, retry, fallback, timeout, and dead-letter queue behind one @baldur.protected decorator. Django, FastAPI, Flask, and Celery adapters.	Baldur is a self-healing reliability layer for Python applications that provides circuit breaker, retry, fallback, and dead-letter queue capabilities behind a single decorator.

What I did

1. context7.json has carried projectTitle and description since the first commit, before the library was ever parsed: https://github.com/baldurhq/baldur/blob/main/context7.json
2. Claimed the library (url + public_key in the same file). Claim succeeded — "Owned by your teamspace".
3. Applied for verification. Approved.
4. Opened the admin Configuration tab. Title and Description were pre-filled with my values. Edited a character, saved with "Save changes", saved again with the original text.
5. Clicked Refresh.

The re-parse did run

before   lastUpdateDate=2026-08-31T04:33:38.982Z  totalSnippets=819
after    lastUpdateDate=2026-08-31T13:15:06.914Z  totalSnippets=847

So this is not a stale-cache or queued-refresh problem. A full re-parse read the repository and still served the generated title and description.

Why it matters

Library search appears to match strongly on the title. Across python circuit breaker library, python retry library with fallback and metrics and self healing python service framework, all 30 results across the three top-10 lists carry a query token in their title or id. With the title reduced to the single word Baldur, the library is only reachable by people who already know the name — it returns nothing for the problem vocabulary its docs are actually about.

Ask

1. Could you apply the two values above manually? There is precedent in #712 and #1036, where the fields were set by hand after the same symptom.

2. Is the admin Configuration Title/Description path expected to work? In #1020 the suggested fix was "you can always claim your library and use the admin view to update these fields" — that is exactly what I did, and it had no effect on the index.

3. If context7.json projectTitle is intentionally no longer honored (per #1036: disabled to prevent LLM injection through free text), the published schema is now misleading. https://context7.com/schema/context7.json still documents it as:

   The display name for your project in Context7. This overrides the default repository name.

   Deprecating it in the schema, or noting the restriction there, would save owners the round trip.

Happy to provide anything else that helps.