I3172 — The compiled context names the small set of capabilities the work needs

○READY wave 0 · p3 · implementation profile · parallel safe

Part of development-runtime — The runtime has a development surface.

Objective

Add a selector over the capability registry so a compiled context lists the capabilities relevant to the request's scope and kinds, each with its reason, within the budget.

Why

2026-10-11: avoid overloading the model with the full catalogue (2527 capabilities on this repository on 2026-10-18, from majordomus capabilities). Milestone development-runtime is named by no intent, so this issue is derived maintenance and serves no criterion (intent-bound-work#exemption-is-typed). Sources: chatgpt-majordomus:c226#16.

Current state

devcontext selects layer objects; capabilities are not candidates.

Desired state

A bounded, explained tool subset.

Scope

• apps/majordomus-cli/src/devcontext
• apps/majordomus-cli/src/capability/registry.rs
• apps/majordomus-cli/src/capability/model.rs
• apps/majordomus-cli/src/capability/handler.rs
• apps/majordomus-cli/src/capability/builtin/devcontext.rs

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• A request about a path lists the capabilities that read or write it, with reasons
• The list respects the budget

Validation

• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --lib devcontext::

Evidence required

• test_context_tool_subset

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3172.yaml. Read it back with majordomus plan show I3172.