fix(roles): restore the exec role's composed-skill allowlist #1071

Merged

coilysiren merged 1 commit from aos/claude/xu59-exec-role into main

2026-08-15 22:02:18 +00:00

coilyco-ops commented

2026-08-15 21:56:18 +00:00

Member

What

Restores the role exec block in .agents/roles.kdl.

Why

agent-compose deploys eight roles today, and exec (Executive Strategist)
is one of them - agent-compose catalog roles lists it, and
.agents/harness-launch-profiles.yaml has carried it all along. Its
roles.kdl block, however, was parked in a block comment and then deleted
by 48c48414 when the code-comments hook stopped exempting roles.kdl.

A role with no block selects nothing. Every Executive Strategist bundle
composed since 2026-08-08 has therefore carried zero AOS methods, without
any validator noticing - check-composed-skills never reads roles.kdl, so
nothing ties the catalogue to the role graph.

Evidence

Unclaimed composed sources in .agents/composed/, before and after:

before - 10 unclaimed - the 2 tooling-advisor-*, the 3 tooling-ceo-*, the 2 tooling-customer-success-*, tooling-discord-community-host, and the 2 tooling-sales-*
after - 5 unclaimed - the 2 tooling-sales-* and the 3 community methods

48c48414's own commit body predicted the advisor and CEO half of that
list. Restoring the parked selectors verbatim re-claims exactly those five.
Every restored selector still resolves against the current catalogue.

pre-commit run --all-files passes.

Not in scope

The five still-unclaimed sources are two separate matters. The 2 sales
methods are deliberate per docs/role-skill-coverage-audit.md. The 3
community methods are orphaned by the nine-to-eight roster collapse, which
also left docs/FEATURES.md, docs/role-composed-principal-methods.md,
docs/role-skill-coverage-audit.md, and scripts/aos-role-question.sh
describing Community and Content Manager roles that agent-compose no
longer deploys, and left aos role question creator with no case. Filed
separately rather than folded in here, because deciding who inherits the
community methods is a roster call rather than a config repair.

Companion

coilyco-bridge/agentic-os-kai carries the same defect and the same fix on
branch aos/claude/xu59-exec-role.

🤖 Generated with Claude Code

## What Restores the `role exec` block in `.agents/roles.kdl`. ## Why agent-compose deploys eight roles today, and `exec` (Executive Strategist) is one of them - `agent-compose catalog roles` lists it, and `.agents/harness-launch-profiles.yaml` has carried it all along. Its roles.kdl block, however, was parked in a block comment and then deleted by 48c48414 when the code-comments hook stopped exempting roles.kdl. A role with no block selects nothing. Every Executive Strategist bundle composed since 2026-08-08 has therefore carried zero AOS methods, without any validator noticing - `check-composed-skills` never reads roles.kdl, so nothing ties the catalogue to the role graph. ## Evidence Unclaimed composed sources in `.agents/composed/`, before and after: * before - 10 unclaimed - the 2 `tooling-advisor-*`, the 3 `tooling-ceo-*`, the 2 `tooling-customer-success-*`, `tooling-discord-community-host`, and the 2 `tooling-sales-*` * after - 5 unclaimed - the 2 `tooling-sales-*` and the 3 community methods 48c48414's own commit body predicted the advisor and CEO half of that list. Restoring the parked selectors verbatim re-claims exactly those five. Every restored selector still resolves against the current catalogue. `pre-commit run --all-files` passes. ## Not in scope The five still-unclaimed sources are two separate matters. The 2 sales methods are deliberate per `docs/role-skill-coverage-audit.md`. The 3 community methods are orphaned by the nine-to-eight roster collapse, which also left `docs/FEATURES.md`, `docs/role-composed-principal-methods.md`, `docs/role-skill-coverage-audit.md`, and `scripts/aos-role-question.sh` describing Community and Content Manager roles that agent-compose no longer deploys, and left `aos role question creator` with no case. Filed separately rather than folded in here, because deciding who inherits the community methods is a roster call rather than a config repair. ## Companion `coilyco-bridge/agentic-os-kai` carries the same defect and the same fix on branch `aos/claude/xu59-exec-role`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

coilyco-ops added 1 commit

2026-08-15 21:56:18 +00:00

fix(roles): restore the exec role's composed-skill allowlist

ci / aos-cli-tests (pull_request) Successful in 16s

Details

ci / ward-doctor (pull_request) Successful in 14s

Details

ci / gate (pull_request) Successful in 59s

Details

b054b8894f

agent-compose has deployed `exec` (Executive Strategist) since the v2
roster, and `.agents/harness-launch-profiles.yaml` lists it, but its
roles.kdl block was parked in a block comment and then deleted by
48c48414 once the code-comments hook stopped exempting roles.kdl. A role
with no block selects nothing, so every Executive Strategist bundle has
composed zero AOS methods since 2026-08-08.

This restores the parked selectors verbatim. Every one still resolves
against the current catalogue, and restoring them also re-claims the two
tooling-advisor-* and three tooling-ceo-* sources that 48c48414 noted
were left unclaimed by any role.

The claim in docs/role-composed-principal-methods.md that Executive
Strategist holds the advisor, PM, and CEO methods is true again rather
than aspirational.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-15 21:56:18 +00:00