adopt the current agentic-os hook baseline (managed block is fossilized at v0.18.0/github) + give the eco MCP an Eco icon #48

Closed
opened 2026-07-04 09:41:15 +00:00 by coilyco-ops · 2 comments
Member

Sibling of coilyco-gaming/steam-ops#4 - same two-part shape, this repo.

1. Refresh the managed agentic-os hook block

.pre-commit-config.yaml carries a managed block pinned to rev: v0.18.0 on the github.com remote, predating code-comments / yaml-strict / leak-guard / the check-skills rename. YAML comment discipline is consequently not enforced anywhere in this repo. Rewrite the block to the canonical forgejo remote at the current release rev with the current hook id set (reference: coilyco-bridge/deploy, or regenerate via agentic-os scripts/apply-agentic-os-hooks.py from the container substrate), then pre-commit run --all-files and fix what the new hooks flag. Add [tool.agentic-os.*] pyproject excludes only where genuinely needed.

2. Eco icon on the MCP server

Kai wants the eco MCP connector tile in claude.ai (served at eco-app.coilysiren.me/mcp) to show the Eco game icon instead of the generic placeholder. The MCP spec added an icons field on server implementation metadata - verify the current spec revision and what the repo's pinned MCP SDK supports (bump if needed), then wire the Eco icon (official game asset, size-appropriate, committed or data-URI) into the server initialize metadata. Done-condition: initialize response carries the icon (assert in a test); the visual claude.ai check is a human follow-up - note it in your closing comment rather than blocking on it.

Provenance: kai-desktop-tower session 2026-07-04, fleet hook-drift survey.

Sibling of coilyco-gaming/steam-ops#4 - same two-part shape, this repo. ## 1. Refresh the managed agentic-os hook block `.pre-commit-config.yaml` carries a managed block pinned to `rev: v0.18.0` on the **github.com** remote, predating `code-comments` / `yaml-strict` / `leak-guard` / the `check-skills` rename. YAML comment discipline is consequently not enforced anywhere in this repo. Rewrite the block to the canonical forgejo remote at the current release rev with the current hook id set (reference: coilyco-bridge/deploy, or regenerate via agentic-os `scripts/apply-agentic-os-hooks.py` from the container substrate), then `pre-commit run --all-files` and fix what the new hooks flag. Add `[tool.agentic-os.*]` pyproject excludes only where genuinely needed. ## 2. Eco icon on the MCP server Kai wants the eco MCP connector tile in claude.ai (served at eco-app.coilysiren.me/mcp) to show the Eco game icon instead of the generic placeholder. The MCP spec added an `icons` field on server implementation metadata - verify the current spec revision and what the repo's pinned MCP SDK supports (bump if needed), then wire the Eco icon (official game asset, size-appropriate, committed or data-URI) into the server initialize metadata. Done-condition: initialize response carries the icon (assert in a test); the visual claude.ai check is a human follow-up - note it in your closing comment rather than blocking on it. Provenance: kai-desktop-tower session 2026-07-04, fleet hook-drift survey.
Author
Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-eco-app-48 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-04T09:41:32Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

— Claude (she/her), via ward agent

<!-- ward-agent-reservation --> 🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-eco-app-48` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-04T09:41:32Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Owner

WARD-OUTCOME: done - refreshed the fossilized agentic-os hook block to the forgejo remote at v0.193.0 and wired the official Eco game icon into the MCP initialize response (asserted on the wire).

Honest retro: part 2 surprised me by being half-done already. The consolidation commit had icons= wired, but at a 16x16 favicon.ico - which is exactly why the tile reads as a placeholder. mcp 1.27.2 already flows the icon onto the wire for both stdio and the Streamable-HTTP transport claude.ai uses, so the real work was the asset, not the plumbing. play.eco is fully Cloudflare-walled, so I sourced the globe from the Eco wiki favicon (48x48, the largest square official asset I could reach) and cross-checked it against the Steam icon-hash API - both are the same blue/green world.

Part 1 was the sneaky one: the old block pinned github.com/coilyco-flight-deck/agentic-os, a dead remote, so those hooks had never actually run. Repointing at forgejo surfaced 27 pre-existing dead links (coily->ward renames, wrong ../ depth from the monorepo consolidation, dataset-survey pages that were never captured). Fixed all of them, no pyproject excludes needed.

Confidence: high. 262 tests green, full hook suite green, and I drove a real HTTP initialize round-trip to confirm serverInfo.icons carries the PNG data URI.

Rough edges / follow-ups:

  • The visual claude.ai tile check is still a human step (I can assert the wire, not the pixels), and it needs a rollout from coilyco-bridge/deploy before the live connector updates.
  • 48x48 is the ceiling for a reachable official square Eco asset. If a crisper high-DPI tile is wanted, someone with the game press kit could drop in a 256px version at templates/assets/eco_icon.png.
  • code-comments stays out of the eco hook set per the generator's C#/Unity skip, so YAML comment discipline is still unenforced here - the generator's call, not mine, but worth a confirm.
WARD-OUTCOME: done - refreshed the fossilized agentic-os hook block to the forgejo remote at v0.193.0 and wired the official Eco game icon into the MCP initialize response (asserted on the wire). Honest retro: part 2 surprised me by being half-done already. The consolidation commit had `icons=` wired, but at a 16x16 `favicon.ico` - which is exactly why the tile reads as a placeholder. mcp 1.27.2 already flows the icon onto the wire for both stdio and the Streamable-HTTP transport claude.ai uses, so the real work was the asset, not the plumbing. play.eco is fully Cloudflare-walled, so I sourced the globe from the Eco wiki favicon (48x48, the largest square official asset I could reach) and cross-checked it against the Steam icon-hash API - both are the same blue/green world. Part 1 was the sneaky one: the old block pinned `github.com/coilyco-flight-deck/agentic-os`, a dead remote, so those hooks had *never actually run*. Repointing at forgejo surfaced 27 pre-existing dead links (coily->ward renames, wrong `../` depth from the monorepo consolidation, dataset-survey pages that were never captured). Fixed all of them, no pyproject excludes needed. Confidence: high. 262 tests green, full hook suite green, and I drove a real HTTP initialize round-trip to confirm `serverInfo.icons` carries the PNG data URI. Rough edges / follow-ups: - The visual claude.ai tile check is still a human step (I can assert the wire, not the pixels), and it needs a rollout from coilyco-bridge/deploy before the live connector updates. - 48x48 is the ceiling for a reachable official square Eco asset. If a crisper high-DPI tile is wanted, someone with the game press kit could drop in a 256px version at `templates/assets/eco_icon.png`. - `code-comments` stays out of the eco hook set per the generator's C#/Unity skip, so YAML comment discipline is still unenforced here - the generator's call, not mine, but worth a confirm.
Sign in to join this conversation.
No description provided.