Skip to content

refactor(config): make OrgConfig.Agents optional and add Phase 4 plan (ADR-0045 Phase 3 PR 6) #2369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ggallen merged 1 commit into from
Jun 18, 2026
Merged

refactor(config): make OrgConfig.Agents optional and add Phase 4 plan (ADR-0045 Phase 3 PR 6) #2369

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/ADRs/0045-forge-portable-harness-schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -692,6 +692,10 @@ forge-specific artifact. The harness and agent definition are portable.
Phase 3 (deprecation), but full removal in Phase 4 may warrant a v2
schema. Consumers that assume `Agents` is always populated need
auditing.
*Note: Phase 3 PR 6 added `omitempty` to the `Agents` field. The
Phase 4 plan (`docs/plans/adr-0045-forge-portable-harness-phase4.md`)
recommends staying on v1 — removal is backward-compatible since
`yaml.Unmarshal` silently ignores unknown keys.*

- **config.yaml agents: block removal timeline.** The `agents:` block is
removed entirely in Phase 4. Consumers that read it directly need
Expand Down
Loading
Loading