feat(agent-compose): support harness-specific source slices #190

New issue

Closed

opened 2026-06-07 05:24:56 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-07 05:24:56 +00:00

Owner

Problem

agent-compose currently gives every configured harness the same source set. A private or harness-specific source therefore leaks path references and doctrine into harnesses that should not receive it.

Scope

Add optional source-level harness selection while preserving one shared output when all configured harnesses select the same sources.

Acceptance criteria

Sources may declare a harnesses allowlist in YAML frontmatter.
Untagged sources remain shared.
Divergent source selections generate per-harness outputs.
Obsolete generated outputs are removed safely.
Drift checking covers every active output and stale generated files.
Tests and repository validation pass.

## Problem `agent-compose` currently gives every configured harness the same source set. A private or harness-specific source therefore leaks path references and doctrine into harnesses that should not receive it. ## Scope Add optional source-level harness selection while preserving one shared output when all configured harnesses select the same sources. ## Acceptance criteria * Sources may declare a `harnesses` allowlist in YAML frontmatter. * Untagged sources remain shared. * Divergent source selections generate per-harness outputs. * Obsolete generated outputs are removed safely. * Drift checking covers every active output and stale generated files. * Tests and repository validation pass.

coilysiren referenced this issue from a commit

2026-06-07 05:25:44 +00:00

feat(agent-compose): support harness-specific source slices

coilysiren closed this issue

2026-06-07 05:25:44 +00:00