Sweep the org profiles, the GitHub profile, and the repo pointer skills after the renames #6

New issue

Open

opened 2026-08-27 03:25:05 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-27 03:25:05 +00:00

Owner

Found while reminting the agent-compose banner on its new description, where the same drift showed up as a third one-liner for one product.

The renames, verified

cli-guard to umbra - GitHub redirects coilyco-flight-deck/cli-guard to umbra, and the live Forgejo description is now "a config driven occlusion framework for your CLIs and APIs".
ward-mcp to mcp-beaver - GitHub redirects coilyco-flight-deck/ward-mcp to mcp-beaver, and the live Forgejo description is now "A MCP server generator with a natural flow".
atlas - absent from canonical Forgejo entirely, no repo matches an atlas search, and coilyco-bridge/atlas is still live on GitHub. Whether that is a delete, a rename, or an orphaned mirror is the one thing this ticket cannot answer from the outside.

Surface 1 - the org profile READMEs

coilyco-flight-deck/.github profile/README.md - 15 mentions of cli-guard and 12 of ward-mcp, zero of umbra or mcp-beaver. Every product link, topic index, and per-repo topic row carries a dead name.
coilyco-bridge/.github profile/README.md - 5 mentions of atlas.
coilyco-gaming/.github profile/README.md - links eco-community-discord and eco-game, neither of which resolves on Forgejo or on GitHub. The live org holds eco-app, eco-mods, eco-ops, factorio-mods, galaxy-gen, sirens-echo, steam-ops, and factory-game-v3.

Surface 2 - the GitHub profile

coilysiren/coilysiren README.md - carries cli-guard, ward-mcp, eco-community-discord, and eco-game, and describes agent-compose as a "context compiler that composes roles, personalities, skills, and tool inventories", which is neither the live Forgejo description nor what the README of that repo now says.
coilysiren/coilysiren .agents/skills/coilysiren-portfolio/SKILL.md - repeats the same agent-compose line, so an agent with no checkout is briefed off it.

Surface 3 - the repo pointer skills

These are generated from each repo's live Forgejo description plus its topics, and a pre-commit hook regenerates and byte-diffs them, so they should never drift. They drifted because the skill directory never followed the repo rename, and the hook compares the wrong path.

coilyco-flight-deck/umbra still ships .agents/skills/repo-cli-guard/SKILL.md. Its frontmatter reads name: repo-umbra with the old cli-guard description, so the directory and the skill name already disagree.
coilyco-flight-deck/mcp-beaver still ships .agents/skills/repo-ward-mcp/SKILL.md with name: repo-ward-mcp. Its description was half swept, reading "turns umbra policy files into guarded streamable HTTP services", which is the old ward-mcp framing with one word replaced.
repo-atlas still points at ~/projects/coilyco-bridge/atlas/, a path with no repo behind it.
repo-agent-compose still carries the pre-rename description line, which is the drift that surfaced this. Its Forgejo description changed today and nothing regenerated the skill.

Done conditions

Kai rules on atlas, since delete, rename, and orphaned mirror each imply a different fix and none is safe to guess.
Every pointer-skill directory matches its repo's current name, and every generated description matches the live Forgejo description.
The regeneration hook fails when a pointer-skill directory does not match its repo name, so the next rename cannot drift the same way.
All three org profile READMEs and the GitHub profile name only repos that exist, with descriptions that match Forgejo.
The GitHub side carries no repo that canonical Forgejo does not, or each exception is recorded deliberately.

Not in scope

Choosing new wording. Every description above already has a canonical value on Forgejo, so this is propagation rather than copy. A product that wants a genuinely new one-liner is a separate ask.

Three public description surfaces still describe a portfolio that no longer exists. Two repos were renamed and their old names survive in every one of them, one repo is gone from canonical Forgejo but still live on GitHub, and two gaming repos are linked from a profile despite existing nowhere. Kai asked for a clean sweep rather than a patch of the one line that started this. Found while reminting the agent-compose banner on its new description, where the same drift showed up as a third one-liner for one product. ## The renames, verified * `cli-guard` to `umbra` - GitHub redirects `coilyco-flight-deck/cli-guard` to `umbra`, and the live Forgejo description is now "a config driven occlusion framework for your CLIs and APIs". * `ward-mcp` to `mcp-beaver` - GitHub redirects `coilyco-flight-deck/ward-mcp` to `mcp-beaver`, and the live Forgejo description is now "A MCP server generator with a natural flow". * `atlas` - absent from canonical Forgejo entirely, no repo matches an `atlas` search, and `coilyco-bridge/atlas` is still live on GitHub. Whether that is a delete, a rename, or an orphaned mirror is the one thing this ticket cannot answer from the outside. ## Surface 1 - the org profile READMEs * `coilyco-flight-deck/.github` `profile/README.md` - 15 mentions of `cli-guard` and 12 of `ward-mcp`, zero of `umbra` or `mcp-beaver`. Every product link, topic index, and per-repo topic row carries a dead name. * `coilyco-bridge/.github` `profile/README.md` - 5 mentions of `atlas`. * `coilyco-gaming/.github` `profile/README.md` - links `eco-community-discord` and `eco-game`, neither of which resolves on Forgejo or on GitHub. The live org holds `eco-app`, `eco-mods`, `eco-ops`, `factorio-mods`, `galaxy-gen`, `sirens-echo`, `steam-ops`, and `factory-game-v3`. ## Surface 2 - the GitHub profile * `coilysiren/coilysiren` `README.md` - carries `cli-guard`, `ward-mcp`, `eco-community-discord`, and `eco-game`, and describes agent-compose as a "context compiler that composes roles, personalities, skills, and tool inventories", which is neither the live Forgejo description nor what the README of that repo now says. * `coilysiren/coilysiren` `.agents/skills/coilysiren-portfolio/SKILL.md` - repeats the same agent-compose line, so an agent with no checkout is briefed off it. ## Surface 3 - the repo pointer skills These are generated from each repo's live Forgejo description plus its topics, and a pre-commit hook regenerates and byte-diffs them, so they should never drift. They drifted because the skill directory never followed the repo rename, and the hook compares the wrong path. * `coilyco-flight-deck/umbra` still ships `.agents/skills/repo-cli-guard/SKILL.md`. Its frontmatter reads `name: repo-umbra` with the old cli-guard description, so the directory and the skill name already disagree. * `coilyco-flight-deck/mcp-beaver` still ships `.agents/skills/repo-ward-mcp/SKILL.md` with `name: repo-ward-mcp`. Its description was half swept, reading "turns umbra policy files into guarded streamable HTTP services", which is the old ward-mcp framing with one word replaced. * `repo-atlas` still points at `~/projects/coilyco-bridge/atlas/`, a path with no repo behind it. * `repo-agent-compose` still carries the pre-rename description line, which is the drift that surfaced this. Its Forgejo description changed today and nothing regenerated the skill. ## Done conditions 1. Kai rules on atlas, since delete, rename, and orphaned mirror each imply a different fix and none is safe to guess. 2. Every pointer-skill directory matches its repo's current name, and every generated description matches the live Forgejo description. 3. The regeneration hook fails when a pointer-skill directory does not match its repo name, so the next rename cannot drift the same way. 4. All three org profile READMEs and the GitHub profile name only repos that exist, with descriptions that match Forgejo. 5. The GitHub side carries no repo that canonical Forgejo does not, or each exception is recorded deliberately. ## Not in scope Choosing new wording. Every description above already has a canonical value on Forgejo, so this is propagation rather than copy. A product that wants a genuinely new one-liner is a separate ask. ## See also * #351 - agentic product identity, marks and banners and the social surfaces they land on. Same portfolio surfaces, different layer.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-bridge/.github#6

No description provided.

Rows
Columns