GitHub description points at the retired cli-guard name

coilyco-ops commented

2026-08-16 00:26:19 +00:00

Member

Problem

Current GitHub description, 105 chars:

MCP runtime that turns cli-guard policy files into guarded streamable HTTP services and container images.

cli-guard was renamed to umbra. Nothing public in the orgs is called cli-guard anymore, so a reader landing here cannot resolve the term to a repo, a doc, or a file format. The description is the first thing shown in the org listing and in search results, so this is the first impression on a repo currently at 0 stars.

The README already says it correctly: "renders a umbra Guardfile". Only the repo metadata is stale.

Proposed change

Single-word swap, 99 chars, shorter than what it replaces and in the same register:

MCP runtime that turns umbra Guardfiles into guarded streamable HTTP services and container images.

Deliberately a minimal diff rather than a rewrite. The existing sentence shape is fine, only the dead name is wrong.

check_repo_pointer_skills regenerates repo-mcp-beaver/SKILL.md from this description, so the pointer skill inherits the same stale name until this lands.

Also

homepage is unset. umbra ships GitHub Pages at https://coilyco-flight-deck.github.io/umbra/ and this repo has no equivalent. Set it if a docs surface exists, or leave it and close that half.

Scope

Content-only. Reverting changes human-facing words and nothing else.

## Problem Current GitHub description, 105 chars: ``` MCP runtime that turns cli-guard policy files into guarded streamable HTTP services and container images. ``` `cli-guard` was renamed to `umbra`. Nothing public in the orgs is called cli-guard anymore, so a reader landing here cannot resolve the term to a repo, a doc, or a file format. The description is the first thing shown in the org listing and in search results, so this is the first impression on a repo currently at 0 stars. The README already says it correctly: "renders a umbra Guardfile". Only the repo metadata is stale. ## Proposed change Single-word swap, 99 chars, shorter than what it replaces and in the same register: ``` MCP runtime that turns umbra Guardfiles into guarded streamable HTTP services and container images. ``` Deliberately a minimal diff rather than a rewrite. The existing sentence shape is fine, only the dead name is wrong. `check_repo_pointer_skills` regenerates `repo-mcp-beaver/SKILL.md` from this description, so the pointer skill inherits the same stale name until this lands. ## Also `homepage` is unset. umbra ships GitHub Pages at https://coilyco-flight-deck.github.io/umbra/ and this repo has no equivalent. Set it if a docs surface exists, or leave it and close that half. ## Scope Content-only. Reverting changes human-facing words and nothing else.

coilyco-ops commented

2026-08-16 00:33:34 +00:00

Author

Member

Banner constraint, for whoever picks this up

Context that was missing when this was filed. agent-compose carries a banner whose tagline is its GitHub description, and the design rule in agentic-os-xxx banner-system.md is that the tagline stays narrower than the heading. That puts a hard ceiling near 42 characters on any描述 that also has to render as banner type.

mcp-beaver has no banner today. assets/banner/ does not exist here, only agent-compose has one across the five promotion-priority repos. So the 99-char replacement proposed above is fine as-is and this issue can proceed unchanged.

The flag is forward-looking. If Designer mints a beaver banner as part of the promotion push, the current 105-char description measures 2.11 times the agent-compose heading width in that type treatment, and the proposed 99-char one is barely better. Either would need a separate short tagline.

If a banner is coming, the decision to make first is whether description and tagline are one string or two. That question is parked in agent-compose#284 for the convention discussion. Landing the cli-guard to umbra Guardfiles swap now does not foreclose it.

## Banner constraint, for whoever picks this up Context that was missing when this was filed. `agent-compose` carries a banner whose tagline **is** its GitHub description, and the design rule in `agentic-os-xxx` `banner-system.md` is that the tagline stays narrower than the heading. That puts a hard ceiling near 42 characters on any描述 that also has to render as banner type. **mcp-beaver has no banner today.** `assets/banner/` does not exist here, only `agent-compose` has one across the five promotion-priority repos. So the 99-char replacement proposed above is fine as-is and this issue can proceed unchanged. The flag is forward-looking. If Designer mints a beaver banner as part of the promotion push, the current 105-char description measures **2.11 times** the agent-compose heading width in that type treatment, and the proposed 99-char one is barely better. Either would need a separate short tagline. If a banner is coming, the decision to make first is whether description and tagline are one string or two. That question is parked in agent-compose#284 for the convention discussion. Landing the `cli-guard` to `umbra Guardfiles` swap now does not foreclose it.

coilyco-ops commented

2026-08-16 00:33:48 +00:00

Author

Member

Typo in the comment above: "any描述 that also has to render as banner type" should read "any description that also has to render as banner type". Two CJK characters landed in place of the English word. No comment-edit surface is exposed through this MCP, so correcting here rather than in place. Nothing else in that comment changes.

coilyco-ops added the

labels

2026-08-17 01:14:23 +00:00

coilyco-ops referenced this issue

2026-08-17 02:26:18 +00:00

README names ward-mcp throughout while stating no relation to ward #75

coilyco-ops referenced this issue from a commit

2026-08-17 02:40:09 +00:00

chore(skills): regenerate the pointer skill off the fixed description (#74)

coilyco-ops closed this issue

2026-08-17 02:40:09 +00:00

coilyco-ops commented

2026-08-17 02:40:21 +00:00

Author

Member

Done. GitHub description is now the sentence you proposed, verbatim:

MCP runtime that turns umbra Guardfiles into guarded streamable HTTP services and container images.

repo-mcp-beaver/SKILL.md regenerated on main in b825196. It had drifted a third way - "umbra policy files" - so it was not carrying the dead name but was not carrying the description either. Regenerated through agentic_os.generators.generate_repo_pointer_skill rather than hand-edited, since check_repo_pointer_skills regenerates and fails on any difference. Confirmed the generator reads the GitHub description, which is why fixing that side was enough to fix this one.

homepage: closing that half. https://coilyco-flight-deck.github.io/mcp-beaver/ returns 404 while umbra's equivalent returns 200, so there is no docs surface to point at and the field stays unset.

One thing I could not do, and it is not this issue. The canonical Forgejo description is not the stale sentence at all - it is the README tagline:

A MCP server generator with a natural flow

So the problem you filed does not exist on the canonical side, and the two hosts now say different things: Forgejo carries the tagline, GitHub carries the descriptive sentence. Aligning them wants a decision about which one belongs in a repo description, and I do not hold admin on the Forgejo repo either way - aosguard ops forgejo repo edit returns 403 for the ops token. Worth its own issue if the split matters; the dead name is gone from both.

Done. GitHub description is now the sentence you proposed, verbatim: ``` MCP runtime that turns umbra Guardfiles into guarded streamable HTTP services and container images. ``` `repo-mcp-beaver/SKILL.md` regenerated on `main` in `b825196`. It had drifted a third way - "umbra **policy files**" - so it was not carrying the dead name but was not carrying the description either. Regenerated through `agentic_os.generators.generate_repo_pointer_skill` rather than hand-edited, since `check_repo_pointer_skills` regenerates and fails on any difference. Confirmed the generator reads the **GitHub** description, which is why fixing that side was enough to fix this one. **`homepage`: closing that half.** `https://coilyco-flight-deck.github.io/mcp-beaver/` returns 404 while umbra's equivalent returns 200, so there is no docs surface to point at and the field stays unset. **One thing I could not do, and it is not this issue.** The canonical Forgejo description is not the stale sentence at all - it is the README tagline: ``` A MCP server generator with a natural flow ``` So the problem you filed does not exist on the canonical side, and the two hosts now say different things: Forgejo carries the tagline, GitHub carries the descriptive sentence. Aligning them wants a decision about which one belongs in a repo description, and I do not hold admin on the Forgejo repo either way - `aosguard ops forgejo repo edit` returns 403 for the ops token. Worth its own issue if the split matters; the dead name is gone from both.

Rows
Columns

GitHub description points at the retired cli-guard name #74

Problem

Proposed change

Also

Scope

Banner constraint, for whoever picks this up